Notion's lost years, near collapse during COVID, staying small to move fast, building horizontal
Executive Summary
Ivan Zhao discusses gradual product fit, systems, small-team coordination and the balance between reusable product parts and customer solutions. Selected third-party transcript coverage excludes AI, personal history, infrastructure incidents, company performance figures and closing recommendations. Notion history and outcomes are his accounts, unverified here. Untimed editorial topics are not video chapters.
Key Takeaways
Product fit can arrive gradually
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
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
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
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
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
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
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.
The Conversation Breakdown
Product fit can arrive gradually
⏱ Untimed topicZhao 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 topicHe 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 topicZhao 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 topicHe 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 topicZhao 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 topicHis 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 topicZhao 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.
Core Frameworks & Ideas
Systems before brute force
Check whether better tools or architecture can solve a bottleneck before assuming more people are the answer.
Lego bricks and boxes
Keep reusable underlying capabilities while packaging a concrete solution a customer understands.
Multi-signal product review
Compare customer response, engineering friction and direct product use when assessing whether a feature fits.
Actionable Next Steps
- ✓Review a staffing request for the underlying bottleneck and possible system improvements.
- ✓Identify one feature that introduces a special case into an otherwise reusable architecture.
- ✓Describe the customer solution separately from the product capabilities behind it.
- ✓Compare customer, engineering and direct-use feedback on a recent release.
Notable Quotes
“I just believe better system is much better than brute force through people.”
“For a while and still is, project management is one of the most important use cases for Notion.”
“I wouldn't do it differently myself, but I wouldn't recommend it.”
The One Thing to Remember
A focused customer solution can sit on flexible building blocks, but a special-case feature can work against the system.