Buzz Usborne in Discovery vs Delivery:
“The best product work rarely comes from executing a brief perfectly. It comes from realizing the brief itself was incomplete, shallow or asking the wrong question entirely.”
And:
“Delivery without discovery creates output, not outcomes. Discovery without delivery creates insight, not impact.”
Those two observations are easy to agree with in theory. In practice, most organizations spend far more time measuring delivery than discovery. Understandable! Delivery leaves evidence: features ship, roadmaps advance, quarterly goals turn green, and progress can be neatly captured in dashboards and status updates. Discovery, by contrast, often looks like a squad of Designers, Product Managers, and Engineers spending weeks questioning assumptions, exploring alternatives, and occasionally concluding that the original idea wasn’t worth building in the first place.
One of the more interesting side effects of AI may be that it forces companies to reconsider where value is actually created. For decades, software organizations were constrained by implementation cost — building things was expensive. As a result, much of the industry’s status, compensation, and organizational influence became tied to the ability to turn decisions into shipped software.
But what happens when implementation becomes dramatically cheaper? The bottleneck simply moves upstream. A world where prototypes, interfaces, and even functioning applications can be generated in hours rather than weeks is a world where delivery matters less, not more. To be clear, deciding what deserves to be built has always been the hard part. What’s changing is that the cost of getting that decision wrong is falling, while the consequences of getting it right become increasingly important.
What is the customer actually trying to accomplish? Which frustrations are real and which are merely reported? Which opportunities are worth pursuing, and which are artifacts of the metrics we happen to be measuring? Which briefs are asking the wrong question altogether?
The irony is that the people who are best at discovery often have the least to show for it. A reframed problem, a sharper understanding of customer needs, or a realization that the most promising opportunity lies somewhere other than where the roadmap originally pointed can be every bit as consequential as a successful launch, even if it’s far more difficult to capture in a dashboard or quarterly review.
Those contributions have always been valuable. They may simply become easier to recognize, now that anyone can ship.
(Via Sidebar, which is excellent. You should subscribe!)