💡

InsightHunt

Hunt the Insights

V

Varun Parmar

Episode #289

Chief Product Officer

Miro

👥Team & Culture🎯Product Strategy⚡Execution

📝Full Transcript

16,038 words
Varun Parmar (00:00:00): Every single day, every single time somebody is pushing your code to production and you're releasing a feature or an enhancement, you are making the product better or you're making the product worse, but the products never remain same. So with every release that your competitor is making and every release that you're making, you are either making chess points, moves against them, positive points, or you're going negative. I think that framework, it actually drives an insane amount of clarity in terms of what you're doing and what the impact is going to be. Lenny (00:00:33): Welcome to Lenny's Podcast, where I interview world-class product leaders and growth experts to learn from their hard-won experiences building and growing today's most successful products. Today my guest is Varun Parmar. Varun is chief product Officer at Miro, and prior to Miro, he was senior vice president and chief product officer at Box. As I share with Varun at the start of our chat, I've always been really curious about the product culture at Miro, partly because everyone I've ever met from Miro has been super interesting and super smart, and partly because they've been able to grow as a business and a product in an incredibly competitive market. (00:01:07): In our conversation, we get really deep into the product values and principles at Miro, their product development process, how Varun approaches competitive threats, how a bimonthly company-wide product demo ritual led to saving months of engineering work on a feature, plus insights into how Miro got started, how they grow today, and what their product team has learned about working with a large sales org. Varun is amazing, I learned a lot, and I hope you find it as interesting as I did. With that, I bring you Varun Parmar after a short word from our sponsors. (00:01:39): Today's episode is brought to you by Miro, an online collaborative whiteboard that's designed specifically for teams like yours. I have a qui...

💡 Key Takeaways

  • 1Speed is the ultimate competitive advantage; aim to be the first to 'hit the brick wall' to learn faster.
  • 2Product organizations should include Analytics and Product Marketing (AMPED) to prevent silos and ensure market fit.
  • 3Every release is a chess move: your product is either getting better or worse relative to competitors daily; it never stays the same.
  • 4Use a binary 'High Quality' vs. 'Not High Quality' visual classification system to align design standards.
  • 5Product leaders must balance two personas: driving accountability within leadership and driving improvement within their streams.

📚Methodologies (4)

👥 Team & Culture

Miro redefines the 'Product Org' not just as PMs, Engineers, and Designers, but as AMPED: Analytics, Marketing, Product, Engineering, and Design. By embedding Product Marketing and Data Science directly into the product streams, they ensure that positioning, competitive differentiation, and data insights are baked into the development process from day one.

Core Principles

  • 1.Include PMM and Analytics as core members of the product leadership team, not just support functions.
  • 2.Practice radical empathy internally: Ask questions to understand the 'why' behind decisions across functions.
  • 3.Structure teams around User Personas (e.g., Enterprise Admin, Developer Platform) rather than just technical components.

"We fundamentally believe the best work happens when we bring different diverse perspectives to the problem and then co-create the outcome."

#amped#organizational#structure
View Deep Dive →
🎯 Product Strategy

Products are never static; with every code push from you or your competitor, your relative position improves or declines. The goal isn't just to move fast, but to be the first to 'hit the brick wall'—to invalidate wrong hypotheses faster than the competition. Strategy is defined by what the competition allows you to do.

Core Principles

  • 1.Zero-Sum Mindset on Quality: Every release either adds positive chess points or negative ones relative to the market.
  • 2.Hit the Wall First: Prioritize speed to discover what DOESN'T work before competitors do.
  • 3.Monitor Competitors implicitly: Use competitor moves to sharpen clarity on your own investments and differentiation.

"Success of a company is a direct relation of what the competition allows you to do... Products never remain same."

#relative#velocity#strategy
View Deep Dive →
⚡ Execution

A structured stage-gate process that tracks cycle times for distinct phases. By classifying projects as Small, Medium, or Large, teams can benchmark their velocity against organizational averages to identify bottlenecks in definition vs. delivery.

Core Principles

  • 1.P-Strat: Strategy definition / Idea pitch.
  • 2.P0: Problem definition (The 'What' and 'Why').
  • 3.P1: Solution definition (The 'How' and Design).
  • +1 more...

"Deliver customer value faster with high quality."

#p-stage#development#process
View Deep Dive →
👥 Team & Culture

Instead of writing 10-page docs defining quality, Miro's design leadership reviews shipped features monthly and tags them binary: 'High Quality' or 'Not High Quality'. This creates a training set (like AI reinforcement learning) for the org to intuitively understand standards.

Core Principles

  • 1.Visual Calibration: Describing 'Pink' vs 'Red' is hard in words, but easy with examples.
  • 2.Binary Classification: Keep it simple (Quality / No Quality) to force a decision.
  • 3.Reinforcement Learning: Regularly sharing these classifications trains the 'product intuition' of the entire team.

"If you've never seen colors and I ask you describe pink... you can't. But if I show you examples, you get it."

#"pink#quality#calibration
View Deep Dive →
← Browse All Episodes