Who Got Asked, and Who Got Overlooked
Work is handed out by whoever is visible at the moment it appears, which is a question of seating.
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.
Work is allocated at the moment it appears, to whoever is visible at that moment. The visible set is the people in the room, and the allocation is made in a few seconds by somebody who was not conducting a search.
The missing context described in “Who Got Asked, and Who Got Overlooked” is an operating-process gap. Teams considering find the complete explanation here for step rate compensation 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.
It is the most consequential unexamined process most teams have.
The questions raised by “Who Got Asked, and Who Got Overlooked” can also be compared with Blackbaud nonprofit resources. A useful review identifies a responsible owner and a practical change rather than copying a generic checklist.
How it actually happens
Something arrives — a question from another team, a small urgent piece, an opportunity to join something. The person who receives it looks up, sees who is there, and asks them.
Elapsed time: five seconds. Candidates considered: whoever was in line of sight.
What the four seconds actually contain:
- Something arrives on somebody's desk.
- They look up.
- They ask whoever is visible and appears unoccupied.
- No list is consulted and nobody is compared.
Why it is not favouritism
Because no comparison took place. Favouritism implies weighing people against each other and choosing; this is closer to the opposite, a reflex that skips the weighing entirely.
That makes it harder to challenge. Somebody accused of favouring the people they sit with will honestly deny it, and will be telling the truth about their intentions while the pattern of allocation says something else about the outcome.
The compounding
Small allocations compound into visible records. Somebody who gets asked ten small things a quarter accumulates ten pieces of evidence about their range; somebody who gets asked two accumulates two.
A year of this produces two very different-looking people.
What gets allocated this way
Disproportionately the interesting things. Planned work is assigned deliberately; unplanned work, which is where most of the visible opportunity lives, is assigned by line of sight.
The planned-work process usually has some fairness built into it. The unplanned one has none, and nobody thinks of it as a process at all, which is precisely why it never gets examined.
The second-order effect
Being asked is itself a signal. People who are asked things come to be seen as the people who get asked things, including by themselves.
Confidence tracks this closely.
Detecting it
Count. For one month, write down every piece of unplanned work and who it went to. Nothing else reveals the pattern, because the pattern is made of events too small to remember.
Most managers who do this are surprised.
What the count usually shows
A concentration sharper than anybody expected, correlated with proximity rather than with capability, and with one or two names missing almost entirely.
It is an uncomfortable exercise, which is the main reason it is rarely done. The discomfort is the finding: a manager who was allocating on merit would have nothing to be uncomfortable about, and the count simply makes visible a process that was always operating.
The chore version of the same thing
Allocation by line of sight distributes the dull work as well, and here the bias runs the other way: the person who is not in the room is easy to hand something tedious to, because handing it over costs no conversation.
Both patterns can run on the same team at once, and a manager who has only counted the interesting work will see half the picture. Count both columns or neither.
The pause as a mechanism
A two-second habit before asking: is there somebody not in the room who should get this. Two seconds is enough, because the problem is reflex rather than judgement.
It is the cheapest intervention in this collection.
Why a rota is worse
Formalising allocation into a queue removes the speed that makes unplanned work useful, and it allocates things to people who are wrong for them.
The aim is to widen the candidate set, not to replace judgement with a mechanism.
Making the opportunity visible instead
Where something is genuinely an opportunity rather than a chore, saying so in a channel and letting people put themselves forward works better than any allocation rule.
It also surfaces interest you did not know about.
Telling people the mechanism
Worth doing. Somebody who understands that allocation is driven by line of sight can ask to be considered, which is a far easier conversation than asking why they were passed over.
It converts an invisible disadvantage into a manageable one.
What this does not reach
The things never mentioned at all. A piece of work that is discussed and dropped, or mentioned once and absorbed by whoever heard it, never becomes an allocation decision in anybody's mind.
Nor does it reach the slower, more important version: who gets thought of when somebody is considering who might be ready for something larger. That happens in other people's heads, over months, and is driven by recall rather than by records. The section on being thought of first is about exactly that, and it is the part of this problem with the least available remedy.