I’m endlessly fascinated by leaders who can operate at every altitude—zooming out on strategy one minute and diving into the weeds the next. That’s why Anneka Gupta’s journey resonated so strongly with me, because it crystallizes how multi-disciplinary leadership accelerates product outcomes and go-to-market execution.
Anneka Gupta is the Chief Product Officer at Rubrik, a cloud management and data security company with a US$6B market cap. Before Rubrik, Anneka spent 11 years leading various teams at LiveRamp, including product, go-to-market, and operations.
One proof point that leapt off the page for me: LiveRamp went from $30M to $200M ARR in 3 years. That kind of growth rarely comes from product alone—it’s the compounding effect of crisp customer segmentation, tight GTM alignment, and a culture that prioritizes outcomes over output. In my own teams, anchoring OKRs to business outcomes rather than feature counts has been the most reliable way to unlock this momentum.
What I admire most is Anneka’s jack-of-all-trades career. Rotating through product, operations, and GTM builds a powerful intuition for how systems interact. I’ve seen the same benefit at scale: PMs who have shipped, sold, and supported the product make sharper tradeoffs because they integrate customer value, revenue mechanics, and operational feasibility in real time.
There’s a counterintuitive hiring lesson here too—why specialist hires can backfire. When the product or market is still evolving, over-optimized specialists often struggle without mature processes and stable interfaces. Early on, I bias toward adaptable builders who can define the playbook, not just run it. Specialists shine once the motion is proven and repeatable.
Altitude control matters. Knowing when leaders should get in the weeds is a differentiator. I’ve found three triggers: existential risk (security, reliability, or reputation), pivotal zero-to-one bets, and repeated cross-functional misalignment. Step in, diagnose at the system level, model the behavior you expect, and then step back out quickly so the team retains ownership.
There’s also one area every PM can improve in: customer-facing fluency. I agree with the principle that PMs should undergo the same training as sales reps. Shadow discovery calls, rehearse objection handling, and learn to speak to value drivers by persona. When PMs can authentically sell the problem and the solution narrative, product discovery gets faster and win rates improve.
Crafting products for different personas is another thread I pull on constantly. Buyers care about ROI, risk, and roadmap; users care about speed, clarity, and control. Great product discovery bridges the two by validating problem severity and adoption friction in parallel. That’s how you avoid building “the best product” that still loses because the buying committee can’t align on value.
I’m also struck by how deftly LiveRamp navigated enterprise shifts like transitioning Acxiom’s customers to LiveRamp and the broader dynamics of why Acxiom chose to buy not build. These moves demand rigorous change management—backwards compatibility, data governance guarantees, and clear migration value propositions. When the incentives align for customers and field teams, integrations become accelerants rather than tax.
Rubrik’s approach to building product underscores the same fundamentals: focus on critical customer outcomes, connect roadmap to go-to-market reality, and measure what matters. In practice, that means linking product bets to explicit revenue or retention hypotheses and setting guardrails so teams can run fast without creating long-term complexity debt.
I also appreciate the humility in reflecting on mistakes and the outsized impact of mentors and peers. The best leaders I’ve worked with narrate their decision-making—what they knew, what they assumed, and what they’d do differently—which compounds organizational learning. It’s the difference between isolated wins and a repeatable operating system.
If I distill my own playbook from these themes, it looks like this: hire for adaptability early, specialize later; anchor to outcomes vs output to avoid local maxima; keep PMs close to the sales and support edges of the system; and practice altitude shifting as a daily discipline. The result is a product organization that learns faster than the market changes—arguably the only durable advantage.
