Note-Taking for Teams: The Knowledge That Leaves When People Do

Teams do not remember things. Individuals do, and the team develops an index of who knows what, a pattern researchers call transactive memory. It is efficient, it emerges naturally, and it has one catastrophic property: it is stored in people, so it leaves with them.

Every organisation discovers this the same way. Someone resigns and it turns out they were the only person who knew why the billing job runs at 3am, what the vendor actually agreed to, and which customer must never be moved to the new plan.

Why the company wiki fails

Almost every team has tried a shared knowledge base and almost every one has watched it rot. The failure is consistent enough to be diagnosable.

Failure Cause
Nobody writes Writing benefits others later, the cost is yours now
Nobody reads Nothing indicates whether a page is current or abandoned
Everything is out of date No owner, no expiry, no signal when reality moved
It becomes a dumping ground No distinction between reference, decisions, and drafts
Search returns eleven versions Nothing was ever deleted

The root cause is that writing documentation is unpaid work with delayed, diffuse benefit. Systems that survive make writing a byproduct of something the writer already needed to do.

The three documents that are worth the effort

Rather than "document everything," which never happens, most teams get the large majority of the value from three artefacts.

1. The decision log. Dated, append-only, one entry per real decision. What was decided, why, what was rejected, and what would make you revisit.

2026-05-02 — Staying on the managed database for now
Rejected: self-hosting. Saves ~$900/mo, costs an on-call rotation we don't have.
Revisit if: we hire a second infra engineer, or spend exceeds $4k/mo.

This is the single highest-value team document, because decisions are what people ask about years later and the reasoning is exactly what disappears. It is also cheap: nobody has to write prose, and each entry takes two minutes. See how to keep a work journal.

2. The runbook. How to do the recurring operational things, written to be followed by someone who does not understand the system. The test is that a new joiner can execute it without asking anyone.

3. The map. Not content, a directory: what systems exist, who owns each, where the real documentation lives. Ten links and a paragraph each. Most "we have no documentation" problems are really "we cannot find our documentation" problems. This is maps of content applied to an org chart.

Everything else can stay in people's heads until it hurts.

Who writes it, and when

The person who understands a system best is the worst-placed to explain it, because they can no longer see what is non-obvious. This is the curse of knowledge, and it explains why expert-written documentation is so often useless.

Two practices follow, and both invert the usual assignment:

New joiners write onboarding docs. In their first month, while still confused, they document what confused them. It is the only window in which anyone can see the gaps, and it closes permanently. See how to take notes in a new job.

Successors write handovers, not leavers. The departing expert answers questions; the person taking over writes the document. A handover written by the leaver lists what they think matters, which is not what the successor needs to know.

The boundary between shared and personal

Not everything should be shared, and blurring this is why people stop writing candidly.

Keep personal Make shared
Your impressions of colleagues Decisions and their reasoning
Half-formed ideas and drafts Processes anyone must follow
Your own learning notes Where things live and who owns them
Frustrations and drafts of hard conversations Commitments made to customers or vendors

People need somewhere to think that is not performative. A team that treats every note as a shared artefact gets less honest thinking, not more documentation. The right structure is a private space per person plus a small, well-maintained shared layer.

There is also a real caution about notes on people. Performance observations, one-to-one notes, and anything about a colleague's behaviour carry legal and ethical weight in most jurisdictions. Write what you would be comfortable having read back to you, and keep it out of shared spaces. See how to take 1:1 notes.

Making it self-maintaining

Attach documentation to work that already happens. A decision entry written during the meeting where the decision was made costs nothing extra. Written a week later it never happens.

Give every page an owner and a date. An unowned page is abandoned by default. A visible date lets readers judge staleness without asking.

Delete aggressively. Wrong documentation is worse than none, because people act on it. See when to delete notes and digital hoarding.

Prefer one obvious place. Two wikis, a Drive, and a pinned Slack message is the same as no documentation.

Where to start if this is a mess

Start a decision log today, in whatever tool everyone already opens. One file, dated entries, no structure. It will be the most-referenced document you have within six months, and unlike a wiki migration, it costs nothing to begin.

More in how to take meeting notes, the best notes app for teams, and personal knowledge management.

More in Personal Knowledge Management

55 more notes on this branch.

Clair Mind connects your own notes exactly like this — automatically, privately, on your iPhone. Get the app →