Write documentation to scale your time - content scales but your time does not
Documentation replaces repetitive meetings and calls.
When to use
When explaining same concepts repeatedly
Don't do this
Defaulting to meetings for information sharing
5 Founders Who Did This
Emphasized that sharing as much context as possible with team members is like downloading your brain into theirs, enabling them to solve problems independently rather than following orders
Created shared 1:1 agenda docs populated ahead of meetings with topics, context, and relevant links. Structured with sections for FYIs, updates, follow-ups, and discussion topics.
Used blog writing as a forcing function for structured thinking about management problems, publishing hundreds of posts over 20+ years that turned daily observations into transferable frameworks
Learned from Cash App engineering lead to share complete narrative context with teams rather than just task-specific information, enabling engineers to identify gaps and ask unexpected questions
Levels replaced meetings with written memos to raise rigor and enable async work. Published investor updates and all-hands recordings with 12-month delay. New hires reported knowing more about Levels after 2 weeks than at previous companies after 5 years