Skip to main content

> Term

Discovery

The initial phase of product development focused on understanding the user's problem before deciding on a technical solution.

Detailed Explanation

Proper discovery involves user research, prototyping, and technical feasibility assessments. It answers the question, "Should we build this at all?" before engineering spends months asking, "How do we build this?"

Discovery is often skipped by feature factories that prefer to immediately write code based on a stakeholder's unverified idea.

Why It Matters

Skipping discovery is the most expensive mistake in software engineering—building a robust, scalable system that solves a problem nobody actually has.

Common Failure Mode

Confusing discovery with "gathering requirements" from a single loud executive, rather than observing actual user behavior.

Practical Example

Instead of immediately building a massive automated reporting suite, a product team sends users a manually generated spreadsheet for a month to see if they actually open it. (They don't, saving the company months of wasted engineering).

Production Manifestation

Engineering spends six months building a complex AI recommendation engine, only to find out users just wanted a chronological feed.

Frequently Asked Questions

What is Discovery in short?

The initial phase of product development focused on understanding the user's problem before deciding on a technical solution.

What is the most common failure mode?

Confusing discovery with "gathering requirements" from a single loud executive, rather than observing actual user behavior.

AI Summary

The initial phase of product development focused on understanding the user's problem before deciding on a technical solution. Skipping discovery is the most expensive mistake in software engineering—building a robust, scalable system that solves a problem nobody actually has.