How to Use Miro for Design Teams

Miro is an infinite canvas. That sounds like a feature, but for most teams it becomes a liability — boards with no structure, nobody knows where anything is, and the tool gets abandoned six months in.

The teams that get real value from Miro set it up intentionally from the start. Here's how.

Setting up your workspace

Miro organizes work into Teams and Projects. If you're a design team inside a larger company, create one Team for the design function and Projects inside it for each product area or initiative.

Name your boards clearly. "Workshop 1" tells you nothing in three months. "Q2 Discovery — Checkout Redesign — Affinity Map" tells you exactly what's on it.

Archive old boards instead of deleting them. You'll want to reference past workshops more often than you think.

Set editing permissions at the project level. Most boards should be editable by team members and view-only for stakeholders unless you're running a live session.

The built-in templates worth using

Miro's template library has dozens of options. Most are mediocre. These four are legitimately useful for design work:

Design Sprint. Covers all five days of the Google Ventures sprint format with pre-built frames for each activity. Useful even if you're not running a full sprint — the individual frames (Crazy 8s, voting, storyboarding) work standalone.

User Journey Map. A clean structure for mapping the steps, thoughts, emotions, and pain points in a user's experience. More useful than building this from scratch.

Affinity Diagram. Blank columns with sticky note areas — the right structure for synthesizing research observations into themes. Works well after user interviews.

Retrospective (4Ls or Start/Stop/Continue). The Miro retro format is clean and the anonymous sticky note mode prevents groupthink. Better than most dedicated retro tools.

Running async workshops

Async workshops are underused. You don't need everyone live at the same time for most activities.

How to set one up:

1. Create a board with clear instructions at the top — not buried in a frame header. Use a text card at the top left that says exactly what participants should do.
2. Assign a section per person (use colored frames labeled with names) so you can see who contributed what.
3. Set a deadline in the frame — "Add your stickies by Thursday EOD" written directly on the board, not in a Slack message that gets buried.
4. Use the voting feature to prioritize after async contributions close. Send a Slack message with the link and a deadline for votes.

Timers are available in Miro for live sessions. Use them aggressively — time-boxed activities get more focused output than open-ended ones.

Linking Miro to Figma and Notion

Figma: You can embed a Figma file directly into a Miro board using the Figma integration. The embed is live — it updates when the Figma file changes. Use this to put your mockups in context next to your research or journey map. In Figma, link back to the relevant Miro board in your file description or cover frame.

Notion: Paste a Miro board link into a Notion page and it embeds as a preview. For research projects, create a Notion page that acts as the project hub — embed the Miro affinity map, link to the Figma file, and include written synthesis. This gives stakeholders a single place to follow the work.

Start collaborating in Miro

Facilitation tips for remote sessions

Test your board before the session. A broken template link or permission issue five minutes into a live session kills momentum.

Don't give a tour of the board at the start. It bores people. Instead, give one instruction ("Add your name to a sticky and drop it in the icebreaker area") that forces them to interact with the board immediately.

Use the cursor tracking. During live sessions, say "follow my cursor" before navigating to a new area. This is the Miro equivalent of scrolling a shared screen.

Lock background elements. Grid lines, instruction cards, column headers — lock anything participants shouldn't move. You'll save yourself from the chaos of someone accidentally dragging your entire framework out of place.

Keep the camera on. Miro sessions where everyone has their camera off have less energy and less honest contributions. Enforce it gently by turning yours on and starting.

The frames that save the most time

A few Miro patterns that consistently work well for design teams:

Weekly design critique frame: A persistent frame where designers drop work-in-progress screens each week. Reviewers add stickies with feedback. No meeting required for simple reviews.

Research repository frame: A timeline-style layout showing all research activities, with links to deliverables. Keeps the whole team oriented on what research has been done.

Decision log frame: One sticky per major design decision, with reasoning and date. Becomes invaluable six months into a project when you can't remember why you went a certain direction.

Stakeholder map: A 2x2 or concentric circles layout showing who's involved in the project and at what level. Run this at project kickoff and update it when things change.

Design in Figma, collaborate in Miro

Miro works when it has structure. Give every board a purpose, keep the templates consistent, and maintain it actively. Boards that go stale are worse than no board at all — they send the signal that the team doesn't care about the process.