How does JPD support continuous product discovery?
Asked by Troy Eberlein:

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


Answers:
author: Tanguy Crusson
body: 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)* {#toc-hId-149288729}

*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](https://www.loom.com/share/c5acafb1584740c98f6871667bac6df8). And here's a [recording for how to reproduce this configuration](https://www.loom.com/share/c74c8cc8e5be4daaa4498bb8d3397bcd)*

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.

comments: author: Troy Eberlein
body: 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!


author: Robert Ogilvy
body: 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.


author: David Nadri
body: [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) - RE different issue types/ parent-child relationships in JPD:

In our JPD project, if we create ideas and set their custom Type and Opportunity fields and then create Opportunity/Solution views now, later when there's a native way to create different issue types and their parent/child relationships, will there be a easy/clean way to convert them properly?


author: David Nadri
body: Hey [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) [@Rohan Swami](/t5/user/viewprofilepage/user-id/2842658) [@Hermance NDounga](/t5/user/viewprofilepage/user-id/430755) !

**RE: \[P2-130\] Issue types, hierarchies and relationships between ideas** {#toc-hId--435626469}
-------------------------------------------------------------------------------------------------

**Any updates you could share with the community on this item on your JPD Roadmap? Is it \~1 month away, \~3 months away, etc? Any insights, prototypes, or designs you can share on its progress would be greatly appreciated.**

We are *desperately* waiting on this capability to allow us to organize ideas using issue types/hierarchies according to our model. We've tried the alternatives using the flexible fields/views approach, but it's not trivial or sufficient for our needs.

The [opportunity solution tree (OST) framework by Teresa Torres](https://www.producttalk.org/opportunity-solution-tree/) is very popular and helps visualize the biggest opportunities and align them to our goals. It's really just a decision tree that helps you make sense of this messy world of product discovery (assessing which opportunity to go after vs every feature/idea that comes in), and helps with strategic alignment. Also, the ability to create an 'Opportunity Solution Tree' (OST) view would be very helpful.

Thank you!

comments: author: David Nadri
body: [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) [@Rohan Swami](/t5/user/viewprofilepage/user-id/2842658) [@Hermance NDounga](/t5/user/viewprofilepage/user-id/430755) - any updates whatsoever that you guys can share on support for Issue types, hierarchies and relationships in JPD?

It's arguably one of the biggest limitations of JPD. It's been raised by many community members across multiple posts and comments in the group and we've been told it's on the roadmap for years, so I'm hoping it's finally here or close. It will significantly improve JPD's capabilities \& use-cases!

We appreciate as much info you could share on this - the community is patiently waiting!


author: David Nadri
body: Hi [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) [@Rohan Swami](/t5/user/viewprofilepage/user-id/2842658) [@Hermance NDounga](/t5/user/viewprofilepage/user-id/430755) - any updates you could please share on Issue types, hierarchies and relationships in JPD?


author: Hermance NDounga
body: Hello David,

We are currently in design phase for this feature!

Stay tuned on the group we should come up with news before the end of the year.

Best Regards,  
Hermance  
Product Manager @ Jira Product Discovery


author: Wes Mason [he / him / his]
body: +100. See: <https://www.producttalk.org/2020/07/opportunity-mapping/>

comments: author: Annie Ioceva _Nemetschek Bulgaria_
body: 100% agree.

We use Miro to capture opportunities trees.


author: Ben Arundel
body: +1 for Miro


author: Mike Hughes
body: Yes need some sort of hierarchy/dependency management. Opportunity/Solution is great, but is only a single parent many children?

Keen to be able to sequence opportunities, where one is dependant on one or more others. This can then be reflected during Prioritisation and be present on the Roadmap as well.


author: David Nadri
body: [@Troy Eberlein](/t5/user/viewprofilepage/user-id/4978856) - checking in here \~a year later: any updates you can share on how you're using JPD in your continous product discovery workflow? Particularly, how are you using JPD to support more of an opportunity solution tree framework?

Have you found a clever way to track opportunities and solutions in JPD or are you using the manual approach mentioned in this article?

comments: author: Troy Eberlein
body: [@David Nadri](/t5/user/viewprofilepage/user-id/3918237) We aren't using JPD yet


author: Bj?rn Brynjar J?nsson
body: 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](https://m.youtube.com/watch?v=l7-5x0ra2tc) few years back and connected with the problem.

I now have a book to read over the weekend ??