The Twenty Minute VCShreyas Doshi: The 6 Product Metrics You Need To Know; The 3 Types of Product Leader | E913
CHAPTERS
- 0:00 – 2:44
Shreyas’s path into product: engineering roots, visas, and first PM role at Yahoo
Shreyas shares how he started as an engineer in the early 2000s, navigated a difficult job market and visa constraints, and gradually got pulled into customer-facing work. Those early customer meetings sparked his interest in product, leading to his first formal PM role at Yahoo in 2006.
- •Early-career context in 2001 Valley and the difficulty of getting roles with visa needs
- •Move to Silicon Valley and exposure to customer interviews as an engineer
- •Realization that he enjoyed customer problem-solving and solution design
- •Decision to skip the traditional MBA route and pursue PM directly
- •First real product management experience at Yahoo
- 2:44 – 4:59
Defining product management and what “product success” really means
Shreyas defines product management as the art, science, and practice of making successful products and making products successful. He then breaks down “success” into three foundational dimensions that anchor how teams should think about outcomes.
- •PM as both creating success from scratch and improving existing products
- •Importance of distinguishing early-stage creation vs. scaling/turnaround work
- •Three pillars of product success: adoption, satisfaction, and business impact
- •Metrics vary by product and stage, but the pillars remain consistent
- •Success requires a balanced view across user, customer, and business lenses
- 4:59 – 6:01
Choosing adoption metrics: why outputs mislead and inputs matter
The discussion turns to the confusion around “the right” adoption metric. Shreyas argues that adoption is an outcome of underlying conditions, so teams should measure the drivers of adoption—not just the end result.
- •Adoption metrics alone can be misleading if treated as the primary lever
- •Adoption is an output; teams should focus on input/driver metrics
- •Usage understanding is required to know what leads to retention/adoption
- •Teams often over-debate metrics instead of shipping and learning
- •Early-stage teams still benefit from an adoption North Star—but not at the expense of inputs
- 6:01 – 9:01
The 6 categories of product metrics and how they fit together
Shreyas lays out a six-part taxonomy for product metrics to reduce confusion and improve decision-making. The key message: there isn’t one “best” metric—teams need multiple categories to see the full picture.
- •Six categories: health, usage, adoption, satisfaction, ecosystem, outcome
- •Each category answers a different question about product performance
- •A single metric cannot represent product reality end-to-end
- •Adoption improves when prerequisites (health/usage) are understood and managed
- •Metric selection should reflect product stage and current constraints
- 9:01 – 11:12
Health (hygiene) metrics: reliability as the silent growth killer
Health metrics measure whether the product meets baseline expectations for availability and performance. Shreyas explains why these metrics rarely drive growth directly, but ignoring them can severely suppress adoption and satisfaction.
- •Health metrics answer: is the product available and performing as expected?
- •User expectations vary by product category (ecomm vs social vs enterprise)
- •Examples: latency, load time, data loss rate, error rates
- •Health issues can invisibly block adoption even if funnels look fine
- •Health metrics don’t propel growth—but neglect can drastically impede it
- 11:12 – 14:34
The North Star Metric is not a panacea: avoid perfection, prioritize learning
Shreyas argues the North Star Metric is widely misunderstood and over-optimized. For early-stage teams, chasing the “perfect” NSM can distract from shipping improvements and building qualitative understanding of users.
- •NSM is useful, but not necessary to perfect—especially early-stage
- •Over-tweaking the NSM can lead to time wasted on measurement vs progress
- •Perfect metrics are often hard to measure and operationalize
- •Qualitative feedback often provides stronger early-stage signal than dashboards
- •Building a routine to review user feedback creates empathy and insight
- 14:34 – 16:48
Who owns product metrics and NSM: founder responsibility with smart delegation
Harry asks whether the CEO/founder or CPO should pick the NSM and prioritize metrics. Shreyas emphasizes that regardless of delegation, the founder must stay deeply involved because top-level metrics shape targets and organizational focus.
- •Core question: does the founder feel competent to define metrics/NSM?
- •Even if not competent, it remains ultimately the founder’s responsibility
- •Delegation to CPO/head of product can help, but founder involvement is required
- •NSM becomes a top-level target-setting and tracking tool
- •Most critical in early-stage contexts where product direction is fragile
- 16:48 – 18:50
The 3 product leader personas: Operator, Craftsperson, Visionary (as “hats”)
Shreyas introduces a framework for understanding senior product leaders through three archetypes. He stresses these are not rigid boxes; strong leaders can wear all three hats, but usually have a dominant mode.
- •Founders often hire VP Product/CPO due to growth or investor/board pressure
- •Three personas: Operator, Craftsperson, Visionary
- •These are hats, not permanent categories—leaders may switch by context
- •Hiring mismatch occurs when the hat needed doesn’t match the leader’s strengths
- •The right choice depends on business reality and founder capability
- 18:50 – 21:08
The Operator: scaling teams and alignment—powerful post-PMF, risky pre-PMF
The Operator excels at cross-org alignment, execution unblocking, and scaling rhythms. Shreyas warns that Operators often struggle with original product insight, making them a poor fit for finding product-market fit from scratch.
- •Operator strengths: scaling teams, cross-functional alignment, execution speed
- •Operator superpower: communication
- •Common weakness: original product insight
- •Pre-PMF hiring risk: an Operator may “operate” without moving PMF forward
- •Operators become crucial as complexity and dependencies rise during scale
- 21:08 – 24:47
When you truly need an Operator: the post-PMF complexity threshold
Using his experience scaling Stripe Connect, Shreyas explains the moment when operating and coordination become the dominant challenge. The transition is tied to product-market fit and organizational complexity more than funding stage labels.
- •Stripe Connect story: small team to massive scale, shifting role demands
- •Signal: work becomes dominated by coordination/management vs product creation
- •Operator value increases with cross-team dependencies and organizational rhythm
- •Not correlated perfectly with Series B/C/etc.; PMF and complexity are decisive
- •Operators help set targets, cadence, and alignment in multi-team environments
- 24:47 – 28:58
The Craftsperson: turning ambiguity into winning product detail (best early-stage default)
The Craftsperson is strongest at product definition, strategy translation, and mentoring PMs. Shreyas frames this persona as the best default for many early-stage companies because it converts vague direction into concrete experiences users love.
- •Craftsperson strengths: product definition, strategy, mentorship
- •Superpower: product insight and translation from ambiguity to concrete UX
- •Focus on pixels, flows, support experience, and end-to-end coherence
- •Typically dislikes large-org ‘taxes’ and constant alignment overhead
- •Often a strong default hire near pre-PMF/early PMF depending on founder needs
- 28:58 – 32:55
What breaks as product teams scale: repetition, alignment load, and meeting gravity
Shreyas describes two common failure modes as teams grow: internal coherence breaks and external dependency overhead explodes. Leaders must shift from one-to-one trust to one-to-many communication and spend increasing time in alignment.
- •Internal break: leader must become a ‘repeater’ of vision/strategy as headcount grows
- •One-to-many communication becomes mandatory; people retain less than assumed
- •Craftspeople often lose energy when away from product deep dives
- •External break: dependencies across sales/support/BD/marketing expand rapidly
- •Scaling increases meetings and coordination—often prompting craftspeople to seek earlier-stage work
- 32:55 – 35:26
The Visionary: inventing what’s next—and why competent vision is rare
The Visionary excels at big-picture invention and seeing what others don’t. Shreyas distinguishes competent vs incompetent vision largely by accuracy over time and highlights Amazon’s principle ‘leaders are right a lot’ as a useful lens.
- •Visionary strengths: big-picture thinking, invention, anticipating the future
- •Competent visionaries are rare; quality shows through being ‘more right’ over time
- •Process/OKRs alone don’t create breakthroughs without creativity and instinct
- •Operators may over-attribute success to process after a product is already working
- •Visionaries often need craftspeople/operators to execute consistently
- 35:26 – 39:02
Visionary vs Craftsperson and how founders should pair roles
Shreyas clarifies that vision is hard to translate into step-by-step product execution, which is where craftspeople shine. He explains why founders are often the visionary and why product leaders frequently need to help reconcile conflicting user feedback into coherent steps.
- •Key difference: visionaries struggle to translate big ideas into concrete steps
- •Craftspeople convert vision into flows, priorities, and shippable sequences
- •Many founders naturally occupy the visionary role early
- •User feedback pulls in many directions; the craftsperson helps create an executable path
- •Effective teams combine vision, craft, and (later) operational scaling
- 39:02 – 47:38
Customer feedback vs roadmap: strategy as the decision filter + the BTD framework
Shreyas argues that being ‘customer-driven’ can become a trap if it means blindly following requests. He introduces the BTD framework (Below table stakes / Table stakes / Differentiation) and illustrates it with Stripe Terminal competing against entrenched incumbents.
- •‘Customer-driven’ can devolve into reactive feature following
- •Strategy should define when to listen and when to say no
- •Stripe Terminal example: incumbents had years of table-stakes head start
- •BTD framework: choose intentionally where to be below, meet, or differentiate
- •Differentiation lets teams earn customer leeway while catching up elsewhere
- 47:38 – 57:12
Angel investing lessons, Collison archetypes, and time-to-value as motivation math
Shreyas shares how investing shifted his focus from ideas to founder capability, then maps Stripe’s founders to the persona framework. The conversation closes with time-to-value: it depends on customer motivation strength, alternatives, and ‘mandate products’ that can tolerate long rollouts.
- •Investing shift: great ideas aren’t sufficient; founder capability is the core bet
- •Litmus test: is the founder among the most capable people you’ve met?
- •Persona mapping: Patrick as visionary+craftsperson; John as unusually strong across all three
- •Time-to-value depends on customer motivation and availability of alternatives
- •‘Mandate products’ (e.g., Workday, NetSuite) can succeed with long time-to-value due to credibility and organizational mandate
- 57:12 – 1:01:27
Rapid-fire close: changed mind on metrics, hiring mistakes, new leader advice, self-assessment, and admired strategy
In quick-fire format, Shreyas revisits the nuance of metric types, warns about resume-driven product hiring, and gives advice for new product leaders to prioritize customer understanding and relationships. He ends with self-reflection on strengths/weaknesses and highlights Lead School’s strategy in India.
- •Changed mind: metrics require category awareness and stage-appropriate emphasis
- •Common hiring mistake: over-weighting resume/titles and under-weighting instinct/fit
- •Advice: deeply learn the customer/domain; don’t force 30-day impact; build relationships early
- •Self-assessment: strength in product sense; weakness in broadcasting progress org-wide
- •Impressed by Lead School’s strategy: combining curriculum, tech, and ops to improve K-12 education in smaller Indian cities
