What does it mean that healthy organizational schemas produce healthy organizational behavior?

Get the shared mental models right and behavior follows naturally. Organizations do not need to control behavior through rules, surveillance, or micromanagement when the shared schemas — the collective mental models of what matters, how the world works, and what good looks like — are accurate, current, and well-aligned. Healthy schemas produce healthy behavior as an emergent property, just as healthy individual cognition produces wise action without deliberate effort for each decision.

Example: Two hospital systems of similar size and resources produced dramatically different patient safety outcomes over a five-year period. System A invested in behavioral controls: mandatory checklists, compliance monitoring, incident reporting requirements, and disciplinary procedures for safety violations. System B invested in schema design: shared mental models of what causes errors (systemic factors, not individual carelessness), what safety means (proactive identification of risks, not reactive punishment of mistakes), and how the organization learns (from near-misses and errors, not just from successes). System A's approach produced compliance without understanding — staff followed checklists mechanically but did not internalize the reasoning behind them. When the checklist did not cover a situation, staff defaulted to habit. Incident reporting was low because reporting was associated with punishment. System B's approach produced understanding that generated appropriate behavior — staff who understood that errors are systemic actively identified risks in their own workflows, reported near-misses as learning opportunities, and adapted their behavior to novel situations because they understood the principles behind the protocols. After five years, System B's patient safety record was 40% better than System A's — not because it had more rules but because it had better schemas. The schemas produced the behavior that the rules were trying to mandate.

Try this: Choose one organizational behavior you want to improve — meeting quality, decision speed, customer responsiveness, code quality, or any persistent behavioral challenge. Instead of creating a new rule or process to mandate the desired behavior, identify the schema that would produce the behavior naturally. What mental model, if shared across the organization, would make the desired behavior the obvious default? Write the schema as a clear statement: 'We believe that [X], which means we naturally [desired behavior].' Then assess: Is this schema currently shared? If not, what would it take to propagate it — through leadership modeling, system encoding, and consistent reinforcement? The schema approach produces more durable behavior change than the rule approach because it changes the reasoning behind behavior, not just the behavior itself.