That a Conversation Is Happening at All
You cannot ask to be included in something you do not know exists. The hardest loss to even notice.
three things · two reached them · one with no channel at all · the room side is not counted
Sorted by whether anything could have carried it.
The hardest thing to miss usefully is the existence of a conversation. Everything else can be asked about; this cannot, because asking requires knowing there is something to ask about.
The practical lesson in “That a Conversation Is Happening at All” is that visibility must be designed rather than assumed. For teams exploring does microsoft teams track your activity, see the service in context can add consistent time and project context when the purpose is explicit, access is limited and managers review exceptions with the people involved.
It is the one loss with no detection mechanism available to the person suffering it.
The questions raised by “That a Conversation Is Happening at All” can also be compared with Gates Foundation resources. A useful review identifies a responsible owner and a practical change rather than copying a generic checklist.
The shape of a conversation that has no edges
It starts when somebody mentions something at a desk. It continues over three days in pieces, between different pairs of people, and at no point does anybody schedule it, name it or notice that it is a single thing.
By the end of the week the team has a shared view about something, and there was never a meeting.
Why this is different from a missed meeting
A missed meeting is visible. It appears in a calendar, somebody can forward the notes, and the person outside can ask what happened.
A diffuse conversation appears nowhere. There is no artefact, no start, no participant list and no moment at which it would have been natural to include anybody. Nobody made a decision to exclude; there was no decision to make.
What it feels like from outside
Arriving at a position that everybody else already holds, without having been part of reaching it, and without being able to identify when it formed.
The usual experience is finding out through an aside.
The second-order loss
Not being in the conversation is one thing. Not having been able to influence it is another, and the second is what actually matters: the person outside had a view that would have changed something and never had an occasion to offer it.
They frequently do not find out that the occasion existed, which means they also cannot learn from the omission. The next one goes the same way, for the same invisible reason.
Why the two cases are not the same thing, although they are treated as one:
| A missed meeting | A diffuse conversation | |
|---|---|---|
| Has a start | Yes | No |
| Appears in a calendar | Yes | No |
| Has a participant list | Yes | No |
| Can be asked about | Yes | Only afterwards, by its effects |
| Leaves an artefact | Usually | Never |
Why "keep me in the loop" fails
It asks the room to recognise a loop. A loop is visible from outside and not from inside: the people in it are just talking.
The request is sincerely agreed to and cannot be acted on.
What can actually be detected
Aftermath. A new assumption, a shifted priority, a reference to something as settled. Each is evidence that a conversation happened.
This is detection after the fact and it is what is available.
The manager's version of the problem
You are in these conversations and will not notice them either. From inside, there is nothing to notice.
The only workable habit is retrospective: at the end of the week, ask yourself what the team now believes that it did not believe on Monday, and where that came from. The answer is frequently a conversation you participated in without registering it as one, and writing down even a third of those is a large improvement on writing down none.
Making the subject visible instead of the conversation
A short list of live questions — things the team is currently chewing on, with no resolution yet — is more tractable than trying to capture conversations.
It gives the person outside something to ask about.
Who maintains that list
The manager, in practice. Five or six lines, updated weekly, naming what is unsettled.
It is low effort and it is the single most useful artefact in this section.
Why it works better than notes
Because it points forward rather than backward. Notes tell somebody what was concluded; a list of open questions tells them where their view could still make a difference.
That is precisely the loss being addressed.
The cost of finding out late
A view offered after a position has settled is heard as an objection rather than as a contribution, and it is weighed accordingly. The same sentence said three days earlier would have been a thought.
So the person outside is not only late; they are pushed into a more adversarial register than they chose, and doing that repeatedly makes somebody look difficult when they were merely slow to hear about it.
The invitation problem
Even with the list, the person outside has to decide whether to intervene, and intervening in something you were not part of is socially expensive.
So the list has to come with an explicit statement that comment on any line is wanted, repeated more often than feels necessary.
What remains unreachable
The conversations nobody characterises as being about anything. A great deal of what a team works out together is not on any list of questions because nobody has formulated the question yet.
Those cannot be surfaced, because surfacing requires formulation and formulation is most of the work. The claim here is narrower: the questions a manager can already name can be made visible cheaply, which converts an invisible loss into a visible one for a meaningful fraction of cases. The rest stays invisible, and anybody telling you otherwise has not tried it.