Everyone is a flight risk
Or The Tempting Idiocy of Asking the Wrong Question
Should I go…
A developer, mid-thirties, once the team’s star. They built the core service, mentored the juniors, carried the pager at 3 a.m. But lately they’ve gone quiet. The standups feel like reruns. They’ve started reading papers on distributed tracing during lunch — papers that don’t fit the roadmap.
Their manager finally asks, “Are you thinking of leaving?”
They shrug. “I’m thinking of arriving somewhere.”
Three weeks later, they do.
… Or should I stay?
Another developer, another day, same profile, same talent. They stay — but not because they’re thriving. They stay because the mortgage looms, because inertia is comforting, because every day feels survivable. Their light dims, their code dulls, their laughter vanishes.
Management calls it retention.
It’s really decay.
Control is a Deep & Tempting Idiocy
There’s a special kind of idiocy that creeps into organisations the moment they start treating people like probabilities. You can smell it in meetings where someone leans back, half-whispering: “Is Mary a flight risk?”
As if humans could be modelled like failing components. As if departure were an anomaly, an exceptional case. As if the most obvious truth in the world weren’t staring them in the face: of course they’re a flight risk. Everyone is.
The question itself betrays a mindset — managerial fatalism dressed as vigilance. It assumes that loyalty is the default and leaving is betrayal. But the modern developer isn’t a serf; they’re a citizen of a vast, borderless republic of code, ideas, and curiosity. They can leave at any moment — to another company, another continent, another life entirely. The real miracle isn’t that people go, it’s that they stay.
The deeper idiocy is control. “Flight risk” is the language of prisons and HR dashboards — an attempt to manage uncertainty through categorisation. It’s the bureaucrat’s dream: if you can measure it, you can mitigate it. You can deploy “retention bonuses,” “engagement programs,” and “pulse surveys.” You can graph loyalty. You can spreadsheet love.
Except you can’t.
Because people don’t leave because of numbers. They leave because of narratives.
Every developer has a story about why they came — usually some blend of mission, respect, curiosity, and promise. That story either evolves with them or it stagnates. When the story stops making sense, flight begins. That’s not disloyalty; that’s physics. Energy seeks a higher gradient.
So when someone asks, “Is that developer a flight risk?” the right response is: “Only if they still have a pulse.” Because flight risk isn’t a sign of dysfunction. It’s proof of vitality. It means you’ve hired people with ambition, imagination, and enough agency to refuse slow suffocation.
The smarter question — the one leaders too rarely ask — is:
“Are we still the best place for this developer to grow?”
That’s the pivot point. It turns the conversation from suspicion to stewardship. From hoarding to cultivating. From control to care.
The organisations that get this right don’t trap people; they launch them. They build alumni networks, not prisons. They celebrate departures like graduations. Because when someone leaves stronger than when they arrived they take your reputation with them — and they’ll send others back in return.
The idiocy of “flight risk” talk is the idiocy of fear masquerading as insight. Fear of being abandoned, fear of being unchosen. But the truth is liberating: You can’t keep anyone. You can only make it worth their while to stay a little longer, do their best work, and leave you proud and having grown.
Every developer is a flight risk. The wise build runways, not cages
People don’t stay because they must; they stay because they can grow. The moment growth stagnates, belonging erodes.
Fear-based management — retention bonuses, guilt, secrecy — merely slows the inevitable. Stewardship-based leadership embraces transience and invests in meaning, mastery, and momentum.
Some Practices
Hold “stay conversations”: ask what’s exciting, not what’s wrong.
Map growth stories, not job titles.
Make exits graceful — share lessons, celebrate contribution, maintain alumni ties.
Encourage internal mobility: a new team beats a new company.
Treat career conversations as ongoing mentorship, not emergency interventions.
Some things to avoid
Turning “flight risk” into a metric. (If you can dashboard it, you’ve already lost them.)
Confusing contentment with commitment.
Assuming retention equals health; some people stay for the wrong reasons.
Weaponising loyalty — “You owe us” — instead of earning it through respect and challenge.
The question “Is that developer a flight risk?” reveals more about the asker than the asked. It’s the language of fear. Better to ask, “Are we still worthy of their ambition?” — and to build a culture where departure isn’t disaster but evidence that you hired the right kind of restless mind.
People leave. Always have. Always will. The art is to make staying, for as long as it lasts, feel like a beneficial flight too.