Category: Executive Presentations

In late 2003, I sat at the back of a senior investment committee at one of the global investment banks where I worked through the middle period of my banking career. The committee met in a wood-panelled room on the eleventh floor of the firm’s European headquarters, with seven approvers seated around a long table — the divisional head, the head of risk, the head of finance, the regional CFO, two business-line MDs from the franchise lines that would have to fund the proposal, and a long-tenured chief operating officer who had been at the firm since the mid-eighties and whose nodded approval most of the room watched for before committing their own. A mid-career managing director from one of the structured-products desks walked in to pitch a multi-million-pound infrastructure spend on a new pricing engine he had been building the case for over eight months. He had a 47-slide deck. His opening slide was the firm’s strategic-priorities matrix, lifted directly from the previous quarter’s board paper, with his initiative mapped against three of the four priorities in a four-quadrant grid. The COO at the end of the table, the one whose nod most of the room was waiting for, opened the printed deck, looked at slide one, closed the deck, and did not open it again. The MD spent eleven minutes walking through slides one through fourteen. At minute twelve, the divisional head — cordially, the way senior people do this — said the words I had now heard half a dozen times that year: “Thanks, this is helpful, why don’t we take it offline and come back next month with a tighter version.” The proposal never came back. Eighteen months later, the same pricing engine was bought from an external vendor at roughly four times the cost of building it in-house. The MD, by then promoted laterally to a different desk, did not pitch internally again for the rest of his time at the firm.

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

This piece walks through what I watched senior investment committees actually approve in twelve minutes — the five-question pattern senior approvers run on every proposal in the room, whether they articulate it or not, and the reason that pattern compresses the decision into a window that is much shorter than the proposers in the room ever believe. The pattern is structural, not stylistic. It does not reward the smoothest presenter or the most senior proposer. It rewards the proposer who has answered the five questions before walking into the room, on the first three slides rather than the last three, and in the vocabulary the committee uses rather than the vocabulary the strategy team uses. The article covers each of the five questions, the diagnostic that catches a weak proposal before it goes into the room, the contrast between an approved pitch and a deferred one, and the collapse pattern the five questions are specifically built to prevent.

Why the twelve-minute window is real and does not extend

The twelve-minute window is not a stylised number. It is the average elapsed time, across the committees I watched over roughly two decades, between the proposer’s first slide going up and the senior approver in the room reaching the silent verdict that determines whether the proposal goes through, gets deferred, or gets sent away with the “tighter version next month” line. The window is short for a structural reason that has nothing to do with senior people being impatient: the senior approver in the room is running a fast pattern-match against every proposal they have approved or declined in the previous three years, and the pattern-match converges quickly. They are not analysing the content in the deck. They are reading whether the proposer has done the work that approved proposers do, and the signals that work has been done are visible in the first three slides. Once the pattern-match resolves, the rest of the meeting is a confirmation exercise. The approver looks for evidence that contradicts the early verdict and, finding none, holds the verdict. The proposer, meanwhile, believes the meeting is still being decided minute by minute on the substance of the deck, and presents accordingly.

What the senior approver is pattern-matching on, in those twelve minutes, is the five-question diagnostic this article walks through. They are not asking the questions out loud. They are scanning the slides for the answers, and the answers are present or absent on the first three slides. The proposers who get the approval are the ones whose first three slides answer the five questions affirmatively; the proposers who get the deferral are the ones whose first three slides leave one or more of the questions unanswered. The strategy-matrix opener that the structured-products MD used in the 2003 committee fails three of the five questions in the first ninety seconds, which is why the COO at the end of the table closed the deck on slide one and did not reopen it. The opener that approved proposers use answers all five questions in the first three slides, which is why their committees end early and their proposals get the approval the deferred proposers were equally entitled to on the substance.

The other reason the window does not extend is the cultural dynamic of senior committees. Once the senior approver has reached the silent verdict, the social cost of reversing it inside the meeting is higher than the social cost of deferring the proposal to a later session. The deferral is the polite default. The verdict-reversal is the exception. Proposers who lose the first twelve minutes almost never recover them in minutes thirteen through forty, regardless of how strong the substantive content in slides fifteen through thirty actually is. The committee will sit through the remaining content cordially, ask a few clarifying questions to maintain decorum, and conclude with the deferral. The proposer walks out believing the meeting was inconclusive and rebuilds the deck for the following month. The committee, meanwhile, has already moved on. The board-of-directors presentation structure that earns the room’s tolerance covers the equivalent dynamic at the board level, where the window is closer to eight minutes than twelve, and the cultural cost of verdict-reversal is higher still.

Question one: is this the decision room or the discussion room

The first question the senior approver runs is whether the proposer has come to ask for a decision or to socialise the thinking that might lead to one. The committee’s time is allocated against decision items; the discussion items belong in pre-reads, working-group sessions, or one-to-ones with the relevant approver in the week before the committee. A proposer who arrives with discussion-shaped content for a decision-shaped slot has misread the room before they have opened their mouth, and the senior approver registers the misread on slide one. The signal is in the wording of the first sentence. “Today I am asking the committee to approve the build of a new pricing engine for the structured-products desk, with a capital commitment of X over Y months, decision required by end of this session” is a decision-room sentence. “Today I’d like to walk the committee through our thinking on the pricing infrastructure across the desk and explore the options the team has been considering” is a discussion-room sentence. The first sentence approved proposers get the room’s engagement; the second sentence loses it inside the opening thirty seconds.

The diagnostic for question one is whether a returning approver who has been on holiday for the previous fortnight could read slide one and immediately know what decision is being asked of them, by when. If yes, the slide is doing its work. If the returning approver would need to read through slides two through ten to find out what the meeting is actually for, the proposal has already failed question one. The most common failure mode is the conditional opener — “Today we’re bringing the committee an update on the work the team has been doing…” — a sentence that names a process rather than a decision. The fix is to write the sentence again, removing every word that signals process rather than commitment, until what is left is one sentence the returning approver could repeat back, in the corridor afterwards, to a peer who was not in the session. The discipline takes about twenty minutes per proposal and is the most-skipped step in committee preparation.

The hardest part of writing the decision-room opener, for most proposers, is the moment when the proposer’s own director or the deal-team consultant wants to soften the sentence to leave the committee “room to land it themselves”. The instinct is reasonable; the softening is fatal. Senior approvers do not want the room to land the decision themselves. They want the proposer to put the recommendation on the table, with the proposer’s own name against it, so the approvers can interrogate the recommendation rather than reconstruct it from the surrounding context. A proposer who softens the opening to leave the committee “space to decide” is signalling that the proposer is not yet sure of their own recommendation, and the committee reads the signal accurately. The soft opener is the slide proposers feel comfortable presenting; the named-decision opener is the slide the committee actually wants to receive. Write the named-decision version.

Question two: has the obvious objection been pre-empted on slide two

The second question the senior approver runs is whether the proposer has already absorbed the obvious objection or is going to make the committee voice it. Every proposal has an obvious objection — the single question the senior person in the room would ask first if the proposer stopped speaking at the end of slide one. For a build-versus-buy infrastructure proposal, the obvious objection is “why are we building this rather than buying it”. For an expansion proposal into a new segment, the obvious objection is “what evidence do we have that we can compete with the incumbent in this segment”. For a hiring-up proposal in a function, the obvious objection is “why now, given the cost run-rate the committee approved last quarter”. Slide two’s job is to name the obvious objection in the committee’s own vocabulary and answer it in two or three sentences. A proposer who pre-empts the obvious objection on slide two passes question two; a proposer who waits for the committee to raise it on the floor fails.

The discipline of slide two is the vocabulary match. Most proposers, particularly mid-career proposers walking into a senior committee for the first time, frame the obvious objection in their own functional vocabulary rather than the committee’s. The structured-products MD in the 2003 committee should have opened slide two with the question the COO at the end of the table would actually have asked first — “why are we building this in-house rather than buying it from the vendor we already use on the equities desk” — and answered it in two sentences using the operational vocabulary the COO used in his own conversations. Instead, slide two was a four-pillar framework summarising the structured-products team’s long-running views on vendor versus in-house build, framed in the team’s own vocabulary. The COO read the slide as evasion. The proposal failed question two on slide two, and the meeting was over by minute three even though the substantive walk-through continued for another nine.

What the senior approver is testing on slide two is not whether the proposer’s answer to the obvious objection is the right one. The right answer is rarely the issue. The test is whether the proposer has done the work to know what the obvious objection actually is, in the committee’s vocabulary, and is willing to put a direct answer on the table on slide two rather than burying it inside a framework on slide seven. The willingness to put the answer on the table early signals the proposer is operating from a position of having considered the objection rather than hoping to deflect it. The framework-on-slide-seven approach signals the opposite, regardless of how strong the underlying analysis is. The 3Ps framework for executive presentation coaching walks through the upstream version of this discipline in the rehearsal phase, where the obvious objection gets identified and pressure-tested before the deck is finalised.

Question three: who carries the downside if this goes wrong

The third question the senior approver runs is whether the proposer’s risk page names the proposer’s own exposure or only the committee’s. Every proposal has a downside; every committee knows it. The proposer who names the downside on the risk page, attaches a probability and an impact to each item, and then names their own personal exposure to each item — the operational consequences for the proposer’s team if the downside materialises, the proposer’s own reputational stake in the outcome — passes question three. The proposer who lists the risks at the committee level — capital at risk, brand risk, regulatory risk, in generic terms — without naming their own exposure fails question three. The signal is what the senior approver reads to determine whether the proposer is asking the committee to share an accountability the proposer already carries personally, or to take on an accountability the proposer is deflecting upward.

The reason this question matters so heavily in the senior approver’s pattern-match is that approved proposals always travel with a proposer who carries the operational accountability for the downside, and senior approvers have learned over careers to spot the proposer who is and is not carrying that accountability. The risk page is where the signal is clearest. A risk page that reads “execution risk: programme delays, mitigated by phased delivery” tells the committee nothing about who is on the hook for the phased delivery, who pays the personal cost if the phases slip, or whether the proposer has thought through the chain of consequence beyond the abstract category. A risk page that reads “execution risk: programme delivery is owned by the proposer’s direct team, with the team’s 2026 deliverables explicitly contingent on the milestones in slide eleven; a six-week slip moves four named downstream commitments into the following quarter; the proposer’s own end-of-year operating commitments are explicitly tied to the four downstream items” tells the committee everything they need to know about who carries the downside. The second version is the version that gets approved.

The discipline of question three is uncomfortable because it commits the proposer to a personal exposure most proposers would rather leave implicit. The implicit version is more pleasant to write and to present. The explicit version is the one that gets the committee’s tolerance for the upside being proposed. Senior approvers calibrate the upside-claim against the downside-exposure visible on the risk page; a proposal with a confident upside slide and a generic downside slide reads as imbalanced, and the imbalance fails question three regardless of how strong the substantive case is. The fix is to rewrite the risk page so every named risk has a named consequence and a named exposure attached, and the exposure includes the proposer’s own. Two hours per risk page is the typical investment, and it is the highest-leverage two hours in the entire deck preparation.

Question four: does the proposer know the operating reality, not just the strategic logic

The fourth question the senior approver runs is whether the proposer understands the operational consequences of the proposal in the affected function’s vocabulary, or only the strategic logic in the strategy team’s vocabulary. The contrast in 2003 was vivid. The structured-products MD’s implication slide read, in essence, “the new pricing engine will deliver tier-three improvements in pricing latency, support cross-asset functionality, and unlock revenue synergies across the franchise”. Every word in that sentence was strategy-team vocabulary. None of it was the language the operations director sitting two seats to the left of the COO would use to describe what the pricing engine would actually mean for her team’s daily run, her batch windows, her end-of-day reconciliation, or her relationship with the desk’s middle office. The operations director read the implication slide for one specific thing: did the proposer understand what this meant for her team. The slide answered no. She did not nod. The COO at the end of the table, watching her not nod, did not nod either. The proposal failed question four on the implication slide, and from that moment the approval was no longer available.

The discipline of question four is the language translation between the strategy paper and the implication slide. Most proposals arrive at the committee having been written using the strategy-team vocabulary in which the underlying analytical work was done. That vocabulary is appropriate for the analytical paper that documented the recommendation; it is the wrong vocabulary for the implication slide that goes in front of the committee. The proposer’s job, in the days before the committee, is to take the strategy-team’s reasoning and translate it sentence by sentence into the operational vocabulary the affected function actually uses. The translation conversation typically happens with a long-tenured chief of staff or operating director from the affected function, in a thirty-minute working session in the week before the committee. The translation takes about two hours per slide and is the second-most-skipped step in committee preparation after question one.

What the senior approver is testing on the implication slide is not whether they agree with the operational implications but whether the proposer has done the work to know what those implications actually are. The agreement is rarely the issue — approval committees usually convene after enough preparatory work that the broad operational direction is already understood by the senior people in the room. The respect signal is everything. The proposer who describes operational implications in the affected function’s vocabulary signals that the proposal was developed with the operational reality in mind. The proposer who reads the strategy team’s sentence aloud signals the opposite, regardless of the actual care that went into the underlying analysis. The translation work is the difference between a slide that earns the operations director’s nod and a slide that loses it, and the operations director’s nod is, in committees of this kind, the leading indicator of the senior approver’s verdict.

Question five: what is the thirty-day ask, and the counter-example I watched succeed

The fifth question the senior approver runs is what the proposer is actually asking the committee to do in the next thirty days. The signal is in the close. “I am asking the committee for approval today of the X capital envelope across Y months, with the first milestone — the architecture-review sign-off — coming back to this committee at next month’s session, and the proposer’s team starting build on the day after this committee” is a thirty-day ask. “Subject to the committee’s direction, the team is ready to begin the next phase of work and would welcome guidance on prioritisation” is not a thirty-day ask; it is a request for a decision the committee is supposed to make on the proposer’s behalf, and senior committees decline that request reliably. The thirty-day ask names what gets approved, what milestone returns, and what the proposer does the morning after. The non-ask close defers all three.

The counter-example I watched succeed, in the same committee room about eighteen months later in mid-2005, was a different mid-career managing director from a different desk — cash equities rather than structured products — pitching a similarly-sized infrastructure investment. The committee was largely the same: the same COO at the end of the table, the same divisional head, the same head of risk, the same operations director two seats over. The MD opened slide one with the named recommendation: “I am asking the committee for approval today of a six-million-pound investment over fourteen months in the cash equities low-latency trading infrastructure, with the first architectural milestone returning to this committee at the September session.” Slide two pre-empted the obvious objection: “The question this committee will ask first is why we are building rather than buying. The two vendor options have been evaluated; both fail on the latency targets the desk needs to compete in the segment; the build option meets the targets at roughly seventy percent of the three-year total cost of either vendor”. Slide three was the risk page, with the proposer’s own end-of-year commitments explicitly contingent on the four named milestones. Slide four was the operations-vocabulary implication slide, written with the operations director two seats to the left in mind — she nodded at minute six. Slide five was the thirty-day ask: approval today, build starts Monday, first milestone returns in September. The COO at the end of the table closed the deck at minute eleven, looked at the divisional head, and said “I’m comfortable”. The proposal was approved at minute thirteen. The MD spent the remaining twenty-seven minutes of the slot taking Q&A on questions the committee had already decided were no longer blockers, which is the question pattern senior committees ask after the verdict has been reached. The contrast with the 2003 session was not about the two proposers’ relative ability or seniority. It was about the structural decisions each had made on the first three slides and the work each had done on the implication page.

The Five-Question Diagnostic and the deferred-proposer counter-example

The Five-Question Diagnostic is the test to run on the first three slides of the deck before the committee runs it on you. The procedure is mechanical and unforgiving, and it is the single most useful ninety minutes a proposer can invest in the day before a senior committee. Print slides one, two, and three. Hand them to a colleague who was not in the planning — a peer from a different function, a long-tenured operating director outside the proposal’s direct workstream, the proposer’s own chief of staff if they were not the architect of the deck. Ask the colleague five questions in order. Is this the decision room or the discussion room. Has the obvious objection been pre-empted. Who carries the downside. Does the proposer know the operating reality. What is the thirty-day ask. The colleague answers each question from the three slides alone, without verbal explanation from the proposer. If all five answers are clear from the slides, the deck is doing its work. If any of the five answers come back garbled or missing, the corresponding slide is not yet right. Cut the line that drifted, rewrite the one that hedged, sharpen the one that was too generic, and run the diagnostic again. Three iterations typically takes ninety minutes and is the difference between an approval and a deferral.

The deferred-proposer counter-example worth carrying into the diagnostic comes from the 2003 committee. The structured-products MD’s first three slides, run against the five questions, failed three of them. Question one failed because the strategy-priorities matrix on slide one was a discussion-shaped opener, not a decision-shaped one — the committee could not tell from slide one what specific decision was being asked of them by when. Question two failed because slide two was a four-pillar framework on the team’s pricing philosophy rather than a direct pre-emption of the build-versus-buy objection the COO at the end of the table would inevitably ask first. Question four failed because slide three’s implication content used the structured-products team’s vocabulary rather than the operations director’s. Three failed questions on the first three slides was sufficient for the senior approver to reach the deferral verdict by minute three, and the remaining nine minutes of presentation were a confirmation exercise. Had the MD run the diagnostic on the first three slides the day before the committee — with a colleague from outside the structured-products team, and an operations director from the affected function — the failures would have surfaced in ninety minutes and the corresponding rewrites would have taken two evenings of work. The cost of the diagnostic, against the cost of an eighteen-month deferral and an external vendor purchase at four times the proposed in-house build cost, was a rounding error.

The diagnostic is mechanical specifically because human judgement — including the proposer’s own — is the wrong tool to use on the first three slides. The proposer is too close to the content to read it as the committee will read it. The diagnostic substitutes a structured five-question pass-run by a colleague for the proposer’s own pattern-matching, which inevitably tells the proposer the slides are fine. The colleague’s pattern-match against the five questions is the closest available proxy for the senior approver’s pattern-match in the committee. The proposer who runs the diagnostic walks into the committee having already passed the test the committee is about to run; the proposer who skips the diagnostic walks in to find out, in real time and at much higher cost, where the structural gaps were. The executive buy-in presentation framework covers the broader application of the diagnostic across approval scenarios beyond senior investment committees, including board-level approvals, executive-committee sign-offs, and strategic-investment review boards.

The collapse pattern: clever opener, missing risk page, generic close

The collapse pattern that the five-question diagnostic is built to prevent has five steps and plays out across the twelve-minute window in a consistent sequence regardless of the proposal’s substance. Step one: the proposer opens with a strategic-context slide or a framework matrix rather than a named recommendation, and the senior approver concludes within the first ninety seconds that the proposer has come to discuss rather than to decide. Step two: the deck arrives at the actual recommendation on slide six or seven, by which point the senior approver has tuned the substantive content out and is using the remaining minutes to decide whether the deferral language will be “come back next month” or “take it offline”. Step three: the implication content is generic — described in the proposer’s own functional vocabulary rather than the affected function’s — and the operations director or chief of staff in the room registers the failure with a non-nod that the senior approver reads. Step four: the risk page lists committee-level risks without naming the proposer’s own exposure, and the senior approver concludes the proposer is asking the committee to take on an accountability the proposer is unwilling to carry personally.

Step five is where the damage compounds, and it is the step deferred proposers most consistently miss when they walk out of the room. The committee’s closing line — “let’s take it offline, come back next month with a tighter version” — is read by the proposer as a request for a redraft and by the committee as a polite decline. The proposer rebuilds the deck for the following month, expands the analytical depth, tightens the strategic-context framework, and adds two more slides of supporting evidence. None of those changes address the five-question failures on the original first three slides, because the proposer never identified the failures. The redrafted deck fails the same five questions in the same first three slides at the following month’s committee, the deferral happens again in a different cordial wording, and after two or three cycles the proposal is quietly dropped. The proposer concludes the committee was “not ready” for the proposal. The committee concludes the proposer was not ready for the committee. Both walk away from the same data with opposite interpretations, and the structural cost shows up eighteen months later in the external vendor purchase at four times the cost.

One thing to do before the next committee

Open your deck at minute T-thirty before the next committee and read slides one, two, and three as the senior approver at the end of the table will read them. Not as the proposer who wrote them. Strip out every word that signals process rather than commitment on slide one. Find the obvious objection the COO-equivalent in your committee would ask first, and put it on slide two with the answer in two sentences. Move the risk page to slide three and rewrite it so every named risk has the proposer’s own exposure attached. If the three slides do not pass the five-question diagnostic when read by a colleague from outside the workstream, do not walk into the committee. Postpone the slot by a week. The committee will tolerate a one-week postponement with the diagnostic passed; it will not tolerate a deferral with the diagnostic failed. The proposer who postpones the slot to fix the first three slides walks in the following week with the approval available. The proposer who walks in this week with the slides unfixed walks out with the “come back next month” line, and next month does not exist for that proposal. Twelve minutes is the window. The first three slides are the work. Do the work.

Frequently asked questions

Is the twelve-minute window really fixed, or does it extend for proposals the committee finds genuinely interesting?

The window does not extend. The committee’s engagement with the content extends — an interesting proposal will hold the room’s attention for the full forty-minute slot — but the silent verdict on whether the proposal will be approved or deferred has been reached by minute twelve in almost every senior committee I observed across two decades. What changes after minute twelve is the texture of the confirmation exercise, not the verdict itself. A proposal the committee finds genuinely interesting but structurally weak on the first three slides will be deferred more politely than a proposal the committee finds neither interesting nor structurally strong; the deferral itself is unchanged. The proposers who experience the twelve-minute window as extending are the proposers who get the approval, and they are mistaking the post-verdict Q&A engagement for the pre-verdict deliberation. The deliberation is over.

If I open slide one with the named recommendation, won’t the committee feel I’m pre-empting their judgement?

The opposite reaction is the consistent one in senior committees. The named-recommendation opener signals that the proposer has done the work to know what they are recommending and is willing to put their name against it for the committee to interrogate. Senior approvers find the recommendation easier to engage with, not harder, when it is on the table from slide one; they can spend the meeting probing the recommendation rather than reconstructing it from context. The committee’s judgement is preserved because the committee can still approve, defer, or decline; what changes is the clarity of what they are deciding. The pre-emption concern is almost always voiced by the proposer’s own director or deal-team consultant rather than by senior approvers themselves, and it is, in practice, a rationalisation for the softer opener the proposer feels more comfortable presenting. The named-recommendation version reads as confidence to the room. The soft opener reads as hedging. Senior approvers reward the first and discount the second.

What is the single most common mistake proposers make on the risk page?

The most common mistake is listing risks at the committee level without naming the proposer’s own exposure. A risk page that reads “capital at risk, execution risk, reputational risk” tells the committee what categories the proposer thought of. It does not tell the committee whether the proposer has thought through the chain of consequence to their own role, their own team’s deliverables, or their own end-of-year commitments. Senior approvers calibrate the upside-claim against the visibility of the proposer’s personal exposure; an upside-confident proposal with a generic risk page reads as imbalanced and fails question three regardless of the underlying analysis. The fix is to rewrite the risk page so every named risk has a named consequence and a named personal exposure attached. Two hours per risk page is the typical investment and the highest-leverage two hours in the entire deck.

How does this pattern apply to committees outside investment banking — insurance, consulting, technology, or government?

The five-question diagnostic is sector-agnostic because the underlying cognitive pattern is human, not industry-specific. Senior approvers in insurance underwriting committees, consulting investment boards, technology capital-allocation committees, and government project-approval bodies run substantially the same five-question pattern-match against substantially the same window. What varies between sectors is the vocabulary of the obvious objection on slide two, the specific operating reality the implication slide needs to translate to, and the texture of the polite-deferral language in the close. The structural moves are identical. A proposer moving between sectors should not need to relearn the diagnostic; they need to relearn the vocabulary the new committee uses and the obvious objection the senior approver in the new committee will ask first. The framework holds, the language adapts.

The Winning Edge — weekly newsletter

The Winning Edge is a weekly (Thursday) newsletter for senior professionals who present at the executive level. One short email a week, focused on the structural moves that separate proposals senior committees approve from proposals they defer with the “come back next month” line. Subscribe to The Winning Edge →

For the broader picture across slides, storytelling, confidence, and delivery, the seven-product Complete Presenter library is the bundle most senior professionals find useful as a single resource — £99 for everything, lifetime access.

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 senior professionals across financial services, insurance, consulting, and technology on the psychology of executive buy-in, investment-committee approvals, and high-stakes proposal structure.