Leadership.

The framework

1. 01

   List the rules you've stopped enforcing.

   Sit down with the rules you personally introduced and mark each one: followed, followed when convenient, or dead. The code review that happens whenever the release is not urgent. The second quote that gets skipped for suppliers you like. The written brief before work starts, which survived four months. Then ask your team to build the same list separately, because theirs will be longer and more accurate than yours, and the gap between the two lists measures what you have stopped being able to see. A rule you announced and then stopped checking did not lapse neutrally. It taught people which of your standards are real.

2. 02

   Trace the first exception, and notice who granted it.

   Every dead rule has a first exception, and it was almost always granted for a good reason by a sensible person, frequently you. Walk one backwards. There was a deadline, a client, a shortage, and skipping the step was the correct call on that particular day. Nothing bad happened, which is exactly the difficulty: the absence of consequence got read as evidence that the step was optional, so the second exception needed less justification than the first and the fifth needed none at all. You will not find the moment anyone chose to lower the standard. The standard moved by being repeatedly and defensibly waived.

3. 03

   One rule, re-set in the room, starting with your own exceptions.

   Pick one rule and say it to people rather than to a document: here's the rule, here is what we have actually been doing instead, here is why it matters, and here is what I'm changing, beginning with the exceptions I granted myself. Then run NASA's move in reverse. Their anomalies were promoted onto the accepted list in writing, with signatures, which is precisely why nobody in the room experienced it as lowering a standard — so take yours back off the list the same way. Name the exception, record in writing that it is an exception again, and let the paperwork disagree with the habit until the habit gives way. Naming your own part first isn't humility theatre. They already know who signed the waivers.

4. 04

   A standard that depends on your attention has a half-life.

   A rule that needs you to notice decays at precisely the rate of your attention, which is why the same standards die in the same businesses every eighteen months. So bolt it to something structural: a step the system will not let anyone skip, a checklist item on the release, a field the invoice cannot be raised without, a standing agenda line asking how many exceptions we granted this month and to whom. Then carry on granting exceptions, because zero was never the target. The target is that every waiver is visible, has a name against it and gets counted, so drift can only happen in the open.