Watch the moment someone brings you a problem. Not the conversation — the half second before it starts.
There is often a small adjustment. A breath, a rephrasing, a decision about how to open. It is brief enough that most leaders have stopped registering it, and it is the most reliable feedback available to you, because it is involuntary.
The pause means someone has calculated the cost of telling you.
What it is not
It is not necessarily fear, and this is where leaders go wrong when they notice it.
The instinctive read is that people are frightened, which leads to the standard response: be warmer, say the door is always open, insist that you want to hear bad news. That rarely changes anything, because in most cases fear was not the mechanism.
The more common causes are duller.
They expect to be solved at. You will take the problem and start fixing it within ninety seconds, and what they actually needed was two minutes to explain the whole thing. So they brace for the interruption and pre-compress the story, which means you get a worse version of the facts.
They expect the temperature to rise. Not anger — intensity. You go up a level when something is wrong, and although it passes quickly for you, they have to be in it. So they choose their moment, which means delay.
They expect it to become theirs again. You will hand it back with additional expectations attached. Bringing you a problem reliably produces more work than not bringing it, and people are rational.
They cannot predict which version of you is available. This is the expensive one. If your response depends on the day, everyone runs a probability calculation before they speak, and the calculation costs time and accuracy.
Why it matters more than it seems
Every one of these produces the same result: you get information later and in worse shape than you would otherwise.
That is a strategic problem, not a cultural one. Most large failures inside a company were visible to somebody early. The gap between somebody knowing and you knowing is where the cost accumulates, and the length of that gap is set almost entirely by what happens in the half second before someone speaks.
You cannot fix this with an open-door policy. The door was never the constraint.
The uncomfortable part
Whatever the cause is, it is almost certainly the shadow of something you are good at.
Speed of response — the thing that makes you effective — is what produces the solving-at. Intensity is often the same trait that makes you compelling in a pitch. The habit of handing things back with expectations attached is usually attached to genuinely high standards.
So the useful question is not what is wrong with you. It is: which of your strengths is being paid for here, and by whom?
That reframe matters, because it stops the pointless attempt to become a milder person and starts a more precise conversation about where the cost is landing.
Where the general answer stops
The four causes above want different responses, and applying the wrong one makes things worse. Being warmer when the real cause is solving-at just adds a friendly delay before the same interruption.
To pick correctly you need to know which of your strengths runs hot under pressure — which is a question about your defaults, not about your team. It shows up in more places than this one, and once you can name it, the pause is usually the easiest of its symptoms to fix.
Ask three people, separately, what it is like to bring you something difficult. Ask for one specific example rather than a general impression. The specificity is what gets you past the polite answer.
Then compare what they say with what you already suspected about yourself. The overlap is where the work is.