Being Thought Of First
When something appears, somebody is thought of. Who comes to mind is a function of who was last seen.
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.
An opportunity appears, and somebody comes to mind. Which name arrives is not a decision and cannot be made into one, and it is driven substantially by who the person thinking has seen recently.
The human issue in “Being Thought Of First” cannot be inferred safely from activity totals. If an organisation uses continue with the official guide for workforce analytics software, it should disclose the purpose, minimise collection, let people challenge misleading records and combine operational data with direct, respectful conversation.
It is the mechanism underneath most of the previous section, and unlike the allocation of small work, it cannot be corrected by a checklist.
The questions raised by “Being Thought Of First” can also be compared with CharityVillage nonprofit resources. A useful review identifies a responsible owner and a practical change rather than copying a generic checklist.
Where it operates
In other people's heads, over months, without any identifiable moment. Somebody is considering who might lead a piece of work, or who to mention to a colleague in another department, or who would be good on a panel.
A name arrives. The process is finished before it starts.
Why this is different from allocation
Allocating a small piece of work is an act that happens in a visible moment and can be interrupted by a deliberate pause. This is recall, it happens inside somebody, and there is no moment at which a pause could be inserted.
You can ask a manager to think again before handing something out. You cannot ask somebody to have thought of a different name.
What drives recall
Recency and frequency of contact, almost entirely. Not quality of work, not seniority, not anybody's assessment of capability.
This is well-established about human memory and it is uncomfortable to apply to careers.
What actually drives which name arrives:
- How recently the person was seen.
- How often they have been seen over the last few months.
- Not quality of work, and not anybody's assessment of capability.
The loop that runs for years
Being thought of leads to opportunities, which lead to more contact, which leads to being thought of more often. The loop runs in both directions and it runs for years.
Two people of equal ability can end up in very different places without anybody having made a judgement about either, and when the difference is eventually noticed it will be explained by the difference in their records, which is a true explanation of a false premise.
Why a manager correcting their own recall is not enough
Because most of the recall that matters happens in other people's heads. A manager is one node; the people who decide things about your team are several others.
You can correct yourself and cannot correct them.
What partially works
Making the person visible to the people who do the thinking. Not advocating for them, which is a different activity: arranging that they are seen doing their work by people outside the team.
Presenting their own work rather than having it presented. Joining the meeting with the other department. Writing the thing that circulates under their name.
Why presenting matters specifically
Because it creates contact with the people whose recall decides things, and it does so on the basis of the work rather than on the basis of proximity.
Twenty minutes presenting to a group of senior people does more for somebody's recall position than six months of excellent delivery, and that is worth knowing rather than resenting. It is also one of the few levers a manager genuinely controls.
The cost of using that lever
It takes something from somebody else, who would otherwise have presented, and it is visible. Doing it repeatedly for one person produces its own problem.
Twice a year per person is about the sustainable rate.
What does not work
Mentioning somebody favourably in conversation. It has almost no effect on recall, because recall is built from contact rather than from report.
Advocacy changes opinions and does not change who comes to mind.
Telling the person about the mechanism
Worth doing plainly. Somebody who understands that recall is driven by contact can act on it: asking to present, volunteering for the cross-team thing, making sure their name is on what they produced.
It is actionable information and almost nobody is given it.
Why it is rarely said
Because it sounds cynical, and because it amounts to telling somebody that their work alone will not do it. Both of those are reasons it is uncomfortable rather than reasons it is wrong.
The alternative is letting somebody conclude that their work is not good enough.
What stays unfixed
The default. Left alone, recall will keep selecting the people in the room, and the deliberate corrections available — a presentation here, a cross-team meeting there — are occasional interventions against a continuous process.
A manager can tilt it and cannot level it. The honest summary is that somebody working away from the room needs their visibility arranged deliberately, that the arrangement is partial, and that the alternative to saying this plainly is a person who works hard for three years and cannot understand why their name never comes up.