Asking for the Decision
Judgment cannot be assessed by asking someone about a system. It can be assessed by asking for one hard call they personally made on something that mattered, and then asking again. The tells are consistent. People who did the work get quieter and reach for examples that are specific and slightly embarrassing. People who stood next to the work stay smooth, and their examples drift toward the system's behavior instead of their own.
Framework 5 of 10 · Chapter 5: Context Is the Edge
Interviews and reviews are mostly built to test whether someone can describe a system. That test has stopped discriminating, because describing a system accurately is now widely available.
What still discriminates is a decision. Not the architecture they would choose in the abstract, but one call they actually made, on something real, where the answer was not obvious and they had to live with it.
The signal is in how the answer arrives more than in what it contains.
When it applies
Hiring loops. Promotion evidence. One-on-ones where you are trying to work out whether someone is ready for more scope. And on yourself, which is the hardest version and the most useful.
How to run it
- Ask for one specific call, not a class of calls. "Walk me through a decision you made that you were unsure about" beats any question about how they would approach something.
- Ask again. Once is not a sample. The same question from a different angle is where the difference shows.
- Listen for the direction the answer travels. Toward their own reasoning, or toward the system's behavior.
- Notice volume and speed. Depth tends to arrive slower and quieter than fluency does.
The specific, slightly embarrassing example is the strongest signal available in a conversation. People do not invent those.
Where it fails
You are tired. You can be tired enough to mistake your own clarity for someone else's failure, and not know which one you have done. This is the main way the tool misfires, and it misfires in the direction of a wrong no.
You conclude from one instance. A single smooth answer means someone was smooth. Noticing is the skill. Drawing conclusions is the part that takes years.
You use it as a trap. Asked adversarially, it produces defensive answers from strong candidates and tells you nothing.
Practice
This week, in a loop or a one-on-one, notice the moment where the answer you are hearing is about the system rather than the person. Do not draw a conclusion from it. Just notice that it happened, and how you felt about it.