Frequently asked questions about thinking, epistemology, and cognitive tools. 497 answers
Conduct the 'leader absence test' — a thought experiment (or, if possible, an actual experiment). Ask: If I were completely unreachable for two weeks, what decisions would stall? What conflicts would escalate? What behaviors would degrade? Each answer reveals a point where the cultural.
Identify one recurring organizational outcome that frustrates you — something that keeps happening despite your efforts to change it. Instead of asking 'Who is causing this?', draw the system that produces it. Map the inputs (what triggers the process), the process steps (what happens in.
Take the system map you created in L-1661's exercise (the recurring outcome that frustrates you). For each system element you identified as a strong driver of the outcome, design a specific system change that would shift the outcome. For structural elements, ask: What structural redesign would.
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.
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.
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.
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?.
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.
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?.
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.
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?.
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 —.
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? Consider four types of.
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.
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.
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).
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 —.
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.
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.
Assess your own leadership approach to systemic change using three questions: (1) Am I setting clear direction — have I articulated what the changed system looks like, why it matters, and how it differs from the current state? Direction is not a mandate; it is a vision that helps people understand.
Conduct a systemic change readiness assessment for your organization. Evaluate your organization's capability across the ten systemic change functions covered in this phase: (1) System identification — can you map your organization's key systems, including boundaries, components, connections, and.
Map the decision flow in your organization for one week. For every decision you encounter — whether you make it, request it, or wait for it — record: (1) What was the decision? (2) Who made it? (3) Who had the information needed to make it? (4) Were the decision-maker and the information-holder.
Audit one week of decisions in your team or organization. For each decision, record: (1) Who made the decision? (2) Who had the most relevant information? (3) How long did the decision take from request to resolution? (4) How much of that time was active analysis versus waiting in queues? (5) Was.
Run a one-week self-organization experiment with your team. For one sprint or work week, give the team full authority over three decisions that are currently made by management: (1) task allocation — let the team decide who works on what, (2) process design — let the team design their own daily.