Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,464,112
Community Members
 
Community Events
176
Community Groups

How does JPD support continuous product discovery?

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 :-)  

3 answers

3 votes

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: 

Can we create different issue types and their relationships? (e.g. parent/child or opportunity/solution)

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!

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.

100% agree.

We use Miro to capture opportunities trees. 

+1 for Miro 

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 🤓🙌

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events