What goes wrong when you ignore that identify the system before trying to change it?

The most common reason fails: Mapping the system you wish existed rather than the system that actually operates. Every organization has a formal system (the org chart, the documented processes, the official policies) and an informal system (the actual decision paths, the workarounds, the shadow processes that get real work done). System identification must map the informal system — the one that actually produces the outcomes — not the formal system that exists on paper. Mapping the formal system produces a beautiful diagram that explains nothing about why the outcomes are what they are.

The fix: Choose a system you want to change. Before designing any intervention, create a system map with four layers: (1) Boundary map — draw a circle around everything inside the system and list what is outside. Include upstream suppliers (who provides inputs?) and downstream consumers (who receives outputs?). (2) Component map — list every actor, process, decision point, and resource inside the boundary. Do not simplify — the components you leave out are often the ones driving the outcome. (3) Connection map — draw arrows between components showing how they influence each other. Label each arrow: information flow, material flow, authority flow, or incentive flow. (4) Dynamics map — identify the feedback loops (reinforcing and balancing), the delays (where time passes between cause and effect), and the accumulations (where things build up before being processed). Compare your map with two or three people who operate within the system. Their maps will differ from yours — the differences reveal components and connections you missed.

The underlying principle is straightforward: Map the current system completely before intervening. Most system change efforts fail not because the intervention was wrong but because the change agent misidentified the system — addressing a visible subsystem while the actual driver sits in a different, invisible part of the organization. System identification requires mapping the boundaries (what is inside and outside the system), the components (what elements interact to produce the outcome), the connections (how elements influence each other), and the dynamics (how the system behaves over time). Without this map, intervention is guesswork.