n o ren
Building & Strategy

Launch Early, Scale Late

Kodak built the first digital camera in 1975, then spent thirty‑seven years learning what not shipping it cost.

Steven Sasson finished a working digital camera in a Kodak lab in 1975. It weighed about eight pounds, wrote a hundredth‑of‑a‑megapixel black‑and‑white image onto cassette tape, and took roughly twenty‑three seconds to do it. Sasson has said management's reaction was, in effect, that the thing was cute and that he should not tell anyone about it. Kodak did eventually sell digital cameras, and by the mid‑2000s it was among the largest sellers of them in the United States. It filed for bankruptcy protection in 2012 anyway.

The failure was not that Kodak never shipped. It was that Kodak shipped after the open questions had already been settled — after the file formats, the retail channel, the sharing habits, and the customer's sense of what a photograph costs had all been decided by companies that spent those years in the market while Kodak protected film. Shipping early is valuable for a reason that has little to do with being first: it starts the clock on information you cannot obtain any other way. A prototype answers questions about the product. A shipment answers questions about the market, and those are the expensive ones.

The trap on the other side is treating a launch as a verdict rather than an instrument. A team that ships early and then spends a year defending what it shipped has paid the full cost of exposure without collecting the return, and the record is full of pioneers who established a category and then watched a fast follower read their results and build the version that won. What separates the two cases is whether the release was designed to produce a specific answer. Cut the next version until a disappointing result costs a week rather than a year, and write down the question it is supposed to settle before it goes out. The advantage was never in being early; it was in being early enough to still change your mind.

Kodak's failure was late learning rather than late shipping — it entered the market after the market's questions had answers.
A prototype tests the product; only a shipment tests the market, and market answers are the ones that reset a roadmap.
Early release pays only if the team is still willing to change its mind after reading the result.

The cost of a delayed launch is not the revenue you postponed — it is the market information a competitor collected meanwhile and now prices into every decision they make.

Treating a launch as a verdict rather than a question turns the cost of shipping early into a sunk expense the team then has to defend.

1
Write the single question your next release is supposed to answer in one sentence, then write the number that would make you kill the feature; if you cannot write the number, you are shipping a hope rather than an experiment.
2
Take the feature currently furthest from launch, cut it until it can go to five real customers this week, and count how many of the five do the thing you built it for within three days.

The research on first‑mover advantage is far less flattering to pioneers than the phrase suggests. Peter Golder and Gerard Tellis's study of category pioneers found high failure rates among the firms that created a market and stronger long‑run positions among the early followers who entered once the technical and customer uncertainties had been resolved. The reading that survives that evidence is not that speed wins but that learning wins, and that shipping is the cheapest instrument for learning most companies have. A pioneer who declines to use the instrument takes the costs of being early without the benefits.

The argument has a real boundary: early release is cheap only where the cost of being wrong in public is low. In regulated products, safety‑critical systems, or businesses where one enterprise buyer's first impression is the entire sales cycle, the information a rough launch buys can cost more than it returns. The useful test is reversibility — whether a bad first release can be corrected before it becomes the market's settled opinion of you. Where it cannot, the learning has to be bought another way, through paid pilots or design partners who agree in advance to see something unfinished.