When pitching a long-term strategic fix, regional leaders prioritized immediate revenue goals. The product team gained traction not by dismissing these concerns, but by acknowledging their validity. This respect builds the trust necessary to balance short-term needs with long-term investment.

Related Insights

Stop trying to convince executives to adopt your priorities. Instead, identify their existing strategic initiatives—often with internal code names—and frame your solution as an accelerator for what they're already sold on doing. This dramatically reduces friction and speeds up deals.

To get buy-in for developer experience initiatives, don't use generic metrics. First, identify leadership's primary concerns—be it market share, profit margin, or velocity. Then, frame your measurements and impact using that specific language to ensure your work resonates.

To get buy-in from skeptical, business-focused stakeholders, avoid jargon about user needs. Instead, frame discovery as a method to protect the company's investment in the product team, ensuring you don't build things nobody uses and burn money. This aligns product work with financial prudence.

When driving major organizational change, a data-driven approach from the start is crucial for overcoming emotional resistance to established ways of working. Building a strong business case based on financial and market metrics can depersonalize the discussion and align stakeholders more quickly than relying on vision alone.

Securing executive buy-in is its own sales stage, distinct from champion agreement. Don't just repeat the demo for the boss. Use executive-level tactics like reference calls with their peers, exec-to-exec meetings to build relationships, or roadmap presentations to sell the long-term vision and partnership.

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.

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.

When hypergrowth causes you to fail internal stakeholders (like Operations), apologies are insufficient. Rebuild trust by going to the CEO and board *together* with the slighted team to advocate for a drastic roadmap pivot that prioritizes their needs, demonstrating true commitment to their success.

When meeting with senior leaders, shift the focus from your status updates to their priorities. Ask what's top of mind for them, what challenges they face, and how you can help. This reframes you from a direct report into a strategic ally, building trust and social capital.

Instead of developing a strategy alone and presenting it as a finished product (the 'cave' method), foster co-creation in a disarming, collaborative environment (the 'campfire'). This makes the resulting document a mechanism for alignment, ensuring stakeholders feel ownership and are motivated to implement the plan.