Labeling a political opponent a flight risk gives decision-makers a ready, HR-approved reason to leave them out of long-term planning and sensitive information.
An example
Months earlier, the director of payments integrations at an accounting-software company had argued against moving the analytics product onto a partner's cloud. That spring a peer mentioned to the chief product officer that she had been taking recruiter calls, which was true of most of the engineering leadership that year. Her retention rating in the HR system changed from low to high risk without anyone speaking to her. Invitations to the three-year planning sessions stopped. She stayed on the distribution list for the formal roadmap, but the working papers for the migration moved to a shared folder she could not open. She went to the chief product officer and asked why she had been left out, and he asked whether she was planning to leave. She said no, and she was back in the planning sessions the next month.
Why it works
The label supplies a ready justification, protecting the company from leakage, so excluding the person takes no argument. Full inclusion starts to feel naive, since every strategy slide shared could walk out the door, and risky, because the decision-maker would personally answer for the loss if the person did leave. The actor never argues against the target; the decision-maker's own fear of being wrong does the work. It needs a formal risk rating that can be filled in, some plausible markers such as recruiter calls, and decision-makers who have been burned before.
The thinking behind it
Erving Goffman Stigma: Notes on the Management of Spoiled Identity (1963) treats stigma as an attribute that discredits a person in others' eyes, and notes that it spreads to the people around them as a courtesy stigma. A flight-risk label works as a mild stigma: it changes how decision-makers read the person, and colleagues who keep sharing papers with them risk sharing the doubt. A direct conversation with the decision-maker is the quickest way to remove it.
Daniel Kahneman Judgment under Uncertainty: Heuristics and Biases (1974), by Amos Tversky and Daniel Kahneman, describes availability: judging how likely something is by how easily examples come to mind. A decision-maker who remembers an insider leaving with a roadmap finds the risk vivid, so a single remark about recruiter calls feels like evidence. That is why the label attaches most easily where leaders have been burned before.
Amos Tversky Loss Aversion in Riskless Choice: A Reference-Dependent Model (1991) holds that losses and disadvantages have greater impact than gains and advantages, though how general the asymmetry is remains disputed. For a decision-maker, sharing plans with someone who might leave risks a visible loss they would answer for, while the gain from including them is diffuse. That imbalance is why exclusion needs no argument once the label exists.
Warning signs
Multi-year planning invitations stop arriving, with no stated reason. Working papers move to channels the person cannot reach while their name stays on formal distribution lists. Meetings they used to attend happen without them and get summarized afterward. Their retention rating changes without anyone speaking to them, and colleagues start asking, casually, whether they are happy where they are.
How to defend yourself
Information starvation with no stated cause is the signal to act on.
- Go directly to the ultimate decision-maker and say plainly whether you intend to stay. A direct answer resets the label faster than anything else.
- Ask HR what your retention rating is and what it is based on.
- Ask to be put back on the specific meetings and papers you lost, naming each one.
- Keep outside contacts discreet during a contested decision, since recruiter calls are what the label attaches to.
If you do intend to leave, say so on your own timing; leaving the label to stand on rumor hands the decision to your opponent.
How a leader shuts it down
Insist on a conversation with the person before any retention rating changes, and record who proposed the change. When someone is dropped from planning, ask who suggested it and on what evidence. Use flight-risk ratings as prompts for a retention conversation and never as grounds for exclusion.