Jira Product Discovery Workflow Best Practices

[Mathew Lederman]

Does anybody have a good, functional workflow they can share for Jira Product Discovery? We're getting started with the tool and I'd like to set best practices up front. The default workflow is garbage (in my opinion) and I'd like to provide the teams with a functional option while not limiting their creativity/options.

[Denis Paul]

Hi Matthew,
I'm not quite sure which part of the workflow you need to design. You are talking views oder the status workflow for JPD tickets?

This is our status workflow which works quite well:

[Testimony Akinkunmi]

Hi Matthew, creating good workflows are not easy. For one, specialized on JPD. It is a notch more difficult. But you could try this, (it is seamless on my end).

1. Ideation Phase

• Capture ideas: Use custom fields for impact, effort, and strategic goals

• Collaborative filtering: Enable voting/reactions for stakeholder input

• Automation:

  text

  When idea is created → Generate Confluence doc template

2. Validation Phase

• Impact mapping: Use matrix view to compare effort vs value

• Automated alerts:

  text

  If idea idle >30 days → Notify owner + move to "Parking Lot"

3. Prioritization Phase

• Scoring system:

  text

  Priority = (Impact × Confidence) / Effort

• Automated sorting: Create smart lists using calculated fields

4. Roadmapping Phase

• Flexible views: Maintain parallel timelines for different stakeholder groups

• Automation:

  text

  When added to roadmap → Post update to Slack/MS Teams 

5. Delivery Handoff

• Seamless integration:

  text

  When status → "Delivery":

  1. Create linked Jira Software ticket.

  2. Copy all research artifacts 

  3. Assign to delivery team

6. Review & Iteration

• Bi-directional sync:

  text

  When delivery ticket → Done:

  1. Update JPD status

  2. Trigger retrospective template