Change Enablement
Why Change Doesn’t Stick
Executive Summary
When change stalls, the default response is almost always to communicate more. More town halls, more leadership messages, more explanation of the why. And when that doesn’t work, more of the same. The assumption behind it is that people are not adopting the change because they do not understand it, do not believe in it, or have not been sufficiently inspired. That assumption is wrong often enough to deserve serious challenge. In most cases the people being asked to change understand exactly what is being asked, and may even agree with it. What they lack is not understanding or motivation. It is the conditions to act.
The conditions that enable sustained change are structural. They live in how work is designed, what people are measured on, how decisions get made, what the approval processes reward, and whether the leaders driving the change actually behave the way they are asking others to behave. When these conditions are aligned with the change, adoption follows with modest communication effort. When they are not, no amount of communication produces the behaviour change the organisation expects.
People do not resist change because they are afraid of it. They resist because the system makes the old way easier than the new way. Fix the system, and resistance largely disappears. This paper sets out mBolden’s framework for change enablement—the discipline of identifying and fixing the structural and behavioural conditions that cause change to stall, rather than layering communications on top of a system that was never designed to support the change being asked of it.
The Communications Trap
The change management industry has built a sophisticated set of tools for communicating change. Stakeholder mapping. Readiness assessments. Change agent networks. Communications plans. Resistance management. These tools are genuinely useful, and on their own, insufficient for producing sustained behaviour change. The reason is simple. Communication changes what people know. It does not change what the system makes it easy for them to do, and behaviour follows ease more reliably than intention.
The pattern plays out in organisation after organisation. A transformation is announced with clarity and genuine commitment. The communications are well crafted, the town halls attended, the message delivered consistently. People understand what is being asked. They nod in the room, then go back to their desks and do what the system rewards, which is usually not the new way. This is not hypocrisy. It is rationality. If the approval processes still require the same sign- offs, the path of least resistance is to use them. If the metrics still measure the same outputs, the rational response is to optimise for them. If the leaders driving the change still decide the same way, the message to the organisation is that the change is aspirational rather than real.
The workforce is also operating under more change than it can absorb. The average employee experienced about ten planned enterprise changes in 2022, up from two in 2016, while willingness to support enterprise change fell from 74 percent to 43 percent across the same period. 1 Adding more communication to an organisation already saturated with change does not move adoption. Communication tells people what is expected. Conditions determine what is possible. Most change programmes invest heavily in the first and neglect the second almost entirely, and treating communication as if it were sufficient is one of the most consistent sources of wasted change investment.
What Conditions Actually Are
Metrics and Incentives
What gets measured shapes behaviour more reliably than almost any other variable. If the metrics governing performance reviews, bonuses, and recognition still measure the old behaviour, the old behaviour continues regardless of what is asked for in town halls. The most damaging version is incompatible cross-functional metrics, where two teams each rationally optimise for their own scorecards in ways that produce conflict. That is a measurement design problem, not a collaboration problem, and asking the teams to cooperate more willingly will not resolve it.
Approval Processes and Decision Rights
If the change requires faster decisions but the approval process still requires the same sign-offs, the change moves at the speed of the process, not the ambition. If it requires frontline judgement but every non-standard decision still travels upward, the delegation is nominal. These conditions are powerful precisely because they are invisible. No one designed them to obstruct the current change. They were built for a different context, and until they are updated they will keep producing old behaviour inside the new structure.
Tools and Information
People use the tools available to them. If the tools meant to support the new way are harder to use or less familiar than the old ones, people find ways to continue with what they know. The workaround becomes the unofficial procedure, and the new tool fails to produce the change it was designed to enable. Information has the same effect. If the new way requires visibility into shared data or each other’s work that people do not currently have, its absence keeps producing the same siloed decisions as before.
Role Definitions and Accountability
When roles are not updated to reflect new ways of working, two things happen. Ambiguity about ownership creates gaps—work that falls between roles, and decisions no one feels empowered to make. And people keep optimising for the role they were hired into rather than the role the change requires, because the formal definition is what they are held to. This is acute wherever a new operating model demands different collaboration across boundaries that the role definitions never captured.
Physical and Digital Environment
Environment shapes behaviour more than most leaders assume. Where people sit. How systems are configured. What information is visible by default. Which meetings are in the calendar. All of these create default behaviours people follow without choosing them. Changing the environment so the new behaviour is the default, rather than something that requires active effort, is one of the highest-leverage and lowest-effort interventions available, and among the most neglected.
Leadership Behaviour
Of all the conditions, leadership behaviour is the most consequential and the most consistently mismanaged. Leaders under performance pressure revert to the behaviours that produced their past success, regardless of what the programme asks for. This is not a failure of character. It is a rational response to a system that still measures and rewards the old behaviour while requesting the new one. If the metrics, incentives, and accountability for senior leaders have not been updated, the change is driven in communications and quietly undermined in behaviour, and the organisation takes its cues from the behaviour.
How to Read the Signs That Conditions Are the Problem
A communications problem and a conditions problem produce different patterns. Communications problems show up as confusion, misalignment, or lack of awareness. Conditions problems show up as something far more specific. People understand the change and can describe it accurately, but are not doing it. Adoption is high right after launch, then reverts within weeks. Pockets of genuine adoption exist where individual leaders changed their own team’s conditions, but it does not spread. Workarounds are widespread and have become the unofficial procedure. The most resistant people are often the most capable, because they have found the fastest path to the outcome and the new way is slower. Leaders say the right things but do not make the decisions that would show the change is real. And the change looks good in steering committee reporting but is invisible in daily operations.
The last two are the most diagnostic. When leaders say the right things and do not do them, the explanation is almost never dishonesty. It is that the system around them has not changed to support the new direction. And when change looks good in reporting but is absent in operations, the measurement system itself has become a conditions problem—tracking activity rather than adoption, and measuring what is easy to count rather than what is actually changing.
The Standard Approach and Why It Falls Short
Most change programmes share a common architecture. Stakeholder analysis. Leadership alignment sessions. Change impact assessment. Communications plan. Training design. Change agent network. Resistance management. Reinforcement communications. This architecture is not wrong. It reflects decades of learning about the communication and engagement elements change requires. The problem is not what is in it. The problem is what is missing.
The conditions approach reorients each step. Instead of developing a communications plan first, it runs a conditions audit before planning. Instead of identifying and managing resistance, it identifies and removes the conditions creating the resistance. Instead of training people on new tools, it redesigns the tools and processes so the new behaviour is easier. Instead of recruiting champions to spread messages, it updates the metrics and incentives so the new behaviour is rational. Instead of tracking adoption through surveys and attendance, it tracks behaviour change in operations. The standard approach treats change primarily as a communication challenge. The conditions approach treats it as a system design challenge in which communication plays a supporting role. A communications-led approach produces a change that people understand. A conditions-led approach produces a change that people can do. The first is necessary. Only the second is sufficient.
The Conditions Audit: Starting in the Right Place
Before designing a change programme, the most valuable investment is a structured assessment of which conditions are aligned with the change and which are working against it. This is not a lengthy research project. In most organisations the obstructing conditions are visible and known to the people doing the work, even if they have never been formally surfaced. The audit makes that tacit knowledge explicit and actionable, by answering six questions. What does the current system make easiest, and what does the old behaviour give people that the new one does not? Are the metrics and incentives aligned with the new direction? Are the approval processes and decision rights consistent with the new ways of working? Do the tools and information systems support the new way or the old one? Are role definitions updated to reflect new accountability and collaboration? And are senior leaders behaving consistently with the change, particularly under pressure?
The output is a prioritised list of conditions to change before launch, concurrent with it, or shortly after. Not all conditions need to be perfect before change proceeds, but the ones that create the strongest pull toward the old behaviour need to be identified early, because they set the ceiling on adoption regardless of how well everything else is executed. The audit also produces a more honest readiness assessment than most, which measure awareness and endorsement. It measures something more fundamental: whether the system the organisation is operating in will support the change it is about to ask for. That answer is more predictive of adoption than any engagement metric.
Sequencing: What to Fix Before You Launch
The sequence of conditions work relative to launch matters more than most programmes acknowledge. Fix before launch the conditions that will directly prevent adoption from taking root—the metrics and incentives that most strongly reward the old behaviour, the approval processes that create the highest friction, and any tool or information gaps that make the new behaviour practically impossible for a meaningful part of the population. Launching into a system that makes the new behaviour harder than the old one produces a burst of initial compliance followed by reversion, which then requires repeated re-launches, each producing less than the last while consuming organisational credibility.
Address concurrently the conditions that take longer to redesign, such as role definitions or multi-stakeholder decision rights, provided the direction of change is visible and credible. Visibility of conditions work in progress is itself an enabler. When people can see the metrics being redesigned and the decision rights being clarified, it tells them the change is real at the system level, not just the communications level, and that sustains discretionary effort while alignment is completed. Reinforce after adoption the work that responds best to real adoption patterns. Formal reinforcement of new roles. Recognition that surfaces the new behaviour. Refinement of metrics based on what early data reveals. The reinforcement phase is also when leadership behaviour matters most, because people are watching to see whether leaders will hold the change when the old way would be faster in the short term.
The Leadership Conditions Problem
Leadership behaviour is both a condition and a determinant of conditions. Leaders create the conditions for everyone around them through the decisions they make and the behaviour they model. The most common leadership conditions problem is the gap between stated direction and observed behaviour. Leaders endorse the change, communicate it, may genuinely believe in it. Then, when performance comes under pressure or a hard decision tests the change, they revert to familiar patterns. They reclaim the decision they were supposed to delegate. They accept the old metric when the new one would look worse. They allow the side conversation that quietly undermines the public commitment.
This is not dishonesty, and usually not even conscious. It is the predictable output of a system that has not updated its demands on leaders. Leadership behaviour is a conditions problem, not a character problem, and the system around leaders needs to change before their behaviour will change and hold. The practical implication is that leadership alignment, which most programmes treat as a one-time pre-launch activity, has to become an ongoing conditions management activity, with explicit conversation about the specific decisions that matter most and visible accountability for them. This is some of the hardest work in change enablement, because it holds senior leaders accountable for behaviour in ways that feel more personal than process accountability. It is also the work with the highest leverage. When senior leaders visibly hold the change under pressure, the message to the organisation is irreplaceable.
Measuring Adoption That Actually Means Something
Most change programmes measure adoption through proxies. Training completion. Survey scores on awareness and readiness. Attendance. Number of champions trained. These are easy to collect and easy to report, and they measure activity, not change. The conditions approach requires a different framework, one that tracks whether the behaviour the change was designed to produce is visible in operations. Are decisions being made at the levels the new model intended, or still travelling upward? Are the new metrics being used as the basis for real decisions, or are people defaulting to the old scorecards informally? Are workarounds decreasing or persisting, and what do they reveal about which conditions are still misaligned? Are leaders behaving differently under pressure, or reverting? Is the change visible in the work product, not just the reporting?
These answers are harder to collect than completion rates, but they are more honest indicators of whether the change is happening, and they identify the specific conditions still misaligned rather than aggregate sentiment. The distinction is not academic. A 2025 study of more than 5,800 project professionals found that only half of projects meet a modern definition of success—delivering value greater than the effort and expense they consume. 2 Measurement designed around operational behaviour rather than programme activity is itself a conditions intervention. It creates accountability for real adoption rather than reported adoption, and it generates the data needed to manage conditions dynamically as the change progresses.
The mBolden Approach to Change Enablement
Our change enablement work starts with a conditions audit before it starts with a communications plan. We invest in understanding the structural features of the current operating environment that will obstruct the change, and we design the conditions work as the primary intervention rather than the supporting one. This does not mean we dismiss communications or the human dimensions of change. It means we treat them as necessary but insufficient. The communications strategy is designed to support a conditions strategy, not to substitute for one. In practice the work focuses on four areas:
Conditions Diagnosis
Identifying the specific structural features—metrics, incentives, approval processes, tools, role definitions, and leadership behaviour—that are aligned with or working against the change, and prioritising which to address before launch, concurrently, or in reinforcement.
Conditions Redesign
Working with the leadership team and function owners to update the most obstructive conditions. This is operating model work as much as change work, because it requires the authority to change metrics, decision rights, and processes, not just communicate about them.
Leadership Conditions Accountability
Establishing the governance and accountability mechanisms that hold senior leaders to the behaviour the change requires, and that make leadership behaviour visible to the people who are deciding whether the change is real.
Operational Adoption Measurement
Designing measurement that tracks whether behaviour is actually changing in operations, not whether activity milestones are met, and using that data to manage conditions dynamically as the programme progresses.
Conclusion
Change that does not stick is almost always change that was well communicated but poorly conditioned. The people understood what was being asked. The leaders endorsed it publicly. The programme hit its activity milestones. And six months later the old behaviours had reasserted themselves—not because the people failed the change, but because the system made the old way easier and more rational than the new way. This pattern is not inevitable. It is predictable, and it is preventable. The conditions that enable sustained change can be identified before a programme launches, redesigned and sequenced, and managed as adoption progresses.
The investment required is modest relative to the cost of re-launching a change that failed because the conditions were not aligned. The more significant requirement is the willingness to ask a harder question before the launch. Not just what do we need people to know and do, but what does the system need to make possible for them to actually do it? That question changes the design of the programme, what gets fixed before launch, and what leadership is held accountable for. And it produces change that holds—not because people were sufficiently inspired, but because the conditions stopped making the old way the easiest choice.
Frequently Asked Questions
Why Do Change Initiatives Fail Even When They Are Well Communicated?
Because communication changes what people know, not what the system makes it easy for them to do, and behaviour follows ease more reliably than intention. When the metrics, approval processes, tools, and leadership behaviours still reward the old way, people understand the change and continue doing what the system makes rational. The failure is in the conditions, not the messaging.
What Is the Difference Between a Communications Problem and a Conditions Problem?
What Conditions Determine Whether Change Sticks?
Why Does Change Adoption Revert After Launch?
How Should You Measure Whether Change Is Actually Happening?
About the Author
Suzanne Knight, MBA, MA is the founder and CEO of mBolden, a global management consulting firm, and the creator of the 4 Layers Model ™ . She has advised more than 80 organisations across 14 countries on transformation, organisation design, and execution, spanning Fortune 500 companies, financial institutions, health systems, and federal and provincial governments.
A former Fortune 100 transformation executive, she now keynotes internationally on digital transformation, leadership, and leading through change, including the load leaders carry and what it takes to sustain it. She is a long-standing instructor at the Schulich School of Business Executive Education.
Her work centres on the thesis that transformation succeeds or fails through execution, and that the quality of the strategy cannot overcome ineffective delivery.
