Change Management: Connecting Purpose With Vision

Since 2010, as a leading keynote speaker on Change Management in india, I have delivered more than thirty sessions on change management to organisations across industries — technology firms navigating cloud migration, manufacturers automating their shop floors, and conglomerates working through post-merger cultural integration. If there is one truth I have absorbed from all of it, it is this: organisations don’t struggle with change because the strategy is wrong. They struggle because the people implementing that strategy were never truly brought along with it.

Change, as a subject, keeps reinventing itself. First it was automation, then cloud, then mobility, then sustainability, and now AI transformation. The technology changes every few years. The human resistance to it does not.

Early in my consulting career, I was brought in to support a post-acquisition integration between two mid-sized companies in the auto components space. On paper, the merger made perfect sense — complementary product lines, overlapping customers, a clean financial rationale. Eighteen months in, attrition on the acquired company’s side had crossed a level that alarmed the leadership team, and productivity had quietly stalled.

When I sat down with employees from the acquired company, the complaint was almost never about the merger logic itself. It was about how it had been communicated — a town hall announcement, a slide with a new org chart, and very little explanation of what it meant for the people in the room personally. One senior engineer told me, ‘I understood the business reason on day one. I still don’t understand what it means for me, eighteen months later.’ That gap — between a leadership team that understands the vision and a workforce that never connected it to their own reasons — is, in my experience, the single most common reason change initiatives stall.

This aligns closely with research McKinsey has published over many years on transformation efforts, which has consistently found that a large majority of major change initiatives fail to fully achieve their intended objectives, and that the most frequently cited reasons are related to employee resistance and inadequate management communication rather than flawed strategy.

John Kotter, whose eight-step model for leading change has shaped how generations of executives approach transformation, made a related observation in his Harvard Business Review work: he found that most failed change efforts stumble not at the strategy stage but at the stage of establishing a sense of urgency and communicating a vision people can actually see themselves in.

One line I repeat in nearly every change management workshop I run is this: people change for their reasons, not yours. Leaders often assume that once they have explained the business case clearly enough, adoption will follow. It rarely does, because a business case answers the organisation’s question — why should we change — but leaves each individual employee’s question unanswered: why should I.

I saw this play out during a digital transformation engagement with a telecom giant. The leadership had a compelling case for moving core operations to a new digital platform, backed by clear cost and efficiency numbers. Adoption among frontline staff remained sluggish for months, until we shifted the entire internal communication campaign away from cost savings and toward a narrative of what the new system meant for each employee individually — less time on manual reconciliation, fewer end-of-day errors that had previously meant late nights, more time engaging directly with customers rather than paperwork. Adoption rates improved meaningfully within a single quarter, without a single change to the technology itself. Only the story changed.

This is the psychological core of William Bridges’ well-known work on transitions, which distinguishes between ‘change’ — the external event — and ‘transition’ — the internal psychological process people must go through to accept it. Bridges argued that most change efforts focus entirely on managing the event while ignoring the transition, which is precisely where resistance quietly builds.

In my own five-step framework for change, first introduced in my book High Performance Leadership, I place enormous weight on the distinction between purpose and vision. Vision belongs to leadership — it is the picture of where the organisation is headed. Purpose belongs to the individual — it is the reason a person is willing to make the personal effort that change demands. The job of a change leader is to be the translator between the two, connecting a leadership vision to a purpose that genuinely resonates with the people expected to carry it out.

Simon Sinek’s well-known work on purpose-driven leadership makes a compatible argument: organisations that clearly articulate why they do what they do generate far deeper loyalty and discretionary effort than those that lead only with what they are doing. I have found this holds true even at the level of a single department rolling out a new process. When I coach managers on communicating change, the first question I ask them to answer, before any rollout plan, is simple: what does this change mean for the person listening to you, not for the company balance sheet.

I recall a conversation with a plant manager overseeing a major automation rollout who initially framed the change purely around productivity metrics in his communication to the shop floor. Workers, quite reasonably, heard this as a threat to their own jobs. When we reframed the same rollout around the purpose of eliminating the most physically strenuous and injury-prone tasks on the line — a purpose the workers themselves had voiced in earlier listening sessions — resistance dropped considerably, and several senior operators became vocal advocates for the very automation they had opposed months earlier.

None of this works, however, without trust. I have watched technically sound change communication plans fail simply because employees did not believe the intention behind them was honest. Harvard Business Review’s research on change communication has repeatedly emphasised that the credibility of the messenger often matters as much as the clarity of the message — employees are highly attuned to whether leadership’s stated purpose for a change matches their observed behaviour during the transition.

This is why I insist, in every change engagement I lead, that the communication must happen in what I call a trusted environment — one where leaders are honest about what employees stand to gain, and equally honest about what they may have to give up. A narrative that only sells benefits, without acknowledging genuine cost or disruption to people’s daily work, tends to erode trust rather than build it.

After more than a decade of coaching, consulting, and speaking on this subject, I have come to a conclusion that sounds less optimistic than most change management literature, but which I believe is more honest: people rarely change because they want to. They change when they have to — when a genuine sense of urgency, tied to a purpose that matters to them personally, makes staying the same feel more costly than moving forward.

The role of a change leader, then, is not simply to announce a new direction, but to manufacture that sense of urgency honestly, connect it to a purpose their people can personally own, and communicate all of it inside a relationship built on trust. Get that sequence right, and change stops being something done to people, and becomes something they choose to do for themselves.