Externalize your reading of someone's reasoning and verify before debating — schemas may diverge invisibly
Before assuming you understand someone's reasoning, externalize your reading of their underlying schema and verify it directly rather than debating conclusions that may stem from invisible schema divergence.
Why This Is a Rule
Most debates are about conclusions while the real disagreement lives in underlying schemas. Two people debating whether to use microservices are actually disagreeing about their mental models of what a "good architecture" is — one prioritizes operational simplicity, the other prioritizes team autonomy. Debating the conclusion (microservices yes/no) without surfacing the schema divergence produces circular arguments where both sides present valid reasoning from different foundations.
Externalizing your reading of the other person's schema — "It seems like you're reasoning from a model where team autonomy is the primary architectural constraint" — and verifying it directly surfaces the actual divergence. If the reading is correct, you've identified where to focus the discussion (the schema, not the conclusion). If incorrect, the correction itself reveals the actual schema, which advances understanding more than another round of conclusion-level debate.
This is the interpersonal application of When disagreement persists despite shared facts, draw both mental models side by side (spatial externalization of mental models): before debating conclusions, make both underlying models visible.
When This Fires
- When a disagreement feels circular — the same arguments keep surfacing without resolution
- Before responding to a conclusion you disagree with
- During any collaborative decision where multiple valid frameworks could produce different answers
- When someone's reasoning seems "obviously wrong" (usually means invisibly different schema)
Common Failure Mode
Debating conclusions directly: "Microservices are wrong for this project" → "No, they're right because..." Each person argues from their schema without making it explicit. The debate generates heat but no resolution because the schemas were never compared.
The Protocol
Before debating a conclusion you disagree with: (1) Articulate your reading of their underlying model: "It sounds like you're working from a framework where [your interpretation of their schema]." (2) Ask them to verify: "Is that accurate, or am I misreading your reasoning?" (3) If accurate → now you can address the schema divergence directly: "I see — my framework prioritizes [X] where yours prioritizes [Y]. Should we discuss which priority serves this context better?" (4) If inaccurate → their correction reveals the actual schema, which advances understanding immediately.