Any update on support for OST (opportunity solution trees)

[Brent Ritchie]

Happy to hear that this is in discovery, but just wondering where it is now? Many product teams are working (or trying to work) in this framework, but JPD kind of lacks that visual spacial format that makes OST's work so well. 

Products like Vistaly exist (which works exactly like this) but having something native in atlassian would be preferable. Any sort of update would be awesome, thanks!

Edit: just noticed one of Atlassian's growth teams even uses CDH, and OSTs, but not sure where they're doing this and how they're linking this back to JPD and then the delivery work: 

https://community.atlassian.com/t5/Jira-Product-Discovery-articles/5-Continuous-Discovery-Best-Practices-from-the-Atlassian-Growth/ba-p/2692056

[Tanguy Crusson · Accepted solution]

Hi everyone, it's been a while since the last update on this topic. Good news: we have started working on this. 

As a first step, we're implementing the concept of "issue type", and "relationships" between these issue types, as you can see in this Loom: https://www.loom.com/share/1d360838826842d396ff57d8048dec59

From there, we'll introduce a new type of view (map/tree), so you can do things like this: 

[Brent Ritchie]

Awesome news! Looking forward to checking out this tool again now that it’s adopting and facilitating this framework!

[Elise Chant]

Amazing. Really really really looking forward to this. 

I've been working around this with custom fields, but I find that when I am creating OST that I want to create Outcome, then Opportunity, then Solution (Idea). At the moment PRD wants me to create Solution initially, which I find a little counter intuitive. 

[Paulo Costa]

Just came across this as I was searching for a way to generarte a visual representation of a tree for our opps and solutions...
This is how we're working in our Discovery board over the last few months. 

We have links/relations between opps and solutions (many times with one solution linking "up" to multiple opps). We have list views for each issue type with specific filters to navigate on open opportunities, drafts, etc.

So I guess you are now working on solving our last issue which is "how the hell can we generate a big mindmap with all our active opportunities and related solutions, so that we navigate through them and have our discovery sessions with stakeholders facilitated?"

Cheers, and we're eagerly awaiting for this!

[Tanguy Crusson]

This is by and large the most awaited feature in the history of this product 😅 

[Max Herberger]

@Tanguy Crusson this looks a-mazing! Can't wait to implement this.

Related question to this: if more and more teams work with opps and solutions, do you think Epics in Jira are still useful? In my experience so far, the solution entities basically replace what we have organized in Epics before. So that might be something to consider as well, because right now JPD solutions can not be visualized and accessed in Jira backlogs in the same way as epics, which would be cool though, to actually replace them in that case.

[Tanguy Crusson]

Thanks @Max Herberger . I really don't see JPD replacing Jira for delivery planning and tracking. We don't even support tasks in JPD. JPD is good from big ideas all the way down to Epic, but below that it's a different world. 

[Jens Schumacher - Released_so]

@Tanguy Crusson I don’t think Max was suggesting that JPD would replace Jira for delivery planning. 

the question, how I’ve read it, was around the relationship of an idea and an Epic. I myself find that Epics often seem redundant and I would prefer to go from Idea straight to Stories and Tasks. But then you‘ll lose the Epic level functionality in Jira. 

How do you guys think of that? Can’t remember if that was covered in the playbook, but don’t think it was. 

[Max Herberger]

Thanks Jens, yes exactly that. When describing problem and solution issues in JPD I'd prefer to use the solutions as epics in Jira, but I can't, because it's different entities. So right now we just tend to not use epic anymore in Jira, but the link between Jira stories and JPD ideas is much weaker displayed in Jira, which is not great.

[Tanguy Crusson]

OK thank you I get it now! Thanks for clarifying, and thanks for the help Jens. There's a number of reasons why we had to choose this model but today we recommend having an issue type at the same level as the idea in the software backlog, at the Epic level or above. You could make it so the Epic doesn't have any description other than a link to the idea (which is why we added the option to embed a card for the idea in the epic's description) but I can't see ideas replacing Epics (because of a whole bunch of platform limitations). 

[Tanguy Crusson]

Hi @Brent Ritchie , we are currently designing a solution for this. Stay tuned.

[Brent Ritchie]

Thanks Tanguy!

[Max Herberger]

Teresa Torres ist doing some free product discovery for you guys here :D https://youtu.be/wJHM3ybdYEs?si=JyTHoJNz-UnC4z3-

[Max Herberger]

Please hurry D: 

[Kranthi Kiran Pulluru]

Hey folks, 

We are is working on an addon to JPD and Jira to bring in Opportunity Solution Trees into your workflow. 

Currently, our team is doing customer research to gain a better understanding of how teams are using JPD, and how they want to adopt ideas from Teresa's book for their product teams.
Would love to invite you for a short chat if you have something to share - https://calendly.com/thought-flow/opportunity-solution-tree-for-jira-customer-interview

[Matti Desmet]

@Tanguy Crusson such a system could be powerful:  https://clickup.com/features/mind-maps