Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

When presenting a recommendation to executives, lead with your conclusion on the very first slide. This 'answer first' approach respects their limited time and attention. You can then use the rest of the presentation to succinctly explain how you arrived at that decision.

Related Insights

Product leaders often feel they must present a perfect, unassailable plan to executives. However, the goal should be to start a discussion. Presenting an idea as an educated guess allows for a collaborative debate where you can gather more information and adjust the strategy based on leadership's feedback.

Condense pages of research into simple visuals like a color-coded rubric summary or a hypothesis validation table. Showing raw data overwhelms stakeholders and invites unproductive questions about minor details, shifting focus from the outcome to your outputs.

Structure your problem statement as a three-part narrative to create urgency. First, anchor it to a recent "change" the company is undergoing. Then, present your solution as the logical "response." Finally, "contrast" the negative outcome of inaction with the positive outcome of your approach.

Don't script what to say on each slide; this sounds robotic. Instead, script the exact transition phrase to get from one slide to the next. This provides a safety net to regain control of the conversation if you go off-track, demonstrating poise and project leadership to executive buyers.

Instead of a traditional story structure, present the most exciting outcome first. This immediately creates either allies who want to believe or skeptics who want to challenge you. Both states are preferable to apathy, as an engaged audience is a listening one.

When presenting to a CFO, brevity is critical. They think in summaries and bullet points, and a lengthy presentation is a sign of disrespect for their time. Your entire business case should be distilled into a single, powerful page to maintain their attention.

Structure your final presentation by calling out specific problems you learned from individual contributors by name. Then, immediately pivot to show how solving their problem directly contributes to the high-level business objective owned by the executive decision-maker. This makes every stakeholder feel heard and demonstrates their strategic value.

Avoid feature-dumping. For each problem uncovered in discovery, state the problem, remind them of its negative consequence, explain how your product solves it, and then articulate what that means for their desired business outcome. This structure ensures every part of your presentation is relevant and impactful.

Executives are inherently skeptical of salespeople and product demos. To disarm them, frame the initial group meeting as a collaborative "problem discussion" rather than a solution pitch. The goal is to get the buying group to agree that a problem is worth solving *now*, before you ever present your solution. This shifts the dynamic from a sales pitch to a strategic conversation.

When communicating with executive leaders, always begin with the high-level, strategic view (the "macro") to establish context and alignment. However, you must be prepared to dive into any level of detail ("micro") they ask about. This approach respects their time while demonstrating your comprehensive understanding and credibility.

Use a 'Memento Narrative' for Executive Updates by Giving the Recommendation First | RiffOn