Frequently asked questions about thinking, epistemology, and cognitive tools. 1668 answers
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.
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.
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.
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.
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. The coalition must.
Running a pilot that is not a genuine experiment. Common corruptions include: selecting the best team for the pilot (guaranteeing success but preventing learning), providing the pilot team with extra resources not available at scale (inflating results), not measuring unintended consequences (only.
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..
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).
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.
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.
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.
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.
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.
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.
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,.
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.
Confusing self-direction with absence of structure. The most common failure is removing hierarchy without building infrastructure — eliminating managers without creating the decision frameworks, information systems, and feedback mechanisms that managers provided. The result is not self-direction.
Distributing decisions without distributing information. The most common failure in distributed decision-making is giving people authority without giving them the information, context, and criteria they need to exercise it well. A product manager authorized to set prices without access to margin.
Self-organization without boundaries. Teams given unlimited self-organization authority with no strategic context, no resource constraints, and no coordination requirements will optimize for their own comfort rather than organizational outcomes. A team might choose to work only on technically.
Purpose as aspiration rather than infrastructure. Many organizations have inspiring purpose statements that have no operational impact — they appear on the website and in the annual report but are never referenced in actual decisions. The failure is treating purpose as a branding exercise rather.
Transparency without context. Raw information without context is noise, not transparency. Publishing a revenue dashboard without explaining what the numbers mean, what is normal versus alarming, and what actions different scenarios warrant produces anxiety rather than alignment. A team that can.
Feedback without correction mechanisms. Many organizations generate extensive feedback data — metrics dashboards, survey results, performance reports — but lack the mechanisms to convert feedback into action. The data exists, but no one is responsible for responding to it, no process triggers.
Retrospectives that produce insights but not changes. The most common retrospective failure is generating rich discussion and accurate diagnosis without producing concrete action. The team leaves the retrospective feeling heard and understood — but nothing changes. The dysfunction persists, and.
Governance rigidity — treating governance structures as permanent fixtures rather than evolving tools. Organizations often treat their governance structures — meeting cadences, approval processes, reporting lines, decision rights — as immutable features of the organizational landscape. The meeting.