Frequently asked questions about thinking, epistemology, and cognitive tools. 9,738 answers
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?
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).
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..
Take the system map you created in L-1663's exercise. For each component and connection, rate its leverage on a three-point scale: (1) Low leverage — changing this element would have minimal impact on the outcome; (2) Medium leverage — changing this element would shift the outcome noticeably but not dramatically; (3) High leverage — changing this element would fundamentally change the system's behavior.
Confusing ease of change with leverage. The easiest things to change in a system (parameters, numbers, surface-level processes) are usually the lowest-leverage interventions. The hardest things to change (goals, paradigms, feedback structures) are usually the highest-leverage interventions. The failure mode is choosing interventions based on ease rather than leverage — producing visible activity (look, we changed something!
Small changes in the right places can produce large systemic effects. Leverage points are the places in a system where intervention produces disproportionate results — where a modest redesign of a single element shifts the behavior of the entire system. Donella Meadows identified a hierarchy of leverage points ranging from parameters (weakest) to paradigms (strongest).
Map the feedback loops maintaining one persistent pattern in your organization — either a pattern you want to preserve or one you want to change. Start with the outcome and trace backward: What produces this outcome? What does the outcome produce in turn? Follow the chain until it loops back to the starting point.
Fighting feedback loops instead of redesigning them. When a reinforcing loop amplifies undesired behavior, the instinct is to push back against the loop's output — adding controls, oversight, and enforcement to suppress the behavior. But the loop continues to operate, producing pressure against the controls.
Identify the reinforcing and balancing loops that maintain current organizational behavior. Every persistent organizational pattern — whether desirable or undesirable — is maintained by feedback loops. Reinforcing loops amplify behavior: success breeds more success, failure breeds more failure, growth accelerates growth, decline accelerates decline.
Before implementing your next system change, conduct a pre-mortem for unintended consequences. Write down the intended change and the intended consequence. Then systematically ask five questions: (1) Who else is affected by this change besides the intended target? What will they do differently?.
Using the risk of unintended consequences as an argument against system change. Every system change has unintended consequences — but so does maintaining the current system. The status quo produces its own consequences, which are often severe but invisible because they are familiar. The failure mode is asymmetric risk assessment: treating potential unintended consequences of a proposed change as deal-breakers while ignoring the actual ongoing consequences of the current system.
Every systemic intervention produces effects beyond what was intended — anticipate and monitor. Complex systems are interconnected: changing one element affects others through pathways that may not be visible to the change agent. Unintended consequences are not failures of planning — they are inherent properties of complex systems.
For a change you are planning or currently implementing, map the resistance forces using a force field analysis. Draw a vertical line representing the current state. On the left, list the driving forces — the pressures pushing toward the desired change (market demands, leadership commitment, cost pressures, competitive threats).
Treating resistance as opposition to be overcome rather than information to be understood. Resistance to system change is usually rational — the resisters are responding to real incentives, real identity threats, or real concerns about the change's viability. The failure mode is labeling all resistance as 'resistance to change' and attempting to power through it, ignoring the legitimate information the resistance carries.
Homeostatic forces in any system push back against change — expect and plan for resistance. Systems develop self-preserving mechanisms that maintain the current state regardless of whether that state serves the organization well. These mechanisms are not conspiracies — they are structural properties of complex systems.
For a system change you are planning, create a stakeholder map. List every person, role, team, and function that interacts with the part of the system being changed. For each stakeholder, document: (1) Their current benefit from the existing system — what do they gain from the way things work now?.
Treating stakeholder mapping as a one-time exercise completed before the change begins. Stakeholder interests, influence, and responses evolve as the change unfolds. A stakeholder who was neutral during planning may become actively resistant during implementation when the change's impact on their work becomes concrete.
Identify who benefits from the current system and who would benefit from the proposed change. Every system serves some interests and neglects others. Systemic change redistributes benefits and costs — creating new winners and new losers. Understanding this distribution before implementing the change is essential for predicting resistance, building support, and designing the change so that it serves the broadest possible set of interests.
For a system change you want to implement, build a coalition map. Identify the three layers of coalition you need: (1) Evidence providers — people who have data, experience, or pilot results that demonstrate the change works. Without evidence, the coalition is advocating for theory. (2) Capability providers — people who can build, implement, or operate the systems required by the change.
Building a coalition of like-minded people who lack organizational diversity. A coalition of enthusiasts who all occupy similar positions (all middle managers, all from the same function, all from the same generation) lacks the organizational reach needed to change the system.
Systemic change requires allies at multiple levels of the organization. No individual — regardless of position or authority — can change a system alone, because systems are maintained by the collective behavior of everyone who operates within them.
Design a pilot for a system change you want to make. Define five elements: (1) Scope — what is the bounded context for the pilot? Choose a team, project, or process that is representative of the broader organization but small enough to monitor closely. (2) Duration — how long will the pilot run?.
Running a pilot that is not a genuine experiment.
Test systemic changes on a small scale before rolling them out broadly. A pilot program is a bounded experiment — a deliberate test of the proposed system change in a contained context where the change can be observed, measured, and refined without risking the entire organization. Pilots serve three functions: they generate evidence (does the change produce the intended outcome?