The Twenty Minute VCJiaona Zhang: Why All Product Teams Should Have a Scorecard & How to Use It | E1154
CHAPTERS
- 0:00 – 2:28
From consulting to product: discovering a builder’s role (and why gaming is PM bootcamp)
Jiaona Zhang shares her non-traditional path into product, moving from economics and consulting into PM work by leaning on analytics as her wedge. She explains why mobile gaming taught her fast iteration, constant learning, and user engagement fundamentals.
- •Left consulting because advising wasn’t enough—wanted to build and iterate
- •Product wasn’t obvious as an undergrad; discovered it through research and curiosity
- •Used analytics/econ background to break into PM despite no CS/elite-school pedigree
- •Mobile gaming’s rapid release cycle creates intense learning reps
- •Gaming builds strong instincts for engagement and iteration
- 2:28 – 3:11
How to break into product management without the “standard” credentials
JZ’s core advice for aspiring PMs is to optimize for repetition and learning velocity rather than brand names. She recommends choosing environments where you can ship frequently and build real craft through continuous cycles.
- •If you can’t enter formal PM rotational programs, find a passion area to work on
- •Prioritize roles/companies where you can ship often and learn weekly
- •High-frequency reps can outweigh slower, quarter-long delivery cycles
- •Early career focus should be skill accumulation and feedback loops
- •Choose opportunities that maximize learning, not prestige
- 3:11 – 6:02
The speed–quality–scope triangle: what to trade off (and why)
JZ argues you can rarely maximize speed, quality, and scope at the same time—something must give. Her preferred trade-off is scope: keep speed for learning and keep quality high enough that market feedback is valid.
- •Define scope as the amount/breadth of features built
- •You usually can’t get speed, quality, and scope simultaneously—especially with new teams
- •JZ trades off scope first to preserve fast learning cycles
- •Avoid trading quality too far or you’ll misread market response (it failed because it was bad)
- •Quality can mean aesthetics, usability, or “job completeness,” depending on customer
- 6:02 – 7:51
Shortening “slow” feedback cycles: leading indicators and rapid qualitative data
Even in industries with slower quantitative outcomes (e.g., SaaS sales cycles), JZ insists there’s always data you can get quickly. She reframes data as information across time horizons—qualitative input now, output metrics later.
- •Data includes qualitative feedback, not just lagging metrics
- •Identify what you can learn in an hour/day/week as leading indicators
- •Use alphas and customer sessions to get immediate signal
- •Separate input signals from output metrics that take months to show up
- •Prototype, test increments, and validate direction before full builds
- 7:51 – 10:35
Codifying learning with a KPI tree: connecting product work to business outcomes
JZ introduces the KPI tree as a way to document how actions and product metrics ladder up to business results. She emphasizes business metrics at the top and argues separating “product” from “business” is harmful.
- •KPI tree structure: top-level output business metrics → input drivers → product metrics
- •Top should be shared company-wide (CEO dashboard metrics, e.g., nights booked)
- •Input metrics explain what must change to move outputs (subs, churn, retention, etc.)
- •Product metrics often start with adoption and satisfaction, then behavior change
- •Purpose is shared understanding of cause-and-effect across the org
- 10:35 – 13:12
When to build metric infrastructure—and the biggest mistakes with metrics
JZ recommends having at least a ‘skeleton’ KPI tree early to avoid panic when growth slows. She warns against metric obsession without a clear narrative of success, investment rationale, and causal links.
- •Have a KPI tree skeleton from early days to understand business levers
- •Growth can mask underlying issues until it stalls
- •Teams need a qualitative “headline” plus a metric—not metrics alone
- •Leaders must understand linkage across business components to allocate investment
- •Common pitfall: focusing on numbers without clarity on what actions drive them
- 13:12 – 16:40
Different metrics for different teams: align on strategy, then tailor incentives
JZ explains that company strategy should be shared across all functions, but execution metrics differ by team. She critiques growth teams that micro-optimize local maxima and advocates for step-function product changes driven by clear hypotheses.
- •Company-wide strategy aligns everyone; team-level metrics can and should differ
- •Sales may need quota; other teams need different goal structures
- •Growth teams need numbers but shouldn’t micro-optimize with tiny tweaks
- •Aim for step-function gains via core product changes
- •Demand explicit hypotheses from teams, not just dashboards
- 16:40 – 17:44
Proving (or killing) hypotheses faster: prototypes, landing pages, staged signals
To avoid lingering too long on failing bets, JZ advocates for early signals at every stage. She describes lightweight testing methods that generate evidence before building full end-to-end flows.
- •Early signals can arrive in hours through user tests
- •Prototype and put in front of target users to gauge desirability
- •Use landing pages/template selection as behavioral data before full build
- •Validate in small increments while keeping the big picture in mind
- •Reduce time wasted by structuring evidence gathering across stages
- 17:44 – 20:13
The product leader as ‘chameleon’: cross-functional boundaries and user closeness
JZ describes product leadership as inherently cross-functional, shifting into sales, support, or other areas to fill gaps in understanding. She also shares tactics for keeping product teams close to users in scalable ways.
- •Product is a chameleon role—leans into other functions as needed
- •Goal is to be the glue across exec team and spot/close organizational gaps
- •Avoid product isolation by building tight loops with sales and support insights
- •Scalable user empathy: systematically mine frontline teams for patterns
- •Consistency requires remembering the core job: deeply understand users
- 20:13 – 22:51
Prioritizing feedback across diverse users: ICP clarity and Venn-diagram intersections
Faced with vastly different customer segments, JZ uses a structured approach: clarify who is not the ICP, then find overlapping needs among the users you do serve. For Linktree, she argues creators and SMBs share key workflow problems in a fragmented digital world.
- •Start by clarifying who is not your user (negative ICP definition)
- •Don’t over-constrain if it artificially limits business potential
- •Use a Venn diagram of segment needs to find intersection priorities
- •Linktree example: unify digital presence amid platform fragmentation
- •Creators are SMBs and SMBs are creators—shared needs enable focused prioritization
- 22:51 – 26:46
The paradox of planning: replace rigid plans with crisp strategy and strong rituals
JZ argues traditional planning cycles disappoint because reality changes quickly. Her alternative is spending most effort on a short, opinionated strategy document and building rituals that create agility with enough structure to avoid chaos.
- •Shift focus from planning/process to strategy/rituals
- •Strategy includes: future worldview, unique advantage, investment areas, and explicit ‘not doing’
- •Keep strategy concise (about two pages) with clear ownership (often CEO + CPO)
- •Planning often collapses by Q1 due to new info, delays, and customer pulls
- •Rituals build organizational muscle and adaptability
- 26:46 – 30:34
Ritual 1—Scorecard: radical transparency and early risk management
JZ’s first core ritual is a weekly scorecard tracking the most important cross-functional projects. It trains teams to surface risk early (yellow/red) and proactively unblock work rather than discovering failure at the end of the quarter.
- •Scorecard focuses on top ~5–10 critical projects, not everything
- •Weekly grading: green (on track), yellow (at risk), red (off track)
- •Early yellow/red is good—enables unblocking before deadlines collapse
- •Great teams anticipate issues and take action before scorecard meetings
- •Spotting problems relies more on judgment than pure data; requires clear success definition
- 30:34 – 37:52
Rituals 2 & 3—Product jams and Demo Power Hour: co-creation, velocity, ownership
JZ contrasts ‘review culture’ with collaborative product jams that compress cycles and reduce waterfall handoffs. She pairs this with Demo Power Hour to normalize showing work-in-progress, build pride, and reinforce shipping velocity.
- •Product jams bring the best brains together to create agility and alignment
- •Frequency depends on stage: near-daily for zero-to-one; targeted jams at key moments later
- •Remote jams require more prep but can work with tools like FigJam/Miro
- •Demo Power Hour encourages showing unpolished work; it’s okay if it breaks
- •Regular demos create visibility, pride of ownership, and a culture of shipping
- 37:52 – 53:06
Hiring product leaders (and navigating rapid change): timing, CEO fit, and generalists vs domain experts
JZ cautions founders against hiring product leadership too early as a form of delegation and distancing from the product. When it is time, she stresses hiring for complementary strengths to the CEO, and discusses when domain expertise matters versus the advantages of generalist product leaders in fast-changing markets.
- •Don’t hire product too early just to ‘scale yourself’; founders must stay close to product
- •Before hiring PMs, seek leverage from existing leaders (EM, designer, support)
- •When hiring a senior product leader, prioritize CEO–product complementarity
- •Risk: visionary CEO + visionary product leader can create competing visions
- •Generalists can learn fast, avoid bias, transfer mental models, and adapt to rapid AI-driven shifts
- 53:06 – 58:18
Quick-fire: PMF mistakes, promotions, product ‘wow’ moments, and product strategy admiration
In the closing rapid-fire, JZ shares concise views on why startups miss PMF, how PMs can get promoted, and which products/companies impress her. She highlights the importance of problem-first thinking, being useful, and learning from bold strategic bets.
- •PMF failure often comes from jumping to solutions without understanding problems
- •Promotion advice: focus on high-impact usefulness and be known for something
- •Recent wow products: ChatGPT’s multimodality; Quest’s improved experience
- •Best orgs have productive tension across functions; product helps channel it
- •Admired strategies: OpenAI’s execution and search push; Meta’s platform chess moves; Disney+ recognizing content as the differentiator
