Every company needs documentation. Well... not really.
If you're a startup griding crazy to get your MVP out and get feedback, you couldn't care less about documentation.
If you have a product out and a couple of customers, docs are not that important. You can just ask around your team across the desk or on a Slack channel.
If you found product-market fit, got your first round of funding, and are scaling your team above 10, you probably also don't need that much documentation. You can just throw hours at it because there are so many of you right now compared to 6 months ago.
If you're a series A or B company with a couple of Ms in ARR, documentation starts to look attractive, but you can go without, no doubt.
If you just IPO'd, you're past 500 people. So much tribal knowledge lingering around... documentation is a problem, but there are workarounds. Just throw more salespeople into the picture. Revenue fixes everything.
But actually... your path was the most inefficient one possible, and documentation could've had the largest impact you could think of:
1. clearing misunderstandings among team members;
2. making the founders' vision clearer to themselves and to the whole company;
3. faster customer support answers;
4. faster or automated onboarding of new members;
5. less knowledge churn;
6. increased engineering productivity;
7. more stable run through the years;
8. less hassle in becoming a remote company when a virus hits out of nowhere.
I could go on... but you already know it. Documentation is how we build things.
Frequently Asked Questions
Yes—keep it light, but don’t skip it. A tiny set of living docs prevents rework, reduces interruptions, and makes it painless to add your next engineer or contractor.
Start with the absolute minimum (1–2 pages total):
- README: what the product does, high-level architecture, current constraints.
- Quickstart: setup, run, test commands, and how to seed data.
- Decision log (short ADRs): a few lines on why you chose X over Y.
- One-page onboarding checklist: accounts to request, repos to clone, environments to access, and daily rituals.
Working cadence:
- Update as you change things, not on a schedule—15–30 minutes after meaningful shifts is enough.
What to skip at MVP:
- Heavy templates, polished diagrams, and process binders. Just capture the essentials you’d otherwise repeat in Slack.
A simple rule: if you typed it twice, document it once.