We all bought into the promise of dual-track agile, right? The idea of a harmonious system where a discovery track constantly feeds a well-oiled delivery track sounds like the promised land of product development. Yet, in practice, I see many teams running a system that’s more of a dressed-up delivery treadmill.
The pressure to ship is immense. Stakeholders want to see velocity, backlogs need to be fed, and engineers need to be kept busy. The result? The ‘discovery’ track becomes a rushed, superficial exercise in validating pre-determined solutions, rather than a genuine exploration of user problems and unmet needs. We end up optimizing the ‘how’ without ever fundamentally questioning the ‘what’ or ‘why’.
This isn’t just a process problem; it’s a strategic one. It’s how we drift into becoming feature factories, burning out our teams on low-impact work and losing sight of the innovative leaps that truly create value. True discovery is messy, uncertain, and doesn’t always fit neatly into a two-week sprint. But without it, are we really building products, or just shipping code?
How does your team protect and prioritize genuine, open-ended discovery work amidst the relentless pressure to deliver features?