What is Deployment Readiness?
Deployment Readiness is the honest measure of how close a capability is to producing its intended outcome reliably, repeatedly, and at viable cost under realistic operating conditions, not in a lab, not on a good day, but in production with the constraints that will actually apply. It asks "can this system do the job for real, yet?" and answers it without flattery.
The same question, can this system do the job for real, yet?, in the language of whoever is asking. Choose your seat above.
Does it actually work in the real world, every day, at a price that makes sense? Or did it only work once, in a lab, on a good day, with the people who built it watching? "Ready" is meant to describe the first. It usually gets claimed for the second. Deployment Readiness is just the honest answer to one question: can this do the job for real, yet?
You call it de-risked. On a milestone slide, "de-risked" almost always means the technology works: lab-proven, demo-passed. Deployment Readiness is the other risk, the one your technical due diligence should be pricing, whether it can be built at rate, at cost, on a real line, before the scale-up cheque clears. A high TRL with low Deployment Readiness is a down-round waiting to happen.
You call it qualified. Qualification is a good day: the A-team, a fresh tool, the inventors watching. Deployment Readiness is the bad day, third shift, B-team, worn tooling, lot variation, and whether the process still holds. It is the level past the gate you already passed, where the yield curve actually lives.
You call it on track. The RAG status is green because the milestones are being hit on paper. Deployment Readiness is the one line that refuses to round up, the honest distance between "demonstrated" and "running at cost through normal variation". The number worth having before the capex clears, not after.
You call it sovereign capability. But funding the demonstrator is not funding the deployment. Deployment Readiness is the rate at which invention becomes producing capability at scale, measured on the line, not at the launch. A country can own the IP, the fab and the announcement and still have low Deployment Readiness.
Why a new term, when TRL and MRL exist
Technology Readiness Levels measure how proven a technology is. Manufacturing Readiness Levels measure how ready a process is to be manufactured. Both are useful and both share a blind spot: they assess the technology and the process in isolation, on instrumented good days, often by the team that built them. Deployment Readiness measures the thing that actually determines whether value is delivered, the capability in its real operating context: the people, the shift patterns, the variation, the cost ceiling, the maintenance reality. A process can sit at a high manufacturing-readiness level and still have low Deployment Readiness because it has only ever run with its inventors watching.
What Deployment Readiness assesses
- Repeatability under realistic conditions, not "it worked", but "it works on the third shift with the B-team and a worn tool."
- Outcome to a known standard, the output meets the qualified specification, measurably, not approximately.
- Viable cost, it produces the result at a cost the business can actually carry, not a cost that only holds at a demonstration volume.
- Operational robustness, it survives the variation that real inputs, real maintenance and real people introduce.
- Honest reporting, readiness is stated as it is, including when it is low. A Deployment Readiness assessment that always returns "ready" is worthless.
Reading it as a level, not a binary
Deployment Readiness is best held as a graded scale, mirrored to but distinct from MRL/TRL, from "demonstrated once under ideal conditions" to "running unattended at target cost and standard through normal operational variation." The discipline is not in inventing the scale; it is in refusing to round up.
The Valley of Death is, in almost every industrial case, a Deployment Readiness gap that nobody measured. The technology was ready. The process was, on paper, ready. What was not ready was the capability in context, and because no one was measuring that, the programme walked into the gap reporting green. Deployment Readiness exists to make that gap visible while it can still be closed. Used honestly, it is the single most useful number in an industrialisation programme. Used to reassure a board, it is worse than no number at all.
This sits on top of capability, Deployment Readiness is how you measure capability honestly. The Field Manual works the lens through real industrial situations.