A message lands in the team channel at 5:47 on a Friday: "Can we find time to talk on Monday?" No agenda, no subject, just that. The person who sent it has already closed their laptop and gone to dinner, untroubled. The person who received it spends the weekend quietly rehearsing every conversation it could possibly be. By Monday morning they have lived through three imaginary versions of it, two of them bad, and done none of the actual resting the weekend was for.
I have sent that message. I have received it. And for a long time I did not understand why something so small could cast such a long shadow.
The difference between a signal and a message
Abraham Zaleznik, writing about the inner life of managers and leaders, noticed that people who are uncomfortable with direct emotional engagement tend to communicate in signals rather than messages. A message says the thing plainly and owns it. A signal gestures at it — indirect, ambiguous, deniable — and quietly hands the receiver the job of decoding what was really meant.
"Can we talk" is a signal. "I'd like fifteen minutes on Monday to go over the API design — nothing to do with your standing on the team" is a message. They cost the sender about the same number of seconds. They cost the receiver a wildly different weekend.
Why we reach for signals
I do not think most people send signals to be cruel. They send them because a signal feels safer. It commits to nothing. It postpones the discomfort of the direct conversation, preserves a little deniability — "I never actually said that" — and lets us avoid, for now, the part with feelings in it. Under the ordinary human instinct to avoid conflict, vagueness can even feel like kindness or caution.
The manager who keeps a budget vague, or a decision half-explained, often believes they are protecting people from worry. More often they are protecting themselves from the hard, direct moment. The softness is real, but it is pointed in the wrong direction.
The cost does not vanish; it transfers
Here is the part that took me too long to see. The emotional labor of a hard conversation does not disappear when you send a signal instead of a message. It just moves. The sender saves themselves the discomfort. The receiver pays it back with interest — in over-interpretation, in rehearsed worst cases, in a weekend spent decoding five words.
Multiply that across a team and you get a low, constant hum underneath the work: people reading tone, parsing who got invited to which meeting, protecting themselves from an ambiguity that, very often, was never meant as a threat at all. None of that energy goes into the product. All of it goes into the fog.
How vagueness quietly breeds politics
A team that cannot reliably get clear messages learns to survive without them. It starts reading signals everywhere — the phrasing of a reorg note, who replied and who went silent, which name was first on the invite. Information becomes something to hoard and interpret rather than something to share. This is how a manager earns a reputation as detached, inscrutable, even manipulative, when the real story may simply be a person who kept avoiding direct conversations.
It is worth saying plainly: the politics are usually not a character flaw in the team. They are the team adapting, sensibly, to a vacuum of clear messages. Fill the vacuum and a surprising amount of the maneuvering quietly relaxes.
A clear message is a kindness, even when it is hard
Clarity is not coldness. Think of the difference between a doctor who says only "we should run some tests" and walks out, and one who says "this looks like a sprain, not a break — here is what we will do, and here is the one thing that would worry me." The first is technically careful and lands as dread. The second carries harder, more specific information and lands as relief — because it hands you something solid to hold instead of a fog to fill with your own worst guesses.
The kindest version of difficult news at work is the same: a clear message that names the thing, owns the feeling behind it, and leaves little to decode. "This part isn't working, here is specifically why, and here is what I'd like us to try" is harder to say than "we should chat sometime" — and far gentler to receive. This is the quiet inversion at the center of it. Vagueness feels gentle to send and lands as anxiety. Directness feels hard to send and lands, more often than we expect, as respect. People can carry almost any clear truth; what wears them down is the fog around it.
The real test is communication under tension
Anyone can send clear messages when things are calm. The test is the hard moment: bad news, a disagreement, a disappointment, an emotion sitting in the room. That is precisely when we retreat into signals — the vague reschedule, the "let's take this offline," the feedback softened until it carries no actual information.
Staying direct and humane right there, when every instinct says to gesture and hedge, is most of what separates a leader's communication from a manager's. The goal is not bluntness; blunt is just a different way of making it about you. The goal is a message that is both clear and kind, delivered at the exact moment clarity is most expensive to give.
The most generous thing you can hand a team living with uncertainty is a clear message — especially when the message is hard. A signal spares you a difficult minute and quietly costs someone else a difficult weekend. When did a vague message once send you spiraling — or when did someone's willingness to just say the thing, plainly and kindly, land on you as pure relief? I would like to hear it.