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.

Inspired by Apple Stores placing iPads crooked to encourage touch, consultants should present strategies with minor flaws. This invites senior teams to "straighten" the plan, creating a feeling of ownership that makes them five times more likely to embrace and execute it.

Don't pitch big ideas by going straight to the CEO for a mandate; this alienates the teams who must execute. Instead, introduce ideas casually to find a small group of collaborative "yes, and" thinkers. Build momentum with this core coalition before presenting the developed concept more broadly.

Technologists often fail to get project approval by focusing on specs and data. A successful pitch requires a "narrative algorithm" that addresses five key drivers: empathy, engagement, alignment, evidence, and impact. This framework translates technical achievements into a compelling business story for leadership.

To make platform progress compelling for executives, avoid code demos. Instead, stage a "before and after" customer scenario. Team members can role-play as a customer and an agent to vividly show how a new API improves the experience or saves time.

When a non-designer provides a polished mockup, designers often feel constrained to only refine it. Presenting intentionally rough sketches signals you're communicating an idea's intent, not a proposed execution, freeing designers to reimagine the solution and collaborate more creatively.

To persuade superiors to adopt a change, remove as much friction as possible. Don't just present an idea; deliver a fully formed plan where their only step is to approve it. Presenting a pre-written memo or a populated list makes it easy for them to say 'yes' by demonstrating you've handled the execution.

Contrary to the 'prototype is the new PRD' trend, early prototypes can prematurely focus feedback on visual details. A written document is a more effective tool for getting buy-in on the core idea and strategy from stakeholders before investing in high-fidelity design.

When a senior stakeholder proposes a potentially disruptive idea, direct resistance ('pushing') is counterproductive and strengthens their resolve. Instead, 'pull' them into a collaborative exploration. Acknowledge the idea, discuss the underlying problem it solves, and then gently steer the conversation back to how it aligns with the agreed-upon North Star, defusing tension.