Selling It Upward: The Executive Presentation
Summary
- Line up an executive sponsor before you request a slot on the leadership agenda, and ask that person to commit to specific roles: protecting the effort, helping with trade-offs, and stating leadership’s appetite for risk.
- Learn what your sponsor stands to lose if the project fails, and build the case around the market evidence that makes backing you a defensible decision.
- Write the argument as a short narrative with an FAQ of likely objections before you build any slides, and pre-wire the answers with the people who raised them.
- Show a prototype and the customer’s own words instead of describing the idea, and treat the demo as a way to show value, not to train the audience.
- Separate risk from uncertainty on one page, list your critical assumptions, and show what happens to the outcome if cost and time double.
- Propose staged funding with explicit stop criteria so that approving the next step is a small, reversible decision.
- Close with a concrete ask that names the decision, the resources, the checkpoints, and the sponsor’s ongoing role, then keep selling after the meeting ends.
Most innovation teams treat the executive presentation as a performance. They polish the slides, rehearse the opening, and hope the room says yes. That framing misses where the decision is actually made. By the time a proposal reaches a leadership meeting, someone has already chosen to carry it forward, someone has already framed what it will cost, and someone has already decided whether to put a reputation behind it. The presentation is the last step of a persuasion process, not the whole of it.
Secure the sponsor before you book the room
Innovation projects rarely become fully funded projects without a sponsor or champion, and a promising idea could be scrapped without one (Kerzner, 2023, p. 66). Early in an idea’s life, sponsors can often be found in middle management, but once a project becomes known, executive-level support may become essential because it provides legitimacy, funding, and human resources (Kerzner, 2023, p. 147). The same page carries a warning: the spotlight also puts the innovator’s career at risk (Kerzner, 2023, p. 147).
A good sponsor does more than vote yes. An executive champion acts as a protector and buffer between the corporation and the venture (Tidd & Bessant, 2014, p. 213). A senior-level sponsor, whether visible or invisible, can help secure additional funding and keep a project from being canceled when it may be on the verge of a breakthrough (Kerzner, 2023, p. 350).
When you recruit a sponsor, be specific about what you are asking. Executives should demonstrate a willingness to support trade-offs and adjustments when necessary, and make clear to innovation teams that they are willing to cancel projects when certain criteria are not met (Kerzner, 2023, p. 143). Turn those expectations into an explicit request. Ask the sponsor to tell your team, early, how much risk leadership will tolerate and what would cause it to stop the work. A sponsor who has said those things out loud is far easier to defend in a room full of skeptics, and far less likely to be surprised by a hard question.
Know what your sponsor risks
Sponsors are not neutral. Managers’ careers often get a boost when they sponsor very successful projects, and those careers can be permanently derailed when they back projects that fail (Christensen, 2000, p. 152). The kind of failure matters. Projects that fail because the market was not there carry far more serious career implications than projects that fail because the technologists could not deliver (Christensen, 2000, p. 152).
The consequence is predictable. Middle managers tend to back the projects for which market demand seems most assured, and they package those proposals to win senior management approval (Christensen, 2000, p. 152). Many of the critical resource allocation decisions are therefore made long before senior management gets involved, when middle managers decide which projects to carry forward (Christensen, 2000, p. 153).
If you are presenting to executives, you are probably presenting a proposal that someone has already screened for defensibility.
Your audience also defines success differently than you do. The executive perspective emphasizes a revenue-generating, commercialized product and balancing cost against competition for funding from other projects, while project teams may prize outcomes that exceed expectations or bring recognition from peers (Kerzner, 2023, p. 180). In a boardroom, the problem compounds. Because board and governance members come from diverse backgrounds, each may see the project differently, which can produce multiple and shifting definitions of success (Kerzner, 2023, p. 66).
Design the presentation around the question your sponsor will be asked after you leave the room: why was this a reasonable thing to back?
Build the case as a narrative, then cut it to a presentation
The strongest preparation for an executive meeting happens before anyone opens a slide editor. A persuasive narrative of roughly six pages describes the problem, why solving it is valuable to customers and the business, and the strategy for solving it, and it is different from a spec (Cagan & Jones, 2021, p. 90). Without that homework, a kickoff presentation can degenerate into design by committee or into deference to the highest-paid person in the room (Cagan & Jones, 2021, p. 91).
Follow the narrative with an FAQ. Writing one forces the author to anticipate concerns and objections from key executives and stakeholders and to write clear answers to them (Cagan & Jones, 2021, p. 91). Then take the step most teams skip. Reviewing those answers with the people would likely raise the concerns shows the executive that the issues were anticipated and the homework was done (Cagan & Jones, 2021, p. 92). Iterate as necessary. By the time the meeting starts, the hardest objections have already been heard and answered.
Once the narrative is solid, the deck nearly writes itself. A presentation built after the narrative flows directly from it (Cagan & Jones, 2021, p. 92). Keep it short. Business plans should not exceed 25 pages and should carry a clear summary, and presentations of them should be short; the elevator pitch test is whether the plan can be explained to a senior manager in the time of an elevator ride (van den Ende, 2021, p. 143).
Treat the business case as a story with enough detail about what the team is trying to achieve, how, for whom, when, and at what cost and reward (Bessant & Tidd, 2015, p. 465).
Each retelling of that story is refined by questions and feedback from the audience (Bessant & Tidd, 2015, p. 465), so every sponsor conversation is a rehearsal.
Finally, connect the story to strategy explicitly.
Senior management often delegates identifying innovation projects but keeps the authority to approve them, and may approve projects without careful consideration of strategic alignment (Kerzner, 2023, p. 135). Do that consideration for them, on a slide, in the language of their priorities. For sponsors and executives, communication works best when it is simple, visual, and focused on outcomes, with no jargon and clear connections between the team’s work and its business meaning (Runtasewee & González Sánchez, 2026, p. 86).
Show it instead of describing it
Executives are asked to imagine things all day.
The fastest way to stand out is to make imagining unnecessary. A realistic, high-fidelity prototype is probably the single most effective technique for persuading an audience of a product idea (Cagan & Jones, 2021, p. 372). If your team has been through a prototyping stage, the prototype is the centerpiece of the meeting, not an appendix.
Pair it with the customer’s voice. Showing customer pain through quotes or video, and bringing executives to user testing, lets decision makers hear the customer’s own words (Cagan & Jones, 2021, p. 372).
An executive who has watched a customer struggle with the current process will not need to be convinced that the problem exists.
That frees your limited time for the part that does need persuasion: why your approach is the right response. Be candid, too, about what the team has learned. Sharing learnings should include the problems as well as the successes, so the audience has what it needs to help find solutions (Cagan & Jones, 2021, p. 373).
Treat the demo with the same intent. A demo for executives is not training and not a test; it is a form of sales aimed at showing value (Cagan & Jones, 2021, p. 373). Do not walk through every screen or hand over the controls.
Show the single path that makes the value obvious, then stop talking and let the room react.
Communicate uncertainty without losing the room
Leaders are used to hearing confident forecasts, and innovation cannot supply them. The honest alternative is not vagueness; it is structure. Start by distinguishing the two things people lump together. Risk can usually be estimated qualitatively or with probabilities, whereas uncertainty is unknowable, yet its fields and degree should still be identified (Tidd & Bessant, 2018, p. 530). Traditional approaches to assessing risk focus on the probability of foreseeable risks rather than true uncertainty (Tidd & Bessant, 2018, p. 530).
A one-page view that lists estimable risks next to the areas of genuine uncertainty tells executives where numbers can be trusted and where judgment is required.
Context also helps. Research indicates that 30 to 45 percent of projects fail to be completed, and over half overrun budgets or schedules by up to 200 percent (Tidd & Bessant, 2018, p. 531). R&D managers tend to be fairly confident predicting technical issues such as development time and cost, but far fewer are confident forecasting commercial aspects (Tidd & Bessant, 2018, p. 531). In one study of project selection, a technical success probability of 0.80 combined with a commercial success probability of 0.20 gave a combined probability of 0.16 (Tidd & Bessant, 2018, p. 532). Sharing numbers like these signals that you understand the base rates and are not asking leadership to suspend disbelief.
Surface risks early, and bring options with them.
Doing so keeps executives from being blindsided when something does not go as planned (Runtasewee & González Sánchez, 2026, p. 86). For initiatives with probabilistic results, reframing the discussion around scenarios, trade-offs, and experimentation instead of the binary of success or failure helps executives become comfortable with uncertainty (Runtasewee & González Sánchez, 2026, p. 86). Be equally careful with prototypes. A pilot may look impressive while scaling it exposes integration challenges, ethical dilemmas, or hidden costs, so executives need to understand the difference between a proof of concept and a production deployment (Runtasewee & González Sánchez, 2026, p. 86).
Assumptions deserve their own slide.
All innovation assumptions should be documented at project initiation (Kerzner, 2023, p. 203). Critical assumptions are those that can cause significant damage to a project if even small changes take place, and they must be tracked closely (Kerzner, 2023, p. 203). Explicit assumptions often contain hidden implicit assumptions, and serious consequences can follow if those prove false (Kerzner, 2023, p. 203). Then stress the plan. Sensitivity analysis can show whether the outcome holds up under different assumptions, for example by asking what happens if the project costs twice as much and takes twice as long (Tidd & Bessant, 2018, p. 552). Varying input parameters by about 10 percent shows which ones matter most to the financial result and deserve the most attention (van den Ende, 2021, p. 143). Because financial projections are always quite uncertain, management is better off not focusing on financial aspects alone (van den Ende, 2021, p. 143).
Ask for a staged commitment
The most useful thing you can do for a nervous executive is shrink the decision. Criteria for stopping the project or program should be made explicit from the outset (Tidd & Bessant, 2018, p. 552). Key technical and market uncertainties should be reduced before any irreversible, costly commitment to full-scale commercialization (Tidd & Bessant, 2018, p. 552). Together these ideas turn a leap of faith into a sequence of checkpoints, each with a defined way out.
Small bets work for a reason that is as much psychological as financial.
Small bets with clear definitions of success and failure gates can help a finance leader overcome the fear of unknowns, since a single big check can feel like a scary bet (Benraouane & Harrington, 2021, p. 150). When the next tranche is modest and the exit criteria are written down, approving it is an easy decision to defend.
Expect the gate conversation to be different from the one in a conventional project. Innovation gate decisions differ from traditional ones: cancellation is highly likely, major budget changes are possible, and risk assessment is almost always required (Kerzner, 2023, p. 202). Leadership also has a part to play. Management must be willing to cancel projects when criteria are not met, and the culture must be failure-tolerant instead of punishing people for accepting risk and uncertainty (Kerzner, 2023, p. 143). Asking your sponsor to restate that commitment in front of the group gives the team protection and gives the executives a clear sense of what they are signing up for.
What separates winning proposals from losing ones
Consider how two ideas fare when a manager asks the same questions of each. Projects aimed at the explicit needs of current customers, or at users the company has not yet been able to reach, tend to win the contest for development resources over proposals for markets that do not yet exist (Christensen, 2000, p. 154). In one illustrative exchange, the proposal that won favor had named customers asking for prototypes, a segment buying over $600 million a year, and an expected margin near 35 percent (Christensen, 2000, p. 153). The competing proposal, by contrast, answered questions about who would buy it, and whether the company could make money, with uncertainty (Christensen, 2000, p. 154).
The lesson is not that bold ideas lose and safe ones win. Resource allocation systems are designed precisely to weed out ideas unlikely to find large, profitable, receptive markets (Christensen, 2000, p. 154).
The lesson is that a proposal succeeds by answering the screening questions with evidence. If your idea targets a market that does not yet exist, the prototype, the customer conversations, and the staged plan carry more weight than they would for an incremental idea, because they replace the market data you cannot yet produce.
Credibility matters as much as content. Teams, executives, and stakeholders are more likely to follow a presenter they believe knows the users, the data, the business, and the market (Cagan & Jones, 2021, p. 373). Without deep knowledge of customers, there will be no trust with key executives (Cagan & Jones, 2021, p. 363). Sharing credit generously, and stepping forward to take responsibility when things go badly, earns respect (Cagan & Jones, 2021, p. 373).
Close with a concrete ask and keep selling
End the meeting with a request that can be answered yes or no. Name the decision, the resources, the next checkpoint, and the conditions under which the work stops. A specific ask also protects your sponsor, who can repeat it to colleagues without improvising.
Then keep going. Evangelism never really stops; when it does, executives get cold feet (Cagan & Jones, 2021, p. 373). Approval is the start of a relationship, not the end of a pitch. One case offers a model of the rhythm: project managers held calls with users twice a week, with management monthly, and with the executive sponsor weekly (Kerzner, 2023, p. 398). A sponsor who hears from the team every week has fresh evidence to use when someone questions the project, and the team hears about trouble early enough to respond.
The executive presentation is where the decision is recorded, but the work that earns the decision happens before and after it. Recruit the sponsor early, understand what that person risks, put the argument in writing, let the prototype speak, be honest about uncertainty, and ask for one step at a time. Proposals prepared this way do not need to be sold hard in the room, because most of the selling has already been done.
Bibliography
Benraouane, S. A., & Harrington, H. J. (2021). Using the ISO 56002 innovation management system: A practical guide for implementation and building a culture of innovation. Routledge.
Bessant, J., & Tidd, J. (2015). Innovation and entrepreneurship (3rd ed.). Wiley.
Cagan, M., & Jones, C. (2021). Empowered: Ordinary people, extraordinary products. Wiley. (Page numbers refer to PDF pages.)
Christensen, C. M. (2000). The innovator’s dilemma: When new technologies cause great firms to fail. Harvard Business Review Press. (Page numbers refer to PDF pages.)
Kerzner, H. (2023). Innovation project management: Methods, case studies, and tools for managing innovation projects (2nd ed.). Wiley.
Runtasewee, M. J., & González Sánchez, A. (2026). Managing AI projects: Drive innovation and successfully navigate the full AI project lifecycle. O’Reilly Media.
Tidd, J., & Bessant, J. (2014). Strategic innovation management. Wiley.
Tidd, J., & Bessant, J. (2018). Managing innovation: Integrating technological, market and organizational change (6th ed.). Wiley.
van den Ende, J. (2021). Innovation management. Red Globe Press.