PRODUCT DISCOVERY
Product Discovery: Use this section to decide whether an idea is worth taking into delivery. Discovery should validate the problem, test assumptions and create evidence before teams commit build effort.

Where should I start?

Select the situation and the page will show the correct next step.

Route through triage first

Check whether the ticket is an incident, BAU request or idea. If it is an idea, the Product Owner creates it in Jira Product Discovery.

Open service desk flow

Create and triage the idea

Product Owners create ideas in the shared Jira Product Discovery space, set the owner, link work items if applicable and leave new ideas in Parking Lot until triaged.

Open Jira idea guide

Run discovery before delivery

If the problem, user need, success measure or stakeholder view is unclear, time-box discovery before creating delivery backlog commitments.

Open getting started

Move to prioritisation

When discovery has clear outputs and a recommendation, move to prioritisation. If approved, create epics and high-level stories in the platform backlog.

Check readiness

Discovery flow

Click each step to see the owner and outcome.

Owner: Service Desk Team
Outcome: Ticket is classified as incident, BAU or idea.
Owner: Product Owner
Outcome: Idea created in Jira Product Discovery and linked to a work item if applicable.
Owner: Product Owners & Platform Owner
Outcome: Ideas are reviewed and prioritised for discovery.
Owner: Product Owners & Platform Owner
Outcome: Problem validated, opportunities explored, assumptions tested and direction defined.
Owner: Product Owners & Platform Owner
Outcome: Prioritised using a framework such as RICE.
Owner: Product Owner & Scrum Team
Outcome: Approved work is refined, planned into a sprint and delivered.

Product discovery pages

Use the cards in order, or jump directly to the part of the process you need.