To balance immediate user needs with long-term R&D, Eleven Labs uses a "3-month rule." If a foundational research solution is projected to take more than three months, the product team is empowered to ship a simpler, faster, tactical solution in the interim.
In early stages, the key to an effective product roadmap is ruthlessly prioritizing based on the severity of customer pain. A feature is only worth building if it solves an acute, costly problem. If customers aren't in enough pain to spend money and time, the idea is irrelevant for near-term revenue generation.
In AI, low prototyping costs and customer uncertainty make the traditional research-first PM model obsolete. The new approach is to build a prototype quickly, show it to customers to discover possibilities, and then iterate based on their reactions, effectively building the solution before the problem is fully defined.
While research is vital, there's a point of diminishing returns. Over-researching can lead to 'analysis paralysis' by revealing too many edge cases and divergent needs, ultimately stalling the momentum required to build and launch a new product.
In a rapidly evolving field like AI, long-term planning is futile as "what you knew three months ago isn't true right now." Maintain agility by focusing on short-term, customer-driven milestones and avoid roadmaps that extend beyond a single quarter.
To avoid choosing between deep research and product development, ElevenLabs organizes teams into problem-focused "labs." Each lab, a mix of researchers, engineers, and operators, tackles a specific problem (e.g., voice or agents), sequencing deep research first before building a product layer on top. This structure allows for both foundational breakthroughs and market-facing execution.
To manage innovation and stability simultaneously, the company designates teams based on product maturity. 'Pre-PMF' teams have a six-month mandate to ship rapidly to find a market or be cut. 'Post-PMF' teams focus on long-term reliability and testing, creating distinct operational speeds within the organization.
When pursuing a long-term strategic solution, dedicate product management time to high-level discovery and partner alignment first. This doesn't consume engineering resources, allowing the dev team to remain focused on mitigating the immediate, more visceral aspects of the problem.
To truly learn from go-to-market experiments, you can't be half-hearted. StackAI's philosophy is to dedicate significant, focused effort for 1-3 months on a single idea. This ensures that if it fails, you know it's the idea, not poor execution, providing a definitive learning.
To bridge the gap between a product's long-term vision and its current state, focus on "progress, not perfection." Deliver a quick, meaningful win for the customer—like a single workflow or integration—to build the trust and momentum needed for them to stay invested in the unfolding roadmap.
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.