Vijay

Vijay Iyengar is Head of Product at Mixpanel, and similar to myself, came from an engineering background before transitioning to product.

9 skills 11 insights

Communication Skills

To effectively decline ideas, first sincerely attempt to find a path to 'yes' and document the process to provide a reasoned 'no'.

"One thing that I've found is the best way to get to a no, if you ultimately need to get there, is to try to make it work. Start trying to make yes work and document how you've tried to make yes work...."
04:55

Engineering Skills

Server-side tracking is superior to client-side SDKs for data reliability, cross-platform consistency, and developer maintenance.

"The biggest mistake is setting up analytics using client side SDKs... start tracking events from your servers instead of from your clients."
35:12

Hiring & Teams Skills

Use a chronological 'story of you' question to evaluate a candidate's self-awareness, priorities, and how they view collaborators.

"One of the questions I ask in the behavioral interview at the start is, walk me through the story of you from college to now... interesting to see where people spend most of their time talking and whe..."
43:43

Leadership Skills

To achieve high-quality design, decouple designers from tactical execution for a set period to allow for deep architectural thinking.

"We said, 'Hey, we can actually do the next three months of projects about any design,' which was a kind of controversial thing to say, 'but we're doing this so that you can take three months with a se..."
16:15

Product Management Skills

Protect your core product from disruption by reinvesting profits rather than diverting existing talent to new ventures.

"If you are the leader in some core product, our takeaway here is you should continue to out invests everyone else in that core and then invest the profits that come out of that core into the next vent..."
00:18

A strong product vision is built on a robust system architecture and a minimal set of powerful building blocks.

"This design driven initiative was really about how can we think about the system architecture of our product? What are the key building blocks of Mixpanel? Where do they need to fit? How few of them c..."
10:53

In a competitive crisis, prioritize the roadmap by quantitatively mapping churn reasons to lost revenue (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 roughly product features we needed to build, so..."
09:21

Standard prioritization frameworks like RICE can kill innovation if confidence and effort scores are applied too early to complex ideas.

"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... ignore the C and E..."
25:35

Structure goals as 'bets' that combine problem definition, hypothesis, execution plan, and success metrics.

"The anatomy of a bet is that it's problem we want to solve, our hypothesis on the solution, and then some plan to win, some plan to actually get there and a way to measure that you got there."
21:18

Use 'appetite' (fixed time) as an input to force scope-hammering, rather than using variable estimates as an output.

"Instead of making the estimate an output of planning, you make the time box or an appetite the input, and you say, 'We want to solve X problem and we're willing to invest six weeks solving that proble..."
27:23

Democratize customer feedback by piping raw, unedited user pain points directly into shared team channels.

"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"
30:43