May 17, 2024, 10:00 AM ETInterview, Fireside Chat

Jiaona Zhang: Why All Product Teams Should Have a Scorecard & How to Use It | E1154

Alex identifies the current era as the "most exciting time to be a product leader" due to the acceleration of innovation and the necessity of rapid iteration.
The product role is described as a "chameleon role" that requires blending into sales, support, and engineering functions to gather critical user insights.
Alex transitioned from an economics background and consulting to product management by leveraging analytics skills to secure a mobile gaming PM role at Google, noting the difficulty of entering without a CS degree or elite pedigree.
The gaming industry was pivotal in developing Alex's product mindset due to its high-frequency "learn and build" cycles, where engaging users requires constant, rapid iteration.
Advice for aspiring product managers without traditional backgrounds is to join a company building a product they are passionate about to secure high-volume learning reps, even if it means starting in a smaller environment.

Alex asserts that in product development, it is mathematically impossible to optimize for speed, quality, and scope simultaneously; one must always be traded off.
Alex explicitly prioritizes speed over scope, arguing that the speed of learning is the primary determinant of a company's survival and competitive edge.
Quality is treated as a non-negotiable constraint; products that fail to meet market quality standards will not be adopted regardless of other factors.
The relationship between scope and quality is defined as a "seesaw," where value is delivered either through high breadth of features (scope) or high depth of experience (quality), depending on the customer's specific need.
In markets where manual processes are replaced by automated tools, the expanded scope of functionality can be interpreted by customers as an increase in quality.

Alex advocates for the use of a "KPI Tree" to align teams, starting with top-level business output metrics (e.g., revenue, ARR) and flowing down to input metrics and product metrics.
Product leaders should own business metrics; separating product from business health is described as "harmful" because products are the vehicle for delivering business value.
The KPI Tree structure flows from business output metrics (financial health) to input metrics (drivers of revenue like subscriptions) to product metrics (adoption, NPS, activation, retention).
Startups should establish the "skeleton" of a KPI Tree on day one to prevent "growth masking problems" and to ensure the organization understands the causal links between levers and outcomes.
A common founder mistake is over-focusing on vanity metrics without understanding the underlying equation of how actions drive specific outcomes.
Alex challenges teams to identify what data can be gathered quickly (leading indicators) within an hour or a day, rather than waiting for slow-moving output metrics like sales cycles.
Growth teams should avoid "micro-optimizing" numbers; instead, they must pursue "step function" changes through meaningful product modifications to achieve global maximums.
Teams must articulate "hypotheses" regarding how specific changes will drive growth, rather than simply accepting a number quota without a strategic narrative.

Alex distinguishes between "planning" (a rigid, often discarded process) and "strategy" (a concise, two-page document outlining vision, investment areas, and exclusions).
The concept of "planning should not exist" refers to discarding detailed, rigid roadmaps in favor of maintaining a clear strategy and adaptable rituals.
Alex proposes three core rituals to replace rigid processes:
- Scorecard: A transparency ritual tracking the top 5–10 most important projects, graded as Green, Yellow, or Red to highlight risks and force proactive de-risking.
- Product Jams: High-intensity, synchronous brainstorming sessions (ideally daily for 0-to-1 products) to align teams on success criteria and rapidly explore solution divergences.
- Demo Power Hour: A weekly forum for showing work-in-progress (even broken versions) to reinforce velocity, ownership, and pride in shipping.
Leaders must model "1.5x urgency" by making faster decisions themselves to instill a culture of speed and impact throughout the organization.
User empathy is driven by frequently bringing actual users into company all-hands to demonstrate the tangible impact of the team's work.

Founders should delay hiring a dedicated product leader until after achieving product-market fit, initially leveraging existing engineering, design, or support staff to build leverage.
Hiring a CPO should focus on finding a leader who complements the founder's specific weaknesses (e.g., sequencing, industry expertise) rather than finding a duplicate visionary.
Alex favors "journalist" style product leaders who lack deep domain bias, allowing them to apply mental models from other industries to spot unique opportunities.
Tension between product and functions like sales and engineering is inevitable and healthy; the product leader's role is to dissipate this tension and convert it into productive prioritization.

Alex does not fear market convergence (e.g., between website builders and link-in-bio tools) because crowded spaces indicate strong user demand and pain points.
The long-term bet is that SMBs and creators will never build their own websites with engineering teams; they will rely on tools like Webflow and Linktree for "pixel-perfect" brand expression.
Linktree's $100 billion valuation potential requires a sequential "crawl, walk, run" approach, moving from being a utility to a destination with repeat usage and brand partnerships.
Webflow is viewed as the tool for deep brand control, while Linktree serves the mass market of creators who need simplicity over advanced features.
Open AI and Meta (via WhatsApp) are cited as companies that have successfully executed on bold, long-term bets despite initial market skepticism.
Alex expresses optimism in "crawl" phase initiatives like integrating data from brands and creators to unlock partnership opportunities, rather than rushing into a consumer-first discovery model immediately.

Common PM mistake: Jumping straight to the solution space without deeply understanding the user's problem.
Path to promotion: Focus on high-impact work in a specific area and build a personal brand of expertise in that domain.
Notable products: Alex cites ChatGPT and Meta's Quest as recent "wow" moments for their technological leaps and long-term vision.
Most common advice to Gen Z: Leverage their innate understanding of new interfaces and platforms that older generations may not grasp.