Switching from Miro to Jira for OST

Question

Hi Community,

I wanted to share a video that I found particularly insightful. It’s a talk where Teresa Torres discusses with the Hemnet company their experience with Miro and Jira Product Discovery (JPD), and their reasons for transitioning from Miro to Jira.

Tools of the Trade: Switching from Miro to Jira Product Discovery for Opportunity Solution Trees - Product Talk

In our case, Miro still seems to be the preferred tool for Opportunity Solution Trees (OST), while we use JPD for evaluating new product ideas and opportunities.

I’m curious to hear your thoughts on this! How are you balancing these tools in your workflow?

Looking forward to the discussion!

Cheers,
Annie

Annie Ioceva _Nemetschek Bulgaria_ · Answer

See my highlights from the video:

Miro for OST

* Miro is great for getting started quickly with Opportunity Solution Trees (OST) due to its unstructured nature.
* However, as the OST grows, it can become cluttered, making it harder to manage and understand. Reorganizing the layout, making space for new elements, can be time-consuming, managing multiple trees becomes challenging. Searching in which tree was an idea captured is time consuming. 
* Miro is best suited for small to medium OSTs where its visual simplicity is an advantage.

Jira for OST

* Jira Product Discovery offers a more structured environment, which is better for medium to large OSTs, though it requires some training to configure effectively.
* Jira Product Discovery organizes data in table view, has many features to search, filter, save views, organize a roadmap.  
* Jira lacks a tree view and is less visual. No way to model a sub-opportunity. 
* If your team is new to OST, starting with Miro might be easier. Once your OST grows, consider moving to Jira, especially if your teams already use Jira for sprints and releases.
* Many teams use both tools and link Miro cards to Jira issues

Modeling Tips in Jira:

* Use categories to represent opportunities and ideas to capture solutions.
* Link an idea to a category and group by category to get a one level tree view.
* Create one special idea for each category - to capture opportunity details.
* Save different views for various opportunities to make navigating the OST easier.
* Represent Objectives and Key Results as custom fields.

I hope this summary would be helpful for teams looking for ways to represent OST in Jira :)

Cheers,

Annie

Tanguy Crusson · Answer

By the way @Annie Ioceva _Nemetschek Bulgaria_ we've started working on a handbook to explain how you can adopt JPD for things like this.

You can find it here: Jira Product Discovery handbook.

Tanguy Crusson · Answer

Thanks for sharing @Annie Ioceva _Nemetschek Bulgaria_ ! In the JPD team we do the same as you do: collaborate in whiteboards (Confluence Whiteboards in our case) to workshop the product strategy - then JPD for driving things forward.

Here's an example of whiteboard (after we've cleaned it up) for how we think of strategies laddering up to product and company goals:

And how we translated that into a roadmap in JPD for 6 months worth of investments: