Most change plans over-invest in executive communication and under-invest in managers.
That is backwards.
Executives can explain why the change matters. Managers determine whether it becomes daily behavior. They translate the change into local work, answer the same question ten times, handle exceptions, correct drift, notice avoidance, absorb frustration, and decide what gets reinforced when the week gets busy.
If managers are unclear, unconvinced, overloaded, or unsupported, the change will decay at the layer where adoption actually happens.
Managers make change specific
A company can announce a new standard globally, but a manager has to make it concrete.
What does this mean for our team? Which meeting changes? Which template do we stop using? What happens to current work in progress? How do we handle customers already in the old process? What does good look like this week? What will I inspect? What will I no longer accept?
Employees trust the manager's behavior more than the launch message. If the memo says the new process matters but the manager still asks for the old artifact, the old artifact wins. If the manager privately signals that leadership will forget this in two weeks, the team will conserve energy and wait.
Equip managers before the announcement
Managers should not learn about major changes at the same time as their teams.
Before launch, managers need:
- the business reason for the change;
- the specific behavior expected;
- what is changing and what is not;
- what old work should stop;
- how to explain tradeoffs and losses honestly;
- what objections are expected;
- what exceptions they can approve;
- what they must escalate;
- what metrics or signals they should watch;
- what language to use when correcting drift.
This is not about scripting robots. It is about giving managers enough context to act as infrastructure rather than rumor routers. It also gives managers a legitimate feedback path: when the design is broken, they need a place to report friction without being labeled anti-change.
Reinforcement beats reminders
Reminder messages are weak reinforcement. Manager behavior is strong reinforcement.
A manager reinforces change when they:
- ask for the new artifact in the normal meeting;
- reject work that follows the old standard;
- praise the first correct use of the new process;
- remove old templates from team routines;
- explain why an exception is or is not allowed;
- connect the change to actual customer, financial, product, or execution outcomes;
- escalate systemic friction instead of letting the team quietly work around it.
This is where adoption becomes visible.
Managers need authority
Do not ask managers to enforce a change they cannot control.
If a manager is expected to stop old behavior but executives keep accepting it, the manager loses credibility. If a manager is expected to prioritize a new workflow but metrics still reward the old output, the manager is trapped. If a manager is expected to handle exceptions but has no decision rights, every exception becomes escalation theater.
Manager reinforcement requires authority, not just communication.
The manager reinforcement script
For each change, equip managers with a simple operating script:
- Why this matters: the business reason, not just the slogan.
- What changes: old behavior, new behavior, and moment of substitution.
- What does not change: boundaries that reduce anxiety.
- First-week expectations: what the team must do now.
- Inspection points: where the manager will look for adoption.
- Exception rules: what can be handled locally and what must escalate.
- Common objections: honest answers, including tradeoffs.
- Friction channel: how managers report design problems.
- Reinforcement language: how to correct drift without turning every miss into a moral failure.
This turns managers into the distribution system for behavior change. The script should be paired with a reinforcement cadence: first-week inspection, two-week exception review, 30-day friction review, and a clear escalation path for design issues managers cannot solve locally.
The operator's rule
If managers cannot explain, inspect, reinforce, and escalate the change, the company is not ready to launch it.
Managers are not a communications audience. They are change infrastructure.
