Constraint Death as Tradition Trigger
Updated
Knowledge on this page was mainly distilled from Tradition Is Just an Inherited Hypothesis.
Questioning inherited practices is expensive. That cost is the whole reason blindly following tradition makes sense as a default bet: traditions save you thousands of small decisions and carry compressed judgment from people who paid for it the hard way. Any framework for re-evaluating traditions must solve for this tension, or it becomes impractical.
The solution is not to audit everything. It is to audit when a constraint dies.
What a Constraint Death Looks Like
A constraint death rarely arrives with a label. It arrives as something new turning cheap, fast, effortless, or possible at all. When one of those changes shows up anywhere near an inherited practice, that practice is due for re-evaluation because the third question of the keep-adapt-discard test (would you invent this today?) is most likely to have a new answer.
The courier radio illustrates the pattern. Two-way radios were the correct solution for dispatching moving drivers when no alternative existed. Then mobile phones became affordable. The practice never announced its own expiration, but the death of the constraint announced itself plainly, in a shop window, with a price tag. That was the trigger, not a scheduled review or a moment of philosophical clarity.
Why Schedules Fail
Running the keep-adapt-discard test on everything you have inherited would spend the exact decision budget traditions exist to save. A quarterly review of all standing practices is itself a tradition that fails question three: facing the actual problem (catching stale practices), you would not invent a calendar-based audit. You would watch for the thing that actually makes practices go stale, which is a change in the constraints they were built on.
AI as Mass Constraint Death
For most of history, constraint deaths were rare. A key constraint might shift once a decade, affecting a handful of practices. Then AI took a whole column of constraints down at once: the cost of writing, drafting, coding, searching, and translating. Every practice resting on any of those constraints came due for re-evaluation simultaneously. The trigger that historically fired rarely is now firing across entire workflows at the same time, which is why inherited processes in knowledge work feel suddenly brittle.
Q&A
How do you notice a constraint death if it does not announce itself?
The article says constraint deaths do announce themselves, just not through the practice they affect. They show up as something new becoming cheap, fast, or possible. A new tool, a price drop, a regulatory change. The signal is in the environment, not in the habit.
Does this mean you should never do periodic process reviews?
The argument is that a constraint-triggered audit is more efficient than a calendar-based one. Periodic reviews are not wrong, but they tend to either waste time on practices whose constraints have not changed or miss the practices that became stale between review cycles.
Why is AI different from previous constraint deaths?
Previous constraint deaths were narrow: one technology shift affected a few related practices. AI collapsed the cost of writing, drafting, coding, searching, and translating all at once. That simultaneity means many inherited practices across different workflows hit their re-evaluation trigger at the same time.
What if a constraint dies but nobody in the organization notices?
That is the common failure mode. The practice keeps running because habits never announce their own expiration. Building awareness of constraint deaths, watching for things that become cheap or effortless, is the main preventive measure. The courier company did not notice the radio was stale until someone explicitly compared it to the new option.