Lenny's PodcastBuilding minimum lovable products, stories from WeWork & Airbnb, and thriving as a PM | Jiaona Zhang
CHAPTERS
- 0:00 – 0:40
Cold open: Build a “known for” superpower to accelerate your PM career
Jiaona shares a core career principle: become exceptionally good at something and build a reputation around it. That reputation attracts harder projects, more trust, and faster growth.
- •Pick a craft area to be “known for” (execution, technical complexity, GTM launches, etc.)
- •Reputation compounds into more responsibility
- •Excellence creates pull: leaders naturally assign critical work to proven owners
- 0:40 – 4:40
Who JZ is: Webflow SVP, Stanford lecturer, and a tour through Dropbox/Airbnb/WeWork
Lenny introduces Jiaona Zhang’s background and why her experience spans both iconic products and high-variance company environments. He tees up the episode’s themes: PM mistakes, lovable products, roadmaps/OKRs, and leadership lessons.
- •JZ’s roles across Webflow, WeWork, Airbnb, Dropbox, and Pocket Gems
- •What the conversation will cover (MLP vs MVP, prioritization, OKRs, first-90-days plan)
- •Framing the episode around hard-won product and leadership lessons
- 4:40 – 6:44
The most common new-PM failure mode: jumping to solutions (and “PMs aren’t CEOs”)
JZ explains the biggest early-career PM mistake: getting attached to a solution before deeply understanding the problem. She also tackles the misconception that PM equals decision-maker, emphasizing influence over authority.
- •Default human tendency: leap to solutions instead of problem discovery
- •Course focus: start with real users and their problems, not your startup idea
- •PMs have limited formal authority; success comes from influence and editing choices
- •Reframing the PM role as opportunity discovery and prioritization, not “calling shots”
- 6:44 – 10:51
Airbnb Plus postmortem: solution-first thinking, weak unit economics, and misaligned strengths
JZ walks through her biggest product mistake: Airbnb Plus. The initiative tried to build trust via inspections and operational processes, but it conflicted with Airbnb’s platform model and economics.
- •Original goal: increase trust and quality assurance for hesitant guests
- •Key issue: competitor fear pushed Airbnb into a managed-inventory mindset
- •Unit economics didn’t work—manual inspection doesn’t scale with Airbnb margins
- •Strategic mismatch: Airbnb’s operational muscle wasn’t built for this model
- 10:51 – 13:46
Executing big visions step-by-step: phases, milestones, and go/no-go gates
They zoom out into a general framework: dream big, but be explicit about what phase you’re in and what you’re trying to learn. JZ advocates for short learning cycles and clear success criteria to avoid sunk-cost traps.
- •Big visions are necessary, but must be coupled with disciplined execution
- •Use “learning phases” with timeboxed experiments and explicit learning goals
- •Do unscalable prototypes early to validate key assumptions
- •Define quarterly milestones and clear go/no-go decision points
- 13:46 – 16:54
How to push back on founders: conviction, align on “spirit,” and bring better options
JZ outlines when and how product leaders should say no—especially when leadership is emotionally invested. The key is to align on the underlying intent and return with stronger alternatives backed by data and reasoning.
- •First check: do you truly have conviction, or are you still learning?
- •If you have conviction, saying no is part of the job
- •Start with the “spirit” (what success looks like for user/business)
- •Bring concrete alternative approaches and supporting evidence
- 16:54 – 20:53
Minimum Lovable Product (MLP) vs MVP: raising the bar in crowded markets
JZ explains why “viable” often isn’t enough anymore—users have abundant choices. MLP depends on what users compare you against and their tolerance for rough edges.
- •MLP: the smallest experience that still feels high-quality and resonant
- •MVP may work when replacing painful manual workflows (e.g., spreadsheets)
- •Lovability is contextual to the audience (designers vs finance/IT users)
- •Competition and alternatives determine the required polish bar
- 20:53 – 22:20
What makes products lovable: polish, power-user wins, and targeted “pixie dust”
Lovability isn’t just delight; it’s reliable quality plus selective over-delivery in places that matter. JZ shares examples like keyboard shortcuts and pre-populated templates that create disproportionate user love.
- •Baseline: the product must be solid (not janky) before delight matters
- •Power-user details (e.g., keyboard shortcuts) can drive outsized affinity
- •“Pixie dust” should be intentional and limited—pick a few moments to over-deliver
- •Trade-off reality: you can’t sprinkle delight everywhere without slipping timelines
- 22:20 – 28:05
Roadmapping & prioritization: stop shipping spreadsheets—tell a coherent story
JZ’s roadmap philosophy centers on narrative and themes rather than lists and scoring columns. A good roadmap helps humans understand why the work matters and provides scaffolding for teams to figure out the “how.”
- •Roadmaps should communicate themes, levers, and narrative rationale
- •RICE-style tables aren’t a roadmap without an interpretive story
- •Themes should be resilient to new learnings (and change when assumptions change)
- •Preferred artifact: a written doc with links to live systems (e.g., Jira) to avoid staleness
- 28:05 – 31:37
Career acceleration for new PMs: build a reputation, then evolve your strengths as you lead
JZ returns to career advice: specialize early to build credibility, then adapt as your scope shifts from execution to leadership. She shares how her “known for” evolved from analytics to execution and beyond.
- •Be known for a specific excellence to earn harder, higher-impact opportunities
- •JZ’s early edge: analytics; later discovered a strength in complex execution
- •Delivering hard launches with small teams builds trust and scope
- •As you manage, the “known for” must evolve beyond pure execution
- 31:37 – 36:08
Designing crisp OKRs: anchor in qualitative success, embrace ambition, and map milestones
JZ argues that OKRs fail when teams fear them and sandbag targets. Her approach starts with a clear qualitative definition of success, then connects ambitious outcomes to a believable milestone path.
- •Start by defining: what would make us say we truly “crushed it” this quarter?
- •A healthy culture doesn’t punish risk-taking when learning is real
- •All-green OKRs often signal insufficient ambition
- •Ambitious outcomes need a credible plan: milestone path quarter-over-quarter
- 36:08 – 43:37
WeWork lessons: empathy in crisis, dangers of over-hiring, and focusing on what’s truly core
JZ recounts leading through WeWork’s 2019 turbulence, including building a team and then navigating layoffs. She distills the experience into leadership empathy, hiring discipline, and aligning investment to what customers actually value.
- •Leadership in downturns: transition planning and people-first decisions
- •Avoid over-hiring; unlock hiring only after milestone gates are met
- •WeWork’s strength is operational + inventory—tech should serve the core job-to-be-done
- •Personal story: choosing to give a retained role to someone else during layoffs
- 43:37 – 51:48
Winning the first 90 days as a product leader: rapid context-building, planning, and trust banking
JZ shares a practical 90-day approach shaped by a hard constraint: she joined Webflow while pregnant and had to go on leave soon after. The plan emphasizes structured listening across functions, surfacing strategic gaps, and building trust before pushing change.
- •Front-load context: meet across functions and levels (leaders + people closest to work)
- •Synthesize quickly (40–50 conversations) to build an accurate “lay of the land”
- •Don’t leave without a plan: identify what continues vs what needs research and decisions
- •Trust as a “bank”: build deposits first; pushing change too fast spends trust you don’t have
- 51:48 – 1:07:31
High-level pattern across Dropbox/Airbnb/WeWork/Webflow + final advice: ask for help
JZ closes with a cross-company meta-lesson: know why people love you and double down on that core advantage before expanding. Her most transformative leadership advice is to ask for help—especially when you feel you “should” already know.
- •Cross-company product lesson: invest deeply in the core “why people love you”
- •Avoid chasing competitors in ways that dilute your advantage (e.g., Dropbox performance vs copycat features)
- •Best leadership advice: be honest about what you don’t know and actively seek help
- •Lightning round highlights: books, hiring for ambiguity navigation, and recent tools (SNOO, Midjourney)
