The Accident of Being Overheard
Deliberate inclusion can reproduce access to information and cannot reproduce being accidentally relevant.
three things · no reached them · three with no channel at all · the room side is not counted
Three things, no channels, and no mechanism proposed for any of them.
Being overheard is the reverse of overhearing, and it is the half nobody discusses. In a room, other people learn what you know by accident, which is how you come to be the person somebody asks.
The practical lesson in “The Accident of Being Overheard” is that visibility must be designed rather than assumed. For teams exploring how to measure employee productivity, check this first-party resource can add consistent time and project context when the purpose is explicit, access is limited and managers review exceptions with the people involved.
Nothing reproduces that, and it is a larger loss than the inbound direction.
Additional sector context for “The Accident of Being Overheard” is available from Association of Charitable Foundations. Check broad guidance against the team’s mission, funding obligations, workforce and jurisdiction.
The inbound and outbound directions
Overhearing is what you pick up. Being overheard is what others pick up about you: what you are working on, what you know, what you have an opinion about.
The second is what builds your position in a team.
How reputation is actually assembled
Not from finished work, mostly. From fragments: somebody hears you explain something clearly, mentions a problem and you happen to know the answer, or says something you correct in passing.
Dozens of these a month, none of them an event.
The same knowledge, arriving two ways:
A thoughtful weekly summary of what somebody has been working on, posted in a channel.
An offhand answer to a question in the kitchen, from somebody who happened to know.
Why deliberate sharing is not a substitute
Because deliberate sharing is a claim. Posting what you know is advocacy, and it is read as advocacy; being overheard knowing something is evidence, and it is read as evidence.
The two produce quite different impressions of the same person. The person who posts a thoughtful summary each week is working at it; the person who answered a question off the top of their head in the kitchen simply knows things. Nobody decides to interpret it this way and everybody does.
The relevance problem
The useful case is somebody mentioning a problem within earshot of a person who happens to be able to help. Neither of them knew in advance that the match existed.
Matching requires both parties to be audible to each other, which is exactly what distance removes.
Why asking does not fix it
The person with the problem does not know who to ask, which is the whole point. They cannot direct a question to somebody whose relevance they are unaware of.
Open channels help a little and only for problems somebody has already articulated.
The articulation gap
Most problems are not articulated until somebody is quite far into them. In a room, a half-formed difficulty gets mentioned out loud long before it becomes a question.
A distributed equivalent would require people to broadcast their half-formed difficulties, which almost nobody is willing to do.
The practice that recovers some of it
Narrating work in public. A short running note about what somebody is doing and what they are finding, where colleagues will see it, creates some of the same incidental matching.
It is a real practice, it works for some people, and it is a substantial amount of writing to sustain.
Who can sustain it
People who write easily and do not mind an audience. For anybody else it becomes a weekly chore that reads as performance, and it is worse than not doing it.
This is one of the few places where the right advice differs by person rather than by situation.
What a manager can do instead
Say out loud, to the team, what the person outside the room knows and is working on. Doing somebody's being-overheard for them, deliberately, in the places they are not present.
It is third-hand and it is better than nothing.
The limits of doing it for them
A manager mentioning somebody's expertise is advocacy again, with the same discount applied. It also does not scale past a few mentions before it becomes conspicuous.
And it makes the person dependent on the manager for something that would otherwise have happened by itself.
What it costs over a year
Fewer unsolicited questions, fewer invitations to look at something, and a slowly narrowing sense among colleagues of what the person is actually capable of. None of it is visible as an event.
The person experiences it as their work becoming more solitary without anybody having decided anything, which is an accurate description of what has happened.
Where it is least replaceable
For junior people, who have no established position and are building one entirely out of these fragments. Somebody senior has a reputation that survives being out of the room; somebody in their first two years does not.
This is the strongest argument in the collection for not placing junior people outside the room.
What remains
The accident. Being relevant to something you did not know was happening, to somebody who did not know you could help, is produced by proximity and by nothing else.
The honest position is that a person outside the room will be asked for help less often, consulted less often and thought of as an expert less often than their knowledge warrants, that narrating work publicly recovers a fraction of it for the people temperamentally able to do so, and that the fraction is small. Saying this plainly at least means nobody spends two years wondering why nobody asks them anything.