Have you heard? My new book Continuous Discovery Habits is now available. Get the product trio's guide to a structured and sustainable approach to continuous discovery. 
I recently sat down with the Consider and Contact team at Hemnet to discuss why they switched from Miro to Jira Product Discovery for building their opportunity solution trees.
This was a detailed conversation where the team walked through:
- Why they started building opportunity solution trees in Miro and why that worked for quite some time.
- The limitations they eventually encountered as their trees grew bigger and their outcomes evolved.
- Why they choose Jira Product Discovery as their new tool of choice
- How they set up Jira Product Discovery to simulate opportunity solution trees even though the product doesn’t support a tree view by default.
- The limitations they face in Jira Product Discovery and the trade-offs they had to make for their new strategy to work.
- Key takeaways and lessons learned that they think other teams making a similar decision should consider.
I thoroughly enjoyed this conversation. As you’ll see in our discussion, no tool is perfect. When choosing a tool, it’s all about trade-offs. Each team has to decide for themselves which trade-offs they can live with and which they can’t.
I want to thank product manager Michelle Rea, UX designer Carl Törnquist, and software engineer Mattias Eriksson for taking the time to not just talk through their tool decision but for also showing in detail how they set it up and how they plan to move forward.
If you are looking for a new tool for creating opportunity solution trees, the video below is a must watch.
Are you new to opportunity solution trees? You can learn more here.
