Frequently asked questions about thinking, epistemology, and cognitive tools. 300 answers
Choose a term that your team uses frequently but may define differently — 'done,' 'ready for review,' 'production-ready,' 'priority,' 'tech debt,' or a domain-specific term. Ask each team member to independently write a one-paragraph definition. Collect the definitions and compare them. Identify.
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.
When team members hold conflicting schemas about the work — different definitions, different expectations, different mental models of how the system behaves — coordination breaks down silently. Schema alignment is the practice of surfacing and reconciling these invisible differences.
Introduce one epistemic practice to your team this week. Choose the one most relevant to your team's current weakness: (1) If your team makes overconfident predictions, introduce calibrated confidence — have each member predict the outcome of the current sprint's riskiest item with a probability,.
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.
Teaching your team the individual epistemic practices from this curriculum — calibrated confidence, assumption surfacing, perspective taking, evidence evaluation — creates collective capability that exceeds the sum of individual skills.
Conduct a team cognitive audit using this ten-dimension framework. Rate each dimension 1-5 (1 = absent or broken, 3 = functional but inconsistent, 5 = well-designed and maintained). (1) Shared mental models — does the team have aligned understanding of the system, process, and goals? (2).
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 —.
Regularly assess how well the team thinks together — across all dimensions of collective cognition — to identify what is working, what is degrading, and what needs redesign. The audit is to team cognition what a health checkup is to the body: not a crisis response but a maintenance practice that.
Assess your own epistemic contribution to your team using this self-audit. Rate yourself 1-5 on each dimension. (1) Do I calibrate my confidence — do I distinguish what I know from what I assume? (2) Do I surface assumptions — do I make my reasoning visible rather than presenting only my.
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.
A team can only think as well as its members allow. Individual epistemic development — the eighty phases of personal cognitive infrastructure you have built — is the foundation on which every team cognitive practice depends. Without skilled individual thinkers, no team architecture can compensate.
Identify one organizational schema that shapes your team's or organization's behavior. Start with a recurring pattern: a type of decision that always goes the same way, a type of initiative that always gets funded (or never does), a type of risk that always gets flagged (or ignored). Ask: 'What.
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.
Every organization operates through shared mental models — collective schemas that determine what the organization perceives, how it interprets information, and what actions it considers possible. These schemas are not written in the org chart or the strategy deck. They live in the heads of the.
Identify one implicit schema in your organization by looking for a behavior that 'everyone just does' without being able to articulate why. Common examples: Who gets invited to which meetings? What information is shared broadly versus held tightly? Which types of initiatives get funded without.
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.
The most powerful organizational schemas are the ones nobody talks about — the assumptions so deeply embedded in how the organization operates that they feel like facts rather than choices. These implicit schemas determine behavior more reliably than any explicit policy, precisely because they.
Run a schema surfacing session with your team or leadership group. Choose one strategic question the organization is currently debating. Ask each participant to independently write answers to three prompts: (1) 'I believe the fundamental challenge we face is...' (2) 'I believe the right approach.
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.
Surfacing and documenting the organization's shared assumptions is the first step to improving them. The practice of making schemas explicit transforms invisible forces into visible choices — choices that can be examined, tested, and deliberately maintained or revised.
Write your organization's strategy as a single schema statement — not what the organization does, but what it believes about how it creates value. Use this format: 'We win by [doing X] for [audience Y] in a way that [differentiator Z].' Then ask two colleagues to write the same statement.
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.
A strategy is not a plan or a set of goals. It is a shared mental model of how the organization creates and captures value — a schema that tells every member what to prioritize, what to ignore, and how their work connects to the organization's purpose. When the strategy schema is clear and shared,.