How Miro builds product: Lessons on competition and moving fast

Executive overview

Building a product is like playing chess against competitors—every release moves you forward or backward. Miro's approach centers on three core principles: embracing competition as a clarifying force, maintaining a team-centric architecture, and prioritizing speed to learn faster than the market. The company uses cross-functional teams, continuous quality calibration, and rapid iteration to stay ahead despite intense market competition.

Core insight: Products never remain the same; with each release you gain or lose ground against competitors.

Understanding your competitive position

Products either improve or decline—stagnation is impossible when competitors constantly ship. The lens of chess moves clarifies what to invest in: every feature either gains you ground or loses it. Your growth trajectory is directly tied to what competition allows you to do. Focus on deep differentiation rather than feature parity.

Why Miro's architecture resists commoditization

Three structural advantages compound over time. First, Miro was built from inception as a multi-persona, team-centric platform, not as a single-use tool extended to teams. Second, the product spans industries (tech, healthcare, manufacturing, aerospace, construction) rather than staying laser-focused on one vertical. Third, certain capabilities are genuinely difficult to replicate without rearchitecting: advanced workshop facilitation, deep agile integration, and asynchronous collaboration at scale.

The AMPED organization structure

Product teams sit within a cross-functional unit called AMPED: Analytics, Marketing, Product, Engineering, Design. Product marketing is embedded at the team level, not separate, so positioning and competitive differentiation happen during feature design, not after. This prevents the classic trap of building cool features customers don't care about.

Maintaining holistic product coherence

Persona-based streams can fragment product experience. Miro corrects this through: structured product reviews for all work (small to medium shared across product org; large work goes through formal gates), a checklist of enterprise requirements that democratizes best practices across all teams, and a culture where cross-functional members actively call out inconsistencies from other angles.

The power of small rituals

MiroConnect, an every-other-Friday event in each hub, surfaces unexpected expertise. Engineers in Berlin saw a team struggling with a three-month feature and implemented it in three hours because they had solved it before. These moments of serendipitous collaboration prevent siloed rework and build organizational cohesion.

Speed as a competitive weapon

Innovation-centric companies win by hitting the brick wall first—learning from failures faster than competitors can move. Speed matters more than perfection when discovering new experiences. The key is removing blockers, not hectoring teams to "move faster." When PMs raise their hands about technical, organizational, or priority challenges, leadership unblocks immediately. This creates a virtuous cycle: early wins build courage to tackle bigger challenges; pattern-matching on solved problems compounds organizational capability.

Measuring progress without overhead

Miro uses a motto—"deliver customer value faster with high quality"—as the organizing principle. Underneath: track whether shipped features moved the metric you predicted, measure cycle times across phases (P-Strat → P0 definition → P1 solution → P2 metric validation), classify work by complexity (small, medium, large), and publish aggregate data so teams benchmark against peers. No surprises, no surprises, just pattern matching. Six-month OKRs with monthly traction reviews replace quarterly replanning overhead.

Building quality muscle

Quality is hard to define in writing but easy to recognize through examples. Design leadership reviews monthly releases and classifies each as high or low quality with brief reasons (e.g., "inconsistent button placement," "missing error state"). Over time, designers see patterns. It's a reinforcement-learning approach to embedding standards without rigid rules.

Roadmaps that serve both customers and agility

Rolling six-month roadmaps with 80% precision for months 1–3 and 50% for months 4–6 give enterprise customers visibility while preserving the agility to pivot on competitive threats, technology breakthroughs, or customer insights. Annual strategy whitepapers articulate key bets and why; teams cascade those into rolling roadmaps.

Competitive differentiation: Positioning and packaging

Do not assume "don't worry about competition, just focus on customers" is right. Understand what competitors can do, their distribution strength, their pricing leverage. Be crystal clear about your unique value relative to alternatives. Package and position those differences explicitly so customers see why you coexist in their tech stack rather than being a better version of something else. Every release either gains or loses chess points.

Innovation vs. maintenance allocation

Horizon One (core business) gets ~70% of resources; Horizon Two (adjacent, 12–36 months out) gets 20%; Horizon Three (3–5 year bets) gets 10%. Within teams, 20–40% of capacity typically goes to tech debt, platform scaling, and architecture—this varies by team criticality. Most teams allocate 60–80% to shipping new value.

Miro's growth model

Product-led growth remains the primary flywheel. Key accelerants: workshops (one person invites 50+, introducing many to the product), Miroverse templates (the FIFA World Cup template got 100K views and 15K copies, ranking in Google search), and integration with sales for enterprise expansion. As the business scaled, high-touch enterprise channels now drive significant adoption because those customers run hundreds of thousands of workshops, multiplying reach.

Working with sales as a PLG company

Bridging self-serve and high-touch is hard work. Embed product marketing across both channels so they carry customer insights from sales back to product and vice versa. Design explicit handoff processes: accounts start self-serve, adoption triggers qualification, sales engages, expansion happens. Treat them as two channels of the same product, not competing units. The relationship remains a work in progress at Miro.

Product leadership development

Product leaders operate in two personas. In the stream-leader role, relentlessly drive improvement—today vs. yesterday, tomorrow vs. today. In the product-leadership-team role, drive accountability: ensure leaders are making right bets for the company. Feedback is most effective when posed as open questions rather than statements, grounded in empathy and business outcomes. Publicly receive feedback and model vulnerability to build trust and psychological safety.

Future roadmap highlights

Miro AI is rolling into general availability. New team rituals capabilities include perspectives (private voting during retros, one-click reveal), deep Jira integration for dependency mapping and program increment planning, sprint planning, and estimation automation. The roadmap increasingly centers on enabling cross-functional teams to run entire workflows asynchronously and synchronously within Miro.