Product Discovery Basics
Product discovery is the work before building–identifying what problem to solve and whether solutions are feasible, valuable, and usable. Discovery prevents shipping solutions nobody wants or building technically infeasible features. Without discovery, teams guess what users need and discover failures only after investment. Discovery combines research (what problems exist and how severe are they?), analysis (why do these problems exist?), and ideation (what solutions could work?). It is not synonymous with research–discovery is a process; research is one activity within that process. Discovery includes competitive analysis, brainstorming, prototyping, and testing. Outcomes of discovery are clear problem statements, validated assumptions, and refined solution directions worth building.
Key Discovery Activities
User research reveals actual problems and desires. Interviews with target users uncover frustrations with current solutions. Analytics reveal where people abandon products and what paths they take. Support tickets highlight problems users encounter using existing products. Competitive analysis shows how similar problems are currently solved. Stakeholder interviews surface business constraints and opportunities. Synthesis across these sources identifies patterns and validates problems worth solving. A team might discover that customers struggle with invoicing in their accounting software not because invoicing is hard to use but because they do not understand invoice numbers for tax purposes. The problem is not software design; it is education. Discovery surfaces that distinction.
Narrowing and Prioritising
Most organisations have more problems to solve than resources to address them. Discovery helps prioritise. Which problems affect the most users? Which do users care about most? Which problems create business opportunity? A problem affecting a tiny segment may not be worth solving despite genuine severity. A problem affecting everyone but minor in impact may not warrant development investment. Prioritisation matrices balancing impact and effort help teams decide. Validate problem framing before advancing: if you solve this problem, will it actually change user behaviour or satisfaction? Solving non-problems wastes effort. Run small experiments or prototypes to test problem framing. A mockup showing a proposed solution often reveals whether users actually want what you are proposing.
a fuller account of accessibility audit scope
Rapid Testing and Learning
Discovery is not indefinite exploration. Set time boundaries–two weeks, one month–for discovery before moving to build decisions. Use rapid prototyping to test ideas cheaply. Paper sketches, clickable wireframes, or crude prototypes reveal problems with approaches before engineering investment. Testing with users is fast and inexpensive at this stage. Five users reviewing a prototype reveal most major issues. Quick feedback loops beat extended speculation. Document discovery findings clearly so building teams understand problem context and constraints. Discovery that goes unshared wastes knowledge. Successful products often trace back to strong discovery work that validated both problem and solution direction. Discovery is not a phase you complete then leave behind; revisit discovery when product changes or new problems emerge. Markets shift, competitors innovate, and user needs evolve. Continuous discovery keeps products aligned with reality.