I’ve seen a lot of chatter lately about the tension between ‘Continuous Discovery’ and traditional roadmapping. We’re all taught to live in the problem space and constantly iterate based on user feedback. But we also have stakeholders, sales teams, and engineers who need—and deserve—a clear vision of where we’re heading in the next 2-4 quarters.
The classic roadmap provides that stability and direction. Continuous discovery, championed by folks like Teresa Torres, provides the agility and user-centricity needed to build something people actually want. When you’re deep in discovery, the roadmap can feel like a rigid, outdated anchor. But without a roadmap, the team can feel like they’re just chasing the latest customer request with no coherent strategy.
This isn’t just a theoretical debate; it’s about the very real challenge of balancing long-term strategic alignment with short-term, evidence-based iteration. Trying to do both can feel like you’re doing neither well. It’s a classic PM balancing act, but the friction seems more palpable than ever as discovery practices become more mainstream.
How are you balancing the strategic predictability of a roadmap with the flexible, learning-based approach of continuous discovery in your organization?