By following this guide, you will plan and run a full five-day Design Sprint inside Miro, producing a tested prototype ready for developer handoff. Expect the setup to take two to three hours and the sprint itself to run across one week with a team of four to seven people.

What You'll Build

  • A reusable Miro board structured across all five Design Sprint phases
  • A completed problem statement, How Might We wall, and a prioritised solution sketch
  • A clickable prototype validated with at least five real users
  • A sprint report exportable to Notion or Confluence for stakeholder sign-off

Prerequisites

  • Miro account with a paid plan (Starter or above for unlimited boards, as of 2026)
  • A defined product challenge or business problem to solve
  • A sprint team of four to seven people, including at least one decision-maker
  • A shared calendar with five days blocked, or an async alternative schedule
  • Basic familiarity with Miro frames, sticky notes, and voting features

Step 1: Set Up Your Miro Sprint Board

Create a new board and name it after your sprint challenge. Use the Miro Frames panel to add five frames in a horizontal row, one for each day of the sprint. Label them: Map, Sketch, Decide, Prototype, and Test.

Why does the frame structure matter?

Miro's frames act as slides during presentations. A clean frame-per-day structure lets you walk stakeholders through the sprint narrative without scrolling chaos. It also lets you lock completed frames so no one accidentally edits Monday's work on Friday.

Within each frame, add a header sticky note with the day's goal and a timer widget set to the main session length. Miro's built-in timer is reliable enough for facilitated sessions, though some teams prefer a shared Cuckoo timer tab for visibility across screens.

Common pitfall: Leaving the board unstructured at the start means teams spend the first session orienting themselves rather than working. Spend thirty minutes on board setup before anyone else joins.

Step 2: Run Day One (Map) as a Structured Workshop

Day one is about aligning the team on the problem. Open with a long-term goal statement using this prompt: "In two years, the product will [outcome]. We know we have succeeded when [metric]." Write this as a large sticky note anchored to the top of the Map frame.

How do you capture the How Might We questions efficiently?

Ask each participant to add sticky notes in silence for ten minutes, each starting with "How Might We...". Use Miro's bulk-create sticky feature to pre-populate a column for each person. After ten minutes, everyone votes with dot stickers, and you cluster the top-voted notes into themes using Miro's clustering tool.

End the day by defining a sprint target: one specific user action on the journey map that the prototype must address. Write it in a different colour sticky and place it at the centre of the Map frame. This single artefact keeps the rest of the week focused.

Pro tip: Record the Day One session using Miro's embedded video widget. Teams in Australia and Canada often run sprints across time zones. An async-friendly recording means a remote participant in Sydney can review the session before the Day Two sketch starts.

Step 3: Run Day Two (Sketch) With the Four-Step Sketch Method

Day two produces individual solution sketches. Each participant works alone. Use Miro's personal frames feature to give each person a private workspace within the board so they cannot see each other's work during the sketching phase.

The four-step sequence is: Notes, Ideas, Crazy 8s, and Solution Sketch. Run each step in Miro using a dedicated zone inside each personal frame.

What is the Crazy 8s exercise and how long should it run?

Crazy 8s asks each person to sketch eight rough ideas in eight minutes. In Miro, use the whiteboard pen or shape tools. Eight minutes is strict. Set the Miro timer and do not extend it. Speed forces participants to bypass their inner editor and produce quantity over quality.

At the end of Day Two, each person creates a three-panel solution sketch on a template frame. The template should show a clear beginning, middle, and end of the user interaction they are proposing. Share a locked template at the top of the Sketch frame that participants duplicate.

Common pitfall: Teams skip the Notes step and jump straight to sketching. Notes is where participants pull in research, data, and competitor references. Without it, sketches are based on assumptions rather than evidence.

Step 4: Run Day Three (Decide) With a Structured Vote

Day three is about picking one idea to prototype. Start with an Art Museum walk: everyone reads all solution sketches silently and places dot stickers on parts they find compelling. Allow one dot sticker per person per sticky note, and give each person ten dot stickers total.

How do you handle disagreement between the decision-maker and the team vote?

The decision-maker gets a "supervote" of three large dot stickers. Their vote overrides a popular but misaligned idea. This is by design in the original Design Sprint methodology from GV. Make the supervote visible and explain the rule before voting starts. It removes ambiguity and keeps the sprint moving.

Once a winner is chosen, create a storyboard in the Decide frame. The storyboard has ten to fifteen panels showing every screen or step the user will experience in the prototype. Use Miro's grid template to lay out the panels in sequence.

Pro tip: At Lenka Studio, we export the Day Three storyboard to a shared Notion page so stakeholders who are not in the sprint can review it asynchronously before the prototype build begins.

Step 5: Build the Prototype on Day Four

Day four is prototype day. The storyboard from Day Three becomes your build brief. You have a choice of tools here.

For teams using Figma, use the Miro-to-Figma plugin (available natively in the Miro marketplace as of 2026) to copy storyboard panels directly as reference frames into Figma. This saves about forty-five minutes of manual redrawing.

For quick clickable prototypes without a designer, use Miro's own prototype mode. Connect frames with hotspot links. Miro's prototype mode supports basic tap navigation and is good enough for user testing on Day Five, especially for concept validation rather than usability testing.

What if the prototype is too complex to finish in one day?

Scope the prototype to cover only the sprint target defined on Day One. If the sprint target was "user completes a booking in under three taps", build only those three screens. Do not add edge cases or error states. A focused prototype tests the core assumption. A bloated prototype tests nothing reliably.

Common pitfall: Teams spend Day Four perfecting visual design instead of testing the idea. The prototype should look realistic enough to provoke honest reactions. It does not need to match your production design system.

Step 6: Run User Testing on Day Five

Day five is the most important day and the one teams most often under-resource. Recruit five participants. Research by Nielsen Norman Group confirms that five users uncover approximately eighty-five percent of usability issues in a test session. More than five adds diminishing returns for a sprint context.

How do you run remote user tests directly in Miro?

Use a separate Miro observation board. Create one row per participant with four columns: Observations, Quotes, Patterns, and Actions. Each sprint team member watches one session and takes live notes in their column. This is faster and richer than a post-session debrief.

For the prototype, share a public Miro link with the participant and ask them to think aloud as they navigate. Record the session with Loom or your video conferencing tool. After all five sessions, the team clusters the observation board and identifies the top three patterns.

Pro tip: If your target audience is in Singapore or the US and your team is in Bali, use UserTesting.com or Maze to recruit participants who match your market. Both tools integrate with Figma prototypes and return session recordings within hours.

Step 7: Export and Document Your Sprint Findings

After Day Five, export the sprint into a format your broader team can read. Miro's export function supports PDF and PNG for individual frames. For a structured report, use Miro's built-in presentation mode to walk through each day's frame in sequence.

Create a sprint summary document with four sections: the problem statement, the chosen solution, the test findings, and the recommended next actions. Teams at Lenka Studio use a Notion template linked directly from the Miro board so the report is always one click away from the source artefacts.

Tag your Miro board with the project name, sprint date, and outcome status (validated, invalidated, or inconclusive). This creates a searchable sprint archive over time, which is useful when a similar problem resurfaces six months later.

If this sprint surfaced questions about whether your broader brand or product positioning is aligned with what users responded to, a quick brand health score assessment can help you identify gaps before the next sprint begins.

Frequently Asked Questions

Can you run a Design Sprint in fewer than five days?

Yes. Many teams run three-day or two-day compressed sprints. Map and Sketch can merge into Day One if you have existing research. The tradeoff is less divergent thinking and smaller solution variety. For a complex problem, five days produces more reliable results.

Does Miro work for in-person Design Sprints as well as remote ones?

Yes. Miro works in hybrid and fully in-person settings using a shared screen or individual laptops. The advantage over physical whiteboards is that the board is automatically archived, searchable, and shareable with stakeholders who were not in the room.

What if a key stakeholder cannot attend all five days?

The decision-maker must attend Day Three to cast the supervote. Days One, Two, Four, and Five can be covered through async video recordings and board comments. Missing the supervote entirely is the one scenario that stalls a sprint, because no one else has authority to commit the organisation to a direction.

How is a Design Sprint different from a regular workshop?

A Design Sprint produces a tested prototype in five days. A workshop produces alignment, documentation, or a prioritised backlog. The sprint's defining feature is the user test on Day Five. Without real user feedback, it is a workshop with sticky notes, not a sprint.

What Miro plan do you need to run a full sprint?

The Miro Starter plan (paid, as of 2026) supports unlimited boards and up to three editors per board, which is enough for a small sprint team. For teams larger than three active editors working simultaneously, the Business plan removes that restriction. The free plan limits you to three boards total, which is not practical for ongoing sprint work.

Next Steps

Your sprint board is now a reusable template. Duplicate it before each new sprint and update the problem statement. Over three or four sprints, you will have a board structure that fits your team's rhythm and needs less facilitation overhead each time.

If you want to move from a tested prototype into a full product build, the handoff from Miro to Figma to development is the next challenge. If your team needs help structuring that process or running a sprint for a product you are planning to build, get in touch with the Lenka Studio team. We run Design Sprints for product teams across Australia, Singapore, Canada, and the US, and we can run one for you remotely or as a facilitated engagement.