An inside look at Mixpanel’s product journey

Vijay Iyengar, Head of Product at Mixpanel and a former engineer who moved from engineering manager to director of product, discusses Mixpanel's journey from a single analytics product to a broader suite and back to a focused core. The conversation covers why they refocused, how they plan and prioritize, keeping product teams close to customers, and common mistakes in setting up product analytics.

01Key learnings

• Protect your core product: rather than moving people from the core to new ventures, invest the core's profits into new bets, since competitors can out-invest you in the core.
• Be cautious adding adjacent products in new categories; bolt-on products that are only mid-tier in crowded categories rarely move revenue much and drain engineering capacity.
• When a product is losing customers to competitors, a focused 'speed' phase working directly from ranked churn reasons can close feature gaps quickly, but it should not be a permanent operating mode.
• Before saying no to new ideas, spend a dedicated short window genuinely trying to make them work and document the attempt; this turns reflexive rejection into a considered decision.
• Consider giving design a protected block of time for system-architecture work so it isn't squeezed in as cosmetic polish at the end of projects.
• Prioritization tip: in RICE, temporarily ignore confidence and effort for high-reach, high-impact ideas so they are not prematurely deprioritized, then score them after exploring solutions.
• Use time-boxed 'appetite' thinking: pick a reasonable timebox and ask what you would build differently with less or more time to find the efficient frontier of cost versus impact.
• Track events from your servers rather than client SDKs to get full reach, consistent cross-platform data, and the ability to fix tracking without waiting for app updates.

02Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.