Frequently asked questions about thinking, epistemology, and cognitive tools. 1668 answers
Assuming that schema alignment is a one-time activity — that once the team agrees on definitions, the alignment persists indefinitely. Schemas drift as context changes, new members join, and the system evolves. The term 'production-ready' may have meant one thing when the system served a hundred.
Introducing epistemic practices as mandates rather than invitations. When a team lead imposes a new practice — 'From now on, we all do pre-mortems before every launch' — without explaining the reasoning or demonstrating the value, the practice becomes an administrative burden rather than a.
Conducting the audit as a one-time event rather than a recurring practice. A single audit produces a snapshot that is informative but perishable — the team's cognitive architecture evolves with every personnel change, project shift, and organizational restructuring. The audit must be repeated —.
Believing that team cognitive architecture can substitute for individual epistemic development. This is the structural fallacy — the assumption that if the process is right, the individuals do not need to be skilled. Decision protocols require individuals who can reason clearly. Retrospectives.
Confusing organizational schemas with official statements. The strategy deck says 'We are customer-centric.' The organizational schema might actually be 'We are engineering-centric' — as revealed by which arguments win in resource allocation decisions, which metrics get reviewed in leadership.
Assuming that implicit schemas are necessarily wrong or harmful. Many implicit schemas are adaptive — they encode accumulated organizational wisdom about what works. The problem is not that schemas are implicit but that implicit schemas cannot be examined, updated, or deliberately maintained. An.
Treating schema surfacing as an intellectual exercise rather than a practical intervention. An organization that surfaces its schemas but does not decide what to do about them has created awareness without change — and awareness without change produces cynicism. ('We had a big workshop about our.
Confusing a strategic plan with a strategy schema. A plan is a list of actions. A schema is a mental model. An organization can have a detailed plan — 'Launch product A in Q2, expand to Europe in Q3, hire 50 engineers by year-end' — without having a strategy schema. The plan tells people what to.
Two symmetric failures. The first is treating processes as sacred — refusing to modify a process because 'it has always been done this way' or because the process was designed by someone with authority. This treats the process as a fixed instruction rather than a living schema, ensuring that the.
Two symmetric failures. The first is value inflation — listing so many values that they provide no guidance. When an organization has eight or ten values, the values cannot function as schemas because they do not resolve tradeoffs. An organization that values 'innovation, quality, speed,.
Trying to change culture directly rather than changing the schemas that produce it. Culture is an emergent property — it arises from the interaction of lower-level components (schemas) and cannot be changed by addressing the emergent property itself. Telling people to 'be more innovative' does not.
Treating schema conflicts as one side being right and the other wrong. When engineering and marketing disagree, the typical organizational response is to decide which team's perspective is correct and force the other to conform. But schema conflicts between functions usually reflect different but.
Assuming that formal onboarding programs are sufficient for schema propagation. Formal onboarding covers policies, tools, and procedures — the explicit layer of organizational knowledge. But the most consequential schemas are implicit: who to go to for real answers, how decisions actually get.
Two failures that are mirror images. The first is schema rigidity — refusing to update schemas until a crisis forces the change. This produces organizations that are perfectly adapted to the past and catastrophically maladapted to the present, which is the pattern described in the example above..
Confusing documented knowledge with operational knowledge. An organization can have extensive documentation — wikis, runbooks, architecture diagrams — and still have a fragile knowledge graph if no one has internalized the documented knowledge well enough to act on it under pressure. Documentation.
Treating knowledge transfer as a departure event rather than an ongoing practice. When an employee gives notice, organizations often schedule a two-week knowledge transfer period. But two weeks is not enough to transfer years of accumulated knowledge — especially the tacit knowledge that cannot be.
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.
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,.
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.
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.
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.
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.
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.
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.