# The change readiness assessment

By Tommy Magee

Type: Framework
Canonical: https://tommymagee.com/resources/change-readiness-assessment

Five checks to run before you plan a rollout, the case, the sponsor, the capacity, the history, and the impact. Don’t launch on red.

**Use this when:** A change is approved and someone wants to set a launch date.

## Why it exists

Most change plans assume the organization is ready and go straight to the launch. But a change that lands during three other rollouts, without a real sponsor, in a team still bruised from the last failed system, will struggle however good the plan is. A readiness check takes a week and tells you where the plan has to work hardest, or whether to wait.

## The framework

1. **The case: Is the reason for the change real, and do people outside the project see it?** If only the project team can explain why, awareness will be the first thing to fail. Test the case on a few people who will be affected and listen to how they repeat it back.
2. **The sponsor: Is there an executive who will visibly drive it?** Not approve it, drive it. Someone senior enough to move budgets and priorities, who will talk about it repeatedly and hold their own leaders to it. No sponsor is a red.
3. **Capacity: How much change is the organization already absorbing?** Count the other rollouts, reorganizations, and system changes landing on the same people in the same window. Change saturation is real, and it shows up as quiet non-adoption.
4. **History: How did the last change go?** People remember the system that was launched with fanfare and then abandoned. If the last change failed, you will need more proof and more patience this time, and you should say so out loud.
5. **Impact: Who changes how much?** Map each affected group by how much their daily work changes. A small change for most people and a large change for a few needs a very different plan from a moderate change for everyone.

## How to use it

1. Run the assessment before you set a launch date, with a mix of leaders and the people who do the work.
2. Rate each of the five checks green, amber, or red, and write one sentence on why.
3. Treat any red as a decision point. Fix it, or move the date.
4. Use the ambers to decide where the plan has to work hardest.
5. Rerun the assessment just before launch. Readiness changes while you plan.

## What a red usually means

- No sponsor. Find one before anything else, or the change will be optional in practice.
- No shared case. Spend the next month on awareness, not training.
- Saturation. Sequence the change behind something else, or remove something to make room.
- A bad history. Start smaller, with a group likely to succeed, and let them be the proof.

## What it looks like

Picture a finance team about to move to a new expense system. The assessment comes back green on the case and the sponsor, red on capacity because the same team is closing the year and moving offices, and amber on history because the last tool was dropped after a year. The launch moves to the second quarter, and the plan starts with one pilot team chosen because they are likely to succeed.

## Where it breaks down

The assessment is a structured conversation, not a measurement. Its value depends on who is in the room and how honest they can be. It also can’t tell you whether the change is the right one, only whether the organization is ready to take it on.

## Try it with AI

```
Help me run a change readiness assessment before we set a launch date. Check five things.

1. The case. Is the reason real, and do people outside the project see it?
2. The sponsor. Is there an executive who will visibly drive it?
3. Capacity. How much other change is landing on the same people?
4. History. How did the last change go?
5. Impact. Who changes how much?

Ask me one question at a time. Then rate each check green, amber, or red with one sentence on why, tell me what any red means for the launch date, and where the plan needs to work hardest.
```

Template: /templates/change-readiness-assessment.md

Topics: Change management, Change readiness, Rollouts
