About this episode
Zoom grew from $1B to $4.5B in months - but behind the scenes, it was chaos.Learn how they froze features, scaled product teams, and held the platform together under global pressure from the head of product at Zoom meetings.----Brought to you by:Jira Product Discovery: Plan with purpose, ship with confidenceThe AI Evals Course for PMs & Engineers: You get $800 with this linkProduct Faculty: Get $500 off the AI PM certification with code AAKASH25----Timestamps:Preview – 00:00:00How Big Zoom Is – 00:02:12Simplifying Zoom UX – 00:03:40From $1 Billion to $4.5 Billion During Covid - 00:04:38The Three-Month Feature Freeze Story – 00:06:38Aakash Shares His Zoom Fortnite Concert Story – 00:07:30Advice for Product Leaders Facing Hypergrowth – 00:09:25Ad 1 (Jira) – 00:11:29Ad 2 (AI Evals Course) – 00:12:43One Thing He Would’ve Done Differently in His Career – 00:13:25Handling Zoom's Overvaluation, Layoffs, and Stock Price Drops – 00:14:20Future of AI in meetings - 00:16:09Zoom’s Shift into Broadcast and Events – 00:18:55Why Send a Meeting When You Could Record a Loom? – 00:21:35Can Zoom Catch AI Avatar Doing Interview - 00:26:23Ad 3 (AIPM Course) – 00:28:11Using Zoom Like a Pro – 00:28:58Cool Things About the AI Companion – 00:32:27Balancing Simplicity While Shipping Great Features – 00:36:37How PMs Can 10x Their Meeting Management – 00:40:42How to Get Hired at Zoom – 00:44:56What’s Unique About How Zoom Builds Products – 00:51:35Lessons Learned from Running QBRs – 00:54:18Culture at Zoom: Metrics Driven or Not - 00:57:03Zoom Team Adopting Prototyping Tools? – 00:58:53Outro – 01:00:17----Key Takeaways:1. Zoom didn’t just scale, it survived a once-in-a-generation demand shock. In early 2020, Zoom grew from $1B to $4.5B revenue and added 180+ PMs in months. To stay afloat, they froze all feature development for 3 months and focused solely on stability, security, and critical user needs.2. Most teams drown in feature requests. Zoom built a triage system. He created structured buckets to track thousands of bugs, asks, and UI issues. This wasn’t just project management. It was the only way to maintain control during chaos.3. The best PMs don’t just fix, they find the root cause. Instead of reacting to symptoms, he emphasized thinking a layer deeper. What assumption broke? What system failed? Root cause thinking kept
