The Pre-Launch Readiness Checklist

Most pre-launch checklists cover the project: budget signed off, timeline agreed, vendor contracts in place, training scheduled. Those matter, and they’re not what this checklist is about. This one covers the question those lists don’t ask: is the organization itself actually ready to absorb what’s coming, regardless of how well the project plan is built.

Run through this before you lock a launch date — not after. Every item here is cheap to check now and expensive to discover after go-live.

Clarity — can people explain it, not just recite it

• Pick five people at random, not the ones who’ll give you the polished answer. Ask them to explain, in their own words, why this change is happening. If you get five different versions, that’s the finding — not a communication failure to fix later, a readiness gap to fix now.
• Check whether the “why” has been explained in terms of what changes for a specific person’s actual day, not just organizational-level language. “Improves efficiency” isn’t an answer anyone can act on.
• Confirm there’s been more than one round of communication. A single town hall or email rarely survives contact with a normal workweek.

Conviction — understanding isn’t the same as belief

• Ask a middle manager, privately, whether they’d have made this same call. Not whether they support it publicly — whether they actually agree.
• Check for a credibility debt: how many of the last several initiatives were announced with similar urgency and then stalled, descoped, or quietly dropped. If the answer is more than one or two, expect guarded reactions regardless of how good this plan is.
• Notice if pushback is vague and low-energy (“here we go again”) rather than specific to this initiative’s actual content — that’s usually a different problem than it looks like, and it needs a different fix.

Capability — verified, not assumed

• Distinguish between “training is scheduled” and “the skill gap has actually been measured.” A training plan is not evidence people have the skill yet.
• Check whether the training timeline finishes before the people who need it are expected to use it — this sounds obvious and is missed constantly.
• Ask who’s identified as the point person when something goes wrong in week one. If nobody has an answer, that’s a capability gap in itself.

Capacity — what’s coming off the plate, not just what’s going on it

• List everything else the affected teams are currently responsible for. If the honest answer is “already at capacity,” a transformation added on top doesn’t get resourced — it gets a subtraction from and probably resented.
• Check whether anything has actually been deprioritized to make room, or whether this is simply one more initiative layered onto an unchanged workload.
• Ask whether the timeline accounts for a normal amount of disruption — a launch date built on an assumption of zero friction rarely survives contact with reality.

Cohesion — ask leaders separately, not in the same room

• Interview two or three senior leaders independently and compare their descriptions of the change. A shared room produces a polite, converged answer that doesn’t reflect what each person actually believes on their own.
• Check for a single, named, accountable owner. “Cross-functional ownership” often means no one is actually accountable when something needs a decision.
• Look for quiet disagreement about scope or timeline between departments that haven’t had to reconcile their assumptions yet — this tends to surface in week three of execution, not in planning, unless someone goes looking for it first.

What to do with what you find

This checklist won’t give you a score — it’s a fast, honest gut-check, not a diagnostic. If more than a couple of these items come back genuinely uncertain, that’s the signal worth acting on: not necessarily delaying the launch, but getting a real answer before you commit a date publicly. The gap between “we think we’re ready” and “we’ve actually checked” is exactly where most of the failure statistics in the published research come from.