To avoid post-launch stalls, operate two parallel tracks. The 'delivery track' executes the current roadmap, while a separate 'discovery track' simultaneously researches and plans for the next 18-24 months. This ensures a continuous flow of validated ideas into the pipeline.
Related Insights
After launching, Figma structured its product development into two parallel workstreams. The "blockers" stream focused on removing known issues preventing user adoption, while the "differentiators" stream focused on building unique, strategic features like design systems to evolve the product and win the market.
In the fast-moving AI space, rigid long-term planning is futile. Lovable uses a flexible six-month product roadmap, while ElevenLabs uses quarterly initiatives for alignment but gives its foundational research teams total freedom from timelines to foster innovation.
A dual-track launch strategy is most effective. Ship small, useful improvements on a weekly cadence to demonstrate momentum and reliability. For major, innovative features that represent a step-change, consolidate them into a single, high-impact 'noisy' launch to capture maximum attention.
Avoid overly detailed, multi-year roadmaps. Instead, define broad strategic 'horizons.' The shift from one horizon to the next isn't time-based but is triggered by achieving specific metrics like ARR or customer count. This allows for an agile response to market opportunities while maintaining strategic focus.
To avoid decline, managers of mature 'cash cow' products must operate on two tracks. They should rapidly test solution-based iterations to optimize the existing product, while simultaneously dedicating resources to high-level problem discovery to identify the company's next source of growth.
In the fast-moving AI sector, quarterly planning is obsolete. Leaders should adopt a weekly reassessment cadence and define "boundaries for experimentation" rather than rigid goals. This fosters unexpected discoveries that are essential for staying ahead of competitors who can leapfrog you in weeks.
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.
A product leader should actively manage development by allocating effort into three buckets: future big bets, core foundation (stability/tech debt), and growth/optimization. The resource allocation isn't fixed; it must dynamically shift based on the product's maturity and immediate business goals.
For net-new products, begin with deep problem discovery. Once a product is introduced, shift to rapid, solution-based iteration and feedback. As the product matures, revert back to problem discovery to find the next growth engine while optimizing the current product.
To prevent rigid plans that break, maintain consistency in your high-level strategic pillars for the year. However, build in flexibility by allowing the specific tactics used to achieve those pillars to change quarterly based on performance and new learnings.
