In my eleventh year of working in organizational development, I led a significant portion of a change management effort at a company moving from a centralized function model to a highly distributed operating structure. The change was necessary — the company had grown past the point where centralized functions could adequately serve business units with very different needs. The case for change was clear, the leadership was committed, the communication plan was thorough, and we had external consultants supporting the technical aspects of the transition. By any measure of formal change management practice, we were doing it right.
It was still largely a failure. Not a complete failure — the structural change happened, and the organization eventually adapted. But the timeline was roughly twice what we had projected, the talent cost was significant (several excellent people left during the transition who we hadn't expected to lose), and the cultural damage — the erosion of trust between some functional leaders and the business units they were now serving — persisted for years after the structural change was complete. We had done the change management correctly and the change management had been inadequate.
What we had missed, I came to understand over the following years, wasn't a tactical gap in the execution. We had missed something more fundamental about what change actually requires from the people experiencing it. The frameworks we were using — and I'd been trained in the most widely used ones — shared a set of assumptions that looked reasonable on paper and failed in practice in consistent, predictable ways. Understanding what those frameworks miss is, I think, among the most practically valuable things an organizational leader can understand about change.
The evidence on organizational change success rates is grim and has been consistently grim for decades. Depending on the study and the definition of success, somewhere between fifty and seventy percent of large-scale change efforts fall significantly short of their objectives. The reasons cited most often in the literature — "resistance to change" and "communication failures" — are symptoms. They describe what you observe when a change effort is struggling. They don't adequately explain why the struggling is so consistent and so resistant to the communication and change management investments that organizations typically make in response to it.
The resistance misdiagnosis — why better messaging doesn't help
The most consequential thing that standard change management frameworks get wrong is their treatment of resistance. In the dominant frameworks, resistance is primarily an information deficit: people resist change because they don't have enough information about why it's necessary, what it will look like, and what it will mean for them. The prescription that follows is more communication — more town halls, more leadership visibility, more articulation of the burning platform and the vision for the future state, more emphasis on what's in it for the people who need to change.
This prescription does something. Better-quality communication about change reduces some of the anxiety that comes from uncertainty about what's happening. It creates some degree of cognitive alignment around the direction. For change that is primarily about process or technology — where people need to understand a new system but aren't losing anything fundamental — communication-focused change management can work reasonably well.
Where it systematically fails is in the much larger category of changes where the resistance isn't an information deficit — it's an accurate assessment of something the change will actually cost. The person who resists a reorganization that will put them in a less visible role isn't confused about what's happening or uninformed about the business case for the change. They understand perfectly well. What they understand, and what the communication-heavy change management approach will never address, is that the change will cost them something real: status, proximity to decision-making, the relationships that were central to how they got things done. Better messaging about why the change is strategically necessary doesn't address any of those real costs.
The communication-heavy approach also carries a specific condescension that people in change processes feel acutely, even when they can't name it. The implicit message of repeated communication campaigns is "you don't understand why this is necessary, so we need to explain it better." For people who understand perfectly well and are resisting because the change will cost them something, that message is experienced as a refusal to acknowledge what they're actually experiencing. The escalating communication doesn't reduce the resistance; it sometimes increases it, because being repeatedly told to understand something you already understand is aggravating.
The loss dimension — what change management frameworks consistently underweight
The second major gap in standard change management frameworks is what William Bridges called the "endings" dimension of transition — the losses that every genuine change involves. Change initiatives are almost universally framed in terms of the future state: what the organization will be able to do that it can't do now, how performance will improve, what the strategic position will look like. This framing makes sense from a change leadership perspective — you want to generate momentum toward the future state, not dwelling on the past.
But the people experiencing change are simultaneously experiencing loss. Loss of familiar routines that had become easy and automatic. Loss of the expertise they'd built over years in the previous way of working, which now needs to be rebuilt in a new context. Loss of the specific relationships that were central to their professional identity — the colleague who sat three desks away, the informal network that let them get things done efficiently, the team they'd built over several years. Loss of the sense of competence that comes from mastery of a well-understood role.
Both things are true simultaneously: the future state will be better in important ways, and the move toward it will involve genuine losses. Change management frameworks that address only the gains produce a systematic gap in the organizational experience of the change. People don't feel that their losses are being acknowledged. What they feel instead is that the organization is asking them to be excited about something while not acknowledging what it's costing them to be excited about it. That gap produces the specific kind of disengagement that looks like change fatigue or cynicism but is actually something more specific: the experience of not being seen.
The difficult thing about acknowledging loss in change management contexts is that it can feel like undermining the momentum toward the future state. If you spend too much time acknowledging what people are losing, you risk reinforcing attachment to the current state and making the change harder. This is a real tension, and I don't want to pretend it isn't. The resolution isn't to dwell on loss indefinitely — it's to acknowledge it genuinely and then move forward. The leaders who do this well say something like: "I understand that this change will cost you something real, and I'm not going to pretend it won't. Here's what you'll be giving up and why I believe what you'll be building is worth it." That statement — which holds conviction about the direction and genuine empathy about the cost simultaneously — is what makes people feel respected enough to move.
The identity dimension — the change management gap that almost nobody addresses
The third major gap in standard change management is the one I find most consequential and least discussed: the identity dimension. Many significant organizational changes don't just alter processes and reporting structures — they alter who people are at work, how they see themselves, and what they're good at. The senior functional expert who is being moved into a generalist business partner role isn't just changing what they do every day. They're giving up an identity that has been central to their professional self-concept — the identity of the expert, the person others come to for knowledge that few others possess.
This kind of identity disruption generates a form of resistance that better communication genuinely cannot address, because the resistance isn't about understanding the change. It's about the threatened loss of a self-concept that the change will require giving up. The person who resists in this way often can't articulate what's driving the resistance in these terms — they offer reasons about the business case or the implementation approach — but the underlying driver is the identity threat.
In my centralized-to-distributed change, this was the primary source of our problems. The functional leaders who were being transitioned into business partner roles had built their professional identities around functional expertise — around being the senior person in the room on their topic, the person whose judgment was definitive. In the new model, they were one of several perspectives the business units would consider, evaluated by their ability to understand the business rather than their depth of functional knowledge. That shift required more than a new job description. It required a fundamental reconstitution of professional identity, and the change management plan had said nothing about that.
What helps with identity-threat resistance is different from what helps with information-deficit resistance. It requires making the identity transition explicit — naming what people are being asked to become, not just what they're being asked to do. It requires acknowledging that the old identity was genuinely valuable and that giving it up is a real cost. And it often requires giving people a new identity narrative that is as compelling as the one they're giving up — not just "you'll be doing this new thing" but "here's what it means to be excellent at this new thing, and here's why the people who develop this new identity will be the most valuable people in the organization going forward."
The bandwidth assumption — what frameworks get systematically wrong about organizational capacity
The fourth gap in standard change management frameworks is the most practical and in some ways the most fixable: the failure to take organizational bandwidth seriously. Change requires bandwidth — cognitive, emotional, and practical. The cognitive work of learning new systems, new processes, new ways of collaborating. The emotional work of processing the losses I've described and reconstituting professional identity. The practical work of doing both of these things while also doing the operational work of running the organization, which doesn't stop during the change.
Most organizations that undertake significant change are already running at or near full capacity. Their people are busy. Their managers are stretched. The leadership team is managing multiple priorities simultaneously. The assumption embedded in most change management plans — that the organization has the available bandwidth to absorb the change while continuing to perform — is simply false for most organizations most of the time. And the failure to test this assumption produces change timelines that are consistently optimistic, and change experiences that are consistently overwhelming.
I've watched change initiatives stall not because the change was wrong or the change management was poor but because the organization simply didn't have the capacity to engage with it properly. The people who needed to be most engaged in building the new ways of working were the same people whose operational responsibilities were most demanding. The leader who was supposed to be championing the change at the business unit level was simultaneously managing a performance crisis in one of their teams. The change initiative that was designed for an organization with bandwidth was meeting an organization that didn't have any.
What helps with the bandwidth problem is genuine assessment before the change launches of what the change will actually require, compared with what the organization actually has available. Not the optimistic estimate — the honest one. And where the gap between required bandwidth and available bandwidth is real, either the scope of the change or the timeline for it needs to be adjusted. The alternative — launching the change anyway and hoping the bandwidth will materialize — produces the change fatigue and stalled momentum that the change management literature treats as mysteries, but that are actually predictable consequences of a mismatch between demand and capacity that nobody was willing to examine honestly.
What actually works — the approach that the standard frameworks underemphasize
The change efforts I've seen work most consistently share characteristics that the standard frameworks consistently underemphasize. They start from a genuine diagnosis of what's driving resistance — what people are actually protecting — rather than assuming that better communication will address whatever the resistance is. They acknowledge loss explicitly and with genuine empathy, not just as a communication tactic but as a real acknowledgment that the change is asking something of people that costs something real. They assess bandwidth honestly before launching and adjust the pace accordingly.
They also tend to involve genuine input into the shape of the change at a level that is real rather than performative. The "consultation" that many change processes include — where people are asked for input that has already been decided — is usually recognized for what it is. What builds the engagement that actually sustains change is consultation that genuinely shapes outcomes: where the timeline is adjusted based on what was learned, where elements of the design are modified in response to concerns raised, where people can see that their input changed something. That kind of genuine input also has a secondary benefit: it surfaces the local knowledge that the people designing the change don't have and that often contains the most important information about how to make it work.
The hardest part of the approach I'm describing is the requirement that leaders hold two things simultaneously: genuine conviction in the direction they're moving and genuine empathy for what the movement costs. Conviction without empathy produces the change management approach that names the resistance as a communication failure and escalates the messaging. Empathy without conviction produces the change process that consults endlessly, adjusts constantly, and never quite arrives at the destination. The combination — moving forward with genuine purpose while genuinely acknowledging what the movement costs — is what produces change that both gets done and gets done in a way that the organization can survive with its culture and relationships intact.
The informal network problem — why change management targets the wrong structure
One final gap worth naming: standard change management frameworks almost universally target the formal organizational structure — the reporting lines, the communication hierarchy, the official change champions designated by title. What they systematically underweight is the informal network — the relationships through which work actually gets done, where real influence lives, and where the organizational culture is actually maintained and reproduced.
Every organization has a formal structure and an informal one, and they're different. The senior vice president whose voice carries the most weight in formal meetings may not be the person whose opinion actually shapes what the organization decides to do. The middle manager who is three levels below the change steering committee may be the person whose interpretation of the change determines how two hundred people understand and respond to it. The informal network — who people actually trust, whose judgment they defer to, whose reaction to the change they're watching — is where the real change management battle is usually won or lost.
The change efforts that have worked best in my experience have invested specifically in understanding the informal network before the change launches: identifying the informal influencers, understanding their concerns about the change, engaging them genuinely rather than treating them as channels to deliver the official message, and involving them in shaping aspects of the implementation in ways that make their concerns visible and addressed. That investment is usually more valuable than the equivalent investment in polishing the official communication materials, and it's done far less often.
Why the frameworks don't improve — and what that tells you about the field
Given that the failure rates of large-scale change efforts have been well-documented for decades, and given that the change management field has had decades to respond to that evidence, it's worth asking why the frameworks haven't improved more than they have. The persistence of the communication-heavy, resistance-as-information-deficit approach, despite substantial evidence of its limitations, is itself a phenomenon worth understanding.
Part of the answer is economic. The change management industry — consultants, training programs, certification bodies — has substantial investment in the existing frameworks. The frameworks that have been most widely taught, most widely certified, and most widely embedded in organizational practice are the ones that are most familiar, and familiarity creates inertia that evidence alone doesn't always overcome.
Part of the answer is that the communication-heavy approach does produce something — it produces motion, visible activity, the appearance of managed change. Town halls, communication plans, readiness assessments — these are observable deliverables that can be checked off. The harder work of attending to identity disruption, loss acknowledgment, informal influence, and honest bandwidth assessment doesn't produce the same kind of observable deliverables. It's less measurable and therefore less defensible to the stakeholders asking what the change management effort has produced.
The practical implication for leaders who want to lead change more effectively: the frameworks you've been taught are not wrong about everything. Clear communication, visible leadership commitment, structured change management processes — all of these contribute to change success. They're just insufficient on their own, in predictable ways. The gap is in the dimensions that require harder conversations and more genuine engagement: the acknowledgment of what the change costs, the honest assessment of identity disruption, the engagement with the informal network, and the realistic treatment of organizational capacity. Those dimensions are harder, they produce less visible activity, and they're harder to delegate to a change management consultant. They also make the difference between change that lands and change that stalls.
Related: Why You Should Communicate Change Before You're Fully Ready, How to Change a Culture You Didn't Build