Notion's lost years, near collapse during COVID, staying small to move fast, building horizontal

Notion's lost years, near collapse during COVID, staying small to move fast, building horizontal — Lenny's Podcast: Product | Career | Growth Summary | Galaxy of Podcasts

The Conversation Breakdown

Product fit can arrive gradually

⏱ Untimed topic

Zhao describes Notion's progress as a gradual ramp rather than a single clear milestone. More people cared about the product and some began paying. His account suggests watching evidence accumulate, instead of waiting for a dramatic moment that declares the business solved.

Consider systems before adding people

⏱ Untimed topic

He favors solving problems through better systems and tools where possible. A small group with broad skills helped Notion work this way in his account. This is not an argument that hiring is unnecessary, but a prompt to check whether headcount is solving the actual bottleneck.

Keep communication costs in view

⏱ Untimed topic

Zhao identifies the difficulty of aligning people's understanding as an organizational cost. His small-bus metaphor makes maneuverability more concrete. Consider how a team structure affects direction and coordination rather than treating a larger team as automatic progress.

Build consistently with the product architecture

⏱ Untimed topic

He describes Notion as Lego for software and says hard-coded sprint features did not fit the rest of the product well. A locally useful feature can work against a broader system. Review whether a feature extends reusable building blocks or introduces an isolated special case.

Listen when different signals reveal a mismatch

⏱ Untimed topic

Zhao says customer response, engineering work and using the feature all helped expose the sprint product's mismatch. It took time to recognize. Compare these signals together rather than dismissing one group's concern as an implementation or marketing problem.

Sell a solution while preserving reusable parts

⏱ Untimed topic

His Lego-box metaphor distinguishes what a customer wants to buy from the underlying bricks. A buyer may want a ready-made solution, not a collection of capabilities. The go-to-market story can be focused even when the product architecture stays flexible.

Do not turn one company story into universal advice

⏱ Untimed topic

Zhao says he would build Notion the same way but would not recommend horizontal software generally. He describes notes and documents as the use case Notion found, not a guaranteed entry point. Use the story to understand trade-offs, not assume copying the category will produce the same result.

Executive Summary (TL;DR)

Key Takeaways

Product fit can arrive gradually

Consider systems before adding people

Keep communication costs in view

Build consistently with the product architecture

Listen when different signals reveal a mismatch

Sell a solution while preserving reusable parts

Do not turn one company story into universal advice

The Conversation Breakdown

Product fit can arrive gradually

Consider systems before adding people

Keep communication costs in view

Build consistently with the product architecture

Listen when different signals reveal a mismatch

Sell a solution while preserving reusable parts

Do not turn one company story into universal advice

Core Frameworks & Ideas

Systems before brute force

Lego bricks and boxes

Multi-signal product review

Actionable Next Steps

Notable Quotes

The One Thing to Remember