Roadmaps & Planning

OKRs can be a powerful tool, but they don't automatically fix underlying cultural issues in your organization. Instead, they tend to amplify and expose the existing culture, whether good or bad. Focus on making your OKRs clear, actionable, and authentically reflective of your day-to-day work to get the most benefit.

Your product strategy and roadmap are two distinct things. Strategy is about defining the coherent actions you'll take to address your key challenges, while a roadmap is a timeline and plan for executing those actions. Focus first on clarifying your strategy, then build a roadmap to bring that strategy to life through specific initiatives and releases.

Traditional roadmapping often relies on predictable technology and market trends. But AI is rapidly evolving, with new capabilities emerging every few months. Instead of rigid plans, focus on staying agile and empirical. Quickly test ideas, learn from what works, and be ready to pivot priorities as the landscape changes.

While planning ahead is important, trying to create a rigid, long-term roadmap can be misleading. Embrace the uncertainty of the future and avoid false precision. Focus on learning quickly, adapting based on new information, and remaining flexible to navigate the unpredictable path ahead.

Roadmaps are important for planning, but they shouldn't be treated as set-in-stone plans. The real value lies in the planning process - using a roadmap to examine your assumptions, get alignment, and adapt as you learn. Focus on the flexibility and iterative nature of roadmapping, not just the final output.