All notes

Defaults Are Decisions Nobody Signed Off On

Somebody picked the default. Maybe it was a developer in a hurry, maybe it was whatever the last system shipped with. Nobody voted on it. Nobody wrote a memo. And yet six months later, that default is how the company works.

This is how policy actually forms in most organizations — not through decision, but through inertia. The setting nobody questioned becomes the rule nobody can explain. Ask why approvals route through three people instead of one, and you won’t get a reason. You’ll get “that’s how it’s configured.”

Defaults survive because changing them requires someone to notice, care, and have the authority to act — three things that rarely align. So the unexamined choice calcifies into the normal way of doing things, and eventually into the only way anyone remembers.

Scott Andrew Alpaugh has watched this pattern repeat across different tools and teams: the setting that was never a decision becomes the hardest thing to undo, precisely because no one owns it. You can’t challenge a choice nobody remembers making.

Good systems get reviewed, not just configured once and left alone. Someone should periodically ask: did we choose this, or did we just never change it? The answer is usually uncomfortable, because most defaults were never chosen at all — they were inherited, then mistaken for intention.

The fix isn’t complicated. Audit the defaults. Ask who set them and why. If no one can answer, that’s not a technical gap — it’s a governance one. The system is making decisions on your behalf, and nobody’s checking its work.