Product Discovery
Product discovery is the work of deciding what to build — validating that a problem is real, worth solving, and solvable — before committing engineering effort to delivery.
Discovery reduces the risk of building the wrong thing. It typically involves understanding users and their problems, gathering evidence, framing opportunities, and testing assumptions about value, usability, feasibility, and viability.
It is continuous, not a phase: teams keep discovering as they deliver. The output of discovery is not a document for its own sake, but better-justified decisions about what belongs in the product.
Before building a new onboarding flow, a team interviews churned users, finds that setup — not features — is the drop-off point, and reframes the work around reducing time-to-first-value.
ArcPM front-loads discovery: it turns one idea into cited market research, competitor analysis, and personas, then carries that evidence forward as the grounding for requirements — all linked in the Connected Product Graph.
See ArcPM