When leaders demand high-fidelity prototypes too early, don't react defensively. Instead, frame your pushback around resource allocation and preventing waste. Use phrases like "I want to make sure I'm investing my energy appropriately" to align with leadership goals and steer the conversation back to core concepts.
Related Insights
Saying 'no' to product ideas is often contentious. At GitHub, the process is simplified by first 'seeking the truth'—rigorously assessing if an initiative aligns with the team's definition of success. If it doesn't, the 'no' becomes an objective, logical conclusion rather than a subjective or political decision.
CEO Dylan Field combats organizational slowness by interrogating project timelines. He seeks to understand the underlying assumptions and separate actual work from "well-intentionally added" padding. This forces teams to reason from first principles and justify the true time required, preventing unnecessary delays.
When a prospect asks for a free pilot, treat it as a sign that you failed to build enough confidence in the outcome. Instead of agreeing, diagnose their uncertainty by asking what they still need help predicting. This shifts the conversation back to value and avoids deploying your best resources on your least committed customers.
Not all design impact can be quantified with metrics. When data is unavailable, frame your value by highlighting contributions to competitive parity, internal team efficiency, or bug reduction. This holistic view of business health resonates with leadership beyond just product managers.
To avoid stakeholders undermining research results later ('you only talked to 38 people'), proactively collaborate with them before the study to define the minimum standard of rigor they will accept. This alignment shifts the conversation from a post-mortem critique to a pre-launch agreement, disarming future objections.
Product teams often fear showing prototypes because strong customer demand creates pressure. This mindset is flawed. Having customers eager to buy an unbuilt feature is a high-quality signal that validates your roadmap and is the best problem a product manager can have.
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.
To get product management buy-in for technical initiatives like refactoring or scaling, engineering leadership is responsible for translating the work into clear business or customer value. Instead of just stating the technical need, explain how it enables faster feature development or access to a larger customer base.
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.
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.
