Everyone's Terrified of AI Taking Jobs. Wrong Fear, Wrong Timeline.

Every second conversation I have right now eventually gets to the same anxious question: “Is AI going to take my job / my team's jobs / my industry?” It's the wrong question, aimed at the wrong timeline, and answering it wrong is costing people more than the thing they're actually afraid of.

Let's deal with the actual data first, because the panic and the numbers don't match. The World Economic Forum's Future of Jobs research projects roughly 92 million roles displaced by AI and automation by 2030 — alongside about 170 million new roles created in the same window. Net positive, globally, on paper. But net positive doesn't mean your job is safe, because the people losing roles are rarely the same people filling the new ones. That gap — not the headline number — is where the real risk lives.

Here's the sharper, more current signal: Stanford's 2026 AI Index found that employment for young software developers, ages 22 to 25, has fallen nearly 20% since 2024 — while employment for developers over 30 kept growing. Same industry, same disruption, opposite outcomes, based entirely on who had already built judgment and experience AI can't yet replicate, versus who was still doing the junior tasks AI now does faster.

Jamie Dimon said the quiet part out loud at JPMorgan's investor meeting earlier this year: “We have displaced people from AI — and we offer them other jobs.” Underneath JPMorgan's flat overall headcount, operations and support roles shrank while client-facing, revenue-generating roles grew. That's not mass unemployment. That's a structural rebalancing — and it's already happening inside large institutions, quietly, without headline layoffs.

So here's the reframe I'd actually offer, because the fear so many founders and professionals are carrying is pointed at the wrong target. The risk was never “AI will do my job.” The risk is “I never developed the judgment, taste, and decision-quality that sits on top of the task” — because that's the layer AI still can't touch, and it's the layer that determines whether disruption threatens you or promotes you.

Practically, that means: stop measuring your relevance by how many tasks you can execute, and start measuring it by how many decisions you're trusted to make. Stop treating AI literacy as optional continuing education and start treating it as the baseline — the way basic computer literacy became non-negotiable twenty years ago. And if you lead a team, the uncomfortable job in front of you isn't deciding who to automate. It's deciding, honestly, who on your team is building judgment right now versus who is still just executing tasks that are already on the clock.

The businesses and careers that come out of this period stronger won't be the ones that feared AI the most. They'll be the ones that got honest, early, about which parts of their value were tasks — and which parts were judgment.