Item: Miro
Rating: 8
Author: Piyush Patel

Overall Satisfaction with Miro

Use Cases and Deployment Scope

I use Miro to document the Architecture diagram. Earlier I used Visio and Lucid. Sometimes we use template for our retrospective meeting.
Business problem : Document the architecture diagram of the business processes.

Pros and Cons

Pros

Flow chart
Architecture diagram
Retrospective meeting template
Online workshop to collect ideas

Cons

folder structure like lucid
sharing mechanism is bit confusing - when to use space vs teams
loading time when we have too many diagrams

Return on Investment

Quick to document
Easy to share within org
Comments and Edit mode

Usability

For our team's day to day work, we use Miro.. We lack feature like lucid folder structure hence the rating.

Tool Usage

template, comments, time keeping, innovation and ideation template

Reduced Tool Overload

yes we were able to decomission few tools and application which were overlapping with Miro capabilities. Miro seems all in one. Reusable templates help to start quick and share.

Alternatives Considered

Lucid Reality Labs

Lucid user experience is not that great and seems built for architecture or flow chart only.

Key Insights

Do you think Miro delivers good value for the price?

Yes

Are you happy with Miro's feature set?

Yes

Did Miro live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Miro go as expected?

Yes

Would you buy Miro again?

Yes

Likelihood to Recommend

Perfect to document architecture diagram - quick and easy to show relationships. Whether its system level architecture or data model architecture.

Comments

Please log in to join the conversation

Miro as Architecture tool