Miro: foundation in our arsenal
Overall Satisfaction with Miro
We generally use Miro for lateral communication among stakeholders with different backgrounds/specializations. It's generally difficult to maintain multiple versions of documents for business and technical team members working on the same project, and giving each a "dashboard"-type experience to directly access relevant information without being overwhelmed with unnecessary details. Miro helps us circumvent that by giving us a "level of details" structure to get the point across as needed without splitting documents into markdown and PPTs.
Pros
- Team knowledgebase
- Progress tracking
- Realtime collaboration
- Adequate permissions system
- Useful template library
Cons
- Custom hosting solution to have Miro on our own platforms
- Better Office integration
- Expanded Agile development tools
- Reduced onboarding time
- Better outsource communication and more value for buck
- Easier tracking of employee progress
Generally, our board start out as idea boards where we collectively post our research and background information for each project. This lets us bring everyone up to speed no matter what their background is (especially for our more domain-specific products) and then we organize the board into UX, high level development, areas needing research, requirements, etc.
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?
Yes
Did implementation of Miro go as expected?
Yes
Would you buy Miro again?
Yes


Comments
Please log in to join the conversation