"You Should Have Asked More Questions"

This was said after information failed to arrive in time and a project went badly wrong. The person holding the information meant it sincerely: they had explained as much as was needed, and if that wasn't enough, the other side should have asked. They believed they had done nothing wrong, and there was nothing dishonest in that belief.

The sentence carries a hidden premise. It assumes the other side knew what to ask about.

But if they had known that, they wouldn't have needed to ask.

You cannot notice an absence

Sharing information proactively is cheaper than making the other side extract it through questions. Most people agree with that much. Where they usually go wrong is in how they picture the gap — as a difference in effort. Five minutes to write it down versus thirty minutes of digging.

The real gap is far larger than that.

A question requires three things before it can even exist. You have to know that the information exists. You have to know who holds it. And you have to phrase it in a way that actually pulls the answer out. Miss any one of the three and no question gets asked. The one people miss most often is the first. They don't know what they don't know.

Something is only visibly missing if you know what belongs in that place. Without that, an empty space doesn't look empty. It looks like nothing at all. An absence doesn't register.

So questions aren't an expensive channel. They're a channel with dead zones built into it. The comparison isn't five minutes against thirty — it's five minutes against infinity. And in practice, the information that causes real damage lives almost entirely in that infinite range, because the things that could have been asked usually already were.

No signal ever reaches the person who knows

Then why doesn't the person holding the information realize their explanation fell short?

Two things compound.

First, once you know something you cannot return to not knowing it. Any judgment of "that's enough" is made against an imagined listener, and that listener already shares most of what you know. The ruler you measure sufficiency with is bent from the start. You measured carefully. You read the marking correctly. The ruler was wrong.

Second, nothing comes back to tell you the ruler was bent. When no questions arrive, that reads as comprehension. But silence means two different things at once: I understood, and I didn't know there was anything to ask. From the knowing side these are indistinguishable — and when a person can't distinguish two readings, they tend to settle naturally on the one that favors them.

So the loop closes. The unknowing side has no clue that would prompt a question. The knowing side has no signal that would correct them. Both parties behave reasonably from where they stand, and the information never moves.

It's a failure with no villain in it. Which is exactly why it happens so often, and repeats for so long.

What comes next

When information arrives late, it arrives after the point of return. Decisions have been made. Work has been done. From there only two things remain: settling the cost, and assigning the blame.

And that is precisely where the sentence appears. You should have asked more questions.

Organizational conflict isn't an unlucky byproduct of delayed information. It's the scheduled next step. Someone has to absorb the loss the gap created, and once the loss exists, arguing over its distribution is the only procedure left. That argument fixes nothing. Next time the information will fail to arrive for exactly the same reason.

What the other kind of organization did differently

I've also worked where information flowed well. Not because the people there were kinder or more diligent. The shape of what they handed over was different.

The organization that worked badly wasn't silent, either. It just communicated conclusions. Here's what we decided. One layer — the topmost one — handed over on its own.

The organization that worked well passed the layers along with it. What the background was. What the intent was. What that made the goal. And what deliverable was chosen to serve that goal. Background through deliverable, shared as a single structure with its levels intact.

This is decisive, and not because it's generous.

When the layers come with it, the receiving side can detect an absence. If you know the background and the intent, you can see when a conclusion doesn't follow from them. Some point stops adding up — how did that goal produce this deliverable? — and that friction is the clue a question needs. Receive only the conclusion and there is no standard left to check it against. You can accept it, and that's all. What's missing stays missing.

Sharing the layers isn't about handing over more information. It's about handing over a coordinate system in which absence becomes visible. It is, in practice, the only way to make an unnoticeable thing noticeable.

Which is why this problem can't be solved by telling people to ask more questions. Telling someone who doesn't know what to ask to ask more is the same as asking nothing of them. The only fix is structural: move from information that flows on request to information that flows by default.

The responsibility sits with whoever can see

Only the knowing side can perceive that a gap exists. The unknowing side cannot see the gap at all, and you cannot hold someone responsible for something they have no way of seeing.

So the obligation to close it falls on the side that can see it. This is a matter of position, not of diligence or attitude. However sincere the explainer was — and they may well have been entirely sincere — that sincerity doesn't relocate the responsibility.

Having no ill intent and having no responsibility are two different axes.

Speaking first costs five minutes. What it costs not to speak, nobody can know in advance.