Do You Need a Dedicated Change Manager for Your Implementation?

Deciding whether your enterprise implementation needs a dedicated change manager? A practitioner's framework for when internal teams suffice and when to hire.

Your enterprise system implementation is underway. The project team is heads-down on configuration, integrations, and testing. The timeline is real, the budget is committed, and the technical work has momentum. And somewhere in the back of your mind sits a quieter question that nobody on the project plan seems to own: who is making sure the organization is actually ready for this?

If you are asking that question, you are already ahead of most leaders. The hard part is knowing what to do with it. Hiring dedicated change management capability is a real cost and a real commitment. Skipping it can be far more expensive, but not always. The honest answer is that some organizations genuinely do not need outside help, and some need it badly and do not realize it until go-live exposes the gap.

This is a framework for telling the difference.

First, the case for not hiring anyone

Plenty of consultants will tell you that you always need a change manager. That is not true, and pretending otherwise is how the profession lost some of its credibility.

You may be fine with your internal team if several of the following are true. You have run a comparable enterprise implementation in the last few years and the institutional memory still lives in people who are still here. You have a named individual, not a committee, whose actual job for the duration of the project is the people side of the change, with the authority and the calendar to do it. Your leadership is aligned and visibly engaged rather than nominally supportive. And your workforce has absorbed major change recently without lasting damage to trust or performance.

If that describes you, invest in your internal capability and protect that person's time fiercely. You may not need anyone else.

The signals that you do need dedicated help

The trouble is that most organizations believe they meet the bar above when they do not. Here are the signals that the people side of your implementation is under-owned, drawn from what actually goes wrong.

Change is somebody's second job. The most common failure is not the absence of a change plan. It is assigning change leadership to a project manager, an HR business partner, or an operational leader who already has a full-time role. The people work then gets whatever time is left over, which is none, right when it matters most.

Your project plan treats training as the change strategy. Training teaches people which buttons to press. It does nothing to address whether they trust the new system, understand why it is replacing the old one, or have any reason to adopt it rather than build workarounds. When the only people-side line item on your plan is end-user training, the strategy is missing.

Leadership support is verbal, not visible. There is a large difference between executives who say the project is a priority and executives who reschedule their own work to sponsor it publicly. The first is the default. The second is what actually moves an organization, and it has to be designed and coached, not assumed.

You cannot name your hardest-to-reach stakeholders. Every enterprise implementation has groups that sit outside the obvious org chart and absorb a disproportionate share of the disruption. Executive assistants and department administrators operating under delegation authority are a recurring example. They act on behalf of leaders, their workflows are deeply embedded, and they are almost never on the stakeholder list until something breaks. If you cannot quickly name the cohorts like this in your own organization, no one has done the analysis yet.

The technical team is confident and the rest of the organization is quiet. Silence is not readiness. When the project team feels good and the wider workforce has gone quiet, that usually means resistance has moved underground rather than disappeared. It surfaces at go-live, when it is most expensive to address.

What a change partner does that a project manager does not

The distinction matters because the two roles are easy to conflate, and conflating them is how the people side falls through the cracks.

A project manager owns scope, schedule, and budget. They make sure the system gets built and delivered on time. A change leader owns whether the organization is willing and able to use what gets delivered. The work is different in kind. It includes mapping who is affected and how severely, designing the sponsorship that leaders need to provide, building the communication and engagement that turns a mandate into genuine adoption, identifying and equipping the people who will support their peers through the transition, and measuring readiness honestly enough that go-live decisions are based on evidence rather than hope.

This work is the same whether the platform is a finance and supply chain system, a workforce management system, an electronic health record, or any combination running at once. The technology determines the configuration. The organization determines whether the configuration ever delivers value. Those are separate problems, and they need separate ownership.

How to decide

If your internal team meets the bar in the first section, resource them well and move forward with confidence. If you recognized your organization in the second section, the question is not whether to invest in change capability. It is whether to build it internally or bring in a partner who has done this before and can stand it up faster than your team can learn it under deadline pressure.

There is no universal right answer, but there is a right answer for your specific implementation, your timeline, and your organization's history with change. Getting that decision right early is far cheaper than discovering it at go-live.

If you would find it useful to think through where your implementation actually stands, I offer a focused advisory consultation for exactly this question. We can pressure-test your current approach, identify where the people side is under-owned, and give you a clear view of what your implementation needs before the stakes get higher.

Heather | Bloom Consulting & Coaching

Business Transformation, Optimization & Change Advisory