Quick Answer: Most approvals are decided before the formal presentation begins. A stakeholder alignment session β a structured pre-meeting with key decision-makers β lets you surface objections privately, refine your narrative based on what you hear, and arrive in the room with commitments already secured. The formal presentation then becomes a ratification exercise rather than a persuasion exercise. This approach works for board approvals, finance committee requests, and any high-stakes executive decision.
Astrid had thirty minutes in front of the investment committee. She had rehearsed the deck twenty times. Her financial model was solid, her slides were clear, and her executive sponsor believed in the project. When the committee chair asked a single question β “What does the operations director think about the implementation timeline?” β the presentation stalled.
The operations director hadn’t been consulted. He sat in the room, visibly uncomfortable. The committee read the room, delayed the decision, and asked for a revised proposal that incorporated operational input.
Three weeks later, Astrid submitted the same project with one structural difference: she had spent the preceding fortnight meeting individually with every committee member and the operations director. By the time she walked into the formal presentation, every objection had already been heard, addressed, and in most cases resolved. The formal presentation took nineteen minutes. The approval was unanimous.
If you’re preparing for a high-stakes approval
The Executive Slide System includes scenario playbooks and slide templates for executive approval presentations β including the alignment and pre-meeting frameworks that help you structure what you learn before the formal session.
Why the Decision Is Made Before You Present
Senior decision-makers rarely change their minds in a committee room. By the time the formal meeting convenes, most members have already formed a view β based on conversations in corridors, emails exchanged with colleagues, and assumptions built from prior context. The formal presentation is where those views are tested, not formed.
This is not cynicism about the process. It reflects how experienced executives make high-stakes decisions: they gather information in advance, test their instincts with trusted colleagues, and arrive in the meeting with a working hypothesis. Your presentation either confirms or challenges that hypothesis. If you’ve done no work to shape it in advance, you’re working against a position that was set before you entered the room.
The most effective executives understand this dynamic and work with it rather than against it. They treat the formal presentation as the final step in a longer engagement process, not the first and only opportunity to make their case.
The pre-presentation alignment session is the mechanism that makes this possible. It is not manipulation β it is thorough preparation. Every concern that surfaces in a private conversation is one that won’t derail the formal meeting. Every commitment secured informally is one that reinforces the approval in the room. And every stakeholder who feels heard in advance is one who arrives in the meeting inclined to support rather than question.
Executive Slide System
Structure Your Approval Presentation to Match the Work Done Before the Room
The Executive Slide System β Β£39, instant access β gives you slide templates for board, finance committee, and investment committee presentations, plus scenario playbooks for navigating stakeholder alignment before high-stakes approvals. Designed for executives who want to arrive in the formal meeting with the decision already moving in their direction.
- Slide templates for approval and board presentations across executive scenarios
- AI prompt cards to map stakeholder concerns before the alignment session
- Framework guides for structuring the narrative around what you hear pre-meeting
- Scenario playbooks for investment committee, board, and finance committee contexts
Get the Executive Slide System β
Designed for high-stakes approval presentations where preparation matters more than performance.

Who to Meet and What to Ask Them
Not every stakeholder needs a dedicated pre-meeting. The goal is to meet the people whose support is essential and whose concerns, if left unaddressed, could derail the formal presentation. For most approval presentations, that list is shorter than it appears.
Start with the decision-makers β the people who will vote, recommend, or formally approve. Understand their current view on the topic before you attempt to inform it. Have they been involved in similar decisions before? Do they have a prior position on this type of investment or initiative? Is there a competing proposal that complicates their thinking?
Next, identify the influencers β the people whose opinion the decision-makers trust. In a finance committee context, this is often the CFO’s direct advisers or the head of internal audit. In a board context, it may be the senior independent director or a non-executive with a strong view on capital allocation. These people may not have a vote, but their informal influence on the final outcome can be decisive.
Finally, identify the potential blockers β the people whose opposition, if expressed in the formal meeting, could damage the proposal even if they are in the minority. Understanding a blocker’s concern before the meeting gives you the opportunity to address it privately, which is almost always more productive than managing it in public.
In each pre-meeting, ask three questions. What do they already know about the proposal? What concerns do they have about it? And what would they need to see to be comfortable supporting it? These questions are not a sales pitch β they are information-gathering. The goal is to understand, not to convince. Convincing comes later, in how you update the presentation.
For the framework behind pre-decision conversations, see The Pre-Decision Conversation: How Executives Secure Approval Before the Meeting.
Running the Alignment Session Effectively
An alignment session is a conversation, not a presentation. Executives who use the pre-meeting to walk through their slides β treating it as a rehearsal β miss the point. The slide deck is not what you bring to this meeting. What you bring is curiosity and good questions.
Keep the meeting short: thirty minutes is usually sufficient. Open by explaining your purpose directly β you are seeking input before the formal session to ensure the presentation addresses the right questions. Most decision-makers respect this directness. It signals that you are thorough, not that you are uncertain.
Listen more than you speak. When a concern surfaces, resist the instinct to immediately counter it. Instead, explore it: “That’s useful to know β can you say more about what’s driving that concern?” Understanding the root of an objection is more valuable than overcoming its surface expression. An objection that sounds financial may actually be about trust. An objection about timing may actually be about resource competition.
Take notes, and be transparent about doing so. “I want to make sure I capture this accurately before I revise the presentation” signals that the conversation will have a real impact on what the committee sees. This is important: if decision-makers sense that the pre-meeting is performative rather than genuinely informative, they stop sharing real concerns.
Close each session by confirming what you’ve heard and what changes you plan to make. “Based on what you’ve shared, I’ll strengthen the implementation timeline and add more detail on the alternatives we considered. Does that address the main concerns you raised?” This gives the stakeholder the opportunity to confirm or correct your understanding before you do the work.
If you’re rebuilding a formal approval presentation around what you’ve heard in pre-meeting conversations, the Executive Slide System includes slide templates and AI prompt cards designed to help you translate stakeholder concerns into a presentation narrative that addresses them structurally, not just rhetorically.

What to Do With What You Hear
The alignment session has value only if it changes something. If you leave every pre-meeting with the same deck and the same narrative, you’ve gathered information that you didn’t act on β which is worse than not gathering it, because it signals to stakeholders that the consultation was cosmetic.
After each pre-meeting, categorise what you’ve heard. Some concerns will be addressed by adding or clarifying information β a new slide, an updated data source, a clearer explanation of a financial assumption. These are structural changes, and they make the presentation more complete. Make them before the formal session.
Other concerns will reflect a disagreement about the underlying business case β a stakeholder who genuinely believes the investment is premature, or that a different approach should be considered. These cannot be resolved with a slide change. They require a direct conversation about the merits, and in some cases, the involvement of a more senior sponsor to navigate the impasse. Identify these early, because they need more time than a slide revision.
Some concerns will be about perception rather than substance β a stakeholder who hasn’t been involved in previous discussions and feels left out, or one who is concerned about credit and visibility when the project succeeds. These are relationship issues, and they are resolved through the pre-meeting process itself: the act of consulting them is the resolution. Make sure they know their input shaped the final presentation.
Keep a simple log of what you heard, what you changed, and what remains unresolved. This is useful for two reasons. It ensures that nothing gets lost between conversations. And if the decision is contested in the formal meeting, your log gives you the basis to say with confidence: “I discussed this with [stakeholder] two weeks ago, and here is how I addressed that concern in the revised presentation.” For related thinking on managing structural change presentations, see Restructuring Presentation: Rebuilding Trust Through Transparent Communication.
Aligning Across Competing Interests
The most challenging stakeholder alignment situations are those where key decision-makers have competing interests β where what one stakeholder needs to hear directly contradicts what another needs to hear. A proposal that involves resource reallocation is a classic example: the function gaining resources welcomes it, while the function losing resources opposes it.
The response here is not to tell different stakeholders different things β that collapses the moment the formal meeting convenes. The response is to find the common ground between competing interests and build the presentation narrative around it.
What both stakeholders share, despite competing interests, is typically a concern about the broader organisational outcome. The function losing resources still cares about the company’s performance. The disagreement is about means, not ends. A presentation that frames the proposal in terms of the shared goal β rather than the redistribution of resources β gives both stakeholders something they can support.
Where interests are genuinely irreconcilable, the alignment session’s value is in surfacing the conflict before the formal meeting rather than discovering it in public. A committee where two factions are in open disagreement is difficult to present to. A committee where the chair knows the disagreement exists and has managed it in advance is a different environment. Use the pre-meeting process to give the chair the information they need to manage the room, as well as to manage your own presentation.
Using the Formal Presentation to Confirm, Not Persuade
When the alignment process has been done well, the formal presentation shifts in character. It becomes a confirmation exercise β a structured walk through the proposal that gives the committee confidence that everything has been considered, rather than a persuasion exercise where the outcome is uncertain.
This changes the tone and the pacing. A confirmation presentation can afford to be shorter, because most of the information has already been shared in pre-meetings. It can acknowledge concerns explicitly β “I know some of you have raised questions about the implementation timeline, so I’ve added a new slide that addresses this directly” β because the concerns are already known. And it can invite a more collaborative discussion, because the presenter isn’t guarding against ambushes.
The questions that arise in a confirmation presentation are also different in character. They tend to be sharper and more specific β looking for the final detail that will complete the picture β rather than broad and exploratory. This is a good sign. It means the committee is doing the final check before committing, not starting the analysis from scratch.
The goal is to make the formal presentation feel inevitable in the best sense: the logical outcome of a rigorous process rather than a surprise outcome from a single event. For guidance on how executive presence supports this dynamic in the room, see Executive Presence in Presentations: The Quality That Closes the Room.
Need the Templates, Not Another Framework?
Slide Templates for Executives Who Present to Senior Decision-Makers
The Executive Slide System β Β£39, instant access β includes ready-to-use templates for board, finance committee, and investment approval presentations, plus AI prompt cards to structure your narrative around what stakeholders actually need to hear.
Frequently Asked Questions
How many pre-meetings is too many before a formal presentation?
There is no fixed upper limit, but the quality of pre-meetings matters more than the number. Five shallow conversations that don’t surface real concerns are less valuable than two deep ones that reveal the actual objections. As a working guide, prioritise the three to five people whose support is essential and whose concerns are most likely to surface in the formal meeting. Beyond that core group, judge based on the political complexity of the specific approval and the time available.
What if a key stakeholder refuses to meet before the formal session?
A refusal to meet is itself useful information. It may signal opposition, disengagement, or a prior commitment to a competing proposal. If a critical decision-maker declines a pre-meeting, work through your executive sponsor to understand their position and whether there is a backstory that you need to account for. It may also be worth adjusting the formal presentation to explicitly invite that stakeholder’s input β framing their engagement as essential to the process rather than assuming their alignment.
Is it appropriate to share draft slides in a pre-meeting?
In most cases, no. Sharing draft slides in a pre-meeting shifts the conversation from concerns to critique β stakeholders start commenting on slide design rather than sharing their underlying concerns about the proposal. The exception is when a specific stakeholder is a subject-matter expert whose input on a particular section of the deck would meaningfully improve it. In that case, share only the relevant section and frame it as a request for input rather than a preview of the full presentation.
The Winning Edge β Free Weekly Newsletter
Practical frameworks for executives who present to boards, finance committees, and senior leadership. Every Thursday.
Not ready for the full system? Start here instead: download the free Executive Presentation Checklist β a one-page reference covering the structural elements decision-makers look for in board and approval presentations.
About the Author
Mary Beth Hazeldine is Owner & Managing Director of Winning Presentations. With 25 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 and approvals.

















