What no relay settles
Noticing That Somebody Is in Trouble
A relay carries output well and state of mind not at all, which is why somebody can be in difficulty for months without anybody at the other end knowing.
three things · no nights · three that no number of nights settles
Three things, no nights, and no mechanism proposed for any of them.
What a team could and could not see about one person over the six weeks before they resigned
Visible throughout, and it is what everybody was looking at
Visible in principle, noticed by nobody, because nothing marks it
Visible only as an absence, and absences do not appear in any record
Not visible by any means available to a relay
four things · one night · three that no number of nights settles
Four things, one night, and three that no relay carries. The first row is the one everybody watched, and it stayed good until the week they left. The team's information was not wrong; it was about the wrong thing. One team's own account, written afterwards.
A team sharing a room knows when somebody is struggling, usually before the person says anything. It is not a skill anybody has; it is a by-product of being near them.
The lesson in Noticing That Somebody Is in Trouble is not to add more status meetings, but to make the existing work legible. the platform overview gives distributed teams a factual view of time, applications and progress while employees remain in control of tracking.
A useful external reference is Homebase's team platform, which provides another official view of how teams organise shared work.
Across a gap there is no equivalent, and the signals that would have been obvious — a tone, a posture, a person who has stopped joining things — do not exist in a channel.
What a relay actually carries
Output. Whether work arrives, when, and in what condition.
Output is a poor indicator for exactly the case that matters. People in difficulty usually protect their output first and longest; it is the thing they can control and the thing they are judged on. By the time output drops, the situation has usually been going on for months.
So a team watching the only thing it can see is watching the last thing to change.
The signals that do exist
Thin, and worth knowing because they are all there is.
Length and texture of writing. Somebody whose messages become strictly transactional — no asides, no questions, nothing beyond the minimum — has changed something. This is noticeable only against their own baseline, not against anybody else's, because some people write that way always.
Volunteering. Somebody who used to pick things up and has stopped. An absence, which means nothing surfaces it; it has to be actively noticed.
Response times at the edges. Somebody who used to answer at the end of their day and now answers only at the start.
Withdrawal from whatever optional contact exists. The person who used to be in the call and is now reliably unavailable.
All four are weak signals, all four have innocent explanations, and all four are only meaningful as changes.
| Signal | Why it is weak |
|---|---|
| Writing becoming strictly transactional | Only meaningful against that person's own baseline |
| Having volunteered for nothing | An absence, and absences surface nowhere |
| Answering only at the start of the day | Has a dozen innocent explanations |
| Withdrawing from optional contact | Optional contact is thin to begin with |
Why nobody notices changes
Because noticing a change requires a baseline, and across a gap nobody holds one.
In a room, the baseline is maintained continuously and unconsciously. Across a relay, each interaction is discrete and the comparison has to be deliberate: is this message shorter than this person's messages usually are? Nobody asks that about anybody.
The practical consequence is that noticing has to be somebody's job rather than everybody's instinct, and the person doing it has to think about individuals periodically rather than reacting to what arrives.
Asking, and the limits of asking
The obvious response is to ask people how they are, and across a gap this works less well than it does in person.
A written "how are you doing?" is answerable with "fine" at no cost, and the social pressure that makes "fine" hard to say in person is absent. Asked in a scheduled call, it is answered in front of a camera, which is worse.
What works marginally better is asking about something specific. "You have not picked anything up for a few weeks — is the current work going badly, or is something else going on?" is harder to deflect, and it demonstrates that somebody has been paying attention, which is itself the thing most likely to produce an honest answer.
Being direct about the limitation
The most useful thing a manager across a gap can do is say the limitation out loud to the people affected.
"I cannot see how you are doing. I will not notice unless you tell me, and I would rather you told me early than late." That sentence transfers responsibility in a way that is uncomfortable and accurate.
It is not a solution. It shifts a burden onto the person who is already struggling, which is the opposite of what anybody wants. It is better than the alternative, which is a team where everybody assumes somebody would have noticed.
The boundary of this page
It is not a mental health page and nothing here is clinical advice. Somebody in genuine difficulty needs help from people qualified to give it, and a manager's job is to make that reachable rather than to provide it.
What this page is about is narrower: that one specific channel of information available to a co-located team is entirely absent here, that no mechanism in this collection replaces it, and that a team which does not know this will believe it is fine right up until somebody resigns.
The honest summary
A relay does not carry this. It is in this section for that reason, and the only responses available are weak ones: watching for changes deliberately, asking specifically rather than generally, and saying plainly that the channel is missing.
Teams that do all three still miss things. Teams that do none of them miss almost everything.