Question 1

What are the key takeaways from Vijay's episode on Lenny's Podcast?

Accepted Answer

1. When your core product is losing to competitors, ruthlessly refocus by sorting churn reasons by ARR and making that your entire roadmap - speed comes from extreme clarity and focus. 2. Great products win or lose based on their system architecture - invest in defining the fewest possible building blocks and how they relate, so every new feature inherits maximum reach and discovery. 3. Invest profits, not people, into new ventures - pulling engineers off the core product to build bolt-on adjacencies leaves you ripe for disruption and produces mediocre products nobody needs. 4. The RICE framework's confidence and effort scores prematurely kill innovative ideas - sit with high-reach, high-impact bets long enough to find creative, lower-effort approaches before scoring them. 5. Give engineers and designers direct, ungated access to raw customer feedback - the culture of engineers emailing customers directly and asking the five whys produces better products than any gatekept process.

Question 2

What does Vijay say about prioritization and focus?

Accepted Answer

"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 roughly product features we needed to build, sorted descending by ARR, took the top 10 things and made that our roadmap, just give every engineer direct access to customers and give them a bucket to go work on." - Vijay Iyengar "We needed to optimize for speed, and speed comes when you have extreme clarity on what you want to do and focus. And so we really just optimize for speed in that time. And so in that first year we moved really quickly and we shipped something like a hundred features in that year and closed a lot of gaps. Again, these are all vanity metrics. Measuring number of features doesn't mean anything." - Vijay Iyengar "So many great products win or lose based on their architecture. I think Notion, for example, that pages in blocks architecture is so strong, and you can hang so many features off of those core building blocks in a way that has such high impact on region and discovery of those features." - Vijay Iyengar

Question 3

What are Vijay's views on prioritization, focus, product-architecture?

Accepted Answer

Vijay Iyengar: "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 roughly product features we needed to build, sorted descending by ARR, took the top 10 things and made that our roadmap, just give every engineer direct access to customers and give them a bucket to go work on." Vijay Iyengar: "We needed to optimize for speed, and speed comes when you have extreme clarity on what you want to do and focus. And so we really just optimize for speed in that time. And so in that first year we moved really quickly and we shipped something like a hundred features in that year and closed a lot of gaps. Again, these are all vanity metrics. Measuring number of features doesn't mean anything."

Vijay

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

TRANSCRIPT

Vijay

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

Vijay

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

TRANSCRIPT

Vijay

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