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.

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.

Don't just ask executives what they want to achieve, as this puts them on the spot. Instead, proactively formulate a hypothesis about their goals and challenges. Presenting this gives them a concrete starting point to react to, confirm, or correct, leading to much faster alignment.

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.

Instead of criticizing the current system, frame a data transformation project as a way to eliminate critical blind spots. Present leadership with specific, unanswerable questions that the new model can solve, linking visibility to tangible outcomes like higher performance and lower acquisition costs.

Operations professionals stuck in a cycle of data cleaning cannot simply state that the system is broken. To secure necessary resources like time, budget, or an executive champion, they must quantify the problem's impact on the business. Data-backed arguments are the only way to get leadership to prioritize operational improvements.

Don't be afraid to surface problems to executives, as their job is almost entirely focused on what's not working. Withholding a problem is unhelpful; clarifying and framing it is incredibly valuable. Your champion isn't offending their boss by raising an issue, they're demonstrating strategic awareness.

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.