Silence is not nothing. It is data. Most people treat it as an absence of information and either panic or ignore it. Both are mistakes. The absence of a reply tells you something specific, if you know how to read it.
Four ways to read it
The person is busy. The most common explanation and the most boring one. Someone is heads down, traveling, or buried under something more urgent than replying to you. This kind of gap usually clears on its own within a normal window and has no charge behind it. The tell is that when they do come back, the reply is short but complete. They answer the actual question instead of apologizing around it.
The person doesn't know what to say. This one is trickier. There is something to report and no good way to say it: bad news, an unresolved situation, or a decision they have not actually made yet. The gap here is a stall, not a choice to withhold. The tell is usually a pattern, not a single missed message: reliable communication that suddenly narrows around one specific topic while everything else keeps moving normally.
The person doesn't have anything to say. Sometimes there is genuinely no update. Nothing has changed, nothing has moved, and saying so out loud feels like admitting to inaction even when inaction was the right call that week. People under-communicate here because reporting nothing feels riskier than saying nothing. It is usually the opposite. The tell is that when you press, the actual content is thin, not evasive. Just short, because there is not much there yet.
The person is checked out. The one everyone worries about first, and the one that is actually correct least often. Someone has genuinely disengaged: lost interest, lost belief in the plan, or is already halfway to a different decision they have not announced. This is the rarest of the four and the most assumed, mostly because it is the loudest possible story and the easiest one to build a narrative around under pressure. The tell is that the gap does not close even after the obvious blockers get removed: the trip ends, the hard conversation happens, the workload clears, and the silence stays anyway.
Match the signal to the person
None of that works without knowing the person's baseline first. Some people talk a lot. They narrate their own process out loud, send updates whether or not anything actually happened, and default to overcommunicating even when there is nothing to report. For that person, a sudden drop into silence is a real signal. Something changed, and it is worth asking about directly.
Some people are economical with their words. They report what matters and skip the narration in between. For that person, a gap is closer to their default state, and a normal pause does not mean anything at all. Read their silence the way you would read a talker's silence and you will trigger a false alarm almost every time, over nothing.
I tend to be economical. If I go quiet for a stretch, it is far more likely I am heads down on the actual problem than that something has gone wrong. I do not send progress updates for the sake of sending them, and I do not perform activity just to reassure someone that work is happening. That is a real mismatch with people who expect frequent touch points as proof of progress, and it is worth saying plainly instead of leaving someone to guess which of the four categories they are actually looking at.
Get the category wrong and it costs you
Treating silence as one thing is the actual mistake, more than any individual misread. It is four different situations that can look identical from the outside and require four different responses: wait it out, ask directly, ask for the real update instead of assuming there is not one, or step in before it goes further. Get the category wrong in one direction and you escalate over nothing, damaging a relationship that did not need saving. Get it wrong in the other direction and you miss something real for months, right up until it becomes a problem too big to fix without everyone noticing.
Knowing the person's baseline is what turns this from a guess into an actual read. I have sat on both sides of it, the founder going quiet and the person trying to figure out why. One of those situations is on the record here, if you want to see the difference between reacting to silence and actually reading it.