Most transformations don’t fail at launch. They fail quietly, somewhere between month six and month fourteen, after the town hall energy has faded and before the new way of working has genuinely taken hold. By the time leadership notices, the organization has usually drifted most of the way back to familiar ground, and nobody can point to the exact moment it happened.
The Organisational Transformation Checklist below exists to catch that drift while there’s still time to correct it, not after. It’s organized into ten structural themes, two questions each, deliberately written to be answered honestly rather than aspirationally.
Key Takeaways at a Glance
- Readiness is structural, not a feeling — it can be checked against specific conditions rather than sensed from a room’s energy.
- The checklist covers 20 questions across 10 themes: desire, direction, process, leadership commitment, change capacity, structural adaptability, capability match, measurement, narrative, and sustained momentum.
- Most transformation failures aren’t failures of ambition or planning — they’re a failure to hold stability and change in honest tension long enough.
- Question 20 — would the change survive if every current champion left tomorrow — is the single best test of whether transformation has actually stuck.
- Score five questions at a time across a few working sessions, not all twenty in one meeting, and resist softening uncomfortable answers.
Readiness Isn’t a Feeling, It’s a Set of Conditions
“We’re ready for this” is usually an emotional judgment, made in a room full of people who already want the transformation to succeed. Genuine readiness is structural, and it can be checked against specific conditions rather than sensed from the room’s energy.
The 20 Questions, Organized Across 10 Themes
1. Desire: why, beneath the market pressure
- Can your leadership team articulate a specific future the organization is moving toward, not just a threat it’s moving away from?
- Would that reasoning sound the same coming from three different senior leaders, or does it noticeably shift depending on who’s asked?
2. Direction: how specific is the destination
- Could a team three levels down the organization describe what the future state means for their own daily work, in their own words?
- Has the direction been translated into anything more concrete than aspirational language like “more agile” or “more innovative”?
3. Process: how disciplined is execution, not just planning
- Does a regular, honest review rhythm exist, with clear milestones and named owners, or does progress get discussed only when someone happens to raise it?
- When the plan and reality diverge, is that gap caught within weeks, or does it typically surface only at the next scheduled review?
4. Leadership commitment: visible, not just stated
- Have senior leaders made a visible trade-off — sacrificing time, budget, or a pet initiative — to back this transformation, or has support stayed rhetorical?
- Would employees three levels down describe leadership’s commitment as consistent, or as strong in meetings and inconsistent in daily resource decisions?
Source: Strategyu
Did You Know?
Research consistently puts organizational transformation failure at roughly 70%: one widely cited breakdown finds 50% of transformations outright fail, 16% produce mixed results, and only 34% succeed. Seventy-two percent of failed initiatives point to workforce resistance or management behavior — not strategy or technology — as the primary barrier.
5. Change capacity: bandwidth, not just willingness
- Has the organization’s actual capacity to absorb change been assessed, or is it assumed that people will “find the time” because the initiative matters?
- Are other major initiatives being deliberately sequenced around this transformation, or is it competing for the same limited attention as everything else already underway?
6. Structural adaptability: is structure itself on the table
- Have reporting lines, decision rights, or team boundaries been genuinely reconsidered where the future state requires it, or is the transformation expected to happen entirely within the existing structure?
- If the current structure quietly contradicts the stated future direction, has anyone been asked to resolve that contradiction directly?
7. Capability match: can people actually do this
- Has the gap between current workforce capability and future requirements been mapped explicitly, role by role, or only discussed in general terms?
- Is there a resourced, active plan to build, hire, or redeploy against that gap, or does the plan currently stop at having identified it?
Source: McKinsey
Did You Know?
McKinsey research finds organizations that track clear KPIs during change implementation achieve a 51% success rate, versus just 13% for those relying on intuition or anecdotal feedback — a nearly 4x difference tied to measurement discipline alone.
8. Measurement: activity versus outcome
- Are the indicators of success defined in terms of actual outcomes, not just initiatives launched or meetings held?
- Is there a genuine, demonstrated willingness to course-correct based on what those indicators show, even when the correction is uncomfortable?
9. Narrative: does the story evolve
- Has the transformation narrative been actively updated to reflect real progress and real setbacks, or does it still sound the way it did at launch?
- Would employees describe the communication as an ongoing conversation, or as something that happened mainly in the first month?
10. Sustained momentum: what happens after the energy fades
- Is the change being reinforced through how success is measured, rewarded, and reviewed, or does it currently rely on the initial enthusiasm to carry it forward?
- If you removed every person currently championing this transformation from the organization tomorrow, would the change itself survive?
Why the Standard Fix Falls Short?
The conventional playbook launches with a well-produced town hall, a compelling deck, and genuine energy, then checks in formally once a quarter and assumes steady progress in between. Momentum fades everywhere, in every organization; the difference between transformations that stick and those that quietly reverse is whether the reinforcing structure behind question 19 was built deliberately before the energy faded, not scrambled together after someone noticed it had.
| Old Playbook | Next Practice |
Launch | Town hall, compelling deck, genuine energy | Same launch, plus a living instrument revisited monthly |
Check-ins | Formally once a quarter | Monthly through the first year, not an annual audit |
Between check-ins | Progress assumed to be steady | Gaps between plan and reality caught within weeks |
Reinforcement | Relies on initial enthusiasm to carry it | Built deliberately before the energy fades (Q19) |
Underlying test | Did we launch well? | Would it survive without its current champions? (Q20) |
Using This Checklist Well
Don’t try to score all twenty at once in a single meeting. Take five at a time, spread across a few working sessions, with the people who will actually carry the transformation in the room, not only the people who designed it. Where the honest answer to a question is uncomfortable, resist the instinct to soften it in the write-up; the discomfort is the useful signal, and softening it is how transformations quietly drift without anyone noticing until much later.
Pay particular attention to question 20. It’s deliberately the hardest one on the list, and it’s the single best test of whether a transformation has actually become part of how the organization works, or whether it remains, underneath the activity, still dependent on a handful of specific people continuing to push it.
The Deeper Pattern
Transformation, at its root, asks an organization to hold two things that feel contradictory: enough stability to function today, and enough willingness to become something different tomorrow. Most transformation failures aren’t failures of ambition or of planning quality; they’re failures to hold that tension honestly, resolving it prematurely in favour of comfort, which is stability, or in favour of announcement, which mistakes launching for arriving.
The organizations that transform well tend to be the ones willing to sit inside that discomfort for longer than feels natural, checking honestly and often against conditions like the twenty above, rather than reassuring themselves with the energy of a single well-run launch.
How Ebullient Helps You Close the Gap?
Most transformation support arrives either as a launch event or as a quarterly scorecard. Neither catches the quiet mid-transformation drift this checklist is built to surface. Ebullient works with leadership teams across the full arc, from diagnosing where the twenty conditions currently stand to building the reinforcing structures that keep transformation honest long after the town hall energy fades.
Leadership reforging
Senior teams are supported in making commitment visible — real trade-offs, not just rhetorical backing — so questions 7 and 8 hold up under scrutiny from three levels down.
Cultural rewiring
We help build the norms that let uncomfortable answers to questions like these surface honestly, instead of being softened in the write-up.
Team alchemy
Structural adaptability and capability gaps get addressed by the cross-functional teams who’ll actually work inside the new structure, not decided above them.
Future mindsets
Monthly re-diagnosis is built into the engagement from day one, so the checklist stays a living instrument through the full first year, not a one-time launch document.
Where Does Your Transformation Actually Stand?
For a faster starting read before working through the full twenty, the Organisational Transformation Readiness Assessment, a shorter ten-question version of this same diagnostic, part of Ebullient’s Wisdom Gap Diagnostics series, lays out the reasoning behind every answer alongside it.
Is Your Organisation Ready for Transformation?
Frequently Asked Questions
Get answers to commonly asked questions about Ebullient.
What is the Organisational Transformation Checklist?
It’s a 20-question diagnostic, organized across 10 structural themes, that leaders use to check transformation readiness and progress against specific conditions rather than relying on how confident the room feels.
Why do transformations that launch well still fail later?
Most failures happen quietly between month six and month fourteen, after initial energy fades and before new ways of working take hold — not at launch itself, which is why ongoing monthly review matters more than a strong kickoff.
Which question on the checklist matters most?
Question 20 — whether the change would survive if every current champion left the organization tomorrow — is the clearest test of whether transformation has become embedded rather than personality-dependent.
How often should the checklist be revisited?
Monthly through the first year is the next practice, treating it as a living instrument rather than a quarterly or annual audit.
Should all 20 questions be scored in one meeting?
No — five at a time across multiple working sessions, with the people actually carrying the transformation in the room, tends to produce more honest, useful answers.
