Core Primitive
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.
You cannot change what you cannot see
The previous two lessons established that organizations run on shared schemas (Organizations run on shared schemas) and that these schemas are often implicit (Organizational schemas are often implicit). This lesson addresses the practical question: how do you make them visible?
The challenge is not merely intellectual. Organizational schemas resist surfacing because they are entangled with identity, power, and belonging. Questioning "how we do things" can feel like questioning "who we are." Peter Senge identified this resistance as one of the core challenges of organizational learning. In The Fifth Discipline, Senge argued that the "mental models" discipline — the practice of surfacing and testing the assumptions that shape organizational behavior — is the most difficult of the five disciplines precisely because it requires people to expose their thinking to examination and potential revision (Senge, 1990).
But the difficulty does not make the practice optional. Organizations that cannot surface their schemas cannot adapt to changing environments, cannot resolve persistent strategic disagreements, and cannot close the gap between their stated intentions and their actual behavior. The cost of implicit schemas is not dramatic — it is chronic. It shows up as slow strategic drift, as recurring problems that never quite get solved, as a vague sense that the organization is working hard but not getting where it needs to go.
Five methods for surfacing organizational schemas
Method 1: Independent elicitation
The most reliable way to surface shared schemas is to ask multiple people the same question independently, then compare their answers. The independence is critical — it prevents anchoring to the first answer and ensures that each person's actual schema is captured rather than their performance of agreement.
The technique is simple. Choose a strategic question or contested topic. Frame it as a completion prompt: "I believe that our competitive advantage is..." or "I believe the biggest risk we face is..." or "I believe our customers choose us because..." Ask five to ten people across levels and functions to write their answers independently. Collect and compare.
The comparison reveals three types of information: convergences (schemas the organization shares so deeply that everyone gives similar answers), divergences (schemas that differ across the organization, indicating misalignment), and absences (schemas that nobody mentions, indicating blind spots). Each type is diagnostically valuable. Convergences may be shared wisdom or shared blindness. Divergences may be a source of creative tension or a cause of coordination failure. Absences may indicate topics that the organization has not thought about or topics that are tacitly understood as undiscussable.
Method 2: Artifact analysis
The organization's artifacts — its documents, tools, processes, and physical spaces — embed schemas in material form. Analyzing artifacts for the assumptions they encode reveals schemas that the people in the organization may no longer consciously hold but that the artifacts continue to enforce.
Examine the organization's performance review template. What does it measure? What does it not measure? The review template encodes a schema of what the organization values in its people. If it measures individual contribution but not team facilitation, the embedded schema values individual performance over collective capability. If it measures output quantity but not output quality, the embedded schema values throughput over craft.
Examine the organization's meeting structures. Who is invited? How is time allocated? Who speaks? What gets decided? The meeting structures encode schemas about authority, information flow, and decision-making. Edgar Schein's method of cultural analysis used artifact examination as the starting point for schema surfacing — not because artifacts reveal schemas directly, but because they provide concrete, observable evidence that anchors the more subjective work of schema interpretation (Schein, 2010).
Method 3: Newcomer debriefing
People who recently joined the organization occupy a unique vantage point: they can see the organization's schemas with fresh eyes, before habituation renders them invisible. A structured newcomer debriefing at thirty, sixty, and ninety days captures this fleeting perspective.
The debriefing questions should target schema-level observations: "What surprised you about how this organization works?" "What unwritten rules have you discovered?" "What did you expect based on the hiring process that turned out to be different in practice?" "What do people here assume that people at your previous organization did not?"
Amy Edmondson's research on psychological safety emphasizes that newcomers will only share these observations if the organizational environment makes it safe to do so. A newcomer who reports "I was surprised that nobody challenges the VP's ideas in meetings" is surfacing an authority schema — but only if they feel safe enough to say it. The debriefing must be conducted by someone the newcomer trusts, and the observations must be treated as valuable data rather than complaints (Edmondson, 1999).
Method 4: Pre-mortem and failure analysis
Gary Klein's pre-mortem technique — imagining that a project has failed and working backward to identify the causes — is a powerful schema surfacing tool because it forces people to articulate the assumptions they are relying on. When a team says "This project failed because the market shifted before we launched," they are revealing a time schema (we assumed the market would remain stable during development). When they say "This project failed because the customer did not want what we built," they are revealing a customer knowledge schema (we assumed we understood the customer's needs without validation) (Klein, 2007).
Historical failure analysis works the same way. Examine the organization's past failures — not to assign blame but to identify the schemas that made the failure possible. What did the organization assume that turned out to be wrong? Were those assumptions ever explicitly stated, or were they implicit? If implicit, how can similar assumptions be surfaced before the next initiative rather than after its failure?
Method 5: Schema mapping workshops
A schema mapping workshop brings together a cross-functional group to collaboratively map the organization's operating schemas. The workshop uses a structured format to ensure that schemas are surfaced rather than debated — the goal is to see the landscape, not to argue about which schemas are right.
The format: (1) Each participant independently lists three to five "things everyone here knows" — beliefs that feel so obvious that they are rarely stated. (2) The lists are shared and clustered by theme. (3) For each cluster, the group asks: "Is this an empirical fact we have evidence for, or an assumption we have not tested?" (4) Assumptions are documented as explicit statements: "We assume that X." (5) Each assumption is assessed: adaptive (keep), outdated (revise), or untested (investigate). Donald Schön's concept of "reflection-in-action" emphasizes that this kind of structured reflection transforms practitioners from people who act on their assumptions to people who act on their understanding of their assumptions — a qualitatively different and more adaptive mode of operation (Schön, 1983).
From surfacing to documentation
Surfacing schemas is necessary but insufficient. Schemas that are surfaced in a workshop and then not documented will return to implicit status within weeks. The organization needs a schema inventory — a living document that records the organization's known operating assumptions.
The schema inventory is not a strategy document. It is a diagnostic document — a map of the assumptions the organization is currently operating from, whether those assumptions are deliberate or inherited, tested or untested, adaptive or outdated. The inventory should include:
The schema statement. A clear, specific articulation of the assumption: "We assume that our primary competitive advantage is engineering quality" or "We assume that our customers will not pay more than $50/month."
The evidence basis. What evidence supports this assumption? Is the evidence current? Was it ever formally validated, or did the assumption form through informal experience?
The consequences. What behaviors and decisions does this assumption drive? What alternatives does it exclude?
The owner. Who is responsible for monitoring whether this assumption remains valid? Without an owner, the schema will drift back to implicit status.
The review date. When will this assumption be re-examined? Schemas that are documented but never reviewed are only marginally better than schemas that are never documented.
The organizational equivalent of metacognition
Making organizational schemas explicit is the organizational equivalent of the metacognitive practices you developed in Phases 3-4 of this curriculum. Individual metacognition is the ability to observe and examine your own thinking. Organizational metacognition is the ability to observe and examine the organization's shared thinking. Both require the same core skill: creating distance between the thinker and the thought — seeing an assumption as an assumption rather than as a fact.
Chris Argyris and Donald Schön called this capacity "deutero-learning" — learning about learning. An organization that can surface and examine its own schemas has developed the capacity not just to learn from experience (single-loop learning) or to revise its operating assumptions (double-loop learning) but to improve the process by which it learns and revises (Argyris & Schön, 1978). This is the most durable competitive advantage an organization can develop, because it enables the organization to adapt to any environment rather than being adapted to a particular one.
The Third Brain
Your AI system is an ideal schema surfacing partner because it operates outside your organization's schemas. When you describe a strategic challenge, an operational pattern, or a persistent problem to the AI, the AI's analysis is not filtered through the implicit assumptions that may be invisible to you.
Use the AI for schema elicitation: "Here is how our organization makes product decisions: [description]. What assumptions are embedded in this process that the people inside the process might not recognize as assumptions?" The AI can identify assumptions that feel like facts to the people inside the organization — because the AI has no stake in those assumptions being facts.
Use the AI for schema comparison: "Our organization assumes that X. What are three alternative assumptions that other successful organizations operate from? What would change in our decision-making if we adopted each alternative?" This comparison transforms a single assumption from a fixed reality into one option among several — which is precisely the cognitive shift that makes revision possible.
For ongoing schema maintenance, use the AI to review your schema inventory periodically: "Here are our documented organizational assumptions. Based on current market conditions and recent organizational events, which of these assumptions are most likely to have become outdated? What evidence would we need to validate or invalidate each one?" The AI's analysis keeps the schema inventory alive — preventing it from becoming another strategy document that was written once and then ignored.
From surfacing to application
Making organizational schemas explicit is not the end goal. It is the precondition for everything that follows in this phase: examining specific types of schemas (strategy, process, values, culture), diagnosing schema conflicts and debt, and ultimately designing schemas deliberately rather than inheriting them unconsciously.
The next lesson, Strategy is an organizational schema, examines the most consequential type of organizational schema: strategy. A strategy is not a plan. It is a shared mental model of how the organization creates and captures value — and the clarity or confusion of that model determines whether the organization acts with coherence or with contradiction.
Sources:
- Senge, P. M. (1990). The Fifth Discipline: The Art & Practice of the Learning Organization. Doubleday.
- Schein, E. H. (2010). Organizational Culture and Leadership (4th ed.). Jossey-Bass.
- Edmondson, A. C. (1999). "Psychological Safety and Learning Behavior in Work Teams." Administrative Science Quarterly, 44(2), 350-383.
- Klein, G. (2007). "Performing a Project Premortem." Harvard Business Review, 85(9), 18-19.
- Schön, D. A. (1983). The Reflective Practitioner: How Professionals Think in Action. Basic Books.
- Argyris, C., & Schön, D. A. (1978). Organizational Learning: A Theory of Action Perspective. Addison-Wesley.
Frequently Asked Questions