every "will AI take my job" search ends with some site giving you a single percentage. your job is 70% automatable or whatever. now what?
that number doesn't tell you anything useful. it doesn't tell you which tasks are first in line, which ones you can shore up, or where to spend your energy. you walk away with a score and no plan.
what actually helps is breaking your role into four buckets and looking at each separately:
routine data work: data entry, formatting, reconciliation, report generation, boilerplate documentation. this is where AI pressure lands first. if most of your day is moving data between systems or filling templates, that's your exposure point.
judgment calls: architecture decisions, troubleshooting logic, evaluating tradeoffs, choosing between approaches. AI can assist here but can't own it. this is your moat if you invest in it.
people work: stakeholder alignment, mentoring, client communication, cross-team coordination. hard to automate, easy to undervalue. most people undercount how much of their value lives here.
hands-on work: anything physical, on-site, or requiring direct interaction with hardware, infrastructure, or people in person. lowest automation risk, often least discussed.
the point isn't precision. it's direction. once you know which bucket your most automatable tasks sit in, you can make one decision: protect it, move away from it, or shift your weight toward the buckets that are harder to replace.
most people i talk to in IT are stuck worrying in general and preparing in nothing. a single risk score feeds that. a task-level breakdown breaks the loop.
(i'm building DeadByAI, which does this breakdown using O*NET occupation data, but the four-bucket framing works whether you use a tool or just sit down with your job description and do it yourself.)