Varun Parmar on Miro’s Product Culture, AMPED Teams, and Competitive Strategy
Source: Lenny’s Podcast Speaker: Varun Parmar Link: Episode
Varun Parmar is Chief Product Officer at Miro, the collaborative visual workspace used by millions of teams. This episode covers the org structure Miro built around autonomous product units, how Varun thinks about competitive strategy at scale, the velocity metrics his team uses, and the cultural rituals that make product quality legible across the organisation.
Key ideas
- AMPED: the full-stack product unit. Miro organises product work into AMPED teams — cross-functional units comprising Analytics, Marketing, Product, Engineering, and Design. Each unit owns a full slice of value delivery rather than a functional layer. The model pushes accountability for outcomes (not just outputs) to the team level and reduces the coordination tax of matrix handoffs.
- Products get better or worse, never stay the same. Every release is a chess move in a competitive game. Competitors observe what you ship, adjust, and reply. Varun frames roadmap decisions not as internal prioritisation but as competitive positioning: the right question is not “what do users want next?” but “what move advances our position against the options competitors now have?”
- Rolling six-month roadmap with explicit confidence tiers. Miro uses an 80% confidence bar for the first three months of the roadmap and 50% for the next three. Publishing the confidence level signals that the roadmap is a hypothesis, not a contract — enabling fast adjustment without eroding trust with internal stakeholders.
- Miro Connect: the demo ritual. A bi-monthly showcase in which engineering teams demo work in progress to the broader organisation. The ritual serves two purposes: surface wins that would otherwise stay invisible (an engineer at the Berlin hub saved three months of duplicated work by demoing at Miro Connect), and create accountability for shipping something demonstrable on a regular cadence.
- Cycle time by size as the velocity metric. Miro measures engineering velocity not by story points or features shipped, but by the time it takes to close a ticket of a given size (small, medium, large). The metric surfaces systemic slowdowns — architectural bottlenecks, review backlog, unclear specs — without incentivising gaming through ticket inflation.
- The PLG and enterprise flywheel. Miro’s workshop use case is naturally viral: one facilitator invites 50+ participants to a single board. That viral loop seeds enterprise adoption, which funds the PLG motion. Parmar describes the flywheel explicitly: individual users adopted through PLG become champions who drive enterprise deals, which fund platform improvements that make the PLG experience better.