Frequently asked questions about thinking, epistemology, and cognitive tools. 300 answers
Choose one important system, process, or decision that your team is responsible for. Check the existing documentation. Does it capture only what (current state, procedures, configurations) or does it also capture why (design rationale, alternatives considered, tradeoffs accepted)? If the.
Two opposing failures. The first is documentation as archaeology — creating documentation that is so detailed and comprehensive that it becomes impenetrable. A fifty-page document that captures every nuance of a system's history but cannot be navigated or searched effectively preserves knowledge.
Documentation is not just a record of what exists. It is a preservation mechanism for organizational schemas — the shared mental models that explain why things are the way they are, not just what they are. Documentation that captures schemas (the reasoning, the context, the tradeoffs) preserves.
Identify one persistent problem in your team or organization — an issue that has been addressed multiple times without lasting resolution. For this problem, distinguish between single-loop and double-loop responses. Single-loop: What actions has the organization taken to address the problem within.
Confusing learning by individuals with organizational learning. When a team member learns a better approach through personal experience, the organization has not learned — a person has learned. Organizational learning occurs only when the new knowledge is embedded in the organization's schemas,.
An organization that cannot update its schemas in response to feedback is dying — it is operating from an increasingly inaccurate model of reality. Organizational learning is the process through which the organization revises its shared mental models based on experience. Single-loop learning.
Conduct a schema debt audit for your team or organization. List five to seven core assumptions the organization operates from (use the schema surfacing methods from L-1623 if needed). For each assumption, answer: (1) When was this assumption formed? (2) What were the conditions when it formed? (3).
Attempting to pay down all schema debt at once. Organizations that discover their accumulated schema debt often try to update everything simultaneously — new strategy, new processes, new values, new culture. This produces change fatigue, resistance, and the failure of all changes rather than the.
Outdated schemas that no one updates create a growing liability — organizational schema debt. Like technical debt, schema debt accumulates silently: each outdated assumption imposes a small cost on every decision it influences, and the costs compound as the gap between the organization's mental.
Choose one strategic concept that your organization's leadership discusses regularly (a strategic priority, a cultural value, or a competitive positioning). Ask people at three different levels — executive, middle management, and individual contributor — to explain this concept in their own words.
Assuming that vertical schema misalignment is a communication problem that can be solved by more or better communication. When the CEO's strategy schema has not reached the front line, the typical response is more all-hands meetings, more strategy documents, more town halls. But communication.
Leaders and front-line workers often hold different schemas about the same reality — different mental models of what the organization does, why it does it, and what matters most. This vertical misalignment is not a communication failure. It is a structural consequence of the different information.
Choose a request or proposal you need to make to a different function. Before presenting it, identify the receiving function's schema: What do they optimize for? What do they measure? What do they consider high-quality work? Then translate your request into their schema. If you are asking.
Expecting one function to adopt another function's schema rather than translating between them. When engineering and marketing disagree, the typical response is to escalate to a leader who picks one side. This forces one function to adopt a schema that does not fit its context. The result is.
Different functions speak different cognitive languages — not just different jargon, but different schemas for what matters, what quality means, and how success is measured. Cross-functional collaboration requires translation between these schemas: the ability to understand another function's.
Conduct a schema audit using this eight-dimension framework. Rate each 1-5 (1 = severely outdated or broken, 3 = functional but inconsistent, 5 = current and well-maintained). (1) Identity schema — Does the organization's self-concept match its current reality? (2) Strategy schema — Is the.
Conducting the audit without the authority or commitment to act on the results. A schema audit that produces scores but no interventions is worse than no audit: it creates awareness of problems without addressing them, which produces cynicism. Every schema audit should conclude with a prioritized.
Regularly assess whether organizational schemas match current reality — across all dimensions: currency, alignment, propagation, documentation, and debt. The schema audit is the organizational equivalent of the team cognitive audit from L-1619, scaled to examine the shared mental models that shape.
List three decisions you have made as a leader in the past month. For each decision, ask: Was this decision about what to do in a specific situation, or was it about how the team should think about a category of situations? Decisions about what to do are operational decisions — they solve the.
Designing schemas through announcement rather than through reinforcement. A leader who announces 'We now value speed over perfection' has not changed the schema — they have stated an intention. The schema changes only when the organizational systems reinforce the announcement: when speed is.
One of the most important jobs of leadership is designing and updating organizational schemas — the shared mental models through which the organization perceives, interprets, and acts. Leaders who focus only on decisions and actions are managing the organization's output. Leaders who design.
Choose one organizational behavior you want to improve — meeting quality, decision speed, customer responsiveness, code quality, or any persistent behavioral challenge. Instead of creating a new rule or process to mandate the desired behavior, identify the schema that would produce the behavior.
Concluding that if schemas are sufficient, rules are unnecessary. Healthy schemas do not eliminate the need for rules, processes, and accountability. They reduce the need for excessive rules by making most behavior self-regulating — people who hold the right schemas naturally behave appropriately.
Get the shared mental models right and behavior follows naturally. Organizations do not need to control behavior through rules, surveillance, or micromanagement when the shared schemas — the collective mental models of what matters, how the world works, and what good looks like — are accurate,.