Lenny's PodcastThe full-stack PM | Anuj Rathi (Swiggy, Jupiter Money, Flipkart)
CHAPTERS
- 0:00 – 0:49
Cold open: Why leaders don’t get the outcomes they want (can’t / won’t / not set up)
Anuj opens with a simple diagnostic for leadership breakdowns: performance issues usually come from capability, motivation/alignment, or poor setup by leadership. He frames the leader’s job as choosing the right intervention—coaching, role changes, alignment work, or redesigning systems.
- •Three failure modes: can’t do (capability), won’t do (motivation/alignment), not set up to do (system/design issue)
- •Leaders should diagnose before reacting with feedback or pressure
- •Coaching/mentoring vs. moving people to better-fit roles
- •Alignment questions: vision buy-in, time, incentives, priorities
- •Setup issues often stem from ways of working, org design, or OKRs
- 0:49 – 5:20
Anuj’s career path: Flipkart to Swiggy to Jupiter Money
Lenny introduces Anuj and why he was the most-requested India-based product leader. Anuj briefly traces his long tenure in product, starting early in India’s modern consumer-internet era and building across multiple major companies.
- •Early PM journey starting at Flipkart in 2010
- •Leadership roles across Swiggy, Snapdeal, Walmart Labs, and now Jupiter Money
- •Why India’s product ecosystem made early PM experience rare and valuable
- •Lenny’s framing: broad scope spanning product, growth, revenue, and marketing
- 5:20 – 8:34
How product building in India differs: ecosystem maturity, expectations, and “software isn’t machinery”
Anuj explains how India’s product management evolved differently because many teams historically built for overseas customers, not Indian consumers. As startups grew, product practices had to be adapted, and broader leadership functions had to learn how iterative software products really work.
- •Pre-2010: strong engineering, but much of the work served global/back-office needs
- •Lack of local PM playbooks, education, and trained talent in early days
- •Leadership from non-software backgrounds often expected predictable ‘machinery-like’ outputs
- •Product maturity improves as leaders experience cycles and learn consumer unpredictability
- •India still converging toward best-in-class modern product practices
- 8:34 – 10:24
When modern consumer internet took off in India: the 2010 inflection + early category pioneers
The conversation pinpoints 2010 as the major ramp-up for India’s modern product era, while acknowledging earlier pioneers. Anuj highlights travel and matrimony as early categories that built uniquely for Indian behavior and norms.
- •2010 as the clearest start of the modern ‘build for India’ wave
- •Earlier exceptions: travel (e.g., MakeMyTrip) and matrimony marketplaces (e.g., shaadi.com)
- •Category patterns: consumer internet often starts with travel in many countries
- •Subsequent startup waves: rides (Ola), food delivery (Swiggy era ~2014–2015), and beyond
- 10:24 – 14:01
India’s scale and complexity: Jio, UPI/India Stack, languages, and pricing realities
Anuj outlines why India is both a massive opportunity and uniquely complex: cheap mobile internet and digital public infrastructure brought huge populations online, but diversity and low per-capita spend reshape product strategy. Success depends on understanding segments, language/culture variation, and willingness-to-pay dynamics.
- •Jio revolution: dramatically cheaper mobile data brought new users online
- •UPI + India Stack: identity/payments rails enabling new product layers and behaviors
- •Extreme linguistic and cultural diversity changes segmentation and UX assumptions
- •Low per-capita spend makes monetization and ‘right paying customer’ selection critical
- •High engagement potential, but harder conversion to sustainable revenue
- 14:01 – 14:54
Designing for new users: most customers don’t care (yet)
Anuj shifts to onboarding and new-user experience, stressing that teams overestimate how much users think about their product. The real challenge is earning attention from people who have heard of you but haven’t committed time or trust.
- •PMs are biased by closeness to the product; users are not
- •New users often have weak context and limited patience
- •Onboarding and first impressions can matter more than deep feature work
- •Start from how users discover you and why they finally decide to try
- 14:54 – 17:16
Scott Belsky’s framework: users are lazy, vain, and selfish (and how to design for that)
Anuj adopts Scott Belsky’s lens to build empathy for first-time users. By assuming users are time-poor, habit-bound, and benefit-seeking, teams can craft tighter messaging, clearer onboarding, and better activation flows.
- •Lazy: limited attention—need immediate value and clarity
- •Vain: resistant to changing habits and routines
- •Selfish: ‘what’s in it for me?’ must be explicit
- •Copy, onboarding, and welcome flows should be designed to overcome these barriers
- •Treat the framework as a forcing function to reject weak experiences early
- 17:16 – 24:20
Operationalizing onboarding: connect marketing promises to in-product reality (Swiggy + Jupiter examples)
Anuj describes aligning acquisition channels, marketing hooks, promotions, and onboarding so the user journey feels continuous. He also extends the same thinking to multi-product apps: don’t overwhelm; earn trust with one hook and introduce adjacent value at the right time.
- •Map the full pre-download story: awareness → trigger → download → first use
- •Ensure onboarding continues the exact promise made in ads/promos
- •Avoid ‘here’s everything we do’; focus on one clear hook value prop
- •Cross-sell in multi-product apps requires behavioral science and timing
- •PMs should understand category consumers as well as marketers do
- 24:20 – 28:52
Working backwards in practice: PR/FAQ as a GTM and alignment tool (plus the power of three)
Anuj explains how he uses Amazon’s working-backwards process beyond defining customer value—he uses it to plan the entire go-to-market “machinery.” He advocates writing three divergent PR/FAQs to explore options, surface disagreements early, and help leaders choose with clarity.
- •PR/FAQ works backward from a launch day with full operational readiness, not just features
- •Use PR/FAQ for negotiation with engineering, marketing, pricing, and business owners
- •Quotes and FAQs surface hidden blockers and build alliances early
- •Write three divergent PR/FAQs to compare/contrast and avoid missing alternatives
- •‘Disagree and commit’ becomes easier after structured option exploration
- 28:52 – 30:39
The FAQ section as a systems check: compliance and marketplace side-effects
Anuj highlights FAQs as a way to institutionalize non-negotiables (e.g., compliance in fintech) and to force marketplace thinking. In multi-sided systems, small changes cascade, so explicit FAQ prompts prevent blind spots across partners and users.
- •Fintech example: FAQs must include compliance/legal sign-offs as defaults
- •Marketplace example: force explicit analysis of impacts across all sides
- •Codify “have we considered X?” questions to reduce repeated mistakes
- •FAQs help teams consult other stakeholders earlier and more systematically
- 30:39 – 33:27
Full-stack PM mindset: owning outcomes, not features (and why range beats narrow specialization)
Anuj argues PMs must be accountable for business and behavior outcomes, which requires broader ‘full-stack’ thinking across product, marketing, engineering, competition, and operations. He references the idea of ‘range’—connecting dots across disciplines—to make better decisions and ship more effective products.
- •Success = behavior change + business impact + capability building (not just shipping)
- •Full-stack PMs build partnerships across functions to pressure-test decisions
- •You don’t need to be the authority in every area, but you must integrate inputs
- •Range mindset: cross-domain exposure helps connect dots and innovate
- 33:27 – 41:36
“Show, don’t tell”: make ideas concrete with end-to-end journeys and strategy-on-a-page
Anuj introduces a visual, high-fidelity method to communicate product direction: build the full user journey (even down to copy and emotional state) rather than abstract explanations. He extends this to leaders via “strategy on a page” to align teams around a shared model of growth and priorities.
- •Build from a real ‘person’ in a real moment, not generic personas
- •Map triggers → first screen → flows; ensure every pixel/copy serves the job-to-be-done
- •For marketplaces, model parallel experiences and emotional states during waiting/uncertainty
- •Create a shared ‘wall’ artifact for stakeholder alignment and decision-making
- •Leader version: strategy-on-a-page / growth-loop style models (often in 3 alternatives)
- 41:36 – 48:59
4BB product strategy: Brilliant Basics, Bread & Butter, Big Bets, Breaking Bad
Anuj shares a portfolio framework to structure strategic prioritization discussions with CEOs and leadership. The goal is to allocate “focus points” across foundational work, incremental improvements, high-upside bets, and existential redefinition moves—making trade-offs explicit.
- •Brilliant Basics: foundational platform/tech debt reframed as essential excellence
- •Bread & Butter: ongoing product backlog improvements within current business lines
- •Big Bets: cross-team, high-upside initiatives requiring PR/FAQ-level rigor
- •Breaking Bad: identity shifts/pivots that redefine the company’s future
- •Use the framework to clarify trade-offs, set expectations, and align execution
- 48:59 – 50:55
Contrarian corner: choose excellence over speed; don’t run doomed experiments
Anuj offers contrarian takes on execution culture. If forced to choose, he recommends thinking harder and shipping better, and argues many experiments should be resolved through thought experiments before consuming company bandwidth.
- •Speed vs. excellence: if you must choose, bias toward excellence
- •Many experiments are predictably weak and should be killed via upfront reasoning
- •Meta-thinking can save significant time compared to ‘ship and see’
- •Quality is especially important when you need something marketable and differentiated
- 50:55 – 53:50
Framework of 3 for great PMs + developing grit and influence
Anuj’s “three essentials” for PMs are sharp problem-solving, grit/drive, and influence. He emphasizes influence as non-negotiable and discusses what can be developed (domain knowledge, decision quality) versus what’s harder to coach (deep drive).
- •Three PM pillars: raw sharps, grit/drive, and influence
- •Domain knowledge can dramatically raise decision quality for ‘average-smart’ PMs
- •Drive is hardest to coach, but leaders can inspire and set conditions
- •Influence is required—PM work is fundamentally about changing minds and behaviors
- 53:50 – 56:21
Why leaders fail: capability vs motivation vs setup (and why setup is usually the culprit)
Returning to the opening theme, Anuj expands the leadership diagnostic into a practical management lens. He argues most failures are ‘setup’ problems—org design, OKRs, and ways of working—and references Conway’s Law and Team Topologies as guides.
- •Performance diagnosis: can’t do, won’t do, or not set up to do
- •Setup issues are often the majority cause of execution failure
- •Org design and OKRs can unintentionally produce poor product outcomes
- •Conway’s Law: product/architecture often reflect organizational structure
- 56:21 – 57:51
AI corner: combine AI with HI (human intelligence) for real product outcomes
Anuj cautions against treating AI as a shiny solution in search of a problem. He recommends designing AI products as a partnership between artificial intelligence and human intelligence—grounded in UX and behavioral science—to create real consumer value.
- •Many teams over-apply AI without clear problem framing
- •Best results come from AI + HI working together
- •Great UX and behavioral science remain essential for consumer AI products
- •Backend-only automation is the exception; most products need human-centered design
- 57:51 – 1:05:08
Marketplace lessons: stability, multi-empathy, and why OKRs/A-B tests can fail
Anuj explains why marketplaces behave differently: complexity multiplies across sides, levers conflict, and network effects break standard experimentation. He recommends anchoring on marketplace stability, clarifying who the company ultimately serves, and using integrated ‘big bet’ narratives rather than isolated OKRs.
- •Marketplaces are multiplicative systems; simple management tools often break down
- •OKRs can create constant cross-side conflict in three-sided marketplaces
- •A/B tests are distorted by network effects and shared liquidity pools
- •Rule 1: keep all sides stable enough that they don’t churn away
- •Define primary service orientation (consumer-first vs seller-first) and align values accordingly
- 1:05:08 – 1:12:29
Lightning round: books, interview questions, life motto, and community building
In rapid-fire questions, Anuj shares influential books, entertainment favorites, and how he interviews PMs using speed vs. excellence trade-offs. He also shares a personal mantra about taking responsibility and describes his “Secret, Secret Soiree” events for connecting with interesting people.
- •Book recs: Working Backwards, How Brands Grow I & II, The Luxury Strategy
- •Favorite show reruns: The Office (US + UK)
- •Interview focus: when to optimize for speed vs. excellence; assess market/risk thinking
- •Life motto: stop externalizing—take responsibility for outcomes
- •Community: “Secret, Secret Soiree” and future cohort-style meetups
