All writing

Knowledge in heads doesn't scale

A new teammate lost three days to a question that had been asked five times before. Why document-first teams move faster.

A new engineer joined the team on a Monday. By Wednesday, he still couldn't run the project on his laptop.

It wasn't his fault. The setup steps lived in one person's head, and that person was on vacation. So he asked in the team chat. Three people gave three different answers. Two of them were out of date.

He lost three days. The team lost a little focus every time someone stopped to help. And the strangest part? It was the fifth time that exact question had been asked that year.

It works until it doesn't

When a team is small, you can get away with it. Everyone sits together. You just ask.

Then the team grows. People work from different places and different hours. Someone leaves, someone new joins. Suddenly the answers that "everyone knows" are known by nobody in particular.

Every question asked in chat gets answered once, for one person, and then disappears. A written answer works for everyone, every time, even at 2 AM when nobody is online.

Write first, then talk

A document-first team has one simple habit: when you explain something, write it down where others can find it.

  • How we work. Setup steps, release process, who to call when production breaks.
  • Why we decided. The options we looked at and the one we picked. Future you will thank you.
  • What we learned. The mistake, the fix, and the lesson, so nobody pays for it twice.

Then, instead of answering the same question again, you share a link. If the doc is wrong, you fix it right there.

A doc is never finished

The goal isn't a perfect handbook that nobody reads. It's a living document that anyone can improve.

If you followed the steps and one was missing, add it. If something changed, update it. If a page is useless, delete it. Small edits from everyone beat one big rewrite from someone who's tired.

That's where the magic happens. When everyone can contribute, everyone feels ownership. The doc stops being "the manager's wiki" and becomes the team's shared memory.

The quiet gift

Writing things down can feel slow. It's not glamorous, and nobody claps for a well-kept setup page.

But every good doc is a small gift to someone you may never meet. The new teammate who gets running in an hour instead of three days. The colleague who can make a decision without waiting for you to wake up.

Write it once, and help people forever.

Keep reading

More from the notebook.

Building3 min read

Praying to the servers

An index that froze the orders table, a shrine for praying while we waited, and why the best server prayer is the one nobody has to say.

Reflections3 min read

The age of personal software

In school, I built a tiny exam schedule app that almost every student on campus used for a couple of days. Then life got busy. Now AI is giving builders their weekends back.