5 questions every change communications plan should answer before go-live

You have a change management plan. You have a communications plan. You might even have a content calendar with emails scheduled through go-live. But here's the test that matters: can your impacted employees actually answer the questions they care about?

If the answer is no, your communications plan has gaps. And those gaps will show up as confusion, resistance, and low adoption on the other side of go-live.

After 15+ years of partnering with organizations through enterprise transformations, these are the five questions we pressure-test every communications plan against. If your workforce can't answer them clearly, there's work to do.

1. Why is this happening and why should I care?

This should be the very first thing your employees hear from the program. Before the timeline. Before the system details. Before anything else.

And it can't sound like a business case written for the board. "We're implementing a new HCM platform to streamline operations and drive efficiencies" is technically true, but it gives an employee nothing to hold onto. Why does this matter to them? What was broken? What happens if the organization doesn't make this change? What does success look like for the people doing the work, not just the people approving the budget?

The program needs a north star. A clear, repeatable narrative that is written in language your colleagues not only understand but that speaks to what matters to them. Think of it as an elevator pitch for the transformation, one that any employee could hear once and explain to a coworker over lunch.

This north star needs to come from senior leaders early and often. If your executive sponsor can't articulate the why in two sentences that would resonate with a frontline employee, the narrative needs more work. And if the first time employees hear about the program is through a project team email rather than a leader they trust, you've already lost ground.

2. What is actually changing for me?

This sounds obvious. It's not.

Most change communications do a solid job of announcing that a change is happening. They explain the new system, the timeline, the business rationale. But they stop short of telling each impacted group what's different about their specific daily work.

A finance team member doesn't need to know the full scope of the ERP transformation. They need to know that the way they process invoices is changing on March 1, here's what the new process looks like, and here's what happens if they continue doing it the old way. That level of specificity requires role-based content, not organization-wide emails.

There are three things every employee needs to understand about the change: what is actually different about how they do their job, why that change is happening, and what the risk is if they don't change their behavior. That third piece is the one most communications plans skip, and it's often the one that drives action.

Here's the other challenge: technology transformations rarely stand alone. A new system almost always coincides with a shift in how the business operates, how decisions get made, and how teams work together. The technology has a go-live date. The ways of working transformation is harder to pin down, which is exactly why it can feel squishy and abstract to employees. The communications need to make it concrete. If you can't describe the behavioral change in terms an employee would recognize in their Monday morning, your messaging isn't specific enough yet.

If your communications plan doesn't include "What's Changing for Me" content tailored to each major role or function, you're leaving your most important audience with unanswered questions.

3. What do I need to do differently starting on day one?

This is where most communications plans fall short. There's a lot of energy around awareness ("the change is coming!") and training ("here's how the system works"), but very little around the behavioral shift in between.

Knowing that a new system exists is not the same as knowing what to do differently when you show up on Monday. Business readiness communications bridge that gap. They tell leaders and employees: here are the three things that are different about how you do your job starting next week, and here's exactly what action you need to take.

If your communications plan jumps straight from awareness to training without a business readiness layer, your workforce will be informed but not prepared. Those are two very different things.

4. Where do I send my questions?

Every transformation generates questions. Lots of them. And that's a good thing.

Engaged employees who are reading the materials you create, processing them, and asking questions are exactly what you want. It means your communications are landing. It means people are paying attention. The goal is never to reduce questions. The goal is to make sure that when people ask them, they get consistent, informed answers regardless of who they turn to.

That's the part most programs underestimate. An employee might ask their direct manager. Another might go to their department leader. A third might email the project team. If those three people give three different answers, or worse, if they don't know the answer at all, it erodes trust in the program fast.

Your communications plan needs to do two things well before go-live. First, establish clear channels where employees can send questions and trust they'll get a real answer. That might be a dedicated inbox, a Slack channel, an FAQ hub, or a network of change champions embedded in each team. The specific channel matters less than the clarity.

Second, and this is the one that gets overlooked, equip your managers, department leaders, and project team members with the same messaging, talking points, and Q&A resources so that no matter who an employee turns to, they get a consistent and accurate response. When a people leader can confidently answer a question about the transformation without having to escalate it, that builds more trust than any email campaign ever will.

5. Who is leading this and do I trust them?

Your employees may never ask this question out loud. But it's the first thing they evaluate when they hear about a new program. Before they process a single detail about what's changing, they're asking themselves: do I know the person leading this? Do they understand this company, my job, and do they have our best interest at heart?

This is why having a strong internal executive sponsor with real organizational clout matters so much. That leader needs to be the voice of the program. Not the systems integrator. Not the project management office. A person your employees already know, respect, and believe in.

When an external implementation partner presents the strategy to working teams, it can feel like something being done to the organization rather than something being led by it. Employees listen differently when the message comes from a leader they trust versus a consultant they just met.

That doesn't mean the system integrator has no role in the narrative. Their expertise and track record are a valuable proof point. "We've brought in a partner who has done this successfully at organizations like ours" is a credibility signal that supports the program. But it supports the program. It doesn't lead it.

The balance to strike is this: your internal executive sponsor is the strategic driver, the face of the program, and the person who connects the change to your company's culture and values. The implementation partner is the expert behind the build. When employees see that combination, they feel led rather than managed, and that distinction shapes everything that follows.

If your communications plan doesn't position an internal leader as the primary voice of the program from day one, you're starting with a trust deficit that no amount of content can overcome.

The pressure test

Pull up your current communications plan and run it against these five questions for each of your major stakeholder groups. If you can't answer all five clearly for each audience, you've found your gaps.

The good news: these are solvable problems. They just require the kind of focused, role-specific communications work that most change programs know they need but aren't always resourced to do.

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

If your transformation is in the planning phase and you want to build communications into the program from the start, or if you're mid-flight and realize the gaps are growing, let's talk.