How to Brief Your Managers in 10 Minutes Without Them Going Rogue

You're about to announce a change that affects multiple teams. Your managers need to be prepared to answer questions, explain the rationale, and keep their teams aligned.

You have ten minutes with them before the announcement goes out.

If you brief them poorly, they'll fill gaps with their own interpretations. They'll emphasize different things. They'll give conflicting guidance. Your carefully crafted message will fragment the moment it hits the manager layer.

Here's the structure that prevents that.

The four-part manager briefing

Part 1: What's decided and what's not (2 minutes)

Start by drawing a clear line between finalized decisions and areas that are still flexible.

"The decision to consolidate regional offices is final. The timeline is final. Which roles will be remote versus relocated is still being determined."

This prevents managers from treating finalized decisions as negotiable. It also prevents them from treating flexible elements as if they're locked, which creates problems when those elements change.

Managers need to know what to defend and what to acknowledge as still in process.

Part 2: The three questions their team will ask (3 minutes)

Don't make managers guess what their teams will care about. Tell them.

For most changes, teams ask some version of: "Does this affect me?" "What do I need to do differently?" "When does this happen?"

Give managers the answers to these questions. Specific answers, not strategic framing.

"Everyone in operations is affected. No one in finance. If someone's in operations and works cross-functionally with finance, they're still affected—it's based on their home department."

"Daily work doesn't change until March 1. Between now and then, they'll need to complete the online training module and attend one briefing session."

"Announcement goes out today. Training available starting next week. Changes take effect March 1."

When managers can answer these three questions clearly, most team anxiety resolves immediately.

Part 3: What to say if they don't know the answer (2 minutes)

Managers will get questions you didn't anticipate. If you don't give them a script for handling unknowns, they'll improvise. And improvisation creates inconsistency.

Give them exact language:

"If you're asked something I haven't covered: 'That's a good question. I don't have that information yet, but I'll find out and get back to you by [specific date].' Then escalate it to me immediately so we can get consistent answers to everyone."

This prevents managers from speculating, inventing answers, or saying "I don't know" with no follow-up plan.

Part 4: What they should not do (3 minutes)

Tell managers explicitly what not to do. Don't assume they know.

"Don't soften the message. Don't add your own commentary about whether you agree with the decision. Don't speculate about future changes beyond what I've shared. Don't promise things that haven't been confirmed."

"If someone pushes back hard, acknowledge their concern, but don't reopen the decision. Say: 'I understand this is difficult. The decision is final, and my job is to help you navigate it. What specific support do you need?'"

Managers need permission to hold boundaries. Most of them want to help their teams feel better, which leads to softening messages or implying things might change. Clear boundaries prevent that.

Why this structure works

This briefing structure gives managers the three things they need: clarity on what's locked versus flexible, answers to predictable questions, and scripts for handling the unpredictable.

It prevents fragmentation. It keeps messaging consistent. It lets managers feel prepared instead of defensive.

And it takes ten minutes.

The mistake most people make

Most briefings focus on context: the strategic rationale, the decision-making process, the long-term vision.

That's useful for manager understanding. But it doesn't prepare them to brief their teams.

Teams don't need strategy. They need operational clarity. Managers need to be equipped to provide that, not just to understand the "why."

When to brief managers

Brief managers immediately before the broader announcement. Not days before: that creates information asymmetry and informal communication. Not after: that makes them look uninformed when their teams come to them with questions.

Immediately before. Same day. Ideally, one hour before the announcement goes out.

This is one example. Not a complete kit.

This shows the four-part structure with a single change scenario. Different types of changes require different manager briefings, ie. reorganizations need different talking points than policy changes. System rollouts need different guidance than budget cuts.

Each requires adapted templates. But the structure holds.