Executives often see "discovery" as a slow, academic exercise. To overcome this, reframe the process as "derisking" the initiative. By referencing past projects that failed due to unvetted assumptions, you can position research not as a delay, but as a crucial step to prevent costly mistakes.
Related Insights
Before a major initiative, run a simple thought experiment: what are the best and worst possible news headlines? If the worst-case headline is indefensible from a process, intent, or PR perspective, the risk may be too high. This forces teams to confront potential negative outcomes early.
Product managers frequently receive solutions, not problems, from stakeholders. Instead of saying no, the effective approach is to reframe the solution as a set of assumptions and build a discovery backlog to systematically test them. This builds alignment and leads to better outcomes.
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.
Tailor your innovation story to your company's risk culture. For risk-averse organizations, proactively acknowledging potential problems, barriers, and what could go wrong is more persuasive. For risk-tolerant cultures like Amazon's, leading with opportunity and the potential for learning is more effective.
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 persuade risk-averse leaders to approve unconventional AI initiatives, shift the focus from the potential upside to the tangible risks of standing still. Paint a clear picture of the competitive disadvantages and missed opportunities the company will face by failing to act.
To capture an executive's attention, connect operational-level problems to their strategic business impact. A slow development cycle isn't just a process issue; explain how it directly causes delayed time-to-market, higher costs, and lost market share to competitors, which are the metrics an economic buyer truly cares about.
Instead of arguing for more time, product leaders should get stakeholder buy-in on a standardized decision-making process. The depth and rigor of each step can then be adjusted based on available time, from a two-day workshop to an eight-month study, without skipping agreed-upon stages.
Leadership often dismisses positioning as a "marketing thing." To get buy-in, connect it directly to sales failures. When prospects are confused on calls ("What are you again?") or miscategorize you, it’s a positioning problem that kills pipeline. Highlighting this revenue impact gets executive attention and resources.
The misconception that discovery slows down delivery is dangerous. Like stretching before a race prevents injury, proper, time-boxed discovery prevents building the wrong thing. This avoids costly code rewrites and iterative launches that miss the mark, ultimately speeding up the delivery of a successful product.
