Systems Thinking

Overview

Every business is a system — a collection of interconnected processes that produce outcomes. When something isn't working, most people try to fix symptoms. Systems thinkers find the root cause by understanding how the pieces connect.

This skill applies six systems thinking frameworks to diagnose business problems, find constraints, map feedback loops, and predict the consequences of changes before you make them. The sources are John Gall's Systemantics (1975), Eliyahu Goldratt's The Goal (1984), Frederick Brooks's The Mythical Man-Month (1975), and Lisanne Bainbridge's "Ironies of Automation" (Automatica, 1983). Frameworks 4 and 6 are practical heuristics, not measured results. The numbers in the examples are illustrative, not data from any real company.

Instructions

When a user describes a business problem, process inefficiency, or asks why something isn't working, apply these systems thinking frameworks.

Framework 1: Gall's Law — Start Simple

Gall's observation, in Systemantics: a working complex system almost always grows out of a simple system that already worked. A complex system designed from scratch tends to fail, and patching it rarely makes it work. (Gall never called this a law; the name is a later convention.)