The P-Stage Development Process
by Varun Parmar • Chief Product Officer at Miro
Varun Parmar is the Chief Product Officer at Miro, leading the product strategy for the visual collaboration platform used by over 50 million users. Prior to Miro, he served as the CPO at Box and held leadership roles at Adobe, bringing over two decades of experience in the collaboration and productivity software space.
🎙️ Episode Context
Varun Parmar discusses Miro's unique "AMPED" product organization structure and how they maintain innovation while scaling globally across 12 hubs. He details their competitive strategy, the specific P-stage product development process, and how they balance speed with high-quality design using unique calibration rituals. The conversation also covers how Miro bridges Product-Led Growth (PLG) with enterprise sales.
Problem It Solves
Standardizes the product lifecycle to measure velocity and ensure alignment without killing agility.
Framework Overview
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.
🧠 Framework Structure
P-Strat: Strategy definition / Idea p...
P0: Problem definition (The 'What' an...
P1: Solution definition (The 'How' an...
P2: Post-ship impact review (Did we m...
When to Use
For mid-to-large product organizations (50+ PMs) needing data-driven insights into operational efficiency.
Common Mistakes
Using the stages as bureaucratic hurdles rather than diagnostic tools to help teams move faster.
Real World Example
Miro tracks the time from 'Insight' to 'Metric Moved'. A team might realize they spend too much time in P0 compared to peers and seek advice to unblock.
Deliver customer value faster with high quality.
— Varun Parmar