Why relying on your implementation partner for change communications is a costly mistake

When an organization kicks off a major technology transformation, the systems integrator typically brings a change management workstream to the table. And on paper, it makes perfect sense to use it. It's the same team, right? They'll be connected, in sync with the technology build, and drive the project forward as one cohesive unit.

That assumption is one of the most common and costly mistakes organizations make during enterprise transformations.

The silo problem hiding inside your SI

Systems integrators are built to deliver technology. Their organizational structure, incentive models, and project management frameworks are all optimized around the build. The change management function, including communications, often sits in a separate workstream that runs parallel to the technology team but rarely intersects with it in a meaningful way.

In practice, this means the people writing your communications are not in the same rooms, the same standups, or even the same Slack channels as the people making design decisions that will fundamentally change how your workforce operates. The comms team gets briefed after decisions are made, not while they're being made. They're translating outputs, not shaping the narrative in real time.

This is where the execution breaks down. Not because the SI's change team lacks talent, but because the organizational structure doesn't allow the communications workstream to be truly connected to the work that matters most.

The template trap

There is certainly value in templates that work. A proven communications framework, a tested stakeholder mapping tool, a go-live readiness checklist: these are useful starting points. But when that template is rinsed and repeated from client to client without adapting to your organization, it stops working.

Your employees can tell when a communication doesn't sound like your company. When the language feels generic, when the tone doesn't match your culture, when the messaging could have been written for any organization going through any transformation, people disengage. They skim it, delete it, and go back to whatever they were doing before.

Having a communications partner who can blend proven best practices with your internal and external brand, your company culture, and language that is genuinely relatable to your employees is not a nice-to-have. It's the difference between communications people act on and communications people ignore.

Lost in translation

Systems integrators dive right in. They move fast, they bring deep technical expertise, and they speak the language of the platform. That doesn't sound like a bad thing until you realize that your employees, your leaders, and even your project team don't speak that language.

When your workforce starts hearing about "fit-gap analysis," "configuration workbooks," "business process owners," and "cutover planning" without context, confusion sets in fast. It's not that these concepts are too complex for your people. It's that nobody has translated them into language that connects to their daily work.

Establishing a clear narrative early in the program that translates the systems integrator's approach into something your colleagues can actually understand is critical. What is being asked of them, what fundamental design decisions mean for their roles, why new terminology matters, and what specific next steps they need to take. Without that translation layer, employees nod along in town halls and walk away without understanding what just happened.

The real cost of getting it wrong

The conventional wisdom is that poor change communications means employees aren't ready at go-live. That's true, but it understates the problem. The cost of getting communications wrong starts long before go-live. It impacts the build itself.

When employees don't understand what's being asked of them during the design and build phases, the inputs that the technology team needs get delayed, deprioritized, or delivered incorrectly. Subject matter experts show up to workshops unprepared because nobody clearly communicated what was expected. Leaders don't prioritize their team's participation because they don't understand what's at stake. Decision-making slows down because stakeholders aren't aligned on the basics.

This creates a cascading effect. The technology timeline stretches. Frustration builds on both sides. The SI team feels like the client isn't engaged. The client's team feels like the SI is speaking a different language. Tension on the project increases, and the root cause is almost always the same: the communications workstream was never truly connected to the work.

What the alternative looks like

The organizations that get this right bring in a communications partner who sits at the intersection of the SI's technical workstream and the client's workforce. Someone who is in the room when design decisions are made, who understands the SI's methodology well enough to translate it, and who knows the client's culture and brand well enough to make the communications land.

This doesn't mean replacing your SI's change management team entirely. It means recognizing that communications is a specialized discipline that requires dedicated focus, brand alignment, and a deep connection to both the program and the people it impacts.

The question isn't whether your transformation needs communications. It's whether the communications workstream is set up to actually deliver.

The gap between your change strategy and your workforce's understanding doesn't close on its own.

If you're heading into a transformation and want communications that are built into the program from day one, not bolted on at go-live, let's talk.