2026-07-14 · Architecture
Where chaos goes
In 1956, W. Ross Ashby proved a theorem. To regulate a system, a controller needs at least as much variety as the system it controls. He called it the Law of Requisite Variety: variety destroys variety — later popularized by Stafford Beer as "only variety absorbs variety." [1]
A business generates variety in a hundred forms. A client sends a voice message on WhatsApp; a supplier's warehouse burns down; a manager promises a discount on a napkin. Meet that with a five-stage funnel and a status field marked in progress, and the controller is short on variety. And here is the part that gets missed: the missing variety does not disappear. That is the organizational analogy I draw from the law, not a conservation theorem about business information. Unrecorded details may end up in people's memories or be lost.
Into people. Into a sticky note, into I remember this client needs a callback, into a manager's voice memo to himself. Formally, the chaos is stored somewhere. But do the others know about it? Is it in one place? Does it surface when the one manager who holds it is on vacation?
Fourteen years later, Conant and Ashby sharpened the edge: every good regulator of a system must be a model of that system. [2] A controller can only regulate what it can represent. Whatever the software fails to model, humans model instead — in their heads, off the record, unsearchable.
For decades this cycle ran one way only. Chaos accumulated. Once enough near-identical situations piled up, the business grew structure around them — a field, a rule, a script. Then the structure broke under load, or got escalated and automated. One turn of that loop took years.
The reason it took years is friction. Structure and friction trade against each other. The Fogg Behavior Model states it precisely: a behavior occurs only when motivation, ability, and a prompt converge in the same moment — and ability is mostly the inverse of friction. [3] No pen within reach — I'll remember it later — and the record is never made. Small friction collapses the completion rate. This suggests one reason structured records can lag behind events: entering them may take more effort than leaving a note. It does not establish a universal multi-year delay.
So what if a thing could be structured the instant it happens — with no separate act of structuring — just by typing into a chat window, from any device? That may lower the effort of recording an event. Resolving ambiguity, checking the proposed structure and making the result findable still take work. We have not measured equivalence to a Post-it or a universal two-minute retrieval time.
Where the business was once bent to fit the tool, the tool now bends to fit the business.
It is 2026. Seventy years after Ashby. Agents provide another route from an ordinary message to a structured record. Rules, forms and earlier automation already handled parts of that work; the opportunity is to cover more of the unstructured input.
References
- Ashby, An Introduction to Cybernetics (1956) — panarchy.org/ashby/variety.1956.html
- Conant & Ashby, "Every Good Regulator of a System Must Be a Model of That System," Int. J. Systems Science 1(2), 1970 — Good Regulator Theorem
- Fogg Behavior Model (B=MAP), Stanford — thedecisionlab.com
godcrm.ai/git/holetron-lab/godcrm
Correction · 29 September 2026: Separated the cybernetics analogy from a theorem about information conservation and removed unsupported first-ever and timing claims.