Beyond the Buzzword: The Real Challenge of Implementing Continuous Discovery


We all talk about the importance of continuous discovery. The idea of weekly touchpoints with customers to co-create solutions is the holy grail for many of us. But let’s be honest: how many teams are truly living this practice versus just paying lip service to it?

The theory is simple, but the execution is fraught with challenges. I see teams treating ‘discovery’ as a phase-gate: a big batch of user interviews they conduct at the start of a project. They front-load the research and then spend months building, effectively losing the ‘continuous’ part of the habit. The real goal is to de-risk our assumptions week by week, not just once a quarter.

The friction is real. Stakeholders demand a predictable, feature-based roadmap. Engineers are heads-down on delivery and don’t have time for interviews. And PMs themselves are often so bogged down in execution that making time for a weekly customer conversation feels like a luxury. The result? We end up right back where we started, making big, risky bets based on stale insights.

What’s the single biggest hurdle your team has faced in trying to make continuous discovery a genuine, weekly habit instead of a sporadic project?