Before approving more headcount for a busy service desk, I counted how many tickets should never have existed. A third of them. Here's how to find failure demand on your team.

Chesterton's fence is usually quoted as a reason to leave old processes alone. Read properly, it asks managers to find out why a rule exists, then make an honest call to keep it or remove it.

A four-word rollback plan, approved like dozens before it, caused a three-hour outage. A case study in normalization of deviance: how capable teams drift from their own standards, what NASA learned...

Put enough pressure on a single number and your team will move that number, not the outcome it stood for. Goodhart's Law, real cases, and what managers can do about it.

Recurring team errors aren't a discipline problem, they're a design problem. Mistake-proofing engineers the error out instead of asking people to try harder.

Most teams sequence work by who shouts loudest or which task feels quickest. Cost of delay prices what waiting actually costs, and changes the order entirely.