Most important take away

Stop spending time on rigid planning and processes; invest 80%+ of your energy in a sharp two-page strategy (vision, unique advantage, what you will and will not invest in) plus three repeatable rituals: a weekly scorecard for transparency, product jams for co-creation, and demo power hour for accountability. Between speed, quality, and scope, always trade off scope first because speed of learning is what compounds, and quality is non-negotiable in a crowded market.

Summary

Actionable insights and career advice from JZ, CPO of Linktree:

Career advice for breaking into product:

• You do not need a CS degree or a Stanford/MIT pedigree. JZ entered product via analytics skills from her econ/consulting background, joining a mobile gaming PM role because she could bring quantitative value.
• Prioritize where you can get the most learning reps. Gaming companies shipping daily produced far more cycles than companies that ship quarterly. “The best PMs have done some stint in gaming.”
• For PMs wanting promotion: stop chasing promotion, “be useful,” do high-impact work in a clear area, and “be known for something” so you are repeatedly picked for that brand.

The speed/quality/scope tradeoff:

• You cannot get all three. Always trade off scope first. Speed drives learning velocity and is existential; quality is required because the market bar is already high.
• Quality and scope have a relationship: in some markets quality means beauty (Notion vs. Google Docs), in others it means automating a previously manual workflow.

Data and feedback cycles:

• Reject the “our cycles are slow” excuse. Data is just information. Even in long-sales-cycle B2B, you can get qualitative signal in an hour by putting an alpha in front of target customers.
• Distinguish leading qualitative indicators from output metrics. Test small increments (landing pages, template pickers) before building full flows.

KPI Trees (metric infrastructure):

• Top of tree: business output metrics (the CEO dashboard - signups, nights booked, ARR). Product owners must own business metrics; separating product from business is harmful.
• Middle: input metrics that drive the business outputs (subscriptions, churn).
• Bottom: product metrics (adoption, then behavior change like retention/activation/conversion).
• Every company should have at least the skeleton from day one. “Growth masks all problems” - companies without a KPI tree panic when growth stalls because they cannot identify their levers.

Strategy over planning (JZ’s central philosophy):

• Spend 80%+ of time on strategy + rituals; almost zero on planning/process.
• A real strategy fits on two pages, is held by the CEO (often co-written with CPO), and articulates: vision/mission, what makes you uniquely positioned to win, investment areas, AND explicitly what you will NOT do.
• Planning cycles are mostly theater - they get blown up by Q1 anyway. Strategy can be updated when new information arrives; rigid plans cannot.

The three rituals (each maps to a principle):

1. Scorecard (principle: transparency)

   • The 10 most important cross-team projects (fewer is better), graded weekly green/yellow/red.
   • Trains teams to spot risk early. A bad team is green-green-green-red. A good team flags yellow early. A great team flags risk AND already has mitigation in motion.
   • Tracking is judgment-based, not data-based - ask the product/design/eng leads if it’s on track against clearly defined success criteria.

2. Product Jams (principle: co-creation/agility)

   • NOT a waterfall review (PM review -> design review -> eng review). A jam condenses cross-functional brainpower simultaneously.
   • For 0-to-1: jam almost daily, ideally in person or as close to synchronous as possible.
   • For mature products: jam at problem definition AND at solution divergence.
   • Remote jams work with FigJam/Miro but require more prep.

3. Demo Power Hour (principle: pride of ownership/accountability)

   • One free-flowing hour where anyone shows work-in-progress. Encourage things to break on stage to reinforce velocity.
   • Builds pride (“I did 3 demos this week”) and shifts culture toward shipping.

Driving urgency:

• Humans are motivated by impact on other humans. Bring users into all-hands every other week to build empathy.
• Model 1.5x the urgency you want from the team. Everything starts at the top.

Hiring a product leader:

• Common mistake: hiring a CPO too early to delegate away product responsibility. Founders must stay deep in product as long as possible. Use existing eng managers, designers, or support staff as leverage first.
• When you do hire, hire for complementarity to the CEO, not similarity. A visionary CEO who hires another visionary creates two competing visions. Define the specific problem the hire solves (sequencing? portfolio expansion?).
• Generalists with cross-domain mental models often outperform domain experts because they apply patterns (e.g., bringing marketplace thinking to a SaaS product).

The product role is a chameleon:

• The product leader is the “glue” of the exec team. They must lean into sales, support, or wherever the gap is. They drive sales/support to expose the team to user feedback at scale.

Prioritizing across user segments:

• Draw the Venn diagram of your customer types’ needs. Don’t artificially constrain - find the intersection. At Linktree: creators and SMBs both need to unify digital presence and reduce social-media workflow friction.

Tech/market patterns mentioned:

• AI-driven product cycles compress timelines; rigid planners struggle, strategy+rituals thrive.
• Great businesses are built in crowded spaces (demand is validated).
• Webflow’s “messy middle” thesis: must go UP the stack (e.g., Intellimize acquisition) to capture expansion revenue since landing engineering replacement is one-time.
• Linktree’s $100B path is consumer-first discovery (crawl: cut a step in the train station; walk: brand/creator marketplace; run: destination for content discovery).

Most common reason founders miss PMF: they jump straight to solutions and skip understanding the problem.

Chapter Summaries

1. Intro and JZ’s path into product: Econ major to consulting to mobile gaming PM. Lesson: optimize for learning reps, not pedigree.

2. Speed vs. quality vs. scope: Always trade off scope. Speed is existential; quality is required to clear the market bar.

3. Feedback cycles and data: Even slow B2B markets yield hourly qualitative signal if you put prototypes in front of customers.

4. KPI Trees: Three-layer structure (business output -> input metrics -> product metrics). Every company needs at least a skeleton from day one.

5. Goals by team: Strategy is shared company-wide; team-level metrics differ (growth teams need numbers BUT must articulate hypotheses for step-function changes, not micro-optimize).

6. Cross-functional nature of product: PM is a chameleon - leans into sales, support, design as needed. Push teams to user contact via cross-functional partners for scale.

7. Prioritizing user feedback across segments: Use a Venn diagram of needs. At Linktree, creators-and-SMBs intersect on “unify digital presence” and “automate social workflow.”

8. Planning vs. strategy: Kill planning. Invest in a two-page strategy (vision, alpha, investment areas, NOT-doing list) co-authored by CEO/CPO.

9. The three rituals: Scorecard (transparency, weekly RAG status on top 10 projects), Product Jams (co-creation, condensed cross-functional brainstorming), Demo Power Hour (pride/accountability, ship-in-progress demos).

10. Driving urgency: Bring users to all-hands; model 1.5x the urgency you want.

11. Hiring product leaders: Don’t hire to delegate. Hire for complementarity. Generalists with cross-domain mental models beat narrow domain experts.

12. Being a PM in the AI era: It’s the most exciting time - if you’re flexible. Strategy+rituals beat plans+processes when the ground shifts monthly.

13. Crowded markets and Linktree’s $100B path: Crawl (cut a step in the discovery chain), walk (brand-creator marketplace), run (consumer discovery destination).

14. Quick fire: Founders miss PMF by skipping the problem. PMs get promoted by being useful and known for one thing. Recent wow: ChatGPT multimodal + Meta Quest. Most product tension: sales and engineering. Admired strategies: OpenAI (search), Zuckerberg (WhatsApp/Quest long bets), Disney+ (content is king).