There is a particular kind of knowing look that passes between two experienced change managers when someone in a meeting says, “We just need to communicate it better.” You have seen it. You may have perfected it. It says: here we go again. No matter the industry, the country, or the size of the organisation, seasoned change managers share a remarkable set of experiences that unite them across every project they have ever worked on. These moments are equal parts frustrating and funny, and they are the unofficial initiation rites of the profession.

This article is for those practitioners who have accumulated enough project scars to nod along knowingly. It is also a useful mirror for anyone newer to the field wondering whether the challenges they face are unique to their organisation, or simply part of the territory. Spoiler: it is the territory. Here are 10 signs you are a seasoned change manager.

Sign 1: You have been brought in after the approach is already set, and asked to “fix” the stakeholder engagement.

You receive a call. The project has been running for six months. The business case was signed off, the solution was designed, the vendor was selected, and the go-live date is locked in. Now, with a few months to spare, the project manager has noticed that the affected teams are not exactly enthusiastic. Could you come in and, you know, get people on board?

This scenario is so common it almost qualifies as a project phase in its own right. Research from Prosci consistently identifies “active and visible sponsorship” and “early change management integration” as two of the top contributors to change success. When change management is bolted on after the key decisions are made, the practitioner is not managing change, they are managing reaction. The stakeholders are not resistant because they are difficult; they are resistant because nobody asked them anything until the answer was already decided.

The seasoned change manager takes this in stride. You quickly assess what can still be influenced, identify the loudest voices in the room, and find the small but genuine opportunities for co-design that remain. You have learned to extract value from constrained circumstances. That said, you also make a mental note to have the “involve us at the beginning” conversation very clearly on the next engagement.

Sign 2: You get funny looks when you mention change activities beyond communications and training.

You are presenting your change plan to the project steering committee. You walk through the stakeholder engagement strategy, the change impact assessment, the resistance management approach, the coaching plan for people leaders, the readiness assessments, and the benefits realisation tracking. Somewhere around the third slide, you notice the expressions. A slight furrowing of brows. A quick sideways glance between the project director and the business lead. Finally someone says, helpfully: “So… when are you doing the training?”

This is one of the most persistent misconceptions in the profession. Many stakeholders still equate change management with communications and a training course. In fairness, those are the most visible outputs of the work, and the ones that directly touch the workforce. But as the Prosci ADKAR model makes clear, awareness and knowledge (which communications and training primarily address) are only two of five building blocks required for individual change adoption. Without desire, ability, and reinforcement, even the most polished training programme will not produce sustained behaviour change.

The seasoned change manager has developed a short, compelling explanation for why the full suite of activities matters. You have learned to connect each activity to a business outcome the steering committee actually cares about. And you have developed a thick skin for the meetings where you come back with a pruned-down plan because “we do not have budget for all of that.”

Sign 3: You feel like the permanent go-between with the project team and the difficult stakeholders.

On one side, you have the project team, who are focused on delivery milestones, technical requirements, and keeping the Gantt chart green. On the other side, you have stakeholders in the business who have real concerns, competing priorities, and a historical reason or two to be sceptical about how IT-led projects tend to turn out. And somehow, inexplicably, you are the person standing in the middle trying to translate between the two worlds.

This bridging role is actually one of the most valuable things a change manager does, even when it is exhausting. Research on high-performing teams consistently shows that communication flow between groups, not just within them, is a critical predictor of project outcomes. The change manager who maintains trusted relationships on both sides of that divide is providing an organisational function that nobody else is formally positioned to perform.

The challenge is avoiding the trap of becoming the unofficial complaint receptacle for both sides. Seasoned practitioners learn to be clear about their role: you facilitate dialogue, surface genuine concerns, and feed them into project decision-making. You are not there to absorb the frustrations of the project team about stakeholder behaviour, nor to commiserate with stakeholders about how the project is being run. You stay useful by staying neutral enough to be trusted by both sides.

Sign 4: You dread manually filling in rows of XLS data for stakeholder matrices and change impact assessments.

The spreadsheet. That great monument to change management effort. You have a stakeholder matrix with 47 rows, a change impact assessment with colour-coded severity ratings that mean slightly different things depending on who last edited the file, and a combined change plan that has been through eleven versions and still has someone’s tracked changes from March lurking in it. Every update requires a half-day of manual reconciliation across three documents, and you are never quite sure if the version on the shared drive is the same one the project sponsor has open on their laptop.

This is precisely the pain point that purpose-built tools like The Change Compass were designed to address. Rather than maintaining disconnected spreadsheets, platforms built for change management allow you to capture stakeholder data, impact assessments, and change portfolio views in one place, with real-time visibility for everyone who needs it. The shift from manual spreadsheet management to structured data entry does not just save time; it also produces more consistent, comparable data across projects, which becomes genuinely valuable when you are managing a portfolio of simultaneous changes.

Until that shift happens on your project, you develop a personal set of hacks: a master template you have refined over years, a clear versioning convention, and a personal rule that you never open the spreadsheet in a meeting on a shared screen without checking it first. Hard-won wisdom, all of it.

Sign 5: Corporate communications persistently rewrites your project communications.

You spend a week crafting a plain-language change communication. It is clear, direct, and human. It explains what is changing, why it is changing, what it means for people, and what they need to do next. You send it to corporate communications for sign-off. It comes back with the subject line changed to something with an acronym, three paragraphs of organisational context that nobody asked for, a reference to the CEO’s strategic priorities from the annual report, and the actual information buried on page two.

There is a real tension here that is worth understanding rather than simply resenting. Corporate communications teams are typically managing brand consistency, legal considerations, executive voice, and a broader messaging calendar that your project sits within. Their instinct to frame every communication in organisational strategy terms is not arbitrary; it reflects a legitimate concern about mixed messages. The problem is that project-level change communications have a different job to do. They need to answer the employee’s immediate question: “What does this mean for me?” Strategic framing, while appropriate in a town hall, often obscures that answer in a targeted update.

The most effective change managers build a working relationship with the communications team early in the project, establish a shared understanding of what different communication types are trying to achieve, and create a review process that preserves the core employee-facing message while allowing the corporate voice to be woven in where it genuinely helps. It takes negotiation, patience, and occasionally a willingness to let go of your favourite sentence. But it is far better than sending communications that read like an internal press release.

Sign 6: You sit through project meetings full of data while the change metrics get skipped entirely.

The project status meeting has a packed agenda. The project manager runs through the RAG ratings, the budget burn, the milestone tracker, the risk register, and the issues log. Then someone glances at the clock and says, “We are a bit over time, can we take the change update offline?” This happens so routinely that you have started positioning your agenda item strategically, just before a topic the project director actually cares about.

The underlying issue is that change metrics, when they exist at all, are often qualitative and subjective in a meeting full of quantitative project data. Stakeholder sentiment, readiness ratings, and engagement scores can feel like soft impressions compared to a milestone completion percentage. This is exactly where tools like The Change Compass make a practical difference: when change data is structured, tracked over time, and displayed visually, it earns a place in the conversation alongside traditional project metrics. A readiness trend line carries more weight in a steering committee than a verbal summary of how you think people are feeling.

Seasoned change managers learn to present their metrics in the language of project governance: red, amber, green; trend over time; risks tied to go-live. When you frame change readiness as a delivery risk, it stops being a soft people topic and starts being a project concern that the committee is already primed to take seriously.

Sign 7: You are the unofficial “dumbing down” translator for project messages.

The technical lead has prepared a briefing for the affected business units. It is thorough, precise, and explains the system migration in detail that would delight an IT architect. It also uses seven acronyms, assumes knowledge of the legacy system’s configuration, and contains a diagram that requires a legend to decipher. You are handed this document forty-eight hours before the briefing session with the request: “Can you make this accessible?”

Translation work is genuinely one of the highest-value things a change manager does, and it is chronically underappreciated. Harvard Business Review has written extensively about the cost of technical communication failures in organisations, noting that when employees cannot understand what is being asked of them, adoption slows and errors increase. The change manager who can take complex technical content and render it in plain language that answers “what does this actually mean for my day-to-day work?” is performing a function that is essential to the success of the project.

Over time, you also develop a secondary skill: helping technical teams understand why this translation matters, and coaching them to communicate more plainly from the outset. Not every technical expert will welcome this feedback, but the ones who do become significantly more effective in business-facing roles. You have learned to frame it not as “your communication is too complicated” but as “your audience needs this information in a slightly different format to act on it.” Subtle, but it lands better.

Sign 8: You struggle to get meaningful time with the project sponsor.

The project sponsor is enthusiastic, senior, and almost completely unavailable. They agreed to be the sponsor because they believe in the initiative; they simply did not factor in that sponsorship in a change management context requires an ongoing time commitment. Their EA protects their diary with the intensity of a border collie. Your standing fortnightly meeting gets bumped more often than it runs. And when you do get in front of them, they have about twelve minutes before the next call starts.

Prosci’s research has consistently ranked active and visible sponsorship as the single most important contributor to change success across more than two decades of benchmarking studies. The sponsor’s visible support, their willingness to communicate directly with the workforce, and their ability to remove organisational barriers are not nice-to-haves; they are the engine of adoption. When the sponsor is absent or disengaged, the change manager is left advocating for a change they cannot personally authorise, which is an awkward position to sustain over months.

Experienced change managers learn to make the most of limited access. You prepare concise, decision-ready briefings that the sponsor can consume in under five minutes. You identify the two or three moments in the project lifecycle where their personal visibility will have the highest impact, and you request targeted time for those specifically rather than a general standing meeting. You also find ways to keep them informed asynchronously, so that when you do get time together, it is used for decisions and actions, not catch-up.

Sign 9: You find out late about other changes that are impacting your stakeholders.

You are three weeks out from go-live when someone casually mentions in a hallway conversation that the finance team, who are a key group in your change impact assessment, are also in the middle of a major system migration that goes live the same week. Or that HR is rolling out a new performance management framework this quarter, and the same frontline managers you are counting on to coach their teams through your change are already stretched thin with that programme’s requirements. Nobody told you. Nobody thought to.

This is the organisational change saturation problem, and it is one of the most underacknowledged risks in portfolio management. McKinsey research on transformation has highlighted that organisations frequently underestimate the cumulative load that multiple concurrent changes place on employees, particularly middle managers who are expected to lead and absorb change simultaneously. When projects operate in silos, there is no mechanism for surfacing this load until it becomes a crisis.

The seasoned change manager develops informal intelligence networks across the organisation specifically to catch these collisions early. You build relationships with peers on other projects, check in with HR business partners about what else is running, and ask the change impact question not just about your project but about the broader landscape your stakeholders are navigating. It takes time and relationship capital, but it is almost always worth it.

Sign 10: You have had actual nightmares about a resistant stakeholder blocking your plans.

You know the one. Every change manager has at least one. The stakeholder who was never quite on board, who asked pointed questions in every meeting, who had a well-developed set of objections to every proposed approach, and who somehow always managed to loop in their executive at the most inconvenient possible moment. You replayed certain conversations in your head on the drive home. You may have, on more than one occasion, jolted awake at 2am because your sleeping brain had conjured a new angle they might use to derail the steering committee presentation.

Here is something that experience teaches you, even if it is hard to see in the moment: the resistant stakeholder is often the most important person in the room. Their objections, frustrating as they are to manage, frequently surface risks that the project team has not adequately considered. Research on organisational decision-making consistently shows that dissenting voices, when engaged constructively rather than managed away, improve the quality of decisions. The resistant stakeholder who becomes a genuine partner in shaping the change approach is worth ten passive supporters.

That does not mean every resistant stakeholder is engaging in good faith, or that every objection deserves to reshape the project plan. It does mean that the experienced change manager approaches resistance with curiosity before they reach for the mitigation strategies. What is the underlying concern? What would need to be true for this person to shift from sceptic to advocate? Sometimes the answer is genuinely satisfying. And sometimes you just have to accept that not everyone will come along, document the risk, and keep moving. Either way, the nightmares do get less frequent with experience.

What these shared experiences tell us about the profession

There is something genuinely useful in recognising how universal these experiences are. It means the challenges you face are not signs that you are working in a uniquely dysfunctional organisation, or that you are doing something wrong. They are structural features of how change management sits within most organisations today: positioned late, resourced lightly, misunderstood frequently, and still somehow expected to produce results. The fact that experienced practitioners navigate these constraints and deliver meaningful outcomes anyway is a testament to the skill and persistence the role demands.

The profession is maturing. The conversation is shifting from “do we need a change manager?” to “how do we build change capability across the organisation?” Tools are improving, data literacy among change practitioners is growing, and the case for early, structured, and well-resourced change management is better evidenced than it has ever been. The experiences described in this article are, for many practitioners, already becoming less common as organisations develop more sophisticated approaches. But for now, if you recognised yourself in at least six of these ten signs, welcome to the club. The war stories are good, and the community is warm.

Frequently asked questions

Why is change management so often brought in late on projects?
Change management is still frequently treated as a delivery support function rather than a strategic one, which means it gets resourced at the same time as other delivery activities rather than at project initiation. This is changing as organisations build more mature programme governance, but it remains the norm rather than the exception in many sectors. The practical fix is to build change management into project initiation checklists and funding models so it cannot be bolted on as an afterthought.

Is stakeholder resistance always a bad sign?
Not at all. Resistance often signals that people are engaged enough with the change to have formed an opinion about it, which is a better position to work from than passive indifference. Experienced change managers treat resistance as information: it tells you where the genuine concerns are, who the informal influencers are, and what the change still needs to address to earn broader acceptance. Resistance that is acknowledged and worked through productively tends to produce more durable adoption than smooth, unchallenged rollouts.

How do you get a disengaged project sponsor to play an active role?
The most effective approach is to make sponsorship actions as specific and low-friction as possible. Rather than asking a sponsor to “be more visible,” identify the three or four concrete moments during the project where their personal involvement will have the highest impact, prepare the materials for them, and make the ask specific. Most sponsors want the project to succeed; they just need help understanding what the role requires in practice, and support in fitting it around an already-demanding schedule.

What is the best way to demonstrate the value of change management to a sceptical project team?
Connect your activities to outcomes the project team is already measured on. Change readiness before go-live reduces post-implementation support tickets. Effective stakeholder engagement reduces last-minute escalations to the steering committee. Strong manager coaching reduces the time to productivity for affected teams. When you frame change management activities in terms of project risks avoided and delivery outcomes improved, they stop being soft people work and start being hard project value. Data helps enormously here, which is why tracking and reporting change metrics with the same discipline applied to project metrics is worth the investment.

References

• Prosci. (2023). What is change management? Prosci.
• Prosci. (2023). The importance of active and visible sponsorship. Prosci.
• McKinsey & Company. (2017). The people power of transformations. McKinsey & Company.
• Kegan, R., & Lahey, L. (2016). How to explain technical topics to non-technical audiences. Harvard Business Review.