The 5C Readiness Model, Explained

Ask most organizations how ready they are for a transformation and you’ll get a single number back — a readiness score, an engagement percentage, a color on a dashboard. The number feels precise. It’s usually hiding more than it reveals.

A blended score can’t tell you whether a team is unready because they don’t understand the plan, don’t believe in it, don’t have the skills for it, don’t have the time for it, or because their own leadership can’t agree on what it actually is. Those are five completely different problems. Averaging them into one figure doesn’t make the picture clearer — it makes the wrong fix equally likely as the right one.

That’s the reasoning behind scoring readiness across five separate dimensions instead of one. We call it the 5C model.

The five dimensions

Clarity

Do people understand why this change is happening — not the slide-deck version, the version they’d repeat to a colleague in their own words. Low clarity usually isn’t a knowledge problem; it’s a communication design problem, and it’s the cheapest of the five to fix once it’s actually identified.

Conviction

Do they believe it’s the right call — for the organization, and specifically for them. A team can score high on clarity and low on conviction: they understand exactly what’s changing and disagree with it anyway. That’s a very different intervention than a team that’s simply confused.

Capability

Do they have the actual skills the change requires. This is the dimension most often assumed rather than checked — a rollout plan says “training will be provided,” which is a plan for capability, not a measurement of it.

Capacity

Do they have the time and headcount to take this on, on top of what they’re already doing. High conviction and high capability don’t matter much if a team is already at 110% and the transformation is one more thing with no corresponding subtraction.

Cohesion

Do leaders and teams agree with each other about what’s actually happening. This is the dimension most likely to be quietly wrong while every other signal looks fine — see our piece on why executive sponsorship alone isn’t enough for what this looks like in practice.

Why five, not one

The value of separating these isn’t academic — it’s that each one points to a different fix. Low clarity gets solved with better communication. Low capability gets solved with training. Low capacity gets solved by removing something else from a team’s plate, or slowing the timeline. Low cohesion gets solved by talking to leaders individually rather than in a room together, since a shared room tends to produce a polite consensus that private conversations don’t.

A single blended readiness score can be identical for a team that’s confused but capable, and a team that’s clear-eyed but overloaded. The intervention for one would actively waste time on the other.

Scoring it per team, not once for the whole organization

The other reason a single organization-wide number tends to mislead: readiness is rarely uniform. One department can be genuinely ready while another, doing fundamentally different work under a different manager, is not — and a rollout sequenced without that visibility often launches everywhere at once, discovering the gap only after the fact in the location where it was actually present all along.

Scoring each of the five dimensions per team or department, rather than once for the whole company, is what turns a readiness assessment from a temperature check into something a leadership team can actually act on before launch — which department goes first, which one needs an extra two weeks, which manager needs support before their team does.