The encyclopedia

The rules, shortcuts, and automations you set up keep running long after the world they were built for has changed, so they quietly go wrong while still looking like they work.

When warnings arrive so often that people stop reading them, the one warning that mattered gets ignored along with the rest.

When you speed something up by routing it through a tool, the human part of it — presence, care, apology, trust — can quietly disappear while the task still looks done.

You get people to go along with you by making the alternative hard to reach instead of by convincing them, so their agreement is not really agreement.

Monitoring you set up for one small safety reason keeps growing until you are watching far more than the problem ever required.

The person, company, or tool you depend on is rewarded for hitting its own number, which is not the same thing as getting you the result you actually came for.

When the same person or tool does the work, checks the work, and decides whether to go ahead, one mistake sails through every stage because nobody uncoupled from it is left to object.

When part of a working setup is going badly, hand that one piece to a different person or tool and leave everything else alone.

Keep the same people, tools, and tasks, and change only the connections around them: what starts the work, what form it arrives in, who owns it, who checks it, and where the exceptions go.

Change how much someone is allowed to decide on their own, without changing what they do: give more freedom where the track record is good and mistakes are easy to undo, and less where a mistake is expensive or permanent.

When a part of your setup costs more upkeep than it gives back, delete it instead of trying to fix it.

Bundle means putting work back into one person's hands in one sitting, when passing it between people, tools, or steps keeps losing details and costing more than the split saves.

Where a failure would really hurt, add a second check that fails for different reasons than the first one.

Take the part of a routine that already works every time and freeze it into a checklist, template, or written rule so it runs without you.

Once someone can reliably do the thing on their own, take the help away, keeping only a small safety net where a slip would be costly.

The S/D boundary rule is the test that tells you whether a stuck problem is a System problem (who or what carries the work, through what handoffs and checks) or a Destination problem (what outcome counts as better, and who has the right to decide). Ask whether everyone would call the same result a win. If yes, compare carriers. If no, stop comparing and settle the goal.