Frequently asked questions about thinking, epistemology, and cognitive tools. 300 answers
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.
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.
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. But.
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 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.
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. Information flow.
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).
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.
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.
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 —.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Heroic leadership — the leader who personally drives every aspect of the change through force of will, personal attention, and direct intervention. Heroic leadership produces change that depends entirely on the leader: when the leader's attention shifts, the change stalls; when the leader departs,.
The leader's role in systemic change is to set direction, remove obstacles, and maintain commitment. Leaders do not change systems through personal effort — they change systems by creating the conditions under which systems can be changed by the people who operate them. The systemic leader is an.
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.
Treating systemic change as a project rather than a capability. Organizations that treat systemic change as a one-time project — something you do, complete, and move on from — develop fragile adaptations. They may successfully execute one transformation, but they do not build the organizational.
Organizations that cannot change their systems cannot adapt to changing environments. Evolution is not a metaphor for organizational change — it is the mechanism. Biological organisms evolve by modifying the systems (genetic, developmental, behavioral) that produce their characteristics..