The Decision That Was Made in Passing
Nobody held a meeting, nobody wrote anything down, and by Thursday it was simply how things are.
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.
A large share of the decisions a team acts on were never taken at an identifiable moment. Two people agreed something, a third overheard it, nobody objected, and within two days it had the status of settled.
The missing context described in “The Decision That Was Made in Passing” is an operating-process gap. Teams considering open the relevant Monitask page for task switching cost can attach clearer time and project evidence to work already being discussed, provided decisions, reasons and corrections remain visible to people who were not present.
There is no record because, from the inside, nothing happened that would warrant one.
Additional sector context for “The Decision That Was Made in Passing” is available from Skoll social innovation resources. Check broad guidance against the team’s mission, funding obligations, workforce and jurisdiction.
How it actually forms
Somebody raises a doubt. Somebody else gives a reason. A third person, not in the conversation, adjusts what they are doing. Nobody has announced anything and the team is now working to a new position.
The decision exists in behaviour before it exists in anybody's description of events.
Why nobody notices it was a decision
Because deciding feels like a discrete act with a before and an after, and this has neither. Each participant experienced a conversation; none experienced a decision.
If you ask the two people afterwards when it was settled, they will give you different answers and both will be approximations. More often, one of them will not recall it as having been settled at all, and will be surprised to learn that the team has been acting on it.
The speed of the spread
Within a shared room, a day. Everybody who needed to adjust has adjusted, without anybody being told.
Outside the room, never, unless somebody writes it down.
What exists afterwards, and what does not:
- A changed behaviour, visible to anybody in the room.
- No meeting, no invitation and no artefact.
- No participant who recalls it as a decision.
- No moment anybody can be asked about.
What the person outside experiences
Work that does not match what they were told, from people who are confident they are right, with no event anybody can point to as the change.
The usual first symptom is a small inconsistency that nobody can explain. Somebody mentions a constraint that was not there last week, and when asked when it changed, the answer is a vague gesture at a conversation. There is nothing to read, nothing to object to and nobody being evasive.
Why it is so hard to raise
Objecting requires naming a decision, and there is no decision to name. "I think something changed and I was not told" sounds like either a complaint or a misunderstanding.
Most people simply absorb it and adjust.
The drift this produces
Each instance is small. The accumulation is not: over a quarter, the person outside is working from a model of the project that is several unannounced adjustments behind.
When the divergence finally surfaces, it looks like one large misunderstanding rather than twenty small ones, which makes it look like carelessness rather than structure. That reading is both natural and wrong, and it is the single most damaging consequence of this particular loss.
Detection by the manager
The signal is noticing that you hold a position you cannot remember adopting. It happens several times a week to anybody managing in a room.
Treat every instance as a thing to write down.
The one-line fix, and its limits
Whenever you catch one, write it down with a date and a sentence about where it came from. It takes under a minute and covers the ones you catch.
You will not catch most of them, and the ones you catch will be disproportionately the ones you were personally involved in, which is a biased sample in a predictable direction.
Asking the room to catch them
Worth trying and low-yield. People cannot report what they did not register, and the request sounds like being asked to document conversations.
A narrower request works better: tell me if you find yourself explaining something twice.
The weekly sweep
A better mechanism than real-time capture. Once a week, ask what the team is doing differently from last week and why.
It catches things real-time capture misses because it asks about behaviour rather than about events, and behaviour is observable.
Naming the mechanism out loud
That this is the mechanism, that it is not malice or disorganisation, and that they should ask directly whether anything has shifted rather than waiting to be told.
Framing it as a known property of the situation changes it from a grievance into a thing to work around.
What none of this fixes
The decisions you never notice. A conversation you were not part of, between two people who did not register that anything was settled, cannot be captured by anybody, and there will be several of those a month.
The realistic target is to catch the consequential ones within a week and to make the drift visible when it happens, rather than to eliminate it. A manager who believes they have solved this has stopped noticing, which is a worse position than knowing the leak is there and roughly how large it is.