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

Teresa Torres describes a conversation with the Consider and Contact team at Hemnet about moving their opportunity solution trees from Miro to Jira Product Discovery. The team initially found Miro effective, but as trees grew and outcomes evolved, the canvas became hard to maintain. They adopted Jira Product Discovery and configured it to simulate a tree, even though the tool lacks a native tree view. The post's central point is that no tool is perfect, so choosing one is a matter of deciding which trade-offs a team can accept. The piece is a brief pointer to a video walkthrough rather than a standalone argument, but it signals a practical question many discovery teams face.

01Key takeaways

• No discovery tool is perfect, so evaluate options by deciding which trade-offs your team can live with.
• A whiteboard like Miro can work well early on but may strain as opportunity solution trees grow large.
• Tools lacking a native tree view can still be configured to simulate an opportunity solution tree.
• Changing tools should be driven by how your outcomes and tree size evolve, not by trend.
• Watch how other teams set up and maintain their trees before committing to a new workflow.

02Key sections

Why Miro worked at first

The team began building opportunity solution trees on a Miro whiteboard, which suited them well for a long period. The visual, freeform canvas made early tree building easy to share and discuss.

Limits as trees grew

As trees expanded and outcomes changed, maintaining the whiteboard became harder. The conversation covers the friction that led the team to reconsider their tooling.

Choosing Jira Product Discovery

The team explains why they selected Jira Product Discovery as their new home for discovery work. They also show how they simulated a tree despite the absence of a native tree view.

Trade-offs and takeaways

The team discusses the limitations they accepted in the new setup and lessons other teams should weigh. The overall message is that tool decisions revolve around trade-offs each team must judge for itself.

03From the post

“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”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.