I used to know the code to my parents’ alarm. Four numbers, tapped out without thinking, fingers moving before the mind caught up. Now, every visit, I ask again. The code’s still in there somewhere, buried like a file you know exists but can’t query anymore.

Organizations lose their codes too. Teams forget why they picked one framework over another. Companies lose track of the instincts that made their first product work. Lessons hard-earned disappear the moment the person who carried them walks out the door.

Individual forgetting creeps in slowly, almost politely. Organizational forgetting falls like a trapdoor. One day the knowledge is there. The next, it’s gone, and what disappears usually isn’t trivial. It’s the hidden reasons something worked, the guardrails that kept a disaster from happening, the lessons no one wanted to learn twice.

Forgetting is inevitable, but choosing not to remember is optional.

Memory inside a company isn’t about saving everything. It’s about deciding what matters enough to carry forward. Most choices fade without consequence. A few deserve preservation: the ones that involved painful tradeoffs, non-obvious calls, or scars from earlier mistakes.

The most useful notes aren't just records of what happened. They capture the frame around it: what was known, what felt urgent, what seemed impossible. That context lets future teams debug a decision instead of undoing it. Writing also bridges boundaries: when engineering says “technical debt” and product hears “behind schedule,” a shared document can turn the invisible into something both can read. And it enables handoffs. A task list is never enough; the person inheriting your work needs to see the thinking that made it make sense.

The trouble is we often postpone. “We’ll write this up once things calm down.” But things never truly calm down, and by the time they do, the details have already leaked away. The fix remains, but the bug that prompted it has blurred. The answer is remembered long after the question is gone. That gap creates its own kind of debt, repaid later in confused handoffs, repeated mistakes, and long re-investigations of decisions that once took an afternoon.

And the skepticism is understandable. Most of us have seen documentation at its worst: many-page specs nobody reads, process manuals written to satisfy compliance audits, artifacts that prove diligence without enabling work. The problem is writing that performs instead of doing a needed job.

Working documentation does real work — it prevents confusion, enables action, and saves time. It reads like helpful conversation, not like homework turned in for a grade. Performing documentation serves bureaucracy instead of people. You can tell which kind you're reading within seconds.

High-functioning teams know this. They treat documentation the way they treat testing: as part of the work, not an optional extra. They write while the tradeoffs are still visible, while the rough edges haven’t yet been sanded into clean hindsight. This isn’t about encyclopedias. It’s about leaving breadcrumbs for whoever comes next, including your future self.

Cleaning out an old project once, I found a two-paragraph note from a teammate who’d already left. Just a quick explanation of why we’d chosen one approach over another, with a simple diagram of the tradeoff.

That scrap of text saved us from undoing a lot of work. We were ready to rip it all out. The note reminded us what problem we were solving and why the imperfect solution was still the best one. Organizational memory works quietly and incrementally. Each captured choice becomes raw material for the next, and each lesson carried forward prevents the next team from burning their hand on the same stove.

Most companies lose their knowledge slowly, then all at once. A few critical people leave and context evaporates. The forgetting curve takes over. But it doesn’t have to. The work is simple but requires discipline: write things down while you still remember why they matter. Not everything, just the decisions that cost something to make, and the ones that will cost even more to unmake.

Sometimes all it takes is a written note, waiting like an old key in a drawer, ready to open the lock. Or like a half-remembered alarm code, still there when you need it.

Like this? Subscribe via email here.