Convert judgments into genuine questions — ask about…
When a judgment forms during an interaction, immediately convert it into a genuine question by replacing the evaluative conclusion with an inquiry about constraints, context, or reasoning ('Why would anyone write it this way?' becomes 'What constraints or context led to this approach?'), because questions activate exploratory cognition while conclusions activate confirmatory cognition.
When This Fires
- During code reviews when your first reaction is "this is wrong/bad/messy"
- In meetings when someone proposes something you instantly disagree with
- When reading documentation or architecture decisions that seem misguided
- Any interaction where a snap judgment forms before you've understood the full context
Common Failure Mode
Converting the judgment into a rhetorical question rather than a genuine one. "Don't you think there's a better way to do this?" is a judgment wearing a question's clothing. A genuine question has an uncertain answer — you actually don't know what the constraints were. If you already know the answer you expect, it's not a real question. The test: would you be surprised by the answer? If not, rephrase until the question is genuinely open.
The Protocol
When a judgment forms during an interaction: (1) Catch the evaluative conclusion (e.g., "this code is over-engineered"). (2) Convert it: "What constraints or reasoning led to this level of abstraction?" (3) Ask it — out loud if in conversation, internally if reviewing asynchronously. (4) Listen to the answer as if it might change your mind. Often it will: the "over-engineering" was a response to a production incident you didn't know about, or a scalability requirement that wasn't documented.