Running before walking works best with a rebuild budget

The speaker is a fictional one. Robert Downey Jr. says the line as Tony Stark in the 2008 film Iron Man, halfway through testing his new flight suit in the workshop. His computer assistant suggests running more checks first. Stark overrides it, flies out over the coast, climbs higher than the suit was designed for, and the suit ices over and falls out of the sky. He recovers just in time, and the flight ends with a crash through the roof of his own house onto a sports car.

As startup advice, the line has something to it. Many products are learned only by launching them. A team that insists on mastering every step in order can spend a year on the walking and never discover what running would have taught. Founders who ship before they feel ready often learn in a week what months of preparation could not show, because users behave differently from plans.

The scene also shows what the approach costs. Stark learns about the icing problem the dangerous way, at altitude, and fixes it for the next suit. He can afford that because he has a mansion to crash into and a fortune to rebuild with. Real founders usually do not. Skipping steps is reasonable when a fall is survivable: a web product that can be patched overnight, an experiment with a small group of users. It is reckless when a failure hurts customers, loses their data or spends money the company cannot replace.

Software is the field where the line fits best, because a crash there is usually cheap. A web company can release a half-finished feature to a small group, watch it fail and roll it back the same afternoon. Teams that treat this as their normal way of working learn at a pace careful competitors cannot match, as long as the failures stay away from anything that cannot be rolled back.

So the useful version is to run early where the ground is soft. Pick the places where a crash teaches a lot and costs little, and walk carefully everywhere else.