It's not fear of missing out anymore. It's Fear Of Becoming Obsolete — and it's quietly shaping how your employees respond to every AI rollout, whether they say it out loud or not.
You've heard of FOMO. At the 2026 SIOP conference — the country's largest gathering of industrial-organizational psychologists — a workshop on human-centered AI in the workplace put a name to the fear that's actually driving resistance inside organizations right now: FOBO, Fear Of Becoming Obsolete.
It's not the same thing. FOMO is about missing an opportunity. FOBO is about losing your relevance entirely — your professional identity, your sense of contribution, your place in the org chart. And unlike FOMO, most people won't say it out loud. It shows up instead as quiet disengagement, slow-walked adoption, and "I just haven't had time to learn it yet."
Open resistance is a management problem you can see and address directly. FOBO is worse, because it hides. Work intensification, loss of professional identity, and eroded psychological safety are real, well-documented barriers to AI adoption — and none of them look like resistance on the surface. They look like busyness. Caution. "Best practices." Slow adoption gets rationalized a dozen different ways before anyone names the real cause.
Leaders who model healthy AI collaboration and build a learning culture — not a competitive one — are the ones who unlock adoption. The organizations that treat AI fluency as a threat ranking system get exactly the guarded, defensive behavior you'd expect.
This connects directly to what I've written about before: the fear employees actually have about AI was never really about the technology. FOBO gives that fear a name and a mechanism — and that's exactly what makes it addressable.
One of the sharper distinctions to come out of this research is the difference between AI literacy and AI fluency. Literacy means knowing what AI is. Fluency means knowing how to actually work with it — day to day, inside your real job, on real problems. Most corporate AI training stops at literacy. That's the trap: employees walk away technically informed and practically no more confident, which does nothing for FOBO and sometimes makes it worse.
Knowing the vocabulary. Understanding broadly what generative AI, agents, and automation are. Passive awareness with no hands-on repetition.
Using AI tools inside your actual workflow, repeatedly, until it's second nature. Knowing what to ask, how to evaluate the output, and when not to use it at all.
The workshop framework breaks AI readiness into three tiers, and most organizations have no idea where their own people actually sit:
Most employees are being asked to jump straight to "Maker" behaviors — building their own prompts, workflows, and use cases — without ever being confirmed at "Consumer" level first. That gap is where FOBO breeds fastest: people who were never given the basics are being asked to innovate, and the anxiety that produces gets misread as resistance instead of what it actually is — a training sequencing failure.
Across every skill level, one meta-skill stood out in the research above all others: knowing when AI is not the right solution. Not "can you use AI" — everyone can eventually learn that. The differentiator is judgment: critical thinking to evaluate inputs and outputs, iterative thinking to refine instead of accepting the first answer, and systems thinking to see how data, tools, and people actually fit together.
That's not a technology skill. It's a human one — which is exactly why change management, not just tool deployment, is the lever that resolves FOBO instead of amplifying it.
If you're running a PROSCI/ADKAR-based rollout, FOBO maps directly onto the Awareness and Desire stages — and it's exactly why so many AI initiatives stall there instead of moving to Knowledge and Ability. You cannot build genuine desire to adopt a tool that your employees quietly believe is coming for their relevance. Naming FOBO explicitly, in plain language, in your kickoff communication, is one of the fastest ways to move people out of quiet defensiveness and into real engagement.
Measure beyond efficiency, too. Time saved is the easy metric — but the real question research keeps surfacing is different: what can your people do now that they couldn't do before? Organizations winning with AI aren't just deploying tools faster. They're redesigning how work actually gets done, with their people ahead of the curve instead of scrambling to catch up.
The AI Efficiency Audit maps where your team actually sits on the Consumer/Maker/Developer curve — and builds the ADKAR plan to move them forward without the quiet resistance.
Start with an audit →Sources: Morelli, N., Gibby, R., & Sodhi, K. (2026). Human-centered AI in the workplace [Conference workshop]. SIOP 2026 Annual Conference. Summary via Guest, F. (2026, April 30). LinkedIn.