Four Laws of Complex System Design
The complete reference document — how the four laws originated, how they interact, decomposability, Beer’s VSM, boundaries you don’t control, and flow & constraints.
Not yet migrated — still live on the old site.
Four Laws of Complex System Design
Why teams and the systems they build keep running into the same failure modes — and a shared vocabulary for diagnosing them. Built around four foundational laws, how they interact, and what happens to work once it starts moving through the structure they create.
- Ashby's Law of Requisite Variety
- Conway's Law
- Brooks's Law
- The Reverse Conway Maneuver
- Beer's Viable System Model
Read
Explore
Managing Process: Flow & Constraints
Little’s Law and the Theory of Constraints, with a worked subscription-billing delivery example.
Read the walkthrough →Conway's Law and Your RevOps Team Structure
Why your CRM, CPQ, and billing systems already mirror your org chart, and how to use the Reverse Conway Maneuver to redraw team boundaries around quote-to-cash instead of department lines.
Read the example →Conway's Law in the AI Agent Era
AI agents inherit your team boundaries, not just your tasks — why an AI SDR or billing-exceptions agent fails exactly where your org chart already had a seam.
Read the example →Why Executive Decisions Stall on Client Projects
Little’s Law, Kingman’s formula, and Weinberg’s numbers, applied to the steering committee instead of the delivery team — why the same sign-off takes six weeks.
Read the example →The Four Laws Across Revenue and Back-Office Teams
Ten worked examples — Marketing, Sales, Customer Success, Finance, and RevOps, each with a SaaS and a services flavor — showing where these laws actually show up in day-to-day work.
Browse the examples →WIP Limits vs. the Theory of Constraints
A WIP limit is a Kanban practice; the Theory of Constraints tells you where to put it. Why conflating them leaves throughput exactly where it started.
Read the breakdown →AI, System 4, and Beer's VSM
AI can supercharge System 4 environmental scanning — but faster signals without a functioning System 5 just produce paralysis at machine speed.
Read the example →Look up
Glossary
Short definitions of every term on this site — Ashby, Conway, Brooks, Reverse Conway, Team Topologies, Beer’s VSM, Little’s Law, and the Theory of Constraints — with links to the full explanation.
Browse the glossary →FAQ
Straight answers to the questions that come up most — how these ideas differ, how they interact, and where to start applying them.
Read the FAQ →Use
Flow & Constraint Diagnostic
A five-step guided diagnostic — plug in your own WIP, throughput, and constraint details to get a personalized Five Focusing Steps writeup you can use in a client conversation.
Start the diagnostic →Flow Formula Calculator
Interactive calculators for Little’s Law, Kingman’s formula, and Weinberg’s context-switching numbers — plug in real engagement numbers to see what they predict.
Open the calculator →Stakeholder Decision Stall Checklist
Check off what’s true of a stalled client engagement to see whether you’re facing a Little’s Law queue problem, a Kingman utilization problem, or a Weinberg signal-distortion problem.
Run the checklist →Downloads
Ashby's Law — Client as Regulator (one-pager)
Not yet migrated — the file still needs copying across from the old site into public-fourlaws/.
Questions, a correction, or want to talk shop?Get in touch →