Frequently asked questions about thinking, epistemology, and cognitive tools. 100 answers
Treating artifacts as purely functional objects rather than as cultural encoders. When organizations redesign office spaces, choose collaboration tools, or restructure documentation systems, they typically evaluate options on functional criteria — cost, efficiency, features. They rarely ask: what.
Relying solely on engagement surveys to measure culture. Engagement surveys measure perception — what people believe and feel about the culture. They do not measure behavior (what people actually do) or outcomes (what the culture produces). Survey responses are also subject to social desirability.
Abandoning a culture change effort because it is not producing results quickly enough. Most culture change initiatives fail not because the approach is wrong but because the timeline expectation is wrong. Leaders who expect visible cultural shifts within a quarter are applying the wrong timescale..
Attempting to change behavior through exhortation rather than through structural change. Telling people to 'collaborate more' without changing the structures that reward individual work is exhortation — it asks people to behave against their incentives. Changing the structures so that.
Treating all resistance as illegitimate and pushing through it with force. Not all cultural resistance is dysfunction preservation. Some resistance carries valid information: the change may be poorly designed, may not fit the organizational context, or may produce unintended consequences that the.
Attempting to eliminate sub-cultures in the name of cultural unity. Sub-cultures are not symptoms of cultural failure — they are adaptations to the different demands of different roles. Engineering needs a sub-culture that values precision and rigor because engineering mistakes can break.
Treating the 'culture eats strategy' maxim as an argument against ambitious strategy. The insight that culture can undermine strategy does not mean the organization should only pursue strategies its current culture supports — that would trap the organization in its current cultural limitations..
Designing feedback loops that measure but do not act. A cultural pulse survey that produces data no one reviews is not a feedback loop — it is a monitoring system without a response mechanism. The feedback loop requires both sensing (detecting drift) and correcting (responding to drift). Many.
Treating culture as a competitive advantage and therefore making it rigid — resisting any cultural evolution to preserve the advantage. The paradox of cultural advantage is that the advantage persists only as long as the culture remains adaptive. A culture that was a competitive advantage in one.
Confusing cultural alignment with cultural conformity. Alignment means shared commitment to a set of behavioral standards and operational practices. Conformity means shared thinking, identical perspectives, and suppressed individuality. The failure mode is using culture as a tool for.
Using evolution as an excuse for inaction. The distinction between evolution and revolution is not the distinction between slow change and no change. Cultural evolution requires active, deliberate, sustained effort — the same effort as revolution, but distributed over a longer timeline and.
Confusing cultural autopilot with cultural health. A self-running culture is not necessarily a healthy culture — it could be a culture that has automated dysfunctional patterns. Bureaucracies run themselves, but they run themselves badly. The distinction is between culture that runs well.
Using systems thinking as an excuse for individual accountability. The insight that systems produce outcomes does not eliminate individual responsibility — it reframes it. Individuals are responsible for the choices they make within the system and for speaking up when the system produces harmful.
Changing the wrong system element. Not all system elements are equally influential. Changing a low-leverage element (rearranging reporting lines, updating a policy document, adding a review step) while leaving the high-leverage elements unchanged (incentive structures, information flows, decision.
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.
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.
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).