You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I just discovered JPD today, so forgive me if this is a noob question.
It strikes me that JPD is very idea-centric, instead of outcome / goal / problem - centric. I would like to see strong support for modern product discovery methodologies like those found in SVPG's Inspired or Product Talk's Continuous Discovery Habits.
I think most companies have a deluge of ideas, often lacking strong linkage to a problem that is clearly worth solving. I want to get out of the feature factory mentality, and looking for tools that support this instead of adding fuel to the ideas bonfire :-)
Hi all, the opportunity/solution tree is a great framework. There are a few teams using it in Jira Product Discovery already. Here's a section from the FAQ about how to do that:
Not yet, but it's on the roadmap. In the meantime you can use the flexible fields and views system to do this. Here is an example:
Demo: grouping solutions by opportunities. And here's a recording for how to reproduce this configuration
More generally we had to pick one noun for the basic object in the app, and were trying to find one that could encapsulate many aspects: problem, opportunity, solution, idea, experiment, feature, etc. We settled on "idea" and we know it's not perfect. What we've built this app for is to help you collaborate on what can best help you achieve your goals, with your teams and stakeholders, taking into account all the data you've got.
Thx for the reply. I had watched that video, and seemed like quite a bit of manual setup. Re: noun, I think that highlights the core issue - an idea is fundamentally different than a problem / oppty / outcome. IMO there would be significant value in JPD natively supporting these different concepts. Thx!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is why I am here. I am glad different issue types and their relationships in on the roadmap. Hoping it is in your Now category with a rocket ship next to it. :)
I will take a look at your demo in the meantime.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for sharing, because I just learned Teresa Torres book, Continuous Discovery Habits, on the topic is now available 🎉
I had seen Teresa Product talk few years back and connected with the problem.
I now have a book to read over the weekend 🤓🙌
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.