An inside look at Mixpanel’s product journey | Vijay Iyengar

An inside look at Mixpanel’s product journey | Vijay Iyengar

Lenny's PodcastJan 26, 202346m

Vijay Iyengar (guest), Lenny Rachitsky (host), Narrator

Mixpanel’s product evolution: from single product to multi-product suite and backWhen and how to expand beyond a core product—and common pitfallsRefocusing on core analytics: churn diagnosis, roadmap based on churn reasons, and rapid feature deliveryDesign-led, system-architecture thinking to create a coherent, scalable product UXProduct planning, betting, and prioritization (RICE, appetites vs. estimates, six‑month cycles)Keeping product and engineering close to customers through open, real-time feedback loopsModern product analytics practices: server-side tracking, data warehouses, and event-centric models

In this episode of Lenny's Podcast, featuring Vijay Iyengar and Lenny Rachitsky, An inside look at Mixpanel’s product journey | Vijay Iyengar explores mixpanel’s Hard Reset: Refocusing From Bloated Suite To Core Analytics Vijay Iyengar, Head of Product at Mixpanel, walks through Mixpanel’s journey from a focused analytics tool, to a sprawling multi-product suite, and back to a single, best-in-class core analytics product.

Mixpanel’s Hard Reset: Refocusing From Bloated Suite To Core Analytics

Vijay Iyengar, Head of Product at Mixpanel, walks through Mixpanel’s journey from a focused analytics tool, to a sprawling multi-product suite, and back to a single, best-in-class core analytics product.

He explains how over-expanding into adjacent categories (messaging, data infrastructure) diluted engineering focus, hurt the core product, and led to high churn—forcing a painful but necessary reset.

The conversation covers Mixpanel’s turnaround playbook: ruthless focus on core gaps, design-led system architecture, a distinctive planning and prioritization process, and a strong culture of direct customer contact for engineers.

Vijay also shares contrarian views on product analytics implementation (server-side over client SDKs) and the growing centrality of the data warehouse and event-based data models.

Key Takeaways

Never underinvest in your core product while chasing new product lines.

Mixpanel’s churn surged when they reallocated engineers from core analytics to adjacent products (messaging, data infrastructure), allowing competitors to out-invest them on table-stakes features and win away customers.

Get the full analysis with uListen AI

Fund new bets with profits, not people from the core.

Vijay argues that if you’re the category leader, you should keep over-investing in the core and use profits (or VC capital) to fund adjacencies, instead of pulling core engineers onto side products that become ‘nth best’ in their categories.

Get the full analysis with uListen AI

Use churn reasons and lost deals to drive a brutally focused roadmap.

To fix their core, Mixpanel threw out existing plans, grouped churn reasons into problem categories, ranked them by ARR impact, and gave engineers direct access to affected customers—leading to ~100 core improvements, higher win rates, and major retention gains.

Get the full analysis with uListen AI

Pair speed-first feature closing with a second, design-led architecture pass.

Their first phase optimized for speed and table-stakes coverage; the second phase, led by design, rethought Mixpanel’s system architecture and visualization consistency, dramatically improving reach, usability, and product coherence.

Get the full analysis with uListen AI

Treat high-reach, high-impact ideas differently in prioritization.

RICE can bury big bets because confidence and effort are initially unknown; Vijay recommends focusing first on reach and impact, exploring promising ideas for a bit, then layering in confidence and effort so you don’t prematurely kill ambitious work.

Get the full analysis with uListen AI

Use time-boxed ‘appetites’ instead of up-front estimates to scope work.

Inspired by Shape Up, Mixpanel often chooses a time window (e. ...

Get the full analysis with uListen AI

Default to server-side event tracking and treat the data warehouse as your source of truth.

Vijay strongly recommends tracking events from servers rather than client SDKs (to avoid data loss, fragmentation, and stale tracking) and increasingly sees customers using the warehouse plus reverse ETL tools as the central hub feeding analytics tools like Mixpanel.

Get the full analysis with uListen AI

Notable Quotes

If you're the leader in some core product, you should continue to out-invest everyone else in that core and then invest the profits that come out of that core into the next venture.

Vijay Iyengar

Don’t take people away from the core to go do those other things, because then you end up distracted.

Vijay Iyengar

We took all the churn reasons... grouped them by category, sorted descending by ARR, took the top 10 things and made that our roadmap.

Vijay Iyengar

You can’t mow your lawn while your house is on fire. You’ve got to put out the fire and then deal with everything else.

Vijay Iyengar

The biggest mistake is setting up analytics using client-side SDKs... We’ve just seen time and time again it leads to poor data quality and difficulty to maintain that data.

Vijay Iyengar

Questions Answered in This Episode

How do you know, quantitatively and qualitatively, that it’s truly time to cut a mildly successful adjacent product rather than keep iterating?

Vijay Iyengar, Head of Product at Mixpanel, walks through Mixpanel’s journey from a focused analytics tool, to a sprawling multi-product suite, and back to a single, best-in-class core analytics product.

Get the full analysis with uListen AI

What signals should founders watch for that they’re starting to underinvest in their core—and how early can those signals be detected?

He explains how over-expanding into adjacent categories (messaging, data infrastructure) diluted engineering focus, hurt the core product, and led to high churn—forcing a painful but necessary reset.

Get the full analysis with uListen AI

How can smaller or earlier-stage teams realistically adopt Mixpanel’s design-led system architecture approach without a large design org?

The conversation covers Mixpanel’s turnaround playbook: ruthless focus on core gaps, design-led system architecture, a distinctive planning and prioritization process, and a strong culture of direct customer contact for engineers.

Get the full analysis with uListen AI

In practice, how do you prevent ‘reactionary building’ when engineers have direct, real-time access to customer complaints and requests?

Vijay also shares contrarian views on product analytics implementation (server-side over client SDKs) and the growing centrality of the data warehouse and event-based data models.

Get the full analysis with uListen AI

As data warehouses become the center of gravity, what new skills and org structures will product teams need to make the most of event-based analytics?

Get the full analysis with uListen AI

Transcript Preview

Vijay Iyengar

The issue for us at the time was that we took people away from the investment in our core product to go do those other things. Like, we, we moved people, right? And so the, the trap there is that you leave yourself ripe for disruption in your core because someone else can out-invest you in, in that core. And so 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, or venture capital, which is maybe, like, net present value of profits or something to that effect. But don't take people away from the core to go do those other things, 'cause then, then you end up distracted.

Lenny Rachitsky

(instrumental music) Welcome to Lenny's Podcast, where I interview world class product leaders and growth experts to help you get better at the craft of building and growing products. Today my guest is Vijay Iyengar. Vijay is currently head of product at Mixpanel. He actually has a very similar career trajectory to myself, where he started as an eng intern at Amazon, then he was an engineer for a while at Uber, then he became an eng manager at Mixpanel, but then he shifted from an eng manager to director of product, and now head of product at Mixpanel. You don't often see people moving from an eng leadership role straight to director of product, so it was really interesting to hear what he took from his eng experience and brought into his approach to product leadership. But we spend the bulk of our time talking about what he's learned from the journey that Mixpanel has been on, where they started with a simple product and scaled to a number of different products, solving many problems for customers, and then made the hard decision to scale back to just a single core focused analytics product. We talk about why they made that choice, what they learned about when it makes sense to expand to new products and when you probably shouldn't, and how they approached that organizationally. We also talk about how Mixpanel builds product, how they think about product philosophy, how they prioritize, and also what you're probably doing wrong in how you set up your analytics for your own product. With that, I bring you Vijay Iyengar after a short word from our wonderful sponsors. This episode is brought to you by Pando, the always-on employee performance platform. How much do you love the performance review process? Mm, yeah. It's time-consuming, subjective, biased, and there's rarely any transparency. With the rapid shift to distributed work, it's a struggle to create the structure and transparency that you want to help your employees have the highest impact and growth in their careers. Pando is disrupting the old paradigm of performance management, including a continuous employee-centric approach so employees stay engaged, see their progression in real time, and know exactly when and how they can level up. With Pando, managers can leverage competency-based frameworks to effectively coach and develop your teams and align on consistent growth standards, resulting in higher quality feedback and higher performing teams. Visit pando.com/lenny for more info, and get a special discount when you sign up and reference this podcast. That's pando.com/lenny. This episode is brought to you by Notion. If you haven't heard of Notion, where have you been? I use Notion to coordinate this very podcast, including my content calendar, my sponsors, and prepping guests for launch of each episode. Notion is an all-in-one team collaboration tool that combines note taking, document sharing, wikis, project management, and much more into one space that's simple, powerful, and beautifully designed. And not only does it allow you to be more efficient in your work life, but you can easily transition to using it in your personal life, which is another feature that truly sets Notion apart. The other day, I started a home project and immediately opened up Notion to help me organize it all. Learn more and get started for free at notion.com/lennyspod. Take the first step towards an organized, happy team today, again, at notion.com/lennyspod. Vijay, welcome to the podcast.

Install uListen to search the full transcript and get AI-powered insights

Get Full Transcript

Get more from every podcast

AI summaries, searchable transcripts, and fact-checking. Free forever.

Add to Chrome