One works on how people move through a change; the other works on whether the change can be carried in the first place.
Why it matters when the plan changes
Most transformation budgets buy the first and assume the second. Communication, training and support are real work, but they cannot create an owner for a decision nobody holds or sequence a dependency nobody mapped. Change management is the discipline of moving an organisation from a current state to a future one; it is silent on whether that organisation is arranged to carry the future state. Where the problem is structural, adoption support treats the symptom and leaves the cause in place.
The tension is that the two look similar from outside and are ordered differently. Change management is usually engaged after a plan is set, to help it land. Execution risk management is most valuable before commitment, when a finding can still change the plan. Sull, Homkes and Sull found that only nine per cent of managers can rely on colleagues in other functions all the time, a gap adoption support cannot close. Running them in the wrong order delivers a well-supported transition to the wrong outcome.
In practice
A change programme runs a substantial change workstream: briefings, training, champions in each unit. Adoption metrics are strong. Delivery slips anyway, because the new model requires a pricing decision that two functions both believe they own. No amount of adoption support resolves an ownership question, and none of it was pointed there.
Evidence
Change management is the discipline concerned with moving an organisation from a current to a future state.
Change management, Wikipedia (2026)Cross-unit commitments are the least reliable part of execution, which adoption support does not address.
Donald Sull, Rebecca Homkes and Charles Sull, Why Strategy Execution Unravels and What to Do About It, Harvard Business Review (2015)
What it cannot tell you
The distinction identifies which kind of problem is in play, adoption or structure, but it does not diagnose the structural cause itself. Knowing that a delivery failure is not an adoption problem does not reveal whether the fix is reassigning ownership, resequencing scope or redesigning a forum. That judgement still requires separate analysis of the specific plan.
Questions
No, they are sequential. Establish whether the plan can be carried and what has to change structurally, then help people through the change that follows. Running adoption support over an unresolved structural problem produces a well-supported transition to something that does not work.
It reduces the friction of a transition, explaining what has changed, building capability, supporting managers through difficult conversations. Wikipedia's account (2026) defines change management as moving an organisation from a current to a future state. Where the structure is sound, that work is what determines how quickly a change beds in.
Create ownership, sequence a dependency, fund a priority or resolve a conflict between two measures. Each requires a decision by someone with authority. Communication can make those gaps visible and cannot close them, which is why adoption metrics can be strong while delivery slips.
The structural read should come first, because its findings may change the plan. Sull, Homkes and Sull (2015) found only nine per cent of managers can rely on colleagues in other functions all the time, exactly the kind of gap that must surface before a change programme is built on a plan that may not survive it.
Ask whether people know what to do and are not doing it, or do not know. The first is an adoption problem. The second, which is more common, is a clarity or ownership problem, and it is resolved by deciding something rather than by explaining it again.