If you are the transformation director, CIO, COO or program sponsor behind a rollout with a dated go-live, you have probably already sat through a communications plan that lists the town hall, the intranet post and the FAQ document, and still felt uneasy about it. That unease is correct. Employee buy-in before implementation is not won at the podium. It is won or lost in the fifty one-to-ones that happen in the fortnight after the announcement, when a middle manager has to say something about the change in their own words, to a person who will judge the whole program by their tone. Get that layer right and the rollout has a chance. Get it wrong and no amount of town hall polish will buy it back.
Buy-In Is Not Won in the Town Hall
The town hall does one job well: it makes the decision public. It does almost nothing to make the decision believed. Belief travels through managers, not slides, and most communication plans hand those managers messages to relay without giving them anything to say about the parts they privately doubt. A manager who does not believe the message still has to deliver it, so they deliver it flatly, hedge it with body language, or quietly signal “I know, but what can you do.” Their team reads that in about four seconds, and the program has just lost a room it never knew it was presenting to.
This is not a failure of effort. A manager who refuses to promise something the program has not confirmed is behaving responsibly, and most communication plans reward exactly that caution. The trouble is that caution sounds like vagueness to the person on the other side of the desk, and vagueness gets filled in by whoever in the team has watched a rollout fail before.
Why the Middle Layer Goes Quiet
The credibility of everything a leader says about a change is set by whether anything happens in the 48 hours after they say it. That is The First 48 Hours, the mechanism at the centre of my Execution Intelligence™ work: a decision is only believed once something visibly stops, starts or changes because of it, inside about two days. A message with nothing attached to it is a promise, and organisations discount promises heavily, particularly ones running their third or fourth change program. A message with one small visible change attached to it is evidence, and evidence is what a middle manager can actually stand behind in a one-to-one. The full version of this argument, and why it matters most in the days right after the decision is made, not in the months before go-live, is set out in why resistance to change hardens before go-live.
Without that evidence, managers are asked to sell certainty they do not have, and most competent managers will not do it. So they go quiet, or generic, and their team correctly reads generic as “there is nothing real to tell you yet.”
What to Say When Someone Asks What It Costs Them
Picture a regional operations manager, sitting across from her general manager three weeks after a new platform was announced for her division. She asks the only question that actually matters to her: “What does this do to my numbers this quarter?”
The reassuring answer, the one most programs reach for, sounds like this:
“Don’t worry, the transition team has this covered. Your targets won’t change and it should be business as usual.”
It is warm, it is fast, and it is the answer that loses her. She has run three of these before. She knows “business as usual” is not a fact, it is a hope, and the moment her numbers move because of the rollout, every word the program has said to her becomes suspect, including the parts that were true.
The honest answer keeps her onside, because it treats her as someone who can handle a real answer:
“Honestly, there’s a good chance your numbers dip in weeks two and three while the team is on the new process, and I don’t want to promise you otherwise. What I can tell you is we’re building a two-week buffer into your target for that period, and Priya’s team goes live a fortnight before yours so we’ll know exactly what to expect before it hits you. I’ll have the adjusted target to you by Friday.”
Nothing in the second answer is more comfortable. It is more useful, and it gives her something concrete to repeat to her own team, which is the point. People do not need to be sold on a rollout. They need to know what changes for them, when, and what it costs.
Three Sentences to Stop Using Before a Rollout
Some lines survive in change communication because they feel safe to say, not because they work. Three worth retiring before the next rollout kickoff:
“This won’t really change how you work.” If it is worth doing, it will change how someone works. Saying otherwise buys a quiet week and a credibility problem the moment reality disagrees with the message.
“We’ll let you know more as we know more.” This is the sentence that fills a program’s silence with the organisation’s own story, and it is rarely a flattering one. If there is truly nothing to say yet, say what will be different by Friday instead, even something small, rather than deferring the whole conversation.
“Everyone is really excited about this.” Nobody believes it, and the room full of people who are not excited now has evidence the program is not being straight with them either.
How to End Every Conversation So It Counts
The practical discipline is simple to state and easy to skip under time pressure: end every buy-in conversation, whether it is a one-to-one, a team briefing or a Q&A after a town hall, by naming the one thing that is genuinely different by Friday and who owns it. Not the whole roadmap. One thing. It might be a form that stops being used, a meeting that changes format, or a decision that has already been handed to a named person. It matters less what the thing is than that it is real, dated and attributable.
This is the same mechanism a program’s change champions use to make a rollout feel real, applied here to every leader carrying the message, not just the willing minority. Two groups need this kind of evidence most: the sceptics, because it is the only thing that outweighs their own experience of programs that talked and did not deliver, and the middle managers themselves, because a leader who can point at something real has stopped asking their team to take the program’s word for anything.
What Honest Communication Buys You at Go-Live
None of this is about being blunt for its own sake. It is about recognising that trust compounds the same way debt does, in both directions. A leader who tells a regional operations manager the truth about a difficult quarter earns the right to be believed at the next milestone. A leader who reassures her instead spends that trust in a single conversation and rarely gets it back before go-live. MIT Sloan Management Review’s analysis of why employees are drowning in change backs this up from the employee side: what wears people out is not the volume of change but poorly sequenced, poorly explained change, exactly the gap an honest, specific conversation closes.
By the time a rollout reaches go-live, the program is not persuading anyone for the first time. It is either drawing on a balance of trust it has been building since the announcement, or it is trying to open an account that is already overdrawn. The language a leader uses in the weeks beforehand is what decides which one it is.
If your program is heading toward an announcement, a kickoff or a run of manager briefings and you want the room to hear something more credible than a comms plan can deliver on its own, get in touch about bringing AJ into the room before the silence sets in, not after.
AJ Kulatunga is a keynote speaker who works with transformation and technology programs on the language and timing that decide whether a rollout earns belief before go-live. He speaks to leadership teams, program sponsors and change champion cohorts on turning decisions into visible, credible movement in the weeks that matter most.
