Choose the discovery path that matches the request.
Scan the approaches and open the one that fits best.
For tightly scoped change work where the problem is mostly understood, but the team still needs clarity on scope, rules, edge cases, and acceptance criteria.
Use when the request is bounded, delivery is near-term, and the main risk is misunderstanding the details rather than choosing the wrong strategy.
For internal workflow or program work where the challenge is understanding roles, approvals, handoffs, exceptions, process gaps, and rollout context.
Use when a workflow, department, branch network, or program needs a shared way of working and success depends on process clarity, ownership, training, and adoption.
For large enterprise products or reusable solutions that must work across multiple teams, units, clients, roles, or governed contexts. This may or may not become SaaS.
Use 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.
For external or public-facing product work where many users are affected and the team must understand adoption, trust, usability, support impact, and behavior at scale.
Use when success depends on whether a large user base can understand, trust, adopt, and repeatedly use the product without creating service or support overload.
For system-dependent work where APIs, data flow, source-of-truth mapping, sync rules, reconciliation, dependencies, and failure handling are central.
Use when the hardest part is not the screen design, but how systems connect, exchange data, recover from errors, and stay consistent over time.
For reporting, scoring, recommendation, prediction, automation, or decision-support work where value depends on data quality, metric logic, model behavior, and user trust.
Use when the product outcome depends on insights, alerts, AI assistance, scoring, dashboards, or decisions that users must understand and act on confidently.
Not sure what kind of discovery this request needs?
Answer a few guided questions and get a recommended discovery approach based on request clarity, risk, urgency, stakeholders, and delivery context.
Learn From the Best
Curated books, articles, frameworks, and references for Business Analysts, Product Managers, and discovery practitioners.