An inside look at Mixpanel’s product journey | Vijay Iyengar (Head of Product)

1. Invest Profits, Not People

If you lead in a core product, continuously out-invest competitors in that core, then use profits (not people or venture capital) to fund new ventures to avoid distracting your core team and leaving yourself vulnerable to disruption.

2. Try to Make Yes Work

As an engineer or product leader, instead of immediately saying “no” to new ideas, earnestly try to make “yes” work and document your efforts; this approach protects fragile ideas and leads to better outcomes.

3. Avoid Nth Best Products

Be cautious about expanding into new product categories where you’ll only be the “nth best,” as these bolt-on products often contribute little revenue while distracting resources from your core offering.

4. Optimize for Speed in Crisis

In highly competitive situations with critical missing features causing churn, prioritize speed to address table stakes problems quickly, focusing on immediate fixes over long-term holistic design.

5. Prioritize System Architecture Design

After addressing immediate feature gaps, prioritize a design-led initiative to define the product’s system architecture and core building blocks, ensuring consistency and maximizing the reach and discoverability of new features.

6. Grant Designers Strategic Breathing Room

To enable strategic design work, temporarily decouple designers from tactical, engineering-led projects, giving them dedicated time (e.g., three months) to focus on holistic product architecture without immediate feature demands.

7. Delay RICE Confidence/Effort

When using the RICE framework, initially ignore the “Confidence” and “Effort” scores for high-reach, high-impact ideas, allowing engineers and designers to explore solutions for a week before re-evaluating with C and E.

8. Use Appetites, Not Estimates

Instead of estimating project duration, set a timebox (appetite) as the input for planning, then explore how the solution would differ if given more or less time to find an efficient frontier of cost and impact.

9. Provide Raw Customer Feedback Access

Create a direct, ungated feed of raw customer feedback (e.g., in Slack) for all engineers and designers, empowering them to consume context, reach out to customers directly, and develop a product mindset.

10. Default to Server-Side Tracking

Avoid client-side SDK tracking for analytics due to poor data quality and maintenance issues; instead, default to tracking events from your servers for cross-platform consistency, environment control, and easier developer adoption.

11. Centralize Data in Warehouse

Utilize a data warehouse (e.g., Snowflake, BigQuery) as the central hub for all company data (product, marketing, sales) to ensure all teams operate from a single, consistent source of truth.

12. Model All Data as Events

Adopt events (time series of user actions) as the universal data model for all analytics, as every customer interaction can be granularly and intuitively modeled this way, enabling powerful sequence-based questions.

13. Cultivate Engineer Product Mindset

Encourage engineers to adopt a product mindset by getting closer to customers, consuming raw customer feedback, and actively engaging with them to foster innovation and build better products.

14. Six-Month Strategy & Bets

Plan on a six-month horizon, starting with a leadership strategy memo, then have teams develop “bets” (problem, solution hypothesis, plan to win, and success metrics) based on this strategy and customer context.

15. Leadership Joins Bet Ideation

Leaders should actively participate in team ideation and solution discovery during planning, contributing ideas and thoughts to foster high-bandwidth communication and ensure alignment on bets.

16. Linked Planning Artifacts

Document planning outcomes using linked artifacts: a Notion database for detailed bets (problem, evidence, impact, success, hypothesis, plan), a summary presentation, and an execution plan for sequencing and staffing.

17. Organize Teams by Paired Tensions

Organize cross-functional teams around long-lived, paired problems that have inherent tensions (e.g., power vs. simplicity), forcing the team to confront and resolve these trade-offs to create better solutions.

18. Enrich Customer Feedback Data

Continuously enrich customer feedback feeds with relevant account information (e.g., ARR, CSM) to provide engineers with necessary context, enabling them to make informed decisions before contacting customers.

19. Build Internal Tools with Reverse ETL

Leverage a data stack with reverse ETL tools (e.g., Census) to push modeled data from your data warehouse to other tools, enabling the creation of low-code internal tools and automating information flow to teams.