Choose discovery before delivery.
Decide what evidence a request needs before build, rollout, or scale.
Choose the discovery path that matches the request.
Pick the lens that matches the request's main uncertainty.
For approved or contracted work where the team can run the full discovery needed before delivery.
Use when the request is bounded, delivery is near-term, and the main risk is misunderstanding the details rather than choosing the wrong strategy.
View detailsUse when a workflow, department, branch network, or program needs a shared way of working and success depends on process clarity, ownership, training, and adoption.
View detailsUse when the team must decide whether the solution should stay custom, become an internal platform, support multiple enterprise contexts, or evolve into a SaaS-friendly product.
View detailsUse when success depends on whether a large user base can understand, trust, adopt, and repeatedly use the product without creating service or support overload.
View detailsUse when the hardest part is not the screen design, but how systems connect, exchange data, recover from errors, and stay consistent over time.
View detailsUse when the outcome depends on reports, dashboards, metrics, migrations, or data outputs that users must understand, trust, and act on confidently.
View detailsUse when the central uncertainty is not just what to build, but whether AI or ML is the right solution, what inputs and controls it needs, and how the team will evaluate, operate, and govern it responsibly.
View detailsNot sure what kind of discovery fits?
Answer focused pattern questions and see which discovery lenses fit best.
Need to understand the risk areas first?
Answer risk-area questions only and see where ambiguity, coordination, technical dependency, governance, or rollout risk is highest.
Learn From the Best
Curated references for PMs, BAs, and discovery practitioners.