Do you need documentation?

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.

Dragos
Dragos
Founder & CEO. Creating awesomeness with code

Read more information about team work, documentation and knowledge management.

And use everything in your work with distributed and remote teams,
to be more effective and organized.