Chapter 1: The New Discovery Imperative
When building became easy, deciding became hard.
A team at FeedLoop, a B2B SaaS company we’ll follow throughout this book, shipped five features in three months. By any traditional measure, they were killing it. Sprints completed on time. Velocity climbing. Stakeholders impressed by the pace. Their AI-assisted development workflow had cut implementation time in half, and they’d used every hour of savings to ship more.
Six months later, three of those features had been quietly deprecated. Fewer than eight percent of customers used a fourth. The fifth, the one that took the most effort, had become a support burden that consumed more resources than it saved.
When the VP of Product asked what went wrong, no one could answer. Not because they lacked data, but because they had never paused to ask whether any of it should be built. They had tested nothing material. They had assumed everything. They had moved fast and built the wrong thing.
This isn’t a cautionary tale about one dysfunctional team. Industry benchmarks point to a broader challenge, although they measure different products and behaviours and should not be treated as universal failure rates. Pendo’s 2024 Product Benchmarks reports that, in its dataset, 6.4 percent of features accounted for 80 percent of click volume. Its 2025 user-retention benchmark reports that only about 30 percent of users were still returning to the software after three months. These figures are directional context, not proof that a particular product or discovery practice will fail.
These are not execution failures. They are failures to validate what was worth building in the first place. We’ve gotten very good at building. We haven’t gotten better at deciding what to build.
Continue reading Chapter 1
1.1 The Paradox of Progress
We can build faster than ever. And we’re wasting more effort than ever.
The paradox is real: the easier building becomes, the more critical it is to know what’s worth building. When implementation was the bottleneck, the cost of a wrong decision was somewhat self-limiting. You couldn’t build that many wrong features because building was slow and expensive. Now you can. And teams do.
Implementation once imposed more friction and often created time for deliberation. Modern tools can shorten implementation substantially, so speed can remove that accidental pause without improving the reasoning that directs the work.
AI and modern product tools are not the problem; they are genuinely useful. The mismatch is that teams have accelerated production without giving equal attention to framing, evidence, and judgment. We can now move faster, but speed does not tell us where to go.
FeedLoop, the composite case study we’ll follow throughout this book, illustrates this pattern through situations drawn from firsthand experience. They built an initial product that let companies collect and organise feedback. Users said the tool was “fine.” Usage data told a different story: seventy-eight percent of users stopped logging in after initial setup. A churned customer captured the problem perfectly: “We’re still making decisions the same way we did before your tool.”
That single sentence would redirect their entire product strategy. But only because they paused to listen.
Project failure. Startup failure. Unused features. AI pilot collapse. Different symptoms, with a recurring cause: decisions made before evidence existed. Teams commit resources, hire engineers, and build roadmaps based on assumptions that feel obvious but have never been tested.
Talented teams make this mistake too. Without a disciplined discovery process, confidence can easily be mistaken for validation.
The uncomfortable truth is that speed amplifies whatever direction you’re heading. If you’re heading towards a worthwhile outcome, speed is an asset. If you’re heading towards the wrong one, speed just gets you there faster.
The complete sample continues through the shift from prediction to judgment, the limits of traditional discovery, the four-layer DJF architecture and the chapter summary.