Ask any executive team before a major transformation whether they're ready, and most will say yes. Ask thepeople actually doing the work, and you'll get a very different answer.
In most organizations, readiness gets assessed through a series of proxies. Has the budget been approved? Yes. Has a vendor been selected? Yes. Does leadership support it? Absolutely. Is there a project plan? Of course. Do we have a steering committee? We've scheduled the first meeting.
None of these things are readiness. They're activity. They signal that a decision has been made and money is moving. But they say very little about whether the organization is actually prepared to absorb the change.
"Signing a contract and being readyto transform are not the same thing. Not even close."
Real transformation readiness operates across three dimensions that most organizations underinvest in:
• Capability readiness: Do the people who will use this system, manage this process, or lead this change actually have the skills to do so? Not eventually, right now, at go-live?
• Structural readiness: Do your governance structures, decision-making processes, and organizational roles support the new way of working? Or will the old structure quietly reassert itself once the project team leaves?
• Data and information readiness: Is the data that this transformation depends on actually in good enough shape to be trusted? Has anyone checked?
Most organizations can honestly say they're ready on one of these dimensions, partially ready on another, and not ready at all on the third. That's a problem, because all three have to be functional for the transformation to land.
Many organizations do conduct readiness assessments. The problem is that they're often designed to confirm a decision that's already been made, not to genuinely evaluate preparedness. Questions are framed positively, risks are documented without consequence, and red flags get softened in the final report because nobody wants to be the person who delays a high-visibility initiative.
A genuinely useful readiness assessment is uncomfortable. It surfaces things people don't want to hear. It creates obligations to address gaps before moving forward. And it requires someone with enough organizational credibility and independence to call things as they are, not as the project sponsors hope them to be.
Start by separating the readiness conversation from the project planning conversation. Too often, readiness gets assessed by the same people who are incentivized to start the project. Bring in a different perspective, internal or external, specifically to pressure-test assumptions.
Build a readiness checklist that goes beyond logistics. Include questions about change fatigue, competing priorities, leadership bandwidth, and the health of the data you're relying on. Be specific about what 'ready' actually means for each dimension, not 'leadership is supportive' but 'the three senior leaders most critical to this change can each articulate what they're accountable for and what they'll stop doing to make room for it.'
And finally: be willing to delay. The cost of starting too early, low adoption, workarounds, rework, disillusionment, is almost always higher than the cost of taking another sixty to ninety days to get genuinely ready. That's a hard conversation to have when the budget is approved and the vendor is ready to mobilize. Have it anyway.
