Let’s talk about the roadmap. For years, we’ve debated the merits of the traditional, timeline-based feature roadmap versus more dynamic, outcome-focused plans. Yet, many of us are still asked to produce that Gantt chart showing features delivered by specific dates for the next 12 months.
This old model feels increasingly broken. It chains teams to outputs, not outcomes, and stifles the very agility we claim to practice. When leadership treats the roadmap as a promise instead of a strategic guide, it turns the product team into a feature factory. The focus shifts from solving real user problems to just shipping what’s on the list, on time, regardless of impact.
The alternative—focusing on clear outcomes (the ‘why’) and empowering teams to discover the best ‘what’ and ‘how’—is where real innovation happens. It allows for learning, iteration, and pivoting based on what you discover from user research and market feedback. It’s about being responsive, not just busy. While this isn’t a new concept, the pressure to adopt it feels more intense than ever.
How are you navigating this in your organization? Are you successfully shifting the conversation from outputs to outcomes with your leadership?