Laws of Software Engineering · Framework
Framework
Deming's System of Profound Knowledge
Four ways of looking at a problem that work together: seeing it as a system, understanding variation, asking how we know what we know, and paying attention to people.
How to use it. When a problem looks simple, you have probably ignored at least one of the four. Variation explains most operational pain. The "how do we know" lens explains most learning failures.
How it gets misused. Cherry-picking a single method, such as Plan-Do-Study-Act, without the rest. The four lenses depend on each other. Variation without the people lens becomes process tyranny. The people lens without variation becomes vibes.
Related
- Framework Improvement Kata A four-step pattern for getting better at anything. Understand the direction. Grasp the current condition. Set the next target condition. Run experiments toward it.
- Framework The Fifth Discipline Systems thinking, personal mastery, mental models, shared vision, and team learning. The five disciplines of an organisation that can learn.
-
Framework Theory of Constraints The speed of any system is set by its slowest part. Improving anything else makes no difference.
Clusters
- The Improvement cluster - How systems get better over time.