Tag: product management leadership

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.

I’ve long believed the best products come from a careful blend of taste, simplicity, and storytelling. Studying how Figma operationalizes these principles has sharpened my own playbook for building, launching, and scaling products. In this piece, I distill the patterns I use and teach: how to approach new products, how to prioritize without losing the plot, and how to use narrative as a force multiplier for teams and customers.

At a high level, here’s the arc I focus on: approaching new products with a strong point of view, shaping product culture that balances craft with outcomes, understanding when to change course, tying business goals to product expansion, going multi‑product deliberately, recognizing the differences between “0 to 1” and “1 to 10” talent, and elevating storytelling from launch polish to a core build-time practice. Along the way, I’ll highlight why taste and simplicity aren’t luxuries—they’re strategy.

When I explore how to build from zero, I start with a crisp customer promise and a single, testable magic moment. The early days demand ruthless focus: one job-to-be-done, one path to value, one reason to share. As teams expand scope, the risk is layering utility without coherence. The countermeasure is systematic simplicity—every addition must make the core value faster, clearer, or more extensible. If it doesn’t, it’s noise.

Product culture is the scaffolding that makes this discipline stick. Speed and operational excellence drive the right kind of urgency; experimentation at scale validates hypotheses without cargo-culting metrics; and rigor in reviews ensures we’re prioritizing outcomes over output. The best cultures pair evidence with taste—data guides, but the bar for quality, narrative, and craft is set by humans with conviction.

Knowing when to change things is both an art and a system. I look for signal in stubborn user friction, plateauing activation, a long tail of workarounds, and moments when a new platform or workflow unlocks 10x value. The framework I use: if a change can simplify the path to the promise, or unlock a whole new class of users without diluting the core, it deserves energy. Change the defaults before changing the philosophy.

Business goals should sharpen, not overshadow, product expansion. Before adding surfaces or SKUs, I insist on clarity around the ICP, the premium moment worthy of pricing, the extensibility story for developers, and the narrative that unifies everything. Multi‑product strategy works best when each product is a chapter in the same book, not a pile of features. That’s why I appreciate how the ecosystem comes together across Figjam: https://www.figma.com/figjam/, Figma: https://www.figma.com/, Figma Dev Mode: https://www.figma.com/dev-mode/, and Figma Slides: https://www.figma.com/slides/—distinct entry points, shared language, and compounding value.

For “0 to 1” product work, I hire for curiosity, taste, and velocity. I want builders who can reduce ambiguity quickly, prototype with whatever tools are at hand, and tell a clear story about why their version of the problem matters. My favorite interview signal is a non-obvious customer insight that changed their roadmap. Entrepreneurial talent shows up in the questions they ask about distribution, pricing, and adoption—not just the feature.

I’m often asked why there aren’t more designer founders. My take: the gap is less about capability and more about exposure to distribution, pricing, and finance. Practical fixes help—give design leaders P&L ownership, put them on customer calls that include procurement, and pair them with GTM partners early. When designers are fluent in business mechanics, their advantage in taste and narrative becomes a superpower.

New product launches work best when the story is built in from day one. I like to “slow-cook” with tight, cross-functional squads, private betas with power users, and an explicit before/after narrative that connects the dots across product, docs, community, and developer ecosystem. As teams scale, I match talent to stage: “0 to 1” thrives in uncertainty; “1 to 10” excels at repeatability, quality, and operational excellence. Both are essential; mixing them at the wrong time creates drag.

Storytelling is not veneer—it’s how we align teams, earn stakeholder trust, and help users see themselves in the product. I anchor roadmaps to a one-sentence promise, show the painful “before,” demonstrate the “after,” and name the magic mechanic that makes it possible. Then I translate that story into prioritization. I stack-rank by value, confidence, and cost, and I’m explicit about what we won’t do. Strategy is as much the boundary as the plan.

If you’re refining your product storytelling, a quick checklist helps: articulate the promise in plain language, show rather than tell with a demo that lands the magic moment in 30 seconds, connect to measurable outcomes, and make the first-run experience feel like the narrative come to life. Don’t bury the lead. If a user can’t explain your product to a teammate after one minute, the story isn’t ready.

The difference between “good” and “extraordinary” product managers is simple to say and hard to do. Good PMs coordinate and ship on time. Extraordinary PMs set a higher bar for taste, simplify relentlessly, and move teams from consensus to conviction. They connect craft to outcomes, use narrative to create momentum, and make decisions that age well because the logic is legible.

Simplicity is a growth strategy. It shortens time-to-value, reduces error surface, and raises retention by making products feel learnable and trustworthy. Tactics I lean on: one hard thing at a time, remove to improve, defaults are design, and compress choices until the right path is the easy path. Simplicity isn’t less—it’s the right less.

Taste, in product and design, is not innate; it’s a practiced sensitivity to what feels inevitable. I cultivate it by collecting exemplars, writing and revisiting product principles, insisting on weekly critiques, and sweating the narrative as much as the pixel. The best teams hold two truths: quality you can feel and outcomes you can measure.

If you want to explore the ecosystem I referenced, here are direct links: Figjam: https://www.figma.com/figjam/, Figma: https://www.figma.com/, Figma Dev Mode: https://www.figma.com/dev-mode/, Figma Slides: https://www.figma.com/slides/.

Whether you’re building your first product or scaling a platform, the throughline remains: lead with taste, ship with simplicity, and align everyone with a story worth rallying around. That combination turns good teams into extraordinary ones—and products into movements.