Five metrics that actually predict readiness — and three that don't

Almost every major project builds a readiness tracker. Almost every readiness tracker ends up measuring the same thing: percentage of activities completed. That number goes up steadily for months, hits 100%, and then the operation still isn't ready to run at nameplate capacity. The tracker wasn't wrong — it was measuring the wrong thing.

The three metrics that feel useful but aren't

Activity completion percentage. This tells you whether tasks were closed, not whether the underlying capability exists. A training program can be "100% complete" because every session was delivered, while competency assessments show half the crew isn't ready to operate independently.

Document approval status. A signed-off procedure is not the same as a procedure the team can execute under pressure. Documentation completion is a precondition for readiness, not evidence of it.

Headcount against organization chart. Filling a seat is not the same as that person being competent, integrated into the team's operating rhythm, and clear on their role during a startup event.

The five that actually predict readiness

1. Competency verification, not training attendance. Track the percentage of critical roles where competency has been independently verified — not just where training was delivered.

2. Cross-functional dependency closure. Readiness rarely fails inside a single department; it fails at the handoffs between them. Track the status of the interfaces — maintenance-to-operations, supply chain-to-processing — not just each department's internal checklist.

3. Simulated response performance. Tabletop exercises and live drills reveal gaps no document review will catch. Track drill outcomes and time-to-resolution, not just whether the drill happened.

4. System and data integrity at go-live conditions. Reporting systems, control systems, and safety systems need to be tested under realistic load and data volume — not just functionally verified in isolation.

5. Decision-making cadence under pressure. Readiness includes whether the leadership team's meeting rhythm — daily stand-ups, escalation paths, priority reviews — actually functions once real operational problems start arriving, not just during planned reviews.

Why this distinction matters

A readiness program built around activity completion gives leadership false confidence: a green dashboard right up until the operation misses its ramp-up curve. A readiness program built around these five measures gives leadership an honest, if occasionally uncomfortable, picture — and enough lead time to close real gaps before they become production losses.

The goal isn't to make readiness tracking more complicated. It's to make sure the numbers on the dashboard actually mean what everyone assumes they mean.