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.
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.
Questions
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.
How is Deployment Readiness different from TRL and MRL?
Technology Readiness Levels assess how proven a technology is; Manufacturing Readiness Levels assess how ready a process is to be manufactured. Both assess technology and process in isolation, often on instrumented good days. Deployment Readiness measures the capability in its real operating context — the people, shift patterns, variation, cost ceiling and maintenance reality.
Why isn't a high Manufacturing Readiness Level enough?
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, under ideal conditions, without the operational variation that production introduces.
Why does Deployment Readiness matter?
Because most industrial programmes fail not at invention or qualification but at the leap from qualified to production — running at rate, at cost, on a different shift, with the actual workforce, against actual variation. Naming the level honestly is the only way to plan that leap; without the measure, programmes claim 'ready' at the demo state and discover otherwise after the cheque has cleared.
How do you measure Deployment Readiness?
By running the capability against the conditions production will actually apply — full operational variation, the maintenance reality, the workforce skill distribution, the cost ceiling, the supply lot variation. The measure is qualitative-with-evidence, not a number: what runs today, what doesn't, what's needed, with the gap stated honestly. The discipline is the honesty, not the rubric.
Who is accountable for Deployment Readiness?
The Modern Industrialist who owns the capability — not the inventor, not the line manager, not the procurement team. The role accountable to repeatable real-world outcome is also the role accountable for reporting honestly on how close that outcome currently sits. Without a named owner, readiness gets reported optimistically by default.