Readiness is the question everyone skips because the answer is uncomfortable and the programme is already funded. It is also the cheapest question in the whole exercise: a week spent on it changes the plan, and a year spent without it changes the budget.
What readiness actually means
Readiness is not appetite, and it is not executive enthusiasm - both of those are abundant at the start of every programme and neither predicts anything. Readiness is the organisation’s capacity to absorb a specific change of a specific size in a specific window, given everything else it is already carrying.
Which means readiness is always readiness for something. A generic readiness score is a personality test. A useful one is scored against the dimensions the transformation will actually move.
The six tests
1. Sponsorship that can spend and stop. Not a named sponsor - a sponsor with the authority to reallocate budget and to cancel a workstream, who has done both before. Test it by asking what the sponsor stopped last year. If the answer is nothing, the sponsorship is ceremonial.
2. Decision rights that are written down. Who decides scope, who decides sequence, who breaks a tie between two directors. Most programmes discover in month four that this was never settled, and the discovery costs a quarter. Test it by asking three people the same question separately.
3. Change saturation. Count what the same population is already absorbing - a system change, a restructure, a regulatory deadline, a new reporting line. There is a finite amount of change a given team can take in a year and it is smaller than planners assume. Test it by listing every initiative touching the same hundred people.
4. Evidence capability. Can the organisation currently measure the thing the transformation is supposed to improve? If the baseline does not exist, no benefit can be claimed at the end and none will be. Test it by asking for last month’s number. If it takes more than a day to produce, that is a finding.
5. Capability in the dimensions that fired. Not headcount - capability at the target maturity level. A dimension that has to move from level 2 to level 4 needs people who have worked at level 4. Test it by naming who, specifically.
6. Benefit ownership. Somebody outside the programme has to carry the benefit in their own numbers, or the benefit is the programme’s opinion of itself. Test it by finding the line in somebody’s budget that moves if this works.
What a readiness score is for
Not a gate. A readiness assessment that produces a red light and stops there has wasted everyone’s time, because the programme will proceed anyway. Its real job is to change the shape of the plan: to move the start date of the workstream that depends on the unready dimension, to add the capability before the dependency rather than after it, and to name which benefits cannot be claimed on the current evidence base.
A readiness assessment with no consequence for the sequence was decoration. That is the test to apply to your own.
What to do when the answer is not yet
Almost always, the answer is not yet, in three of the dimensions - and that is an actionable answer, not a refusal. Sequence the ready dimensions first and buy the time to fix the others. Reduce the target level in one dimension from four to three and check whether the benefit survives; often it does, and half the cost does not. Split the programme so the unready part starts two quarters later with a named precondition.
The one response that never works is to note the finding in a risk register and proceed on the original date.
Where readiness sits in a transformation
After the horizontal gap analysis - you cannot assess readiness until you know which dimensions are live - and before the plan is costed, because readiness is what sets the sequence and the sequence is what sets the cost. In our one-week engagement it is one of the named deliverables, produced alongside the dimension shortlist and the maturity gaps, so the plan that comes out the other end is already sequenced against the organisation’s actual capacity rather than its stated intent.
What transformation management is explains the two gap analyses that come first. How to build a transformation roadmap covers what happens with the answer. We run the week in Ireland, the United Kingdom, the United States and Australia, where we have representation - the engagement and what it produces.