Product discovery
Definition
Product discovery is the process of figuring out which problems are worth solving and what solutions will actually work — before the engineering team writes a line of production code.
Marty Cagan and the SVPG community brought the term into mainstream product management, contrasting it with delivery (building what's already been decided). Discovery is the "what should we build" phase; delivery is the "how do we build it" phase.
Discovery work includes user interviews, prototype testing, data analysis, and assumption mapping. The goal is to reduce four risks before committing to build: value risk (will users want it?), usability risk (can users figure it out?), feasibility risk (can we build it?), and viability risk (should the business build it?).
A common mistake is treating discovery as a phase — something you do at the start of a project and then move past. Modern product thinking treats discovery as continuous: the team runs discovery experiments every week, in parallel with delivery.
Discovery sessions are whiteboard-heavy. Teams sketch user journey maps, draw assumption trees, and map opportunity spaces. The whiteboard becomes a live artifact of what the team believes and what still needs to be tested. BoardSnap captures those sessions as structured summaries, so the insights from discovery don't sit as a photo in someone's camera roll.
Examples
- Running five user interviews to test whether a proposed feature solves the stated problem
- Building a low-fidelity prototype in an afternoon to test a navigation concept
- Mapping assumptions on a whiteboard and sorting them by risk + unknowns
- Analyzing activation data to identify where users drop off before reaching value
Snap a product discovery. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.