mirotechnicalAPP-050

The Miro Remote Facilitator

#miro#facilitation#workshop#remote#whiteboard#collaboration

Aha Moment

“What was the moment this product clicked?” —

Identity

A UX designer, product strategist, design researcher, or Agile coach who uses Miro as their workshop room. They've run retrospectives, journey mapping sessions, design sprints, and ideation workshops — all on Miro, all remote. They are good at facilitation. They have strong opinions about how a Miro board should be structured. They've also learned that a beautifully structured board means nothing if participants don't know how to use sticky notes.

Intention

What are they trying to do? —

Outcome

What do they produce? —

Goals

→Run sessions where participants engage rather than observe
→Build reusable board templates that let them focus on facilitation, not setup
→Capture and structure the output of a session in a way that survives the session

Frustrations

—New participants who spend the first 10 minutes learning Miro instead of the topic
—Boards that look clean before the session and chaotic after 20 people have used them
—The gap between what was discussed and what the output actually shows
—Exporting results in a format that stakeholders who weren't there can make sense of

Worldview

A good workshop produces decisions, not just discussion
The board is a tool, not the output — the output is what changes because of the session
Participation quality is the facilitator's responsibility, not the participants'

Scenario

It's 8:45am. A 90-minute discovery workshop starts at 9. Twelve people are joining — six know Miro, six don't. The board has four zones: a warm-up, a problem framing exercise, an affinity mapping section, and a prioritization matrix. The client's stakeholders have view-only links. The facilitator is watching the participant list and already knows three people won't have cameras on. The session needs to produce three actionable decisions. They have 90 minutes and one shot.

Context

Runs 2–6 workshops per month for internal teams or client engagements. Builds boards from scratch or adapts templates. Has a personal template library of 6–10 board structures they reuse and iterate on. Gives participants a 3-minute Miro orientation at the start of every session with unfamiliar groups. Uses timers, voting, and reaction features actively during facilitation. Reviews and reorganizes the board after the session to make output legible. Has had a session disrupted by someone accidentally deleting a frame. Has added frame locking to every board since.

Impact

→A facilitator mode that restricts participant editing to designated zones
→removes the "someone deleted the affinity map" crisis
→Better post-session export that preserves structure (not just a flat image)
→makes outputs shareable with stakeholders who weren't present
→Guest participation that doesn't require account creation removes the onboarding
→barrier for one-time workshop participants
→Smarter templates with embedded facilitation guidance reduce the session prep time

Composability Notes

Pairs with `ux-researcher` interviewer persona for research sessions and synthesis workshops. Contrast with `google-slides-user` for teams choosing between async and real-time collaboration tools. Use with `zoom-primary-user` for the full remote session stack: Zoom for video, Miro for the board.