Requisite Variety
The Systems Method for Working with AI — Beyond Prompts and Tools
Everyone has access to the same AI models. Yet the results differ by an order of magnitude. Why?
It's not the prompts. It's not the tools. It's who controls whom.
In 1956, cybernetician W. Ross Ashby formulated the law of requisite variety: only variety can absorb variety. A modern AI model produces an enormous variety of outputs. An engineer armed with prompt collections has a handful of templated reactions. In that pair, the question of who is steering is arithmetic, not willpower.
Power tools made carpenters faster — and made it easier to drill straight through the workpiece. AI is the power tool of knowledge work. This book is about keeping the feel of the material in your hands.
It gives you a method, not tips:
- See what you actually operate: not a model, but a system — you, the model, the context, the tools, the artifacts.
- Separate your goal from the proxy the machine optimizes — the gap between them is where disappointment lives.
- Build norms and control loops that turn one-off wins into repeatable results — and make agents safe to trust.
- Understand AI slop as a diagnosis, not bad luck: low-variety input produces average output.
Written primarily for software engineers. Useful for anyone who works with LLMs seriously. A short final part addresses managers: how to see whether a team is producing or merely circulating.
What's not inside: tool reviews, model comparisons, prompt collections. Everything in this book will still be true three model generations from now.
Read a full chapter below — in Ukrainian, the language the book is written in first.
Get new chapters and essays
English essays land in the Requisite Variety section of my newsletter; Ukrainian chapters — in the main feed. Pick what you need.