Frequently asked questions about thinking, epistemology, and cognitive tools. 100 answers
Assuming that hiring smart individuals automatically produces smart teams. This is the composition fallacy — the belief that team intelligence is the sum of individual intelligences. Research consistently shows that team performance correlates weakly with average individual IQ and strongly with.
Assuming that shared mental models form automatically from working together. They do not. Proximity creates familiarity, not alignment. Two engineers who have worked side by side for three years may have fundamentally different models of how the deployment pipeline works, what 'ready for review'.
Making thinking visible only during retrospectives or postmortems — treating externalization as a corrective practice rather than an ongoing cognitive infrastructure. If the team only surfaces its thinking after something goes wrong, the externalization is reactive rather than proactive. The.
Attributing team cognitive failures to individual weakness — blaming the person who did not speak up rather than the architecture that suppressed their contribution. Telling a team to 'be more open' or 'share your concerns' without changing the structural conditions that produce silence is like.
Confusing psychological safety with niceness, conflict avoidance, or lowered standards. Psychological safety is not about making everyone comfortable. It is about making it safe to be uncomfortable — safe to disagree, safe to point out problems, safe to say 'I do not understand,' safe to challenge.
Confusing demographic diversity with cognitive diversity. Demographic diversity (gender, ethnicity, age) correlates with cognitive diversity but is not identical to it. A team of five people from different demographic backgrounds who all attended the same business school and worked at the same.
Building the map once and never maintaining it. A transactive memory system is a living representation that must evolve as people learn new skills, systems change, and team members join or leave. A static expertise map from six months ago is worse than no map — it creates false confidence in.
Over-engineering decision processes to the point where every minor choice requires a formal protocol. Decision protocols are cognitive infrastructure for high-stakes decisions — choices that are difficult to reverse, that have significant consequences, and that benefit from multiple perspectives..
Two failure modes dominate team retrospectives. The first is ritual without reflection — performing the retrospective ceremony without the cognitive work of actual analysis. The team goes through the motions, lists complaints and compliments, records action items, and returns to work unchanged..
Two symmetric failures. The first is conflict avoidance — treating all disagreement as negative and working to eliminate it. Teams that avoid conflict achieve false harmony at the cost of suppressed information, unexamined assumptions, and decisions that reflect the preferences of the most.
Two opposing failures. The first is meeting proliferation — scheduling meetings for everything because synchronous conversation feels productive, even when the cognitive work does not require real-time interaction. Information sharing, status updates, and simple approvals rarely benefit from a.
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.