When two people map the same situation differently, the divergence reveals uncaptured complexity
When two schemas of the same situation diverge between people, treat the divergence itself as information about complexity the territory contains that neither schema fully captured.
Why This Is a Rule
When two people describe the same situation differently, the default interpretation is "one of us is wrong." But Korzybski's "map is not the territory" principle suggests a better interpretation: both maps are incomplete, and the divergence between them reveals complexity in the territory that neither captured alone.
Person A's schema emphasizes technical risks. Person B's schema emphasizes organizational dynamics. The divergence doesn't mean one is wrong — it means the situation contains both technical and organizational complexity, and each person's schema captured a different facet. The most accurate model of the situation requires integrating both schemas, not choosing between them.
This reframe is powerful because it converts disagreement from a problem (who's right?) into information (what complexity are we collectively revealing?). The areas where schemas agree are well-understood territory. The areas where they diverge are the exact locations where the situation is more complex than either person realized.
When This Fires
- Two colleagues describe the same project, meeting, or situation differently
- Your perspective and someone else's seem irreconcilable despite shared facts
- A team debrief reveals fundamentally different accounts of what happened
- Internal parts of your own thinking produce conflicting schemas of the same situation
Common Failure Mode
Debating whose schema is correct rather than investigating the divergence as data. "You think it's a leadership problem, I think it's a resource problem — let's argue about which it is." The more productive move: "Our schemas diverge at this point. What aspect of the situation is producing this divergence? Is it possible that leadership AND resources are both factors, and our schemas each captured one?"
The Protocol
When schemas diverge: (1) Resist the urge to determine who's right. (2) Map both schemas explicitly — what does each person's model include? (3) Identify the divergence points: where do the schemas tell different stories? (4) For each divergence point, ask: "What complexity in the situation could explain why two reasonable people would see this differently?" (5) Build a richer model that integrates both schemas' insights. The integrated model is almost always more accurate than either individual schema.