The PodKnowledge|← All Episodes
Based on Lenny's Podcast data
Lenny's Knowledge Sketch · Mixpanel

Inside Mixpanel's Pivot:
Focus Over Features

Vijay Iyengar
Head of Product, Mixpanel
JAN 26 2023
Core Insight

Invest Profits,
Not People

CORE PRODUCTPROFITS→ NEW BETSMOVED PEOPLE = CHURNdon’t do this
"Don't take people away from the core, you leave yourself ripe for disruption and end up distracted."
  • Mixpanel hit 40% revenue churn after splitting eng across 3 products
  • Customers didn't stop needing analytics, they churned to competitors who out-invested the core
  • Expand with profits (or VC), never by moving engineers off the core
Framework

Mixpanel's 3-Phase Product Turnaround

PHASE 1Feature Sprint PHASE 2Design System RESULT60% → 90% Ret. 2018–2019 2019–2021 2022+ NPS 16 → 50 · RETENTION 60% → 90%
40%
churn before pivot
100+
features in year one
50
NPS (was 16)
Phase 1, Feature Sprint (2018–2019)

Sorted all churn reasons by ARR lost. Made the top 10 the entire roadmap. Gave every engineer direct access to the customers with those problems. No top-down feature specs, engineers invented the solutions. Shipped 100+ features in year one.

Phase 2, Design System (2019–2021)

Paused tactical feature work for 3 months so design could rethink system architecture from scratch. Identified fewest possible building blocks. Result: every new feature now inherits consistent UX automatically, multiplying reach with zero extra work.

The Sequencing Principle

You can't mow the lawn while the house is on fire. Stop the bleeding with speed (Phase 1), then invest in quality (Phase 2). Don't skip the sequence, they each have a context where they're right.

Playbook

How Mixpanel Plans & Prioritizes

6-Month Planning Cycle, The "Bets" System
  • Leadership writes a strategy memo: company direction for the next 12 months
  • Teams develop bets, not OKRs, not features. Anatomy: problem + hypothesis + plan to win + success metric
  • CPO and Head of Design join every team's FigJam jam session, actively contribute ideas, don't just review
  • Conclude with company-wide roadshow for alignment before locking plans
Team Structure: Paired Problems

Teams own long-lived problem pairs in tension. Example: Power & Simplicity is one team, they're forced to make that trade-off themselves, not escalate it.

Other pairs in play: data trust + onboarding; collaboration + price-performance.

Fix the RICE Trap

Problem: C (confidence) + E (effort) in RICE systematically kill your highest-reach ideas, because innovative work is always murky to estimate.

Fix: Drop C and E for a week. Bring engineers + designers. Sincerely try to make the idea work. You'll find a higher-confidence, lower-effort approach. Then add C+E back and RICE normally.

Goal: End up with a mix of innovative bets, incremental improvements, and tech debt, not just what was easiest to scope.

Appetite over Estimates (Shape Up)

Set a time box (appetite) as the input, not an estimate as the output. Pick 6 weeks. Then ask: what would we do differently in 4 weeks? 8 weeks? Find the efficient frontier, then ship something complete, not milestone one of an unfinished idea.

Tactics

Engineer-to-Customer Direct Line

  • Pipe all CS/sales customer gaps into a Slack channel, raw, ungated, no PM filter
  • Engineers react with an email emoji to claim a thread, then email that customer directly
  • Enrich the feed: tag with account ARR, CSM name, tier, engineers have context before reaching out
  • Expand the signal set: NPS, Twitter mentions, win/loss notes, all pipe into the same feed via data warehouse
  • Use reverse-ETL (Census) to push from BigQuery → Slack/Notion so it's enriched and real-time
Biggest Analytics Mistake Client-side SDK tracking drops 20–30% of events (ad blockers), duplicates events across iOS/Android, and is frozen for old app versions. Track from your servers instead, it's just structured logs with a user ID. Instant cross-platform, always current, zero drops.
Contrarian

Product Myths Vijay Debunks

✗ Expand products to grow revenue INSTEAD → ✓ Adjacent bolt-on products rarely become best-in-class. They contribute 5–10% revenue while starving your core of the engineers who could have made it unbeatable. Cut mild successes early, it's 10x more painful than you think.
✗ PMs should own all customer context INSTEAD → ✓ Give every engineer and designer a raw, ungated feed of real customer feedback. Engineers who email customers directly build better products, and it takes cognitive load off PMs being the only bottleneck to customer truth.
✗ RICE is the gold standard for prioritization INSTEAD → ✓ RICE systematically kills your best ideas because C and E are murky for high-reach, innovative work. Drop them first, explore the idea for a week, then bring them back. Your most innovative bets will survive.
✗ Client-side SDK tracking is the default INSTEAD → ✓ Server-side tracking is 100% cross-platform, always up-to-date, and drops zero events. It's just structured logs with a user ID, engineers have been doing it for decades. Make it the default; supplement with client-side only when needed.
Based on Vijay Iyengar's episode on Lenny's Podcast. All ideas on this page are from the episode.Watch on YouTubeFollow @vijayiyengar on X
GO DEEPER IN THE EPISODE
04:12 How Vijay learned to be more open-minded to new ideas07:15 Mixpanel’s journey12:53 When to optimize for speed14:03 The feature phase vs. the design phase17:26 The importance of not losing focus on your core product20:03 How Mixpanel organizes teams around buckets of problems20:53 Mixpanel’s most recent six-month time horizon planning cycle23:09 Mixpanel’s favorite tools25:16 The RICE framework for prioritization (and when to ignore the C and E)26:57 The problem with estimations, and why Basecamp suggests using a six-week time box30:17 How Mixpanel keeps product teams and engineers connected to customers via Slack33:31 SaaS tools Mixpanel’s teams use35:15 The biggest product analytics mistakes37:43 The present and future of analytics41:09 How adopting a product mindset has helped Vijay grow his career41:58 Lightning round
Every sketch here began as a transcript.

Send us yours and we’ll draw it. $1 a transcript.

Sketch mine →
𝕏︎ X / Twitterin LinkedIn📸 Instagram🔗 Copy link
0:00