Frequently asked questions about thinking, epistemology, and cognitive tools. 497 answers
Two failures that mirror the meeting design failures of L-1611. The first is async overload — routing everything through written channels, producing a flood of documents, threads, and comments that no one has time to read thoroughly. When everything is async, nothing gets the attention it.
The most common team memory failure is documentation that exists but is not maintained — the 'write-once' pattern where knowledge is documented at creation time and never updated. Within months, the documentation diverges from reality, and team members learn to distrust it. Worse, they stop.
Two opposing failures. Information overload — routing everything to everyone, which produces a flood that no one can process, and causes the most important signals to be lost in noise. The team that copies everyone on every email, posts every update to a shared channel, and invites everyone to.
Protecting team attention so aggressively that the team becomes unresponsive to legitimate signals. A team that never responds to escalations, customer feedback, or changing conditions is not managing its attention — it is ignoring its environment. The goal is not to eliminate all reactive work.
Distributing work based on equality rather than equity — giving everyone the same amount of work regardless of the cognitive demands of that work. Two tasks that take the same number of hours may have vastly different cognitive loads: debugging a race condition in a concurrent system is more.
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.