What's written down is owned

I have a simple rule at work: if it isn’t written down, nobody owns it. Including me.

That sounds strict. It’s actually the opposite. Writing things down is how I get to stop carrying everything around in my head.

The problem with “just ask me”

For a while I was the person you asked. How does this work? Where’s that file? What’s the step after this one?

I liked being helpful. But every question that only I could answer was a small bottleneck with my name on it. If I was out, the work waited. That’s not a team. That’s a line outside my door.

What I write down

Not everything. Just the stuff that keeps coming back.

• How to run it. The steps, in order, in plain words.
• What to check. How you know it worked, and what it looks like when it didn’t.
• Who owns it. One name, so nothing falls between people.
• What’s not done yet. Honest gaps beat a doc that pretends to be finished.

Where it paid off

When I helped rebuild how our team delivers, most of the work wasn’t new tools. It was docs, workflows and a delivery playbook. Boring on paper. But now a teammate can pick up a task without waiting for me to be free.

Same with every tool I build. The doc ships with it, or it doesn’t ship.

What I’ve learned

• Write it while it’s fresh. A week later I’ve already forgotten the tricky part.
• Short beats complete. A one-page doc people read beats a perfect one nobody opens.
• Check for the artifact, not the checkbox. “We documented it” means nothing. “Someone new followed it and it worked” means everything.

The real reason

Knowledge shouldn’t live in one head or one laptop. When it’s written down, the team owns it, and I get to move on to the next thing.

I’m still not great at keeping every doc current. But a slightly stale doc beats no doc every time.