Frame 1 · Five domains
Where does the change land?
A change rarely touches just one thing. You work through five domains systematically: people, processes, technology, structure and policy. So that nothing is overlooked.
Where does the change land hardest? The matrix maps per domain what shifts, how heavily it weighs, and when it arrives. Not from assumptions, but tested with the people who feel it.
A change rarely touches just one thing. It touches roles, processes, systems, structures and sometimes policy. The change impact matrix works through those domains systematically and records per domain: what exactly is changing, how heavily does that weigh, and who carries it? So that you are not surprised afterwards by what you could have seen in advance.
You work through a fixed set of domains so that nothing is overlooked. People: do the roles, the skills, the way of thinking change? Processes: does how the work runs change? Technology: which systems and tools are replaced or added? Structure: do reporting lines or responsibilities shift? Policy: do rules, procedures or compliance requirements change?
Per domain you record the shift: how is it now, how will it be later? That delta is the starting point. Only after that do you judge the severity.
Here is a trap. Most assessments give one severity score: high, middle, low. But severity is not one thing. A large shift that is easy to absorb asks for less intervention than a small shift that is fiercely contested.
You gain precision by asking two questions: how large is the shift (the size), and how hard is it to absorb (the resistance)? A score on both gives a far sharper picture of where your energy should go.
The most valuable insights do not come from the direct impact analysis. They come from the second order effects: what breaks elsewhere when this changes? A new system for the finance department also touches the planning department that pulls data out of it every day. A change in the reporting line changes who decides on priorities on the floor.
You only discover those effects by talking to people. That is where the workarounds surface: the ways people get the work done today, which the change disrupts. Record those as new rows in the matrix, instead of letting them appear later as surprises.
The matrix is not only a snapshot. Impacts land at different moments in the change. Some early, at the announcement. Others only at go-live. Others again creep in during the months after.
The strategic question is: where do several impacts land at the same moment with the same group? That is a peak load point. At that moment the vessel is full, and further change does not get in any more. You only spot that when you lay the impacts next to each other on a timeline. Interventions, communication and support have to land just before such a peak, not after it.
We do not build the impact matrix from behind a desk. We start from visits to the ground and conversations with the teams who do the work. We test our assessment in a workshop with operational leads. And we tie every severity score to an owner who makes sure the right intervention lands at the right moment. The matrix becomes the standing item on every steering group meeting: not as a reporting tool, but as a shared picture of where it is tight. Read more about how we work →
At the start of a change, as soon as you are past the vision and the stakeholders and want to understand where the change lands hardest. It also works halfway through a change that is stalling, because it exposes which impacts have been overlooked and where the peak load sits.
In a conversation we help you map the impact systematically, so you see in advance what you would rather not discover afterwards.