![Sanjay M.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Sanjay M.")
SM

Sanjay M.

Managing Director

Consulting

Small-Business (50 or fewer emp.)

8/13/2026

"Fishbone diagrams for root cause analysis are a game changer"

5/5

What do you like best about Mindomo?

I do UX research and use Fishbone (Ishikawa) diagrams weekly for root cause analysis after usability sessions. Mindomo added Fishbone as a first-class diagram type, and it's genuinely well-implemented — you can build it out with the same TAB/ENTER speed as a regular mind map, and if the analysis grows beyond a fishbone shape, I can convert it into a concept map without losing anything. Being able to attach interview clips (audio recordings) and screenshots directly to the "cause" branches means my whole analysis lives in one artifact. Review collected by and hosted on G2.com.

What do you dislike about Mindomo?

Nothing that affects my workflow. A minor thing: when I share a fishbone with stakeholders unfamiliar with the format, they occasionally need a quick orientation but that's on the diagram type itself, not Mindomo. Review collected by and hosted on G2.com.

What problems is Mindomo solving and how is that benefiting you?

Root cause analysis used to live in a mix of Miro sticky notes and a text doc summary. Now the analysis, the evidence (audio, screenshots), and the write-up notes all sit in one Mindomo diagram I can export as a PDF report for the team. Review collected by and hosted on G2.com.

Show More

Current UserValidated ReviewerSource: Organic

See what 95 reviewers think of Mindomo

4.9 out of 5 · Verified reviews from real users

[
Read all reviews
](https://www.g2.com/products/mindomo/reviews)