We’ve all been there: the ‘discovery phase.’ It’s that sacred block of time before a big project kicks off, dedicated to user research, requirements gathering, and de-risking. But is this model, a relic of project-based thinking, actually holding us back? By front-loading all our learning, we create a huge gap between insight and execution. By the time we start building, our ‘validated’ assumptions might already be stale.
True continuous discovery isn’t a phase; it’s a parallel, never-ending process. It’s about creating a weekly cadence of customer touchpoints with your core triad—PM, Design, and a Tech Lead—to continuously test assumptions as you build. This shifts the focus from delivering a pre-defined set of features to achieving measurable outcomes. Instead of a ‘big reveal’ of requirements, the team builds a shared understanding of the user and the problem space, course-correcting in small, informed increments. It’s the ultimate antidote to the feature factory, ensuring you’re always building what matters now.
This shift is more cultural than procedural, and it’s a tough one to make. So, what are the biggest hurdles you’ve faced when trying to embed continuous discovery into your team’s weekly rhythm?