Frequently asked questions about thinking, epistemology, and cognitive tools. 9,738 answers
For a recent change in your organization, assess whether the system actually changed by applying three tests: (1) The attention test — does the improved outcome persist when leadership attention moves to other priorities? If performance reverts when the spotlight moves, the system did not change — effort changed.
Measuring only the intended outcome and ignoring system health indicators. A change that produces the intended outcome while degrading system health (increasing burnout, reducing morale, creating technical debt, eroding trust) has not improved the system — it has traded one problem for another..
Define how you will know the system has actually changed, not just appeared to change. Systemic change is real only when the system produces different outcomes under normal operating conditions — without extra attention, heroic effort, or temporary workarounds. Many change efforts produce initial improvements that fade as the organizational attention moves elsewhere, revealing that the system itself did not change — only the effort level did.
Identify one behavior in your organization that you have been trying to change through training, motivation, or persuasion. Ask: What structural change would make the desired behavior the default — the easiest path — without requiring individual motivation to sustain it?
Implementing structural changes without considering the behavioral adaptation they will produce. People do not passively accept structural constraints — they adapt to them, work around them, and sometimes subvert them. A structural change that is too rigid (removing all decision flexibility) produces workarounds that undermine the structure.
Changing organizational structures changes behavior more reliably than training or persuasion. Structural change modifies the environment in which behavior occurs — the rules, roles, processes, tools, and physical arrangements that shape what people do. Behavioral change attempts to modify the behavior directly — through training, coaching, incentives, or persuasion — while leaving the environment unchanged.
Audit the incentive system for one role in your organization. List every metric that is measured, reported, or rewarded — both formally (performance reviews, bonuses, promotions) and informally (what gets praised in meetings, what gets attention from leadership, what gets criticized). For each metric, ask: If someone optimized exclusively for this metric, what behavior would they exhibit?
Designing incentives that optimize one dimension at the expense of others. Every metric creates pressure toward the measured dimension and neglect of unmeasured dimensions. A sales team incentivized on revenue will pursue revenue at the expense of profitability. An engineering team incentivized on velocity will pursue speed at the expense of quality.
What gets measured and rewarded determines what people actually do. Incentive design is the most powerful lever for systemic change because incentives operate continuously, automatically, and at scale — shaping behavior across the entire organization without requiring individual intervention.
Map the information flows for one decision process in your organization. Choose a recurring decision — a hiring decision, a prioritization decision, a resource allocation decision. For each step in the decision process, identify: (1) What information is available to the decision-maker? (2) What information is missing that would improve the decision?
Information overload — routing too much information to too many people. The solution to information gaps is not more information; it is the right information. Flooding people with data produces the same decision quality as depriving them of data — because the relevant signal is buried in irrelevant noise.
Changing who gets what information and when changes organizational behavior. Information is the input to decisions. When the information changes — when different data reaches different people at different times — the decisions change, and with them the organizational outcomes.
Audit the decision rights for your team or function. List the ten most common decisions your team makes. For each decision, identify: (1) Who currently makes this decision? (2) Who should make this decision? (the person closest to the relevant information and most affected by the outcome). (3) What approval is currently required?
Delegating decisions without delegating information and accountability. Pushing decisions down the organization without ensuring that the decision-makers have the information they need produces poor decisions — not because the people are less capable but because they lack the inputs that good decisions require.
Clarifying who can make which decisions restructures organizational behavior. Decision rights — the formal and informal authority to commit the organization to a course of action — are the most consequential element of organizational design. When decision rights are clear, decisions are made quickly by the people best positioned to make them.
Map the end-to-end process for one type of work your team produces. Document every step from initiation to completion, including: (1) Active time — how long does each step take when someone is actively working on it? (2) Queue time — how long does the work sit waiting between steps? (3) Handoffs — where does the work move from one person or team to another?
Redesigning the process for the ideal case while ignoring exceptions. Every process has a 'happy path' (the ideal sequence when everything goes well) and exception paths (what happens when things go wrong, inputs are incomplete, decisions are contested, or requirements change). Process redesigns that optimize the happy path while ignoring exceptions produce faster processes that break catastrophically when exceptions occur — which they always do.
Changing how work flows through the organization changes outcomes. Process redesign modifies the sequence, timing, dependencies, and handoffs through which work moves from initiation to completion. Well-designed processes produce consistent outcomes efficiently. Poorly designed processes produce inconsistent outcomes wastefully — not because the people within them are careless but because the process itself creates bottlenecks, errors, delays, and rework.
Identify one technology tool your organization uses that was deployed as an automation of the existing system rather than as a systemic change. Ask: What new information flows does this tool make possible that we are not using? What process changes could this tool enable that we have not implemented?
Believing technology will change the system without deliberate system redesign. Technology is an enabler, not a cause, of systemic change. A new tool deployed within an unchanged system produces the same outcomes at higher cost — the tool automates the existing dysfunction rather than replacing it.
New tools can force systemic change by changing what is possible and what is easy. Technology is not a neutral instrument — it is a structural force that reshapes the systems in which it is deployed. Introducing a new tool changes the information flows (who knows what), the process flows (how work moves), the decision rights (who can act), and the incentive structures (what is visible and measurable).
For a change your organization has implemented, assess its sustainability using four tests: (1) Incentive alignment — are people rewarded for the new behavior or the old behavior? If the incentives still support the old behavior, the change will revert when attention shifts. (2) Process embedding — is the new behavior embedded in formal processes or dependent on informal commitment?
Confusing implementation with completion. The most common failure mode is declaring victory at implementation — announcing the change is done, dissolving the change team, and moving organizational attention to the next priority. Implementation is the midpoint of change, not the endpoint. The period after implementation — when the change must be reinforced, refined, and embedded — is where most changes succeed or fail.
Changes that are not reinforced by the system will revert — build sustainability in. Systemic change does not end at implementation. Every change faces a sustained gravitational pull toward the pre-change state — the inertia of old habits, the persistence of old mental models, the decay of change energy as organizational attention moves to new priorities.