Frequently asked questions about thinking, epistemology, and cognitive tools. 300 answers
At your next team retrospective, replace the standard 'What went well / What didn't / What should we change' format with a structured reflection protocol. Step 1 (5 minutes): Each team member independently writes answers to three questions — 'What surprised me?' 'What pattern am I seeing.
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..
Regular team reflection — structured retrospection on what happened, why, and what to change — is the mechanism through which teams learn. Without it, teams repeat the same failures and miss the same opportunities, regardless of individual intelligence.
Assess your team's conflict profile using Jehn's three-type framework. For each type, rate your team on a 1-5 scale. (1) Task conflict — 'Team members regularly disagree about ideas, approaches, and technical decisions.' (2) Process conflict — 'Team members disagree about who should do what and.
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.
Healthy disagreement — task conflict about ideas, approaches, and interpretations — improves team decisions. The absence of conflict does not signal harmony. It signals suppression of the cognitive diversity the team needs to think well.
Audit one recurring team meeting using these five metrics. (1) Preparation ratio — what percentage of attendees read pre-work before the meeting? (2) Voice distribution — how many unique people speak substantively? (3) Decision clarity — does the meeting end with clearly stated decisions and.
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.
Meetings are the primary site where teams think together. A poorly designed meeting wastes collective cognitive capacity. A well-designed meeting is a cognitive tool that produces thinking no individual could achieve alone.
Identify one recurring synchronous meeting that could be partially or fully replaced by asynchronous collaboration. Design an async alternative using this template: (1) Document format — what information will be shared and in what structure? (2) Contribution protocol — who contributes, by when,.
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.
Much of a team's best thinking happens outside meetings — in written documents, code reviews, design proposals, and structured asynchronous exchanges. Designing for asynchronous cognition extends the team's thinking capacity beyond the limits of synchronous time.
Conduct a 'team memory audit.' List the ten most important pieces of knowledge your team holds — architectural decisions, operational procedures, customer context, historical lessons. For each item, answer three questions: (1) Where is this knowledge stored? (Specific location — not 'somewhere in.
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.
Documentation, shared notes, and knowledge bases are the team's externalized memory. Without designed memory systems, teams lose institutional knowledge through turnover, forget hard-won lessons, and repeatedly solve problems they have already solved.
Map one critical information flow in your team. Choose a type of information that matters — customer feedback, production alerts, requirement changes, or technical discoveries. Trace its path from origin to the person who acts on it. For each step, answer: (1) How does the information move from.
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.
The right information reaching the right people at the right time is a design problem, not an accident. Information flow is the circulatory system of team cognition — when it is blocked, restricted, or misdirected, the team's cognitive capacity degrades regardless of individual talent.
Track your team's attention allocation for one week. At the end of each day, have each team member spend two minutes recording how they spent their time across three categories: (1) Planned work — tasks aligned with the team's stated priorities. (2) Reactive work — tasks that were not planned but.
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.
What the team collectively pays attention to determines what it accomplishes. Team attention is a finite resource that can be designed, directed, and protected — or squandered on whatever is loudest, most urgent, or most emotionally salient.
Map your team's cognitive load distribution. For each team member, estimate three dimensions on a 1-5 scale: (1) Task complexity — how cognitively demanding is their current work? (2) Context switching — how many different contexts do they manage simultaneously? (3) Interrupt load — how frequently.
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.
Distribute cognitive work based on capacity and capability, not just availability. A team where one member is overwhelmed while others are underloaded is not using its collective capacity — it is wasting it.