Journal
|Stefania

Product discovery: understanding what's worth building

Product discovery is the work a team does to understand which problem is worth solving — and for whom — before committing to building a solution. That's the whole definition. Everything else is technique.

Most teams I meet don't lack discovery methods. They have interview guides, opportunity trees, experiment templates. What they lack is the willingness to let discovery change their mind. The roadmap is already promised, the feature is already named, and discovery becomes theatre: interviews run to confirm a decision that has already been made.

You can tell real discovery from theatre with one question: what evidence would make you not build this? If nobody can answer, it isn't discovery. It's documentation for a decision that predates it.

Good discovery starts from the decision, not the method. What are we actually trying to decide — whether the problem exists, whether our solution fits it, whether people will change their behaviour for it? Each of those needs different evidence, and most need far less machinery than teams assume. Not every question deserves an A/B test. Some just need five honest conversations and the discipline to hear the answers.

The classic objection is that discovery slows delivery down. My experience is the opposite: teams skip discovery to move fast, then spend quarters shipping variations of something nobody asked for. Slowing down at the front makes everything downstream faster, because the direction holds under pressure instead of shifting with every stakeholder meeting.

AI has made this more true, not less. You can now prototype in hours what used to take weeks, which means you can put something concrete in front of users almost immediately. That's a gift for discovery — and a trap. Faster building means you can also validate faster in the wrong direction, mistaking the speed of iteration for the quality of learning.

The teams that do discovery well don't treat it as a phase that ends when development starts. They treat it as a rhythm — a continuous habit of checking that the problem is still real, the bet still makes sense, and the evidence still points where they're going.

Product Rhythm logo

Every product has a rhythm. I make it my practice to find it.

© 2025–2026 Stefania Tardito · Product Rhythm (portfolio & product thinking)