Externalize your reading of someone's reasoning and verify…
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.
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.