Lenny's PodcastAn inside look at how Miro builds product | Varun Parmar (CPO of Miro)
CHAPTERS
- 0:00 – 0:31
Teaser: Competing release-by-release in a crowded market
Varun opens with a memorable framing: every production release makes your product better or worse—never the same. In competitive markets, each ship is effectively a “chess move” against competitors, and that lens creates clarity on impact.
- •Products never stay static; every release changes the perceived quality
- •Customers implicitly compare your releases to competitors’ releases
- •Think of shipping as gaining/losing points over time
- •Competitive context can sharpen prioritization clarity
- 0:31 – 4:02
Show setup: Why Miro’s product culture is worth studying
Lenny introduces Varun (CPO of Miro, former CPO at Box) and sets the agenda: go deep on Miro’s product principles, process, speed, and quality. He also tees up Miro’s growth in a highly competitive space.
- •Varun’s background and why Lenny sought him out
- •Focus areas: product values, process, competition, speed, quality
- •A preview of concrete rituals (e.g., company-wide demos)
- •How Miro grew despite intense category pressure
- 4:02 – 5:17
Varun’s entry point and Miro’s global footprint
The interview begins and quickly clarifies Miro’s global operating model. Varun explains Miro’s hubs and the split between a Europe-centered product org and a worldwide go-to-market org.
- •Miro operates across ~12 hubs globally
- •Product org primarily based in European hubs
- •Go-to-market presence is global across regions
- •This structure shapes internal collaboration norms
- 5:17 – 9:16
Operating cross-culturally: Empathy and teamwork as “anti-silo” defaults
Varun describes how distributed teams force Miro to practice empathy not just with customers, but internally across time zones and functions. He highlights teamwork as a core CEO-driven value to reduce functional silos and improve co-creation.
- •Empathy used for both customer insight and internal alignment
- •Product org must deeply understand field/sales/customer perspectives
- •Teamwork is treated as a foundational operating philosophy
- •Cross-functional co-creation drives better outcomes
- 9:16 – 11:48
Empathy in action: Design sprints and the origin story of Miro Talktrack
Varun shares how Miro uses the five-day design sprint framework to validate hypotheses quickly. He explains how customer empathy during prototyping led to Talktrack’s distinctive approach: synchronizing board movement with audio/video to preserve collaboration (not just communication).
- •Design sprints used to validate concepts quickly (5-day loop)
- •Talktrack choice: synchronize board movement vs. generic screen recording
- •Core insight: users want collaboration while watching (comments, stickies, reactions)
- •Prototype feedback drove a differentiated implementation path
- 11:48 – 17:09
Why Miro stands out: Team-centric product strategy and broad applicability
Lenny asks why Miro keeps winning as competitors enter. Varun attributes differentiation to a team-first lens (not single-persona tools), cross-industry applicability, unique workshop/agile capabilities, and strong community energy.
- •Miro builds for teams, not a single persona workflow
- •Architecture and prioritization follow a cross-functional innovation model
- •Used across many verticals beyond “digital product teams”
- •Workshop/agile facilitation features create durable differentiation
- •Community love is positioned as a growth and product fuel
- 17:09 – 19:43
Org scale and structure: Streams organized around personas (plus horizontals)
Varun outlines Miro’s size and how product work is organized. Streams primarily map to key personas (enterprise admin/security, developers/platform, etc.), supplemented by horizontal teams like growth, infrastructure, and data science/AI.
- •~1,800 employees; large product org footprint (as stated in interview)
- •Streams/domains primarily align to key personas
- •Examples: Enterprise (IT/security/compliance), Platform (developers)
- •Horizontal streams: PLG growth, infrastructure, data science/AI
- •Goal: align teams to create value per persona
- 19:43 – 22:57
Preventing persona silos: AMPED + transparent product reviews + enterprise checklists
Lenny probes the downside of persona-based structures (fragmentation). Varun explains how Miro counters this with AMPED (cross-functional product org definition), open product review practices (Slack + formal reviews), and democratized enterprise requirement checklists.
- •AMPED = Analytics, Marketing, Product, Engineering, Design
- •“Product org” means cross-functional AMPED, not only PM/Eng/Design
- •Small/medium work shared broadly; big work goes through formal reviews
- •Company-wide visibility via Slack channels encourages dot-connecting
- •Enterprise requirements codified into checklists to avoid late surprises
- 22:57 – 24:31
Why product marketing sits inside teams: Positioning, packaging, and competitive clarity
Varun explains the rationale for embedding product marketing deeply into cross-functional teams. The goal is to ensure what ships can be positioned and differentiated, especially in competitive markets where messaging, packaging, and sales enablement matter.
- •PMs can over-index on solution delivery vs. market narrative
- •Product marketing adds rigor on positioning and differentiation
- •Packaging and enablement help translate features into buyer value
- •Embedding PMM reduces “built it, but it didn’t land” risk
- •Competitive context increases the ROI of strong PMM integration
- 24:31 – 34:21
Competition-first realism: Growth, distribution, and pricing as major variables
Varun challenges the advice to ignore competitors, arguing growth often tracks what competition enables or constrains. He highlights competitive advantages like distribution reach, pricing/packaging power, and “good enough” functionality as drivers of category outcomes.
- •Varun’s thesis: company growth often correlates with competitive dynamics
- •Examples from collaboration markets where large incumbents enter
- •Three competitive forces: product adequacy, distribution, pricing/packaging
- •Strategy implication: define and defend your unique place in customers’ minds
- •Differentiation must be both real (capabilities) and communicable (positioning)
- 34:21 – 37:50
Speed as advantage: ‘First to hit the brick wall’ + removing blockers
Varun argues speed is decisive in innovation-heavy competitive markets—learn faster, pivot earlier, and stay ahead. He frames slowdowns as largely caused by blockers (technical, organizational, priority) and emphasizes leadership’s job is to remove them quickly to create a virtuous cycle of wins.
- •Philosophy: be the first to hit the brick wall to learn fastest
- •Speed matters most when outcomes are uncertain and competition is active
- •PMs want to move fast; blockers are the real constraint
- •Leadership should make it easy to raise blockers and resolve them quickly
- •Momentum builds organizational pattern-matching for faster future execution
- 37:50 – 47:44
Operationalizing ‘value fast, high quality’: Cycle-time telemetry and design quality triage
Varun introduces Miro’s simple product-org motto: deliver customer value faster with high quality—and ties it to evaluation and measurement. He describes how Miro measures cycle times through stage gates (P-STRAT, P0, P1, P2) and runs a recurring design review that classifies shipped work as high quality or not, using examples to train judgment.
- •Motto anchors performance systems: customer value, speed, quality
- •Customer value defined as usage + measurable metric movement
- •Cycle time tracking across stages: idea → problem → solution → shipped → metric impact
- •Benchmarking by project size (small/medium/large) to spot variance
- •Monthly design leadership triage: binary quality classification + rationale to build shared taste
- 47:44 – 53:49
How product development runs: Strategy artifacts, rolling roadmaps, and ‘Miro Connect’ demos
Varun explains how teams plan without losing agility: an annual internal strategy white paper plus a rolling six-month roadmap updated quarterly with different confidence levels. He also shares a distinctive ritual—Miro Connect, a recurring demo “trade show” that sparks serendipitous problem-solving and accelerates execution.
- •Annual product strategy white paper sets bets, rationale, and outcomes
- •Rolling 6-month roadmap updated every 3 months
- •First 3 months targeted at ~80% precision; next 3 months ~50% precision
- •Agile coaches support teams while preserving autonomy in rituals
- •Miro Connect (every other Friday): informal demos that can unlock cross-team help and save months of work
- 53:49 – 1:01:17
Execution system details: OKRs cadence and the product team stack
Varun describes how Miro sets goals: company OKRs cascade into the AMPED org, with planning evolving from quarterly to 6-month key results and monthly traction reviews. He also walks through the tool stack—Jira/Confluence plus docs and BI tools—while highlighting how Miro boards serve as hubs for research, synthesis, reviews, presentations, async feedback, and live dashboards.
- •OKRs start at company level and cascade into AMPED streams
- •Shift to 6-month KRs to reduce replanning overhead; monthly traction checks
- •Core stack: Jira for tickets; Confluence for specs; Google Docs/Coda used too
- •Miro as end-to-end project hub: research artifacts, ideation, workshops, product reviews
- •Async reviews via Talktrack; dashboards embedded (e.g., Looker) directly into boards
- 1:01:17 – 1:10:28
Balancing big bets and reliability: Tech debt allocation, three horizons, and leader accountability
Varun explains how investment splits vary by team maturity and system criticality, with a baseline allocation to maintenance/architecture that can rise for platform-heavy areas. He then layers in the three-horizons model (70/20/10) and closes with a people philosophy: product leaders must simultaneously drive improvement in their stream and accountability across the leadership team.
- •Maintenance/architecture investment typically 20–40%+ depending on team/system needs
- •Platform scale demands continuous infrastructure investment (tech roadmap led by CTO)
- •Three horizons allocation: 70% core, 20% adjacent (12–36 months), 10% future (3–5 years)
- •Leadership dual persona: stream leader drives improvement; leadership member drives accountability
- •Accountability practiced via open, empathetic feedback—often framed as questions
- 1:10:28 – 1:25:10
Growth engine, enterprise motion, and what’s next: Miroverse, sales alignment, AI, and lightning round
Varun shares how Miro got early traction through community outreach, content/SEO, listings (e.g., Capterra), and viral loops—then explains how templates and Miroverse became an acquisition channel. He covers the realities of adding a sales motion to a PLG business, previews upcoming product areas (Miro AI and agile/ritual enhancements), and ends with a lightning round and listener call-to-action.
- •Early growth: community focus, content marketing, SEO, viral loops, trial → freemium evolution
- •Templates/Miroverse as a top-of-funnel channel (example: FIFA template virality + SEO indexing)
- •PLG remains core; enterprise provisioning amplifies the flywheel at large scale
- •Sales + self-serve integration requires deliberate handoffs and shared operating model (PMM bridges)
- •Roadmap teasers: Miro AI expansion, agile/ritual features (private retro mode, Jira program board/PI planning)
- •Lightning round: recommended books, favorite show, interview question, and operating principles
