Gall's Law
Every complex system that works grew out of a simple system that worked. Complex systems designed from scratch almost never work and can't be fixed. So start with the smallest working version and let it grow.
by John Gall · 9 ideas
Every complex system that works grew out of a simple system that worked. Complex systems designed from scratch almost never work and can't be fixed. So start with the smallest working version and let it grow.
Every new system creates problems of its own that didn't exist before. A new approval process brings delays, workarounds and people to manage it. Expect side effects and budget for them.
The moment a system exists, its first goal becomes keeping itself alive and growing. Its official purpose comes second. Judge a team or tool by what it actually rewards, not by its mission statement.
A system rarely does what its name says. People do the real work, often around the official process, not through it. When something gets done, find out who really did it and protect that.
Inside a system, things are what the reports say they are. If it isn't in the dashboard, it doesn't exist. Leave the reports regularly and look at the real thing with your own eyes.
Borrowed from chemistry: a system pushes back against any change you force on it. Pushing harder usually brings more resistance, not progress. Look for the force that is holding things in place and work with it instead.
Safety mechanisms add parts, and every added part is another thing that can break, often in surprising ways. More safeguards don't always mean more safety. Simpler designs are often the safer ones.
A system works best when it goes along with what people already want to do. Fighting human nature takes constant effort and eventually loses. Make the right action the easy and natural one.
A working system is rare and its reasons for working are often hidden. Changing or replacing it can break what you didn't understand. Before you redesign something that works, find out why it works.