What do you dislike about Miro?
CSV import is the one that bit me this week. Upload a spreadsheet and you get a table object on the canvas, not sticky notes — so a grid of items I wanted as draggable cards had to be unpacked by hand. Small thing, but it's the obvious behaviour and it isn't the default.
Pricing is the bigger issue for an agency. Editor seats are fine for the core team, but we have people who touch a board twice a quarter and paying full freight for them is hard to justify, so we end up working around it. Some AI features also sit a tier higher than I'd like given how much they're pitched.
Very large boards will chug on older laptops, which shows up when a client joins on whatever machine their IT gave them. The mobile app is fine for reviewing but I wouldn't build on it.
Support answers are good when they come, but the first reply is usually a docs link before anyone actually reads the ticket. Review collected by and hosted on G2.com.
Recommendations to others considering Miro:
In the past our planning process used to result in information being leaked. Each workshop would end with a whiteboard, after which someone would take a photograph of it, another person would retype what was on the board into a document, and within a week the document and the version that people remembered would have diverged. Nowadays the whiteboard is the record of the meeting. We copy it every week, the decision log is carried forward, and when four weeks are placed side by side it is possible to see exactly where the same obstacle keeps reappearing.
Specifically, the time spent on client kickoffs decreased from a two-hour session together with a half-day devoted to writing it up to just the session itself combined with about twenty minutes. AI clustering now carries out the initial review of the 80 workshop stickies in one minute rather than half an afternoon. For all the projects we manage, this amounts to a few hours each week being returned to each project team.
The second problem it dealt with was that of client reviews. When a view-only link is sent, the feedback appears on the board alongside the item it refers to, rather than arriving as a WhatsApp voice note about 'the third screen'. This results in fewer rounds and fewer misinterpretations. Review collected by and hosted on G2.com.
What problems is Miro solving and how is that benefiting you?
In the past our planning process used to result in information being leaked. Each workshop would end with a whiteboard, after which someone would take a photograph of it, another person would retype what was on the board into a document, and within a week the document and the version that people remembered would have diverged. Nowadays the whiteboard is the record of the meeting. We copy it every week, the decision log is carried forward, and when four weeks are placed side by side it is possible to see exactly where the same obstacle keeps reappearing.
Specifically, the time spent on client kickoffs decreased from a two-hour session together with a half-day devoted to writing it up to just the session itself combined with about twenty minutes. AI clustering now carries out the initial review of the 80 workshop stickies in one minute rather than half an afternoon. For all the projects we manage, this amounts to a few hours each week being returned to each project team.
The second problem it dealt with was that of client reviews. When a view-only link is sent, the feedback appears on the board alongside the item it refers to, rather than arriving as a WhatsApp voice note about 'the third screen'. This results in fewer rounds and fewer misinterpretations. Review collected by and hosted on G2.com.
