By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

Lenny's Podcast

Ivan Zhao: Why Notion hides no-code Lego inside productivity

Through sugar-coated broccoli framing and a willingness to reset: Notion threw away its developer tool to find PMF as productivity software.

Lenny RachitskyhostIvan Zhaoguest

Mar 6, 20251h 12mWatch on YouTube ↗

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

CHAPTERS

Jump to publisher timestamps

Chapter summaries

Notion’s “lost years” and the sugar-coated broccoli insight
Lenny opens by framing Notion’s first 3–4 years as “lost years,” prompting Ivan to explain the core early mistake: building what he wanted rather than what most people wanted. Ivan shares the key reframing—hide a deep vision (end-user programmability) inside a form factor people already value (productivity software).
- •Early Notion iterations focused on easy developer tools; most users didn’t care
- •Realization: embed the vision inside a productivity tool people use daily
- •“Sugar-coated broccoli” metaphor for packaging ambitious ideas
- •Balancing personal taste/values vs. market needs to avoid art-project vs. commodity traps
From Urumqi to programming contests to Canada: Ivan’s formative years
Ivan recounts growing up in Urumqi, moving to Beijing, and getting into programming through competition as a path to better schools. He then describes immigrating to Canada at 16 and how art, games, and building websites for artist friends shaped his desire to democratize software creation.
- •‘Small town’ Urumqi is a 4M-person city; later move to Beijing
- •Programming Olympiad route to academic opportunity (2nd in Beijing)
- •Move to Canada at 16; broad interests beyond CS (art + games)
- •Building websites for artists revealed the gap: most people can’t create in software
Engelbart, Smalltalk, and the original dream: no separation between users and builders
Ivan explains how studying computing history led him to pioneers like Engelbart, Alan Kay, and Ted Nelson. Engelbart’s “Augmenting Human Intellect” crystallized a mission: tools should expand human problem-solving, and computing should be malleable for users—not locked behind applications.
- •Engelbart’s paper as a catalytic ‘obsession’ moment
- •Core belief: builders and users shouldn’t be separated in computing
- •Smalltalk/Xerox Alto as inspiration for malleable, editable systems
- •Critique: the app paradigm won, contributing to today’s fragmented SaaS world
Throwing away the code: rebuilding after the wrong technical bet
The conversation turns concrete: Notion repeatedly restarted, including a major rewrite after betting on unstable Web Components pre-React. Ivan describes the hard decision to rebuild on a more reliable technical foundation before time and money ran out.
- •Multiple rewrites over ~4 years; restarting wasn’t theoretical—it was necessary
- •Web Components instability made debugging and progress unpredictable
- •Decision: reset the codebase/company to avoid running out of time
- •Lesson: foundations matter; bad tech choices can threaten survival
Staying alive: mom’s bridge loan, going down to two people, and Japan reset
Ivan shares the scrappy survival mechanics: family support, layoffs down to just Ivan and cofounder Simon, and relocating to reset morale. The Japan period becomes a creative, high-output chapter—coding and designing intensely while minimizing burn.
- •Mom helped kickstart and later bridged the company financially
- •Layoffs reduced team from five to two to regain runway
- •Japan/world travel used as a morale and focus reset
- •High-output ‘birthday every day’ rhythm: code → eat → code
Founder advice from the trenches: emotional resilience and the power of resets
Ivan and Lenny extract lessons for struggling founders: emotional regulation, courage to reset, and building for values as a durable energy source. Ivan emphasizes that better abstractions can let you catch up fast—making resets more rational than they seem.
- •Highs not too high, lows not too low; sleep as a personal reset tool
- •Courage to abandon momentum-driven paths that don’t matter
- •Building for values is more durable than chasing scorecards alone
- •Resets work because improved abstractions compound faster than linear effort
What product-market fit felt like: gradual ramp, investor inbound, and the ‘dog treats’ signal
Ivan describes PMF not as a single “boom” moment but as a gradual increase in real user pull and revenue. A quirky milestone—VCs finding their private office address and sending dog treats—signaled a new level of external attention, though Ivan learned to avoid seeking validation through meetings.
- •PMF experienced as a steady ramp, not a discrete milestone
- •Early signals: revenue growth, users reaching out, and investor inbound
- •Dog treats story: VCs hustling to get attention via gifts
- •Investor advice: don’t confuse fundraising conversations with product truth
Staying small to move fast: systems over headcount and ‘talent density’
The discussion shifts to Notion’s operating model: unusually lean headcount, profitability, and delayed hiring of classic roles (sales, PM). Ivan attributes this to multipotential teammates, a systems mindset, and measuring “talent density” rather than growth in people.
- •Lean approach enabled by founders’ breadth (code, design, sales, storytelling)
- •Internal overhead is communication/alignment—not just execution
- •Notion used internally as a meta-tool to build company systems
- •Talent density (revenue per employee) as a compounding advantage
The ‘small bus’ metaphor: scaling decisions, speed, and seatmates
Ivan offers a memorable organizational metaphor: a company is a bus—smaller buses turn faster and accelerate more easily. Leadership’s job is choosing who sits on the bus and keeping it tight so the organization stays maneuverable.
- •Small teams maneuver better; size slows turning and acceleration
- •Leaders choose ‘seatmates’—who you hire shapes pace and experience
- •Optimize for agility through systems rather than brute-force hiring
- •Metaphor used internally to reinforce lean, aligned execution
Designing the office as an artist studio: aesthetics, comfort, and tool inspiration
Ivan explains Notion’s office culture choices—no shoes, shared table, obsessive wall-color selection—as both pragmatic (creativity, comfort) and value-driven (ugly environments hurt). Conference rooms are named after timeless tools to remind the team they’re building products meant to last.
- •Office as a creative instrument: avoid harsh lighting and sterile design
- •Home-like furniture and cozy spaces to support flow and collaboration
- •Aesthetic standards as part of values, not decoration
- •Conference rooms named after durable tools (Macintosh, LAMY pens, rice cookers)
Craft and values: how Notion makes decisions and navigates tradeoffs
Ivan articulates Notion’s philosophy: craft is the fusion of values, taste, and technical skill to make the right tradeoffs. He expands tradeoffs beyond speed/quality into shifting technology constraints (e.g., AI as a new material) and stable human constraints (resistance to learning).
- •Craft = values + taste + technical know-how expressed through tradeoffs
- •No free lunch: every product/business decision exchanges one benefit for another
- •AI framed as a new ‘material’ enabling new tradeoff frontiers
- •Successful products balance technology possibilities with human behavior limits
Leadership growth and a values drift: the ‘non-Lego pieces’ period
Ivan reflects on leadership changes required as Notion grows—especially becoming a one-to-many storyteller even when it drains him. He also shares a candid misstep: shipping features that violated Notion’s Lego philosophy (hardcoding project-management concepts like sprints), creating internal and customer “rejection.”
- •CEO evolution: storytelling must scale from 1:1 to 1:many
- •Marketing/positioning as truthful ‘entry points’ into resistant minds
- •Values drift example: hardcoded project-management features broke the Lego system
- •Realignment came through feedback, technical pain, and re-committing to first principles
Near collapse during COVID: the single Postgres doomsday clock and the shard-or-die sprint
Ivan recounts one of Notion’s most dangerous crises: explosive COVID growth pushed their single Postgres instance to its limits, risking a total shutdown. The company halted feature work, mobilized engineers, and raced to implement database sharding under intense time pressure.
- •Notion originally ran on a single Postgres instance; scaling by ‘bigger machine’ hit a ceiling
- •A visible doomsday clock: running out of storage threatened total outage
- •All-hands engineering focus; feature work paused to prioritize survival
- •Lesson: avoid premature optimization, but plan infrastructure inflection points earlier
Building horizontal software: segmentation, ‘Lego boxes’ vs ‘Lego bricks,’ and bundling cycles
Ivan and Lenny explore the joy/pain of horizontal platforms: they take longer to reach clarity and require intentional segmentation. Ivan contrasts bricks (primitives for builders) with boxes (ready-made solutions for enterprises), then zooms out to the historical pendulum of bundling vs. unbundling in software.
- •Horizontal products face huge problem spaces; segmentation becomes essential
- •Most users want ‘Lego boxes’ (solutions), not raw bricks (primitives)
- •Horizontal advantage: no market wall—yet you must create clarity in GTM
- •Macro cycle: paper → early PC unbundling → Microsoft bundling → SaaS unbundling → rebundling trend emerging
AI on top of Notion’s Lego set: writing, Q&A/connectors, and agentic assembly
Ivan outlines how LLMs changed Notion’s trajectory: AI writing was the first layer, then AI Q&A across workspace knowledge with connectors, and now a third wave—AI agents that can assemble workflows and tools from Notion’s building blocks. The thesis: bundled, centralized data makes AI dramatically more useful.
- •AI writing is the ‘easy slice’ when users already work in text daily
- •AI Q&A/search becomes powerful when information is bundled in one place
- •Connectors address external systems (Jira, Zendesk) while pulling knowledge into Notion’s core
- •Future: AI coding/agents can ‘assemble’ Lego bricks, lowering the barrier to building custom software
Tools and human potential + lightning round: creativity, beauty, and learning sideways
Ivan closes with a philosophy: tools extend humans, and then shape us—so builders should choose what parts of human nature they amplify. He emphasizes creativity and beauty as Notion’s north star, encourages learning beyond tech by stealing patterns from history, and ends with personal recommendations and a craft-focused motto.
- •McLuhan principle: we shape tools; tools shape us
- •Notion aims to amplify creativity and beauty rather than zero-sum instincts
- •Advice: look beyond tech (history, literature, documentaries) for enduring patterns
- •Lightning round themes: complex systems, ‘Connections’ documentary, craft-as-motto, and ways to reach Ivan/hiring ‘misfits’

Publisher timestamps

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.