Purpose
Use Product Discovery Workshops to understand the problem, gather user and stakeholder evidence, test assumptions and decide whether an idea should proceed, park or stop before delivery effort is committed.
When to use
- The problem is unclear or different stakeholders describe it differently.
- The request is solution-first and needs reframing.
- Success metrics, user need or journey impact are not yet understood.
- The idea needs evidence before it moves to prioritisation or backlog creation.
Inputs
- Idea in Jira Product Discovery.
- Problem or opportunity statement.
- Business owner and key stakeholders.
- Any service desk tickets, evidence, data, user feedback or workflow context.
Outputs
- Problem statement.
- User needs and insights.
- Constraints, risks and assumptions.
- Solution options, not designs.
- Proposed outcome and success metrics.
- Recommendation: Proceed, Park or Stop.
Responsibilities
The Product Owner owns discovery and keeps the documentation lightweight but visible. Stakeholders and business SMEs provide context, constraints and success criteria. Design / UX and Engineering / Tech Lead support where user research, journey mapping or feasibility input is needed.