The executive briefing — talking to operations directors and above
Three minutes, not thirty
The conversation with the operations director, the planning director, or the chief operating officer follows a different rhythm to any other planning conversation. The audience has less time and more decisions to make. They want the outcome, the risk, and the recommendation, in that order, in three minutes — not the model, the methodology, or the assumptions. The planner who arrives with thirty minutes of explanation gets twelve minutes of attention and leaves with a decision deferred. The planner who arrives with three sentences of executive summary gets a decision, often in the same meeting.
What an executive actually needs
Three things, every time.
The outcome. What will happen if nothing changes. “December SL is forecast at 67% against an 80% target; that’s a 13-point miss visible to the customer for roughly six weeks.” One sentence. Concrete consequence.
The risk. What you’re less sure about and what would make it worse. “The forecast assumes the December marketing push is the same shape as last year; if it’s 10% larger, the miss extends to 18 points.” One sentence. Names the uncertainty before they ask.
The recommendation. What you want them to do. “I’m recommending we open the outsource overflow for weeks 49–51 at an incremental cost of £94k; the alternative is to accept the SL miss.” One sentence. Specific. Has a number.
If you can’t do all three in three sentences, you don’t yet have the brief. Go back and write it down before the meeting.
What to leave out
Executive briefings fail more often from over-inclusion than under-inclusion. Three categories of content belong in the appendix, not the meeting.
Methodology. “We used Holt-Winters with weekly seasonality and a marketing-spend driver” means nothing to an operations director and burns thirty seconds of attention. They’ll ask if they need it. They usually don’t.
The walk-through of how the model evolved. The journey from first cut to final answer is interesting to you. It’s noise to the audience. Show the answer; describe the journey only if asked.
Caveats that don’t change the recommendation. “Of course there are limitations; the model assumes…” If the limitation doesn’t change what you’d recommend, it doesn’t belong in the brief. If it does, surface it as a named risk in paragraph two.
Anticipating the questions
Three questions recur after almost every executive briefing. Have an answer ready for each before you walk in.
“How confident are you in the number?” The honest answer is rarely “very.” A useful answer is “the central estimate is X, the realistic range is Y to Z, and the thing I’d watch in week 1 to know which end we’re heading toward is W.” That answer treats the executive as a partner in managing uncertainty, not as an audience for false confidence.
“What would change your mind?” The best version of this question. The worst answer is “nothing — we’ve done the analysis.” The right answer is the named signal you’re watching for. “If December week 1 lands more than 8% above forecast, I’ll come back with a revised ask.”
“Have you talked to [adjacent function]?” Almost always asked, and the planner who can answer “yes, here’s what finance / recruitment / marketing said” gets a decision faster than the one who has to leave the meeting to check. Build the relationships before the briefing, not after.
The two failure modes that matter
Hedging the recommendation. “You could do A or B; either has merits.” The executive will reasonably ask “what would you do?” If the planner can’t answer that, the planner has brought analysis but no judgement, and the briefing becomes a discussion the executive has to lead. Always bring a named recommendation. You can be wrong. You shouldn’t be silent.
Over-explaining when the room is convinced. The most common waste of executive time is the planner who keeps explaining after the decision has been made. Watch for the signal — the nod, the “okay, do it,” the body language shifting to the next item — and stop. The executive who heard the decision and is ready to move on doesn’t need the appendix.
When to escalate and when to absorb
Not every planning issue belongs in an executive briefing. The planner who escalates everything becomes background noise; the planner who escalates nothing becomes invisible until something has already gone wrong. The discriminator is simple: does the issue need an executive decision, or can the planning team handle it?
Escalate when: a trade-off needs to be approved at a level above the planning team, a budget envelope needs to be opened, a regulatory or reputational risk is implied, or an adjacent function (finance, HR, marketing) needs aligning. Absorb when: the issue is operational, the planning team has authority to resolve it, or the consequence is small enough that the executive’s attention is more valuable elsewhere.
A useful rule: every escalation is implicitly a request for a decision or a resource. If you can’t name which, it isn’t ready to escalate.
The standing-relationship investment
The most important executive-briefing investment isn’t the briefing itself — it’s the standing relationship that makes the briefing land. A fortnightly thirty-minute one-to-one with the operations director, with no agenda required, transforms how briefings are received. The executive develops context for how the planning team thinks, the planner develops context for what the executive is worrying about, and the formal briefings become collaborative rather than transactional. Planners who don’t have this relationship spend their formal briefings catching up; planners who do spend them deciding.
Conclusion
The executive briefing is a different conversation to every other planning conversation. The audience has less time, more decisions, and no appetite for methodology. The discipline is brutal compression: outcome, risk, recommendation. Three paragraphs. Three minutes. One decision. The planners who land these consistently get a seat at decisions that shape the operation; the planners who don’t get briefed instead of consulted. The skill is learnable and the practice is unglamorous: write the brief, cut half of it, then cut half again. What survives is what should have been said.
Next in the series: The team-leader handoff — the planner’s most-frequent conversation.
Pair this with building planning function credibility, the first 90 days as a contact centre manager, and numbers TLs should track.