What is the Valley of Death in manufacturing?
In an industrial context, the Valley of Death is the gap between a technology that works in principle and a capability that produces it reliably at scale — where most innovation programmes fail not for lack of funding or invention, but because the capability to make the thing was never built. It is a capability gap, not primarily a funding gap.
Two different valleys — name the right one
The phrase carries two meanings that share almost nothing but a name. The first is financial: the cash gap a start-up faces between seed money running out and revenue or later-stage funding arriving. That one is solved with money. The second is industrial: the gap between a prototype that works on a good day and a production system that makes the thing reliably, to standard, at a cost the business can survive. That one is not solved with money alone — and confusing the two is how programmes get funded straight into failure.
This entry is about the second valley. It is the one Kaipability is built to cross.
Why programmes fall in
- The prototype is mistaken for proof. A demonstrator that works under controlled conditions is read as evidence the hard part is done. It usually means the hard part is about to start.
- Capability is assumed to follow invention. The implicit theory is that once the technology exists and the money is there, the ability to make it appears on its own. It does not. Capability is built deliberately or not at all.
- Readiness is reported optimistically. No one is rewarded for saying the line is at low readiness, so the number drifts upward on slides while the shop floor tells a different story.
- The work is handed across a boundary. R&D passes it to operations, or a programme passes it to a supplier, and no single person remains accountable for whether the thing actually gets made.
- The horizon ends at the demonstrator. The plan, the funding and the attention all run out at the prototype, exactly where the capability work begins.
Where it sits in the lifecycle
| Stage | What exists | What is still missing |
|---|---|---|
| Invention | A technology that works in principle | Any evidence it can be made repeatably |
| The valley | A prototype and, often, funding | Qualified, repeatable production capability |
| Capability | A system that makes it to standard, at cost | Nothing structural — it is across |
The valley is not a stage you pass through by waiting. It is crossed only by building the capability the prototype did not require and production cannot do without.
Most post-mortems blame the market, the timing, or the funding round that did not close. Look closer and the same fact recurs: the thing was invented, the thing was funded, and the thing was never made reliably enough to matter. That is a capability failure wearing a financial disguise. If you name the valley correctly — a capability gap, not a money gap — you fund the right work: honest readiness, accountable ownership, and the deliberate construction of the ability to produce. Naming it wrong funds activity and calls the result bad luck.
Crossing the valley is the whole point of treating capability as the asset, and the reason Deployment Readiness has to be reported honestly. The Red Book is the discipline for getting across.