Why Q3 Planning Decks Get One Department to Nod and Five to Push Back

In 2018 I was working with a senior leader at a mid-cap European insurance group on her Q3 planning presentation. She was presenting to the executive committee — six functional heads plus the chief executive — and her own team was the largest of the six functions. She had spent two weeks building a thirty-one-slide Q3 plan that walked the committee through her function’s priorities, her function’s resource needs, her function’s milestones, and her function’s dependencies on the other five. The deck was structurally clean and the analysis was rigorous. The chief executive, whom she had pre-briefed the day before, opened the meeting by saying he was strongly supportive of the plan. Within twelve minutes the meeting had turned. The chief marketing officer wanted to know why her function’s campaign timing assumed a Q3 product readiness date that conflicted with what marketing had budgeted for. The chief technology officer wanted to know whether the resource ask included the platform work his team would need to deliver. The chief financial officer wanted to know whether the budget figures had been reconciled with the rolling forecast. The chief operating officer wanted to know whether the operations team had been consulted on the implementation timeline. The chief human resources officer wanted to know whether the headcount assumptions matched the recruiting pipeline. Five questions, five departments, twelve minutes. The plan was not approved in the meeting. It went away for “alignment work” and came back four weeks later as a substantially different plan.

I have now watched roughly forty senior leaders present Q3 planning to multi-functional executive committees, and the structural mistake is reliably the same. The senior leader writes the deck from their own functional lens because that is the lens they think in, prepares the deck thoroughly within that lens, pre-briefs the most senior person in the room, and then walks into a meeting where the other five functions are reading the deck through their own lenses and finding gaps. The gaps were not invisible. They were not addressed because the senior leader did not see the deck through the other five lenses before walking in. The Q3 planning presentation that holds together is structurally different: it is built lens-by-lens, departmental question by departmental question, with the senior leader’s own functional view appearing as one of six perspectives rather than the controlling perspective.

(This article was created with AI assistance; all stories and insights are based on 35 years of real client work.)

The cross-functional format I want to describe in this article is the structural template I now teach for any Q3 planning presentation that goes to a multi-functional executive committee. It is unfamiliar at first because it requires the senior leader to put their own function in line with the others rather than at the centre. The structural reward is that the meeting runs cleanly, the decisions are made in the room, and the post-meeting alignment work that usually takes three to four weeks gets compressed into the meeting itself. The cost of the format is two days of additional preparation upstream of the meeting. The payoff is a Q3 plan that starts on time rather than a month late, which is materially valuable when the executable year shrinks every quarter and Q3 is already the quarter with the holiday window inside it.

Why five departments push back on a Q3 planning presentation that one department nods through

An executive committee sitting through a Q3 planning presentation is not one audience. It is six audiences in one room. Each functional head is reading the deck against their own function’s priorities, constraints, and unanswered questions. The chief marketing officer reads every page of the deck through a “what does this mean for the campaign calendar and the brand commitments we’ve made” lens. The chief technology officer reads through a “what platform work does this assume and is the engineering capacity there” lens. The chief financial officer reads through a “do the numbers reconcile with the rolling forecast and the board-approved envelope” lens. The chief operating officer reads through a “what does delivery look like and where are the operational pinch points” lens. The chief human resources officer reads through a “what does the headcount picture look like and is recruiting aligned” lens. The chief executive reads through a “does this hold together as a strategic move for the year” lens. Six lenses, simultaneously, on every slide.

When the senior leader writes the deck from their own functional lens — let’s say a chief revenue officer presenting Q3 sales planning — the deck answers the chief revenue officer’s questions exhaustively and the other five functional questions partially or not at all. The chief executive, who is the senior leader’s direct sponsor, finds the deck convincing because it answers the strategic question well. The other five functional heads do not find the deck convincing because it does not answer their question well, and they each raise their question in the meeting. The senior leader, who has spent two weeks preparing, is forced to think about five new departmental angles in real time under questioning, which never goes well even for very senior presenters. The meeting moves into “alignment work” and the plan is not approved.

The structural mistake is not lack of preparation. The senior leader prepared thoroughly. The structural mistake is preparing from one lens when the room is reading through six. The fix is upstream of the deck: before drafting any slides, the senior leader sits with each of the other five functional heads (or their chiefs of staff if a one-to-one is not possible) for thirty minutes each and asks the same two questions. What is the principal question you will be reading the Q3 plan against? What would a deck that answered your question well look like on the slide that touches your function? The answers feed the deck structure. The deck then has a slide each for the six departmental lenses, written in the language each functional head uses, answering the question each functional head is reading for.

The cross-functional format that aligns six departments at once

The cross-functional Q3 planning format runs twelve slides. Slide one is the Q3 ask, in a single sentence: “We are asking the committee to approve the Q3 plan with the following six departmental commitments and three cross-functional dependencies.” Slide two is the visual map of the six departmental commitments and the three cross-functional dependencies, fitting onto a single page so the committee can see the whole shape of the plan at once. Slides three through eight are one slide per department, in a fixed rotation. Each department’s slide answers their question in their language: marketing’s slide on the campaign-and-brand commitment, technology’s slide on the platform work and engineering capacity, finance’s slide on the budget reconciliation and forecast alignment, operations’ slide on the delivery and pinch points, HR’s slide on the headcount and recruiting alignment, and the senior leader’s own function’s slide on the substantive functional commitments. The senior leader’s own function appears in rotation, not at the centre. That structural move alone is what tells the other five departments that they are being heard.

Slides nine and ten are the cross-functional dependency slides. Slide nine shows the inter-departmental dependencies as a single visual: marketing depends on technology for X; finance depends on operations for Y; HR depends on the senior leader’s function for Z. The committee can see at a glance where the cross-functional risk concentrates. Slide ten is the resolution: what each pair of departments has agreed to commit to in the next two weeks to keep the dependency on track. The pair-by-pair commitments are pre-agreed in the upstream conversations with the five functional heads, so by the time the slide appears the committee is reading commitments they themselves shaped rather than commitments the senior leader is imposing. That is the structural reason the cross-functional format aligns six departments in a single meeting rather than requiring six rounds of post-meeting alignment work.

The dependency slide that prevents the post-meeting unwinding

The dependency slide — slide nine in the cross-functional format — is the structural mechanism that prevents the post-meeting unwinding that usually follows a Q3 planning meeting. The committee approves the plan in the room. The departments go away and start scoping their own work. Within two weeks the dependencies start to surface: technology realises the platform work will take longer than marketing assumed; finance realises the budget reconciliation does not quite hold once HR’s headcount numbers come in; operations realises the delivery timeline assumes a Q3 launch readiness that conflicts with what marketing committed to. The plan, approved in the meeting, falls apart in the execution because the dependencies were not surfaced in the meeting. The senior leader gets to do the entire Q3 alignment again, three weeks late, with the chief executive starting to ask questions.

The dependency slide closes this gap by surfacing the inter-departmental dependencies in the meeting itself. The committee can see the dependencies, debate them, and resolve them in the room. The resolution slide that follows captures the pair-by-pair commitments. When the meeting ends, the dependencies are documented, the resolutions are agreed, and the committee has a single shared view of what each pair of departments needs to do to keep the plan on track. Three weeks of post-meeting alignment work get compressed into thirty minutes of committee discussion, which the room generally welcomes because the alternative is six separate post-meeting alignment cycles each functional head has to run individually. The structural framework the Executive Buy-In Masterclass teaches for stakeholder-alignment in committee work applies directly to the dependency slide.

Why the close is one cross-functional decision, not six departmental decisions

Slides eleven and twelve are the close. Slide eleven is the cross-functional decision the committee is being asked to make. Not six departmental decisions — one cross-functional decision that the committee can approve together. The framing is critical. If the close asks the committee to approve six things one at a time, the committee will negotiate the individual departmental components, which fragments the meeting and almost always results in one or two departments’ components going back for further work while the others are approved. The plan is then half-approved, and half-approval is structurally indistinguishable from deferral because the dependencies between approved and deferred components break the executability of the whole.

The single cross-functional close gives the committee a binary choice: approve the cross-functional plan in its current shape, or defer the whole plan with a clear stated reason. The committee will almost always approve in the moment if the upstream work has been done well, because the alternative — deferring the whole plan into a month of cross-functional alignment work — is unattractive to every committee member individually. The committee that would have negotiated the six departmental components piece by piece will, faced with a single cross-functional close, approve the whole package and move on. That is the structural shape of a Q3 planning meeting that runs in under an hour and produces a Q3 plan that starts on time.

Slide twelve is the implementation cadence the committee is also approving by approving the plan: weekly cross-functional check-in for the first four weeks, bi-weekly for weeks five through eight, monthly for the remainder of the quarter. The cadence is built in because the cross-functional risk is highest in the early weeks of Q3 execution, when the dependencies first start to test against reality. The committee approving the cadence at the same time as the plan signals that the executive committee, not the senior leader alone, owns the cross-functional execution. That signal carries through into the weekly cross-functional check-ins, where the functional heads attend personally rather than delegating, because they themselves committed to the cadence in the planning meeting.

Frequently asked questions

Is the upstream conversation with the other five functional heads worth two days of additional preparation?

It saves three to four weeks of post-meeting alignment work, so on a pure time-economics basis it pays back many times. The harder question is whether the senior leader feels comfortable approaching the other five functional heads in advance of presenting. The discomfort is almost always the senior leader projecting their own concern about appearing under-prepared onto the functional heads, who themselves welcome being asked. Every functional head I have spoken to about this prefers to be asked their question upstream and to have it answered well in the meeting than to have to raise it during the presentation. The upstream conversation is read as collaborative, not insecure.

Does the cross-functional format work for a smaller committee — say three departments rather than six?

Yes, and it compresses cleanly. With three departments, the twelve-slide format becomes a nine-slide format: three departmental lens slides instead of six, but the structural sequence is identical. With two departments, the same logic produces a seven-slide format. The format scales down well because the structural moves — lens-by-lens rotation, dependency slide, single cross-functional close — do not depend on having six departments. They depend on having more than one. A two-department committee that approves a plan together using this format gets the same alignment benefit as a six-department committee.

What if my chief executive insists I present from my functional lens because that is what they prefer?

The cross-functional format still works because the senior leader’s own functional lens appears as one of the six departmental slides in rotation. The chief executive who prefers a single-lens narrative gets a single-lens narrative on the senior leader’s own slide, while the other five functional heads get the slides they need. Pre-brief the chief executive on the structural shape of the deck — one lens per department in rotation, with the senior leader’s lens treated equally rather than centrally — and frame it as a tactical move to get the plan approved in the meeting rather than referred for alignment work. Most chief executives, presented with that trade-off, approve the cross-functional format.

What is the most common mistake senior leaders make with the dependency slide?

Trying to resolve every dependency in the slide itself rather than naming the dependency and the pair-by-pair commitment. The dependency slide is structurally a surface, not a resolution. It shows the committee where the cross-functional risk concentrates. The resolution slide that follows captures the commitments. The senior leader who tries to resolve every dependency on the dependency slide loses the structural separation between visibility and accountability. The committee benefits from seeing the dependencies first as a shape and then as commitments, in that order, because it lets them debate the shape before debating the commitments.

The Winning Edge — weekly newsletter

The Winning Edge is a weekly newsletter for senior professionals who present at the executive level. One short email a week on the structural moves that separate decks committees approve in the meeting from decks they defer for alignment work. Subscribe to The Winning Edge →

For the wider library of presentation assets senior leaders draw on across a planning cycle — slide system, storytelling primer, Q&A taxonomy, delivery references — the Complete Presenter bundle (£99) collects them in one place. See the broader catalogue at our services page.

About the author

Mary Beth Hazeldine is Owner & Managing Director of Winning Presentations Ltd. With 24 years of corporate banking experience at JPMorgan Chase, PwC, Royal Bank of Scotland, and Commerzbank, she advises executives across financial services, healthcare, technology, and government on structuring presentations for high-stakes funding rounds, board approvals, and strategic decisions.

The next time you build a Q3 planning presentation, do three things instead: have the upstream conversation with each of the other functional heads before drafting any slide; give each department one slide in rotation rather than presenting from your own functional lens throughout; and close with a single cross-functional decision rather than six departmental decisions the committee would have to ratify one at a time. The Q3 plan that holds together in committee is structured around the room’s six lenses, not around the senior leader’s one. The senior leader who learns this in their first multi-functional Q3 meeting saves themselves the post-meeting alignment work every subsequent quarter.