We all champion the ideal of ‘continuous discovery.’ It’s the gold standard for building products that truly resonate. We read the books, listen to the podcasts, and aspire to be the PM who is constantly talking to users and uncovering game-changing insights.
But let’s be honest about the reality on the ground. The pressure to ship is immense. Stakeholders demand roadmap certainty, engineering needs clear specs for the next sprint, and the business is focused on velocity. In this environment, deep, generative user research can feel like a luxury we can’t afford. It’s often the first thing to get squeezed when a deadline looms, relegated to ‘when we have time,’ which, of course, is never.
This isn’t just a process failure; it’s a strategic risk. When we sacrifice consistent discovery for the sake of perceived velocity, we end up in the ‘build trap.’ We ship outputs instead of outcomes, get disconnected from our users’ evolving needs, and risk spending months building features that ultimately miss the mark. The challenge isn’t choosing discovery or delivery. It’s about finding a sustainable, pragmatic rhythm that braids them together.
How do you protect and integrate continuous discovery habits when the pressure for delivery is at an all-time high? What lightweight tactics have actually worked for you?