Ben Satchwell argues most capability framework rollouts fail in the first email by leading with what: structures, levels and process. People engage only once they understand why and what it changes for them. Translate organisational rationale into individual relevance, sequence communications purpose first, then mechanics, address appeal and threat honestly.
The first communication about a new capability framework almost always leads with the what. Here is the structure. Here are the five capability domains. Here are the four proficiency levels and how they are defined. Here is the timeline for completing your self-assessment. It is thorough, it is accurate, and it is why so many rollouts are met with silence.
This is the communication mistake nearly every rollout makes: leading with what, when you should lead with why
People won’t engage with the mechanics of a framework until they understand its purpose, and most communication never reaches the purpose at all. This is the communication mistake nearly every rollout makes: leading with what, when you should lead with why. It is the same error whether you are introducing a capability framework, a competency framework or a skills taxonomy. The detail of the construct is not what wins attention. The reason it exists is.
Why, how and what
Simon Sinek built a career on a version of this idea. His golden circle argues that effective communication starts with why, then how, then what, and that most organisations get the order exactly wrong by starting with what they do and never reaching why they do it. You can argue about how universal the model is. As a description of how change communication fails, it is hard to beat. We open with the what because the what is what we built and what we are proud of, and we assume the why is obvious. To us, it is. To the person reading the email, it is not.
Here is why starting with what fails in practice. A proficiency-level table answers a question nobody has asked yet. Before someone cares how they will be assessed against a capability, they need to know why the organisation is assessing capability at all, and, crucially, what it means for them. Lead with structure and you are asking people to learn a system before you have given them a reason to. Most won’t. They will skim it, file it, and wait to see if it matters.
Even your ‘why’ is probably wrong
There is a deeper failure hiding in most “why” communication too. Even rollouts that do explain the why tend to explain the organisational why: this supports our strategy, this aligns development with business goals, this gives us a common language for capability. All true, but all completely inert to the individual. Nobody updates their behaviour because it serves the org chart. The why has to be translated into individual relevance, and that translation is the part teams skip.
Individual relevance answers the question every person silently asks when a new framework lands: what does this do for me, or to me? Does it make my development conversations less vague? Will it help me make the case for a move I want? Does it change how I will be judged for promotion? Will it expose gaps I would rather keep quiet? Some of those are appealing and some are threatening, and a good communication addresses both honestly rather than pretending only the appealing ones exist. People can smell a message that only sells.
The translation isn’t hard, it is just usually missing. Take your organisational rationale and ask, for each main audience, “so what does this mean for this person’s Tuesday?” A graduate, a mid-career specialist and a people-manager all have different answers, and a single all-staff email written in organisational language speaks to none of them. Trust matters here too. Gartner’s research on change has found that employees with high trust in their organisation have far greater capacity to absorb change than those without it, and little erodes trust faster than communication that talks at people about structure while ignoring what they actually want to know.
Sequence the message
To do this well, Sequence the communication. The first message is purpose, in plain language, translated into what it means for the individual. Only once that has landed do you introduce the structure, the levels and the process, by which point people have a reason to read them. Lead with the table and you have lost the room before you have made your case.
There is a discipline cost to this. Leading with why means resisting the urge to show how much careful work went into the framework’s design. The proficiency descriptors you laboured over are not the opening act. They are the reference manual people consult once they have decided the thing is worth their attention, and that decision is made on the why, not the what.
So before your next rollout, look at the first thing people will read. If it opens with structure, levels or process, rewrite it. Open with why this exists and what it changes for the person reading it. Get that right and the structure will get read. Get it wrong and expect silence.
Ben Satchwell is Head of Capabilities at Acorn PLMS
