Why Teams Forget Why They Made Decisions

Ask a team why they use the database they use, and someone can usually answer. Ask why they chose it over the two alternatives they looked at, and the room gets quieter. Not because nobody thought it through at the time — almost always, someone did — but because the thinking never made it past the meeting it happened in.

This gets blamed on memory, and it isn't really a memory problem. It's a structural one: the places where decisions get made — meetings, Slack threads, hallway conversations — are not the places where anything gets kept. And the places that do keep things — wikis, tickets, changelogs — are built to describe what's true now, not to preserve why something became true in the first place.

So the decision survives, stripped of its reasoning, the way a headline survives without the article. "We use Postgres" is a fact anyone can find. "We chose Postgres over the alternative we'd been running for two years because of a specific operational problem it kept causing" is the actual decision — and that part depended on someone writing it down within the same hour it was decided, because a week later it had already started blurring into a much vaguer memory of "yeah, we thought about it and picked Postgres."

It's also not really a discipline problem, in the sense that telling a team to "document decisions better" rarely fixes it. The advice isn't wrong, it's just aimed at the wrong bottleneck. Most teams that fail to preserve decision reasoning aren't lazy about documentation in general — they document plenty. What they don't have is a place specifically shaped for a decision, as opposed to a place shaped for information. A "why did we do it this way" question doesn't have an obvious home in most tools, so it doesn't get written anywhere, not because nobody cared enough, but because there was nowhere for it to naturally go.

The fix isn't more discipline. It's a place shaped like the question you'll eventually ask — see What Is Decision Memory? for what that actually looks like.