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.
Related Insights
When planning, differentiate the 'roadmap' from a simple to-do list. The roadmap should outline 5-7 major strategic shifts or capabilities you need to acquire—such as building a personal brand or mastering paid ads—not just the daily tasks required to get there.
A product roadmap's value is in the planning process and aligning the team on a vision, not in rigidly adhering to a delivery schedule. The co-founder of Artist argues that becoming a feature factory focused on checking boxes off a roadmap is a dangerous trap that distracts from solving real customer problems.
True business agility requires constantly syncing nested plans—tactical, operational, and strategic. It also involves managing efforts across three time horizons: the 'now, next, and beyond.' This military-inspired framework ensures immediate actions align with long-term vision amidst constant change.
Don't just tweak last year's product plan. Start from a blank slate by defining business goals first, then allocate resources to the value propositions needed to win. This avoids getting stuck in maintenance mode and forces a focus on strategic priorities.
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.
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.
LEGO's CEO has settled on a four-year strategic planning cycle as the ideal cadence. He finds three-year plans create a constant sense of urgency, while five-year plans feel too abstract. A four-year horizon is long enough to execute major initiatives but short enough to remain tangible and relevant.
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.
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.
Don't build a feature roadmap and then write OKRs to justify it. Instead, start with the outcome you want to achieve (e.g., "move metric X to Y"). This frames all features as experiments designed to hit that goal, empowering teams to kill features that don't deliver value.