We all champion the need for continuous discovery. We read the books, attend the webinars, and nod along in meetings. But when the pressure is on, the delivery roadmap almost always wins. Stakeholders want dates, the backlog is overflowing, and the engineering team is measured on velocity. Suddenly, that crucial user research and experimentation gets pushed to ‘next quarter.’
This creates the classic ‘feature factory’ scenario, where we get incredibly efficient at building things nobody truly needs. We’re shipping output, but are we driving outcomes? This is the Discovery-Delivery Paradox: the tension between exploring the unknown (what should we build?) and executing on the known (let’s build it efficiently).
Treating discovery as a ‘Phase Zero’ project that precedes development is a recipe for failure in an agile world. The real challenge is weaving these two tracks together so they run in parallel, constantly informing one another. But how do we do that without context-switching our teams into oblivion or losing all semblance of predictability?