3 min read

Readiness Is Not a Checklist: Find the Launch Gap Before Launch Day

A launch plan can say every dependency is covered while the systems are still unready. Here is how a capability-based readiness check surfaced a billing gap six weeks before a multi-team launch.

Launch ReadinessProduct OperationsDependency ManagementProduct Leadership

Readiness Is Not a Checklist: Find the Launch Gap Before Launch Day

A launch checklist can be complete while the launch is not ready.

The checklist often answers, “Did we document the requirement?” Launch readiness needs a harder question: “Can every system do what the launch requires today?”

I learned the difference while coordinating a network-product launch that depended on fourteen downstream systems. Each team had a list of requirements. What we did not have was a shared view of whether those systems could actually meet them.

Requirements describe a destination

A requirement might say that billing must distinguish a new product variant. That is useful, but it does not tell us whether the billing system can represent that variant, whether the rate engine recognizes it, or whether the change has been tested end to end.

If a plan only tracks requirement ownership, teams can report green because someone has accepted the task. The launch still inherits the gap between the intended state and the system’s current capability.

Map dependencies, then assess capability

I brought the dependencies into one map and made it the shared source of truth. It showed which systems and teams had to be ready, where the hand-offs were, and which unresolved items could block launch. We classified blockers by priority and made ownership explicit across the teams.

Then we added a readiness assessment alongside the requirements. For each dependency, we asked what the system could do now, what evidence supported that answer, and what remained before it could support the launch.

That assessment surfaced a critical issue six weeks before launch: billing could not distinguish the new product variant in its rate engine. The requirement existed. The capability did not.

We escalated with a worked fix rather than a vague warning. That gave the responsible team a concrete problem to resolve while there was still time to test the change before the first bills went out.

Make the map useful under pressure

A dependency map is only valuable if it helps teams make decisions. A practical version should include:

  • The capability each dependency must provide—not just a task title.
  • The accountable owner and teams required to deliver or validate it.
  • Evidence of readiness, such as a test, a demonstrated flow, or an agreed operational procedure.
  • Blockers, their impact, and the decision or escalation needed to clear them.
  • A named decision-maker for scope changes and go/no-go calls.

Prioritisation helps separate launch-critical blockers from work that can safely follow. The point is not to label every open task red. It is to make the consequences of unresolved work visible early enough to act.

Readiness is a product and operations question

A system can pass its technical test and still be unready for the people who operate it. Ask whether downstream teams can identify failures, route exceptions, support customers, and recover if a dependency does not behave as expected.

For migrations, readiness also means defining rollback criteria before the migration begins. For a multi-team launch, it means checking that the full customer journey works across the boundaries between systems—not just that each team has completed its own work.

The launch held its date, and the billing gap was closed before first bills went out. More importantly, the method changed the conversation from “Are we on track?” to “What can the system do today, and what evidence do we have?”

A question worth asking in your next launch review

Pick the most important dependency on your plan. Ask its owner to demonstrate the required capability—not to read the requirement back to you.

If nobody can show that the system can do it, you have found a readiness gap. Finding it weeks early is project work. Finding it on launch day is incident work.