Jan 26, 2023 · 46m · lennys-podcast
An inside look at Mixpanel’s product journey | Vijay Iyengar
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Mixpanel Head of Product Vijay Iyengar breaks down the company's dramatic turnaround to refocus on its core analytics engine, sharing tactical frameworks for product prioritization, engineering collaboration, and modern data architecture.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 27.3% of the talking time here. How this is scored →
Lenny as informed peer 3.5 Guest teaching 5.5 Guest disagreement 1.2 Lenny pushing back 1.6
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 35:20 Vijay's hot take rejecting client-side SDKs
Vijay delivers a contrarian stance challenging industry-standard analytics setups, calling client-side SDK tracking a widespread mistake that causes dropped events and broken maintenance.
Hardest push from Lenny ▶ 12:50 Lenny questions the sustainability of pure feature sortingLenny presses Vijay on whether an ARR-sorted feature backlog created a disjointed product that ultimately lacked synergy, prompting Vijay to defend it as necessary crisis triage.
Biggest teaching moment ▶ 36:20 Vijay breaks down server-side logging advantagesVijay breaks down technical limitations of client-side tracking across iOS/Android and explains why server-side logs with user IDs solve platform fragmentation and versioning lag.
Lenny holds their own ▶ 19:18 Lenny's anchor tenant synthesisLenny demonstrates deep product strategy knowledge by synthesizing Vijay's multi-product cautionary tale into the requirement for a dominant 'anchor tenant' product before attempting to bundle adjacent tools.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| Transitioning from Engineering to Product Leadership | 4 | 5 | 1 | 2 | Lenny draws on his shared background transitioning from engineering to product to probe Vijay on engineering mindset traps. Vijay explains having to unlearn the automatic reflex to say 'no' to new ideas, offering practical advice for engineers to earnestly try to make 'yes' work first. | |
| Mixpanel’s Evolution: Expansion, Churn, and Refocusing | 3 | 7 | 1 | 1 | Vijay details Mixpanel's crisis in 2018 when revenue churn hit 40% due to engineering spreading thin across messaging and data infrastructure rather than core analytics. Lenny mostly listens and prompts as Vijay details how Mixpanel pivoted by grouping churn reasons and prioritizing by ARR. | |
| Balancing Feature Catch-Up with Holistic Design | 4 | 6 | 2 | 3 | Lenny questions whether a purely feature-driven, revenue-sorted roadmap risked creating a disjointed product. Vijay agrees but reframes it as necessary triage during a crisis, using an analogy of putting out a house fire before mowing the lawn. | |
| Creating Space for Design and System Architecture | 5 | 6 | 1 | 2 | Vijay outlines the danger of building 'nth best' adjacent products that distract from the core and advises investing profits rather than core personnel into new bets. Lenny synthesizes the insight into the concept of an 'anchor tenant' product requirement. | |
| Product Planning and the Six-Month Bet Framework | 3 | 6 | 1 | 1 | Vijay details Mixpanel's planning cycle around 6-month bets and paired-tension problem statements (like power vs simplicity). Lenny asks structured procedural questions about templates, deliverables, and timelines while Vijay explains collapsing the traditional W-framework. | |
| Sponsor: Lemon.io Developer Matching | 5 | 6 | 2 | 2 | After the sponsor read, the conversation shifts to prioritization frameworks where Vijay critiques standard RICE scoring for killing innovative ideas. Lenny contributes his own practitioner preference of removing confidence scoring from RICE, and Vijay shares Basecamp's appetite concept. | |
| Connecting Engineering Directly to Customer Feedback | 4 | 6 | 1 | 2 | Vijay describes Mixpanel's direct-to-customer Slack feed where engineers can directly email churned or frustrated users with zero gatekeeping. Lenny expresses astonishment and immediately asks how they manage risk and prioritization with massive accounts. | |
| Internal Tooling and the Modern Data Stack | 3 | 5 | 1 | 1 | Vijay explains how modern data stack tools like BigQuery and Census allow engineers to create internal tools and automate qualitative signals with minimal code. Lenny confirms standard team tooling before asking where to find public writeups. | |
| The Future of Analytics and Data Warehouses | 4 | 8 | 3 | 2 | Vijay delivers a strong contrarian take against client-side SDK tracking, arguing server-side logs provide 100% reach and avoid JavaScript ad-blocker event dropping. He explains how data warehouses are becoming the loading dock of events while SQL remains unsuited for sequence analytics. | |
| Cultivating a Product Mindset Across Engineering | 3 | 4 | 0 | 1 | Vijay summarizes the value of nurturing a product mindset across engineering before jumping into the lightning round. Lenny facilitates rapid-fire recommendations on books, shows, and industry thought leaders like Gibson Biddle and Shishir Mehrotra. | |
| Connecting with Vijay and Mixpanel Updates | 1 | 1 | 0 | 0 | Lenny wraps up the episode by asking where listeners can follow Vijay online and how they can support Mixpanel's evolution. |
Statements from this episode (21)
Iyengar: Engineers should spend 10 minutes trying to make ideas work before saying no
“Just take 10 minutes to consider the idea and just sincerely consider how might we make it work. And if at the end of those 10 minutes, it's like futile and there's no path, it's fine to say no. And it's a good, good instinct to say no, actually, in a lot of c…”
Mixpanel experienced roughly 40% revenue churn on core product in 2018
“And what ended up happening was that by 2018, we had this big churn problem. We had something like 40% churn, revenue churn, our core product.”
Mixpanel set roadmap by sorting customer churn reasons descending by ARR
“We took all the churn reasons that our customer success and sales teams had been painstakingly collecting for years, grouped them by category, which was like roughly product features we needed to build. Sorted descending by ARR, took the top 10 things and made…”
Mixpanel raised retention from 60% to 90% between 2018 and 2022
“And so the end result of that phase, which is from, you know, 2018 to maybe late 20 21, 2022 was our retention went from about 60% to 90% and our NPS went from 16 to 50.”
Iyengar: Highly competitive markets require optimizing product development speed over holistic design
“In a very competitive context where there are just table stakes features that customers need and that's been validated by the market, you need to optimize for speed more so than anything else. But it is an approach that outlives its usefulness pretty fast.”
Iyengar: Involving design late without dedicated architecture time blows up scope
“We would get towards the end of the project, bring design in, and they would use each project as an opportunity to squeeze in like, oh, and we can simplify here. And that's just a classic way to blow up scope at the end of the project because there wasn't a de…”
Iyengar: Fund new product expansion with profits or VC, not core personnel
“If you're the leader in some core product, our takeaway here is you should continue to out-invest everyone else in that core and then invest, you know, the profits that come out of that core into the next venture, like invest profits and not people. Or venture…”
Iyengar: Cutting mild product successes is 10x more painful than expected
“It's also 10 X more painful than you think to cut mild successes than anything else. And just organizationally it's painful and there's teams that have whole road maps and you know, it's a really painful experience.”
Iyengar: Assign competing tensions to a single team to force trade-off resolution
“Some of those problems have a tension with each other, like power and simplicity. There's a trade off there, right? And we want one team to own both so that they can, they're kind of forced to confront that tension and beat that trade off.”
Mixpanel limits product roadmap to 10–12 bets per half
“We aren't a huge product team, and we, we're not going to do like, 50 things and a half. We're going to do maybe 10 to 12 things. And so that's enough that we don't, we can do something that doesn't scale if that enables high bandwidth communication between us…”
Vijay Iyengar: RICE Framework Prematurely Deprioritizes High-Impact Bets
“One of the traps with RICE that we observed is that the C and E, the confidence and effort, Tends to cause you to prematurely deprioritize potentially high-reach, high-impact bets, really innovative things.”
Vijay Iyengar: Software Estimation Expects Outputs Before Understanding the Scope
“I think the core problem with estimation is you're asked to estimate things before you know what the thing is. And it's just a strange output to be expected to produce.”
Iyengar: Varying timeboxes reveals the efficient frontier between cost and impact
“One approach I found that works better is Pick a reasonable sounding appetite and just explore the two to three options around it. Pick six weeks and then say, what would we do differently if we only had four weeks or eight weeks? And you'll kind of naturally …”
Vijay Iyengar: Adopting Basecamp's Shape Up Process Halfway Will Fail
“I think that rigor, like the rigor they applied to that across the board, you need to do it all the way. You can't adopt the process halfway, I think is the challenge. Otherwise you end up with people shipping like milestone one and then moving on, which is no…”
Mixpanel gives engineers direct, unfiltered access to all customer feedback feeds
“What this created was this culture where all engineers and designers could consume that raw feed of direct points of customer with no gatekeeper, no process to access it, no pre-aggregation.”
Mixpanel routes customer feedback from BigQuery to Slack via Census
“Basically all these feeds information land in our data warehouse, which is BigQuery. And from there, they're pushed out via a reverse CTL tool we use called Census to Slack and Notion.”
Iyengar: Writing SQL is sufficient to build internal operational tools
“You can build internal tools with very little code. If you can write SQL, you can build an internal tool basically, and that pushes information to the teams that need it.”
Mixpanel Head of Product: Client-Side SDK Tracking Is Analytics' Biggest Mistake
“I think the biggest mistake is, is setting up analytics using client-side SDKs, client-side tracking.”
Iyengar: Web Client-Side Analytics Drops 20% to 30% of Events
“Due to ad blockers and other unreliable things in the JavaScript world, you end up dropping 20 to 30% of your events.”
Iyengar: Data warehouses are poor analytical tools for event sequences
“Data Warehouse is becoming the loading dock for all of this data, which can be very easily modeled as events. But it's not a very great analytical tool for events because SQL is optimized for rows and tables and joints and not events and sequences of events an…”