Discovery Deliverables

Why Catalog Deliverables?

Every module in this guide produces an artifact. Knowing the full set — and when to use each — helps you assemble a complete discovery practice instead of relying on just one favorite tool.

The Core Deliverables

• Customer segments & personas (Module 2) — who you're designing for.
• Research plans & interview/survey scripts (Module 3) — how you'll gather evidence.
• Problem statements & JTBD statements (Module 4) — the framed problem.
• Customer journey maps (Module 5) — the end-to-end experience and friction points.
• Competitive/market analysis & benchmark matrices (Module 6) — the external landscape.
• Opportunity Solution Tree (Module 7) — outcome, opportunities, solutions, experiments.
• Solution concepts & evaluation matrices (Module 8) — candidate solutions, scored.
• Hypothesis statements & assumption maps (Module 9) — what you believe and why.
• Experiment plans & validation results (Module 10) — what you tested and learned.
• Discovery metrics dashboard (Module 11) — process + outcome health.
• Stakeholder alignment notes (Module 12) — who's informed, who's contributed.
• PRD (Module 15) — the delivery handoff document.

Choosing the Right Deliverable for the Moment

Not every initiative needs every artifact in full form — scale the rigor to the size and risk of the decision. A small UI tweak might only need a lightweight hypothesis and a quick test; a new product line warrants the full set, from segmentation through PRD.

Keeping Deliverables Connected

The biggest mistake is creating these as disconnected documents. Strong teams thread a single narrative: the persona informs the problem statement, which feeds the OST, which justifies the hypothesis, which is tested and then documented in the PRD — each artifact citing the one before it.