We all know the rhythm of the two-week sprint: plan, build, ship, repeat. It’s a powerful engine for delivery. But lately, I’m hearing from more PMs that this engine is running so hot it’s burning the most critical fuel we have: genuine user discovery.
The classic ‘dual-track agile’ model was meant to solve this, creating parallel streams for discovery and delivery. In reality, under immense pressure to maximize output and show constant forward momentum, the discovery track often gets squeezed. It becomes a rushed, superficial exercise—grabbing a few user quotes to justify the next feature on the roadmap instead of uncovering deep, unmet needs.
This isn’t just a process problem; it’s an impact problem. When we prioritize the act of shipping over the outcome of what we ship, we risk building beautifully engineered solutions to problems nobody has. We create feature bloat and chase vanity metrics, ultimately wasting more resources than we ‘saved’ by cutting research corners. It’s a false economy that slowly erodes product-market fit. We need to stop seeing discovery as a separate, pre-development phase and truly integrate it as a continuous practice.
How is your team balancing the relentless demand for delivery with the non-negotiable need for deep, continuous discovery?