The answer was one sentence long.

Somebody asked an engineer in a review why he had chosen Postgres. He knew the answer instantly. It was one sentence: the workload is relational and they were already running it elsewhere.

What he actually said took four minutes. It covered two alternatives he had rejected, an argument about a scaling scenario nobody had raised, a caveat about a benchmark, and a short apology for the length. All of it accurate.

The person who asked had wanted the one sentence. What they got instead was four minutes of evidence that the decision might not be solid, because nobody defends an obvious call that hard.

What the length is saying

People read the amount of justification as a signal about how much justification is needed. That is a rough heuristic and mostly a fair one, and it means quantity carries meaning independently of content.

So a long defence of a simple point does not communicate rigour. It communicates that the point is contested, and the listener updates accordingly, usually without noticing they have done it.

Nobody defends an uncontroversial decision for four minutes. So the room concludes it must be controversial.

Where it comes from

Over-explaining is pre-emptive defence. You are answering objections that have not been made, in advance, because somewhere along the line it was not safe to just be believed.

That somewhere is often early. Children who had to build a case for ordinary requests learn to arrive with the full argument prepared. But it also gets installed in adults quickly, by one manager who queried everything, or a job where being wrong once was expensive.

It never feels like defensiveness from the inside. It feels like being thorough, or considerate, or making sure they have the full picture. That is why pointing it out to somebody rarely helps: you are describing a behaviour, and they are experiencing a virtue.

The shape it takes

• The pre-emptive caveat. Listing the weaknesses in your own position before anyone has looked at it.
• The full audit trail. Explaining the process that produced the answer, when the answer was what was requested.
• The unasked alternative. "I did consider X, but." Nobody asked about X.
• The apology for length, delivered at length, which extends the thing being apologised for.

The actual difficulty

Being brief is easy. Staying quiet afterwards is not.

You give the one sentence answer and then there are two seconds of nothing, and those two seconds feel like the room deciding you are underprepared. So you fill them, and the filling is the whole habit reasserting itself in a smaller space.

The two seconds are not judgement. They are a person taking in what you said. Sit through them a dozen times and they stop registering, which is roughly how long it takes.

Not always wrong

Sometimes the long version is correct. A genuinely contested decision, a room that will need to defend it later, a person who has actually asked for your reasoning. Context is a real thing to provide.

The test is whether you chose it. Length that responds to the situation is judgement. Length that arrives identically whether you are talking to your manager, your team or your partner about where to eat is a reflex, and reflexes are worth knowing about because you did not pick them.

The engineer looked at a transcript of a different meeting and found his average turn ran a little over ninety seconds while everybody else sat around twenty five. He had genuinely believed he was one of the quieter people in that room.