Why do people say I did not answer the question?

Usually because you answered a nearby one. Someone asks "when will it be ready" and you explain what is blocking it — genuinely relevant, and not the date they asked for. From the inside it feels like answering; from the outside it reads as avoidance, especially when the real answer is bad news.

What if I do not know the answer?

Say that, then say when you will know. "I do not have that number — I will have it by Thursday" costs you nothing. Filling the gap with adjacent detail is what damages trust, because the listener can tell the question was heard and stepped around.

How can I tell whether I do this?

It is hard to hear in yourself, because in the moment you were being responsive. A transcript makes it visible: the questions put to you, paired with what you actually said next, so you can judge the two side by side rather than from memory.

How to answer the question you were actually asked

This is the single most useful finding in most reports, and it almost never happens through evasion. It happens because the question touched something you know a great deal about, and you answered the interesting question instead of the asked one.

In your report: Did you answer the question · questions put to you, paired with what you said

The adjacent answer

They ask what it costs. You explain how it works. Both are about the same system, and only one was the question. The listener now has to ask again, or give up and guess.

What does the migration cost us in downtime? — Well, the way the replication works is that we copy in the background and then verify, and the verification is the part that…

About four hours. The copy runs in the background, so the only downtime is the cutover.

The question behind the question

When a client asks “is this risky”, they are usually asking “should I be worried, and are you on top of it”. Answering only the literal question leaves the real one hanging.

Say the uncomfortable number

The most common reason an answer arrives late is that the speaker does not like it. Delaying it does not make it smaller, it just makes the listener wonder what else is being managed.

There might be some impact, it depends on a few things, we would need to look at it closely.

Worst case, four hours down on a Sunday. Here’s how we keep it to one.

Check yourself at the end of a turn

One habit fixes most of this: before you stop talking, repeat the question to yourself. If your answer does not contain a direct response to it, add one sentence that does.

Your report pairs every question put to you with what you actually said, and tells you whether the answer landed, arrived late, or never arrived.

Common questions

Why do people say I did not answer the question?: Usually because you answered a nearby one. Someone asks "when will it be ready" and you explain what is blocking it — genuinely relevant, and not the date they asked for. From the inside it feels like answering; from the outside it reads as avoidance, especially when the real answer is bad news.
What if I do not know the answer?: Say that, then say when you will know. "I do not have that number — I will have it by Thursday" costs you nothing. Filling the gap with adjacent detail is what damages trust, because the listener can tell the question was heard and stepped around.
How can I tell whether I do this?: It is hard to hear in yourself, because in the moment you were being responsive. A transcript makes it visible: the questions put to you, paired with what you actually said next, so you can judge the two side by side rather than from memory.

See which of these is yours

Paste a transcript from a real meeting and find out, rather than guessing.

Check a real meeting

No account, and nothing is stored.