I can run an interview, so why don't the answers tell me anything?

You know how to run the room. You ask the questions, you fill the hour, you take notes. That was never the hard part. The hard part is this: you have no fixed idea of what you are listening for. So every answer sounds reasonable, because you have not decided in advance what an unreasonable one would sound like. You are not evaluating. You are transcribing. This is fixable, and it is fixable before you ever sit down with a candidate. The work is not in the room. It is in the ten minutes before it, deciding what you actually need to know and what evidence would prove or disprove it.

◆ How this problem reads on the two dials

GuidanceKnowledge

Coaching

More to learn

1:1 with AureliusWith others (a Pod)

Mostly you & the coach

A little with peers

The person already has the interviewing mechanics; what they lack is a framework for turning answers into judgment, which is primarily a teachable skill with light coaching to apply it to their actual next interview.

How the two dials adapt to you →

What’s really going on

You are collecting words, not judging them. Before the interview, decide the three things you must learn about this person, and what a true answer to each would sound like. Then listen only for that. An answer means nothing until you have already decided what it would mean if it were true.

🔒 What you’ll build togetherUnlock by starting

A moveBefore the interview, write down the three specific claims this role requires the person to prove true about themselves. Not traits — claims, like 'can make a decision with incomplete information.'

A moveFor each claim, write the answer a person who is faking it would give. It will sound almost identical to the true answer. Know the difference before you hear either.

A moveIn the interview, when you hear a claim, ask for the one detail a person who did not actually do the thing could not invent. A name, a number, a decision they'd reverse.

A moveAfter each answer, silently answer one question: 'What did this prove, and what did it fail to prove?' If you cannot answer that, you have not yet heard the answer — you have only heard the sound of it.

A moveRight after the interview, before you talk to anyone else, write your judgment on each of the three claims: proven, disproven, or unknown. Do this before your memory softens the edges.

What changes unlock by starting

You walk into interviews with three specific things to test, not a vague sense of 'good fit.'
You catch yourself nodding along to a plausible-sounding non-answer, and stop it.
You can explain, in one sentence per claim, why you believe or doubt it — not just a feeling.
Your notes after an interview become decisions, not descriptions.

One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.