No, I don’t mean that time of year: 🎄 - 🕎. I mean planning for what your teams will work on for the next year… What new features, enhancements, and perhaps all new products are you going to deliver in 2026? If you’re not sure where to start with this, we’ve got you, or, well, Jira Product Discovery (JPD) does!
Jira Product Discovery helps product teams capture customer insights, prioritize ideas, and build roadmaps. It bridges the gap between initial ideas and development by providing a dedicated space to organize and prioritize potential work, making it easier to decide what to build next.
I often get asked: why not just put your ideas and enhancement requests in your Jira backlog? You could, but I can certainly think of some developers who, when faced with being assigned one or more bugs to fix this sprint, will scan the backlog for something, anything better to work on… Seeing a new feature, they’re gonna pull that into the sprint and work on that instead! I would!
JPD is purpose-built to help your product team create ideas using out-of-the-box or custom templates, so you know you’re capturing all the details needed to make go/no-go decisions. It allows you to define the criteria that matters to you, then helps you prioritize those ideas and build a roadmap that you can share both internally and externally with stakeholders.
Let’s say I have these ideas in JPD of possible new features we might build for our travel app:
I can have JPD rank these ideas for me using my own custom criteria. Below shows the impact score JPD has given my ideas:
We can see that the new rewards program ranked highest, while the VR travel feature didn’t do so well… No one really wants to skip the sunblock and pretend to go to the beach via virtual reality; we want real sand between our toes!
Based on the above, we might build a high-level roadmap that looks like this:
This roadmap shows that we’re working on the new rewards program now, with our second and third ranked ideas after that…. And, VR travel? Well, that landed in our Won’t do column, but now we can let stakeholders know that we don’t plan to build that feature.
We can share this roadmap as is, or, if the stakeholders want timeframes, we can build that too:
I organized the above timeline by goals in Atlassian Home, but you can organize your timeline by one of 25 fields, including status, customer segment, impact score, and more. Just click on Group by, in the upper left, to see all the options!
The main benefit of creating these views is being able to easily share them with your teammates or external stakeholders.
To share views with your team (e.g. those who have access to your site)
Click on Share in the upper right-hand corner of your screen
Click the blue Copy link button and share an always-up-to-date link with your peers or export a static version of the view as a JPEG or CSV file
To publish a read-only view externally (e.g. senior leadership or stakeholders):
Click on Publish in the upper right-hand corner of your screen
Add specific email address or team aliases you wish to share with
In the bottom left, click Settings, to configure which fields you want visible to your stakeholders
Click Copy link to copy the published URL and send it out via email or messaging app
That’s it! You’ve defined your ideas for the next year, had JPD rank them for you, then shared your upcoming roadmap with those who need to know…
I think it’s time for your holiday beverage of choice, don’t you? 😀
Peggy Graham
0 comments