Core Primitive
New members absorb organizational schemas through onboarding, socialization, and observation — but the propagation process is largely undesigned. What new members learn is determined more by who they sit near, who mentors them, and what they observe in their first weeks than by any formal onboarding program. Organizations that design their schema propagation deliberately can shape which schemas new members acquire and which they question.
How organizations reproduce their thinking
Every organization faces a fundamental challenge: how to transmit its accumulated knowledge, practices, and mental models to new members. The technical dimension of this challenge — teaching new members the tools, systems, and procedures they need to do their work — is well-understood and typically well-managed through structured onboarding programs. The schema dimension — transmitting the shared mental models that determine how the organization actually operates — is far more consequential and far less deliberately managed.
John Van Maanen and Edgar Schein identified six dimensions along which organizational socialization varies: collective versus individual (are newcomers socialized in groups or one at a time?), formal versus informal (is the process structured or unstructured?), sequential versus random (are there defined stages or is the order ad hoc?), fixed versus variable (is the timeline predictable or uncertain?), serial versus disjunctive (do experienced members guide newcomers or are newcomers left to figure things out?), and investiture versus divestiture (does the organization affirm newcomers' identities or require them to adopt new ones?). These dimensions determine not just what newcomers learn but how they learn it — and therefore which schemas are propagated accurately, which are distorted, and which are lost (Van Maanen & Schein, 1979).
The channels of schema propagation
Schemas propagate through organizations via multiple channels, each with different characteristics.
Formal onboarding. Structured orientation programs, training sessions, and documentation transmit the organization's explicit schemas: stated values, official processes, role expectations, and tool usage. Formal onboarding is efficient for explicit knowledge but largely ineffective for implicit schemas, because implicit schemas by definition cannot be articulated in training materials. The gap between what formal onboarding teaches and what new members actually need to know is a measure of the organization's reliance on implicit schemas.
Mentoring and coaching. When an experienced member mentors a newcomer, they transmit not just technical knowledge but operational schemas: how decisions really get made, who has influence, what behaviors are actually rewarded, how to navigate the gap between stated and operating values. The quality of schema propagation through mentoring depends entirely on the mentor's own schemas — if the mentor holds well-calibrated schemas, the newcomer acquires well-calibrated schemas. If the mentor holds outdated or idiosyncratic schemas, the newcomer acquires those instead. This is why mentor selection matters: the organization is effectively choosing which schemas to replicate.
Observation and social learning. Albert Bandura's social learning theory demonstrated that people learn behaviors by observing others, particularly others who are successful and high-status. In organizations, new members observe how established members behave — who speaks in meetings, how leaders respond to bad news, what gets celebrated and what gets punished — and infer the operating schemas from these observations. Observational learning is the primary channel for implicit schema propagation, and it operates independently of (and sometimes in contradiction to) formal onboarding. When the onboarding says "We value candor" but the new member observes that people who deliver bad news get sidelined, the observation wins (Bandura, 1977).
Peer socialization. When new members join in cohorts — as in large hiring waves or structured programs — they develop shared schemas through peer interaction. The peer group creates a shared interpretation of organizational experiences: "Did you notice that the VP never asks follow-up questions?" "Is it normal that we never test in staging first?" Peer socialization can either reinforce or challenge organizational schemas, depending on whether the peer group's interpretations align with or diverge from the organization's intended schemas.
Artifact interaction. The organization's tools, documents, processes, and physical spaces propagate schemas passively. A codebase full of comments like "HACK: this is temporary" and dates from three years ago propagates a schema of accepted technical debt. A meeting-heavy calendar propagates a schema of decision-making through synchronous discussion. A Slack culture with rapid response expectations propagates a schema of always-on availability. These artifact-transmitted schemas are rarely designed deliberately — they accumulate as byproducts of organizational history.
Schema fidelity and drift
Schema propagation is never perfectly faithful. Like a game of telephone, each transmission introduces small distortions. Over multiple generations of propagation — from founders to early employees to mid-tenure employees to recent hires — schemas can drift significantly from their original form.
Simplification. Complex schemas get simplified during propagation. The founder's nuanced schema — "We prioritize speed, but only when we have adequate monitoring and rollback capability" — becomes "We move fast" in the version passed from manager to new hire. The nuance that made the schema safe is lost, and what remains is a simplified version that encourages speed without the safeguards.
Localization. Schemas get adapted to local contexts during propagation. The organization's global schema of "customer-centric" gets interpreted differently in the sales team ("close deals customers want"), the support team ("resolve customer issues"), and the engineering team ("build reliable systems"). Each localization is a reasonable adaptation, but the localized schemas may diverge to the point where "customer-centric" means something fundamentally different in different parts of the organization.
Selective transmission. Mentors and peers transmit the schemas they consider important and omit the ones they consider obvious or unimportant. An engineer mentoring a new engineer might thoroughly transmit the technical quality schema but fail to transmit the customer empathy schema — not because they reject customer empathy but because they consider it someone else's responsibility to teach. The result is new members who hold partial schemas: well-calibrated in some dimensions and uncalibrated in others.
Mutation through experience. New members modify the schemas they receive based on their own experiences in the organization. If a new member follows the "speak up in meetings" schema and gets shut down by a senior leader, they modify the schema: "speak up in meetings, but not when [senior leader] is present." The modified schema is more accurate for their specific situation but diverges from the intended organizational schema. Over many such mutations, the organization's schema landscape becomes increasingly heterogeneous.
Designing schema propagation
Organizations that rely on accidental schema propagation get accidental results. Organizations that design their schema propagation can influence which schemas new members acquire and with what fidelity.
Explicit schema documentation. Write down the organization's most important operating schemas — not just as values or policies but as specific mental models with examples. "We believe that system owners make deployment decisions. This means: if you own a service, you decide when and how to deploy changes, and you are accountable for the outcome." Documentation does not replace informal learning, but it provides a reference point that new members can use to calibrate the informal schemas they absorb.
Structured exposure. Design the new member's first weeks to expose them to the schemas you want them to acquire. If the ownership schema is important, ensure new members observe owners making deployment decisions in their first week. If the customer empathy schema is important, have new members spend time with customers before they write their first line of code. The early experiences create the interpretive framework through which subsequent experiences are understood.
Mentor calibration. Select and prepare mentors explicitly for schema propagation, not just technical guidance. Help mentors articulate their own schemas ("What do you believe about how decisions should be made here?") and identify which schemas are organizational versus personal. A mentor who can distinguish between "the organization believes X" and "I personally believe X" provides more useful guidance than one who transmits their individual schemas as organizational truths.
Schema check-ins. At thirty, sixty, and ninety days, ask new members to articulate the schemas they have acquired: "What do you believe is most important here? How do decisions get made? What gets rewarded? What gets punished?" Compare their articulated schemas with the intended schemas. Divergences reveal propagation failures that can be corrected while the new member's schemas are still forming.
The Third Brain
Your AI system can help design and monitor schema propagation. Before a new hire starts, describe the key schemas you want them to acquire and ask: "Design a first-week experience that would naturally expose the new member to these schemas through observation, interaction, and guided practice. What should they see, who should they talk to, and what experiences should they have?"
The AI can also serve as a schema calibration partner for new members. Have new members describe their understanding of how the organization works to the AI, and ask the AI to compare their description against the organization's documented schemas: "This new member believes [X, Y, Z]. Here are the organization's intended schemas: [A, B, C]. Where are the largest gaps, and what experiences might close them?"
For ongoing propagation monitoring, use the AI to analyze schema consistency across cohorts: "Here are the schemas articulated by employees who joined in Q1 versus Q2 versus Q3. Are the schemas consistent, or are they drifting? If drifting, what is the direction and likely cause?" This analysis reveals whether the organization's schema propagation is maintaining fidelity or degrading over time.
From propagation to evolution
Schema propagation addresses how existing schemas are transmitted to new members. But organizational schemas must also evolve — changing in response to new environments, new information, and new challenges. The organization that propagates its existing schemas perfectly but never updates them is an organization that is perfectly adapted to the past.
The next lesson, Schema evolution in organizations, examines how organizational schemas evolve — the mechanisms through which organizations update their shared mental models, the barriers to schema evolution, and the practices that enable deliberate schema change.
Sources:
- Van Maanen, J., & Schein, E. H. (1979). "Toward a Theory of Organizational Socialization." Research in Organizational Behavior, 1, 209-264.
- Bandura, A. (1977). Social Learning Theory. Prentice-Hall.
Frequently Asked Questions