Jira Product Discovery Reviews and Ratings

Use Cases and Deployment Scope

We use Jira Product Discovery to gather product ideas, feedback from stakeholders, and ultimately prioritize the features based on impact and effort. Prior to Jira Product Discovery, we only had a platform to gather feedback from customers however no clean way to actually triage it. The is where Jira Product Discovery was able to come in to solve the issues. We are not able to not only collect ideas but also score ideas by using customizable criteria and link them directly within the Atlassian ecoverse.

Likelihood to Recommend

It's a great tool for early stage ideation and prioritization in order to get alignment across product, design, and engineering. It works really well when teams are trying to consolidate scattered ideas into one validated pipeline. The scoring model and ability to link ideas directly to our regular Jira makes it easy to prepare for roadmap views.

Use Cases and Deployment Scope

We use Jira Product Discovery for bug and error management for our dev teams.

It provides an efficient platform for which these can be raised, tracked and logged across the business. Whether internally or from an external source via support.

All dev teams across the company utilise this.

All customer facing teams have access to it as well.

Likelihood to Recommend

Jira Product Discovery has been really useful for:

- Centralising Bug Logging across multiple teams- we have lots of software facing teams in the business and Jira Product Discovery provides a useful platform to log centrally rather than monitoring a bug related inbox

- helps to prioritise bugs based on its impact across the business

- great for tracking patterns with bugs

Use Cases and Deployment Scope

Jira Product Discovery helps us consolidate these inputs in one central place, score ideas based on business value, technical efforts and customer impact and create clear roadmaps that are easy to understand. The product supports transparency during planning discussions and it ensures that we invest resources into initiatives that align with goals. Our use case mainly focuses on improving collaboration during early stage product planning.

Likelihood to Recommend

It is well suited for early stage product planning where ideas need to be collected and compared and evaluated. We use it to capture each insight, score ideas based on impacts and alignment done on those initiatives.

It is less appropriate in scenarios where development work is already fully defined and execution focused.

Use Cases and Deployment Scope

In my day-to-day activities, I utilize Jira Product Discovery in 2 ways: as a backlog of prioritized and unprioritized ideas, as well as a way to communicate the ideas/initiatives that are in motion. The first use case covers the process of generating ideas and documenting them for future discovery. The second use case is extremely useful when communicating with stakeholders across the org about the things in motion and their progress. The great integration between Jira Product Discovery, Jira and Confluence allows me to link the corresponding product requirements, UX flow and work items (epics, stories, tasks). Thus, the entire org is available to track progress, check details and stay on the same page. Jira Product Discovery allows you to use the predefined fields and benefit from tools like the effort/impact matrix, but it also gives you the flexibility to define custom fields and go beyond the one-size-fits-all solution. There are some limitations, though, e.g. timeline view of initiatives allows you to place a single entry per idea, which is not sufficient if you develop cross-platform solutions which may run at different paces. I believe this limitation is mainly there, as Atlassian offers dedicated tools for project management that are coming in the Premium tiers or as stand-alone solutions.

Likelihood to Recommend

Well-suited:

- Collecting a backlog of ideas from internal stakeholders.

- Linking the work items from various projects to a single idea/initiative

- Effort/Impact analysis

Less appropriate:

- Timeline visualizations e.g. GANTT charts

Use Cases and Deployment Scope

We use this to layout a complex and interlinked product roadmap. We link all the team work back up to the strategic initiaives which helps everyone know what they are contributing towards. We have a number of views to suit different stakeholders and to keep a single source of truth about ideas and what's coming up across the whole organsiation.

Likelihood to Recommend

If you are already using Jira at a team level, this is the missing piece to glue the entire product system together end to end. It's familiar to use if you're a Jira user and it's simple enough for most stakeholders to be able to view roadmaps and engage without prior Jira knowldge.

Use Cases and Deployment Scope

Our Product Team was looking for a "front door" ideation tool, and after evaluating over ten different products with similar functions and features, we found that Jira Product Discovery was the perfect fit for our business.A key factor in our decision was the seamless integration with Jira and Confluence, as our DevOps and Delivery teams already work within these Atlassian tools. This minimal integration and reduced administration burden, combined with the familiarity of the Atlassian ecosystem, significantly lessened the learning curve for our teams and leaders.The support we received from our account and technical teams was exceptional. They provided assistance every step of the way, including feature demos tailored to our unique business needs, ensuring everyone felt comfortable with the new tool.

Likelihood to Recommend

- Jira Product Discovery is the starting point for all ideas to be looked at and worked through ranking and sizing

- All product managers are working in the same system, using same langauge but unique processes

- Our research teams can work and attach insights directly to ideas and bets without needing to have these in seperate places

Use Cases and Deployment Scope

We used this tool in tandem with Productboard and we used Productboard to push stories and things we needed our developers to have and this was the tool where we would handoff our stories to Dev.

Likelihood to Recommend

It was great for handing off projects to Developers and give it into their hands especially by being able to connect to Product Board. Was tricky though sometimes going back and finding things when those backlogs get really lengthy and titles start not helping as much...etc.