Forgetting as Governance

The quarterly review after the missed forecast always starts the same way. Someone pulls up a timeline. Someone else identifies the moment the number went soft. And then, reliably, someone proposes a fix that is actually a scar: a new check-in cadence, a tighter approval gate, a standing committee that will meet every two weeks until further notice. Further notice never arrives.

Nobody in the room is proposing anything unreasonable. That's the problem. Each addition points to something real, an event, a failure, a moment when someone was present and visibly accountable for something breaking. The target is almost never abstract risk but the reputational residue of having been in the room when things went wrong. Institutions remember embarrassment more vividly than error, and the response to embarrassment is always structural: a new gate, a new cadence, a new committee. The scar becomes the org chart.

And structure, once added, is nearly impossible to remove. Because addition signals responsibility and subtraction signals risk.^[1] Introducing a review reads as diligence. Eliminating one reads as exposure. Even when the conditions that justified the control have changed entirely, the emotional memory of the original incident remains intact. To propose removing a safeguard is to implicitly argue that the cost of protection now exceeds the risk of failure, and that's a claim almost no one in an institution shaped by recent harm is willing to make out loud.

I've sat in these rooms and watched the next layer get added. I've nodded, because the logic was sound and because objecting would have required me to argue that the thing we were all still upset about wasn't worth preventing. Which of course it was. The dishonesty was subtler: we were building permanent architecture to address a temporary wound, and everyone knew it or should have known it, and nobody said so, because saying so would have meant owning a different kind of risk.^[2]

Most dysfunction isn't designed or nefarious. It accumulates. The committee formed after one bad quarter becomes permanent. An approval step added after a compliance scare survives three leadership transitions. The risk log outlives the risk it was originally logging. Organizations are structurally excellent at addition and structurally terrible at subtraction, because subtraction is political. The people empowered by an added layer are never the ones incentivized to remove it.

Over time, reaction hardens into identity. The cautious organization tells itself a story about discipline. And somewhere else, a different organization learns the opposite lesson from its own wound (that friction killed the opportunity, that hesitation was the real threat) and begins subtracting with the same unreflective certainty. Reviews shrink. Documentation gets deferred. Speed becomes culture. But the subtraction is just as unreflective as the addition was, which means it compounds in the same way: shortcuts solidify, workarounds become architecture, institutional memory fragments across undocumented decisions and private threads. The same problems recur because the system has no durable retention.

Caution and velocity present as opposites, but in practice they're siblings. Both are responses to pain. Both calcify into doctrine. The difference is tempo, not structure. Cautious systems decline gradually through missed opportunity, the kind of erosion that shows up in exit interviews nobody reads and pipeline metrics that soften slowly enough to explain away. Fast systems fail discontinuously: a hidden dependency breaks, a compliance gap surfaces, a key person leaves and the memory leaves with them.^[3]

Neither recognizes itself as miscalibrated. The cautious system looks and feels like professionalism all the way down, right up until the moment it can't ship anything that matters.

Healthy systems require both memory and forgetting. Memory preserves lessons. Forgetting prevents calcification. But almost no organization builds mechanisms for deliberate expiration. When was this approval step introduced? What incident justified it? Do the conditions that produced that incident still exist? If the answer is no, the structure remains anyway, because no one has been assigned the job of asking.^[4]

That's the part I keep circling. Not that organizations overcorrect (they obviously do) but that the overcorrection becomes invisible precisely because it resembles good judgment. One more review. One more escalation. One more gate. The sincerity of each individual response is what makes the accumulation so difficult to challenge. You can't argue against any single layer without appearing to argue against diligence itself.

The scar becomes strategy. And nobody even remembers the wound.