Miro

What Miro is and how it differs from a physical whiteboard

Miro is a proprietary cloud platform for visual collaboration. It brings notes, diagrams, documents, prototypes and other representations onto a shared canvas. Teams can work simultaneously or leave contributions for later review. Since 26 October 2026 it has belonged to Bending Spoons, following completion of the previously announced acquisition.

A physical whiteboard displays what fits on its surface and depends on people being present. Miro expands that space and preserves relationships, comments and context. The advantage is not filling an unlimited canvas, but helping a group understand a problem, compare interpretations and leave an outcome readable beyond the workshop.

Reference documentation: Miro — Company and leadership · Bending Spoons — Miro acquisition completed · Miro — Mapping and diagramming.

History, acquisitions and platform development

Andrey Khusid and Oleg Shardin founded RealtimeBoard in 2011 to share visual ideas with clients and teams outside the same room. Accel led its Series A in 2018. On 6 March 2019 it adopted the name Miro, inspired by artist Joan Miró and an ambition extending beyond whiteboarding.

• 2021–2022: Amsterdam became a co-headquarters alongside San Francisco. A $400 million Series C was announced in January 2022 during the expansion of distributed work. Funding is a business milestone rather than a measure of product quality.
• 2022: Around, focused on video communication, announced its acquisition by Miro.
• 2024: Uizard joined in June, bringing AI design and prototyping experience. In October Miro introduced Innovation Workspace, broadening its visual-work proposition.
• 2026: Miro announced the acquisition of Reforge, its team and products, subject to closing conditions. Canvas 26 introduced further AI workflows and connections; Bending Spoons completed its Miro acquisition in October.

The closing announcement identifies Khusid as CEO and co-founder. Current publications identify Jeff Chow as chief product and technology officer. Acquisitions explain the platform’s direction, but do not establish that every acquired product is integrated or included in every licence.

Reference documentation: Miro — Amsterdam co-headquarters, 2021 · Miro — RealtimeBoard becomes Miro · Miro — Rebranding account · Accel — Investment in Miro · Salesforce Ventures — Series C investment · Bending Spoons — Miro acquisition completed · Around — Acquisition by Miro · Miro — Uizard joins Miro · Miro — Reforge announcement · Miro — Innovation Workspace, 2024 · Miro — Canvas 26 developments · Miro — Jeff Chow, product leadership.

A visual workspace for thinking and testing ideas

Miro provides a visual board for organising notes, diagrams and other content. Frames divide working areas, structure a presentation and support content export. This helps separate stages of a discussion: context, observations, hypotheses and decisions. A board is particularly useful when a team needs to see how its contributions relate.

Its value is not an automatically generated conclusion, but making collective reasoning visible. Short notes can lose nuance, so add sufficient context and distinguish observations from proposed lines of investigation. A neat-looking diagram can still contain contradictory assumptions or incomplete information. Agree what the visual symbols mean before participants interpret them differently, and give uncertain claims an explicit place rather than forcing premature agreement.

Reference documentation: Miro Help — Frames.

Turning a canvas into an interpretable model

Shapes, notes and connectors represent processes, relationships, sequences and groups. Frames give sections a reading structure. A journey map describes stages and experiences; a process diagram describes activities and decisions. Choosing the format requires deciding which question the group is answering.

When describing a work task, distinguish activity, person or role, input, output and exception. A line between boxes may mean sequence, dependency or information exchange; define it in the legend. Without that convention, two people can agree with a drawing while understanding different processes.

Size and position also communicate. A large note does not necessarily describe a more important problem, and an isolated note may contain a critical exception. Preserve text labels and links to original observations rather than relying entirely on colour.

A simple check is to ask someone outside the workshop to explain the process from the board. If they cannot distinguish facts, decisions and questions, the model needs further organisation. Visual clarity is tested through others’ understanding rather than apparently tidy boxes.

Reference documentation: Miro Help — Frames · Miro — Mapping and diagramming.

Facilitation, Engage and independent contributions

Miro provides facilitation features such as timers and voting depending on the plan. Engage adds polls, scales, open questions, rankings and other canvas activities. Documentation lists general availability and inclusion in Business, Enterprise and Education from late June 2026; older descriptions as an add-on may be outdated.

Private mode temporarily obscures other people’s sticky-note content during contributions. It can prevent the first visible answer from influencing everyone else, but Miro warns that it is not a data-protection feature. It does not replace permissions for sensitive information.

A safety workshop can begin with individual contributions, continue with clarification and finish with agreed classification. Ask “At which stage did you observe this difficulty?” rather than vote on who is right. Voting orders preferences or discussion priorities; it does not determine harm probability or validate a control measure.

Facilitation should also accommodate people using phones, joining late or needing to describe observations verbally. An alternative contribution route and recorded context avoid confusing proficiency at moving notes with the quality of an insight.

Reference documentation: Miro — Engage activities · Miro — Private mode · Miro — Plans and features.

Sidekicks, Flows and AI prototypes

Sidekicks assist with canvas context. Flows connect steps that transform content into outputs such as documents, diagrams and prototypes. Access and allowances vary by plan. Prototypes creates and edits interface representations from instructions or visual references; a navigable screen is not yet an integrated, tested application.

In an OSH review, AI can group observations or prepare an initial summary while retaining links to original notes. Grouping “not enough space to unload” with “not enough time to unload” may hide two different problems behind similar wording. Review a group’s members and meaning before accepting it.

Miro states that these interactions are not used to train or fine-tune models or shared with providers for that purpose. Separately, it documents interaction collection for feature improvement and controls to disable it. Training policy alone does not describe every aspect of data handling.

A concrete prototyping use is testing how a guide is presented on screen: what appears first, how the version is identified and where questions go. Validation checks whether people understand the journey; it does not establish that a management system has been deployed.

Reference documentation: Miro — AI Workflows overview · Miro — Prototypes · Miro — AI security administration · Miro — AI quality improvements.

Integrations, external agents and asynchronous work

Integrations connect boards with execution tools. Jira Cards, for example, represents linked issues and synchronises information according to configuration. Distinguish a connected card from a manually copied note: the latter can become stale despite looking similar.

MCP allows compatible agents to access Miro context through authorisation and administrative controls. Connections may read or modify content according to enabled capabilities. Understand granted scope and output destinations before connecting; drawing a task on a canvas does not authorise every external operation.

Talktrack records explanations alongside work, including screen content or a call, for later review. An asynchronous explanation can avoid repeating a workshop, but needs a purpose and a reference to the explained version. If the board changes, the earlier narration may no longer describe it accurately.

At session close, identify which decisions stay documented in Miro and which actions move to another tool. Linking them avoids showing an executed idea as outstanding or an action as completed when it was merely transferred.

Reference documentation: Miro — MCP administration · Miro — Jira Cards · Miro — Talktrack.

Plans, access and connectivity

The offering distinguishes Free, Starter, Business and Enterprise, alongside educational options and add-ons. The free plan provides three active boards and no private boards. This matters during trials: free access does not make the plan suitable for every internal document.

Facilitation, export, AI and governance depend on edition and licensing. Compare editors, guest participation and required organisational controls. A budget based only on meeting attendance may not reflect actual workspace administration.

Miro runs in browsers and applications, but its documentation does not offer an offline mode equivalent to online collaboration. For a visit with uncertain connectivity, prepare an exported reference and a way to record findings afterwards. Network dependence should not become a surprise once the workshop begins.

A small pilot can test external access, simultaneous editing and retrieval of results. Include the least-privileged role. If only the creator can find or interpret the board, collaboration is not yet sustainable.

Reference documentation: Miro Help — Who has access to my board? · Miro — Free plan · Miro — Plans and features · Miro — System requirements.

Accessibility and preserving a readable outcome

Canvas accessibility depends on structure, contrast, text and assistive-technology support. Miro offers guidance and a checker, but a large, disorganised board can remain difficult to navigate. Use clear titles, a reading sequence and labels that do not rely solely on colour.

A text alternative should preserve the same useful information: context, observations, questions and decisions. An image alone is insufficient for someone unable to interpret it. A short navigation exercise before the workshop can reveal barriers without consuming the main discussion.

Exports support formats such as PDF, JPG, SVG and CSV depending on content, plan and device. Comments are not included in ordinary exports, and a board CSV does not preserve every visual relationship. A decision existing only in a comment may disappear from the delivered document.

To preserve a session, select relevant frames, place the date and version within the content and open the export. Check text, order, necessary links and unresolved questions. A complete but unreadable screenshot is less useful than an organised summary retaining important evidence.

Reference documentation: Miro — Accessible boards · Miro — Export boards.

Community, Distributed and Canvas

Shared templates and experiences contribute to Miro adoption. The organiser describes Distributed 2019 as its first virtual user conference, so an unsupported timeline beginning in 2017 is not repeated. Canvas 2024 continued community events and product-development presentations.

The reviewed company page reports more than 100 million users and 250,000 organisations. These provider figures do not automatically indicate daily use, effective participation or workshop outcomes. Adoption helps explain the example ecosystem but does not replace a suitability test.

When reusing a template, ask which method it represents and what assumptions it contains. A matrix for prioritising product ideas may provide visual inspiration, but its axes should not be presented as a validated occupational-risk assessment method. Adaptation needs a clear purpose and stated limits.

Reference documentation: Miro — Company and leadership · Miro — First virtual conference · Miro — Canvas 24 event.

Uses in participation and preventive learning

• Describing a task: map stages and interactions to prepare later observation of real work, without mistaking the diagram for a completed assessment.
• Preparing a participatory session: group questions and experiences so the team can identify missing information and who might provide it.
• Reviewing communication: place material versions beside comments from different audiences before writing the final version.

Sabentis proposes these as ways to organise work. Board participation does not guarantee representativeness: consider absent people, unequal digital access and the possibility that a dominant opinion displaces relevant experience. A facilitator should preserve differences that matter to subsequent investigation.

Worked example: separating facts, questions and proposals

Hypothetical example. A group is preparing to review a materials-receiving process. It wants questions for a workplace visit without treating explanations raised in the meeting as established facts.

1. Create separate frames for process description, reported facts, open questions and proposals. Add a legend explaining each area.
2. Request specific notes: what happens, when and in which context. Avoid personal names or details unnecessary to understanding the task.
3. Connect each hypothesis to the observation it attempts to explain. If evidence is missing, retain it as a question even where several people agree.
4. Assign each question a source or later observation capable of resolving it. Separate approved measures from ideas still requiring assessment.
5. Prepare a summary of decisions, questions and owners. Export the session reference and check that relevant frames and the date are retained.

The acceptable result is a list of verifiable questions and an accurate account of agreements. The session does not establish that real work matches the diagram or that a proposed measure is sufficient; those checks belong to the subsequent work.

Checking the case: 32 notes arrive. Clarification reveals nine distinct questions; the rest repeat points or provide context. Four are answered from current documents, three require workplace observation and two need another shift’s input. The summary retains all nine with status and source rather than reporting “32 risks” or “32 improvements”. A week later, the three observations are added with dates and results, even if they contradict the initial drawing. Acceptance requires tracing each conclusion back to its question and evidence. Unresolved minority views remain visible.

Reference documentation: Miro Help — Frames.

Participation, information exposure and closure

Miro allows boards to be shared through several routes. Its documentation explains that where access levels overlap, the highest access applies. An individual viewing invitation does not restrict someone who also has editing rights through a team or public link. Review all access routes before adding internal information.

Moving and grouping notes can hide disagreements. Retain unresolved questions and avoid treating a vote as technical validation. If the board changes after the meeting, identify the version supporting the summary. Offer an alternative for participants with access or reading difficulties so they can contribute without depending entirely on a visual whiteboard. A participant’s silence should not automatically be recorded as agreement.

Reference documentation: Miro Help — Who has access to my board?.

When to choose Miro and what should leave the board

Miro fits exploration, workshop preparation and shared explanation-building. Before choosing it, check participants can use it and that the visual format adds value. A very large board may make a specific decision harder to find afterwards.

After a workshop, Notion can help retain a written explanation, while Asana can organise agreed tasks. Decide where the approved result is held and link to it from the board so a preliminary idea does not continue circulating as an instruction.

Frequently asked questions about Miro in OSH

Does a workshop map prove how work is done?

No. It records participants’ descriptions. Reconcile them with actual work and other sources when the decision requires it.

Does voting for a proposal mean it is safe?

A vote expresses group preferences, not a technical assessment. Suitability requires appropriate criteria and review.

What should be retained afterwards?

Context, participants or represented roles, decisions, open questions, owners and a dated content reference. Retain only necessary personal information.

Reference documentation: Miro Help — Frames.