RETROSPECTIVE RECORD · PREPARED 16 SEPTEMBER 2026The archive · 100 retrospective records ↗
productivityatlas.

The archive / Platform change

Platform change / From the archive · 6 March 2019 event · prepared 16 September 2026

A whiteboard renamed itself a year before remote work needed it

Miro's 2019 rebrand post explains why RealtimeBoard changed its name, months before remote work made whiteboards common.

Visual published with the cited source for this record: A whiteboard renamed itself a year before remote work needed it
Visual published with the cited source, shown for identification of the record. Credit: miro.com · source page ↗ Rights: owner-review-pending.

A rename, dated and explained

On 6 March 2019, the company behind an online whiteboard called RealtimeBoard announced it was renaming itself Miro. Founder and chief executive Andrey Khusid wrote that the earlier name no longer reflected what the product had become, and that the company wanted a name that is direct and defines a brand-new category of collaboration tools, rather than one describing the mechanic, a shared board, alone. Miro's company page traces the product back further, to 2011, when Khusid built a first version to help his design agency communicate with remote clients, an origin the rebrand announcement frames as evidence the company understood distributed work before the term was common.

Who a whiteboard is for, and what it does differently

The announcement's stated reasoning treats a whiteboard as a distinct category from a document: a space where a team looks at the same spatial layout together, in real time or asynchronously, rather than reading linear text in turn. Khusid described the whiteboard as sitting at the centre of a lot of team ceremonies, meaning workshops, retrospectives and planning sessions where the value is seeing relationships between ideas laid out, not only recording a decision. That is a genuinely different task from a shared document or a chat thread, and it explains why the rename bet on visual collaboration as a durable category rather than a feature of some other tool.

What the announcement could not have known

The rebrand happened roughly a year before large numbers of teams were forced into remote work, a timing the company's own retrospective materials now present as prescient. That framing should be read carefully: a 2019 name change was a bet on a growing category of distributed teams, not a forecast of a specific global event, and the announcement itself makes no such prediction. Miro's about page states the company now serves more than 100 million users in 250,000 organisations, a figure describing the platform today rather than at the time of the rename, and it should be read as a current company claim rather than a historical measurement from 2019.

Questions to ask before you adopt it

  • Does your team's work benefit from a shared spatial layout, or would a linear document serve the same purpose?
  • How much of the value depends on live, same-time collaboration versus asynchronous contributions over days?
  • What happens to board content and structure if you need to export it to another tool later?

A rename is a marketing decision, not proof of product quality, and the 2019 announcement should be read as the company's own account of its reasoning rather than an independent assessment. What it does establish reliably is the date and the stated intent: a whiteboard company chose to be named for what it does, ahead of the moment that made the category obvious to everyone else.

Sources & reading trail

RealtimeBoard is Now Miro ↗

Dates the rebrand to 6 March 2019 and gives the founder's stated reasoning for the name change.

Source published: 6 March 2019 · Retrieved: 16 September 2026

About Miro ↗

Traces the product's 2011 origin as RealtimeBoard and states the company's current scale.

Source published: Not established · Retrieved: 16 September 2026

Announcements and papers establish the record; the friction reading and the adoption questions are Productivity Atlas editorial analysis. This retrospective draft does not imply the site published on the event date.