Lesson brief
AI pioneers warn that the jobs most exposed to large language models are the ones that happen entirely behind a keyboard: drafting, summarising, classifying, looking up rules, and writing routine code. If your role is mostly text-in, text-out, you are operating on the same surface where current models are improving fastest, and the timeline being discussed inside the labs is measured in a couple of years rather than a generation.
The mechanism is data availability. Models learn from the enormous archive of human intellectual output that already lives on the internet, which is why office work was the first domino. Robotics lags because there is no equivalent dataset for moving a body through a messy, unfamiliar physical world. The distinction worth holding in your head is routine knowledge work, where outputs are predictable, versus contextual work, where the value sits in physical presence, judgement under ambiguity, or relationships built over time.
The tradeoff in auditing is honesty versus comfort. It is tempting to label your work as creative or strategic because that feels safer, but a credible audit forces you to count the hours you actually spend on routine tasks. If eighty percent of your week is composed of work a competent assistant model could draft a first pass on, your exposure is high regardless of your title, and a transition plan needs to start now rather than after the layoff.
Core takeaways
- List every recurring task you do in a typical week and time-box each one in hours.
- Tag each task as routine knowledge work, contextual judgement, or physical presence.
- Routine keyboard tasks face the shortest displacement timeline and the steepest cost curve.
- Robotics lags software automation because no internet-scale dataset exists for physical work yet.
- Job titles disguise exposure; the audit must be at the task level, not the role level.
- A role above fifty percent routine knowledge work needs an active transition plan within twelve months.
Practice
Open a blank spreadsheet and list every task you performed in the last working week, one per row. In the second column, estimate hours spent. In the third column, tag the task as Routine (predictable input to predictable output behind a keyboard), Contextual (requires judgement, relationships, or physical presence), or Mixed. Sum the hours per category and calculate the percentage. If Routine is above forty percent, circle the three highest-hour routine tasks and write one sentence per task on what a current AI assistant would still get wrong. That short list becomes the starting point for your defence strategy in later lessons.
Quiz
FAQ
- Is my job at risk from AI?
- Partly — almost everyone's job is, in the sense that some tasks within it will change. The right question isn't 'will my job exist' but 'will the version I do today exist'. Most jobs are partially exposed, not fully replaced.
- What skills will be most valuable?
- Skills that complement AI rather than compete with it: judgement under ambiguity, building trust, navigating organisations, original problem framing, creative synthesis, anything requiring physical presence or accountability. Pure information processing is the most exposed category.
- Should I learn to code?
- Useful for many adults, not essential for everyone. Coding literacy (enough to read code, brief a developer, prototype with AI assistance) is more broadly valuable than full-stack mastery. Pick the level that matches what you're actually trying to do.
Reflection questions
- Which takeaway here is most uncomfortable to apply to your life right now?
- Where in your week could the exercise above realistically run for 7 days?
- What is the smallest, bad-day version of this lesson's idea you could do tomorrow?
- Who in your life would benefit most from you applying this?
- What would have to be true in 90 days for this lesson to have mattered?
Common mistakes in this area
- Waiting for the restructure announcement.
- Refusing to use AI on principle.
- Confusing ‘AI-proof’ with ‘AI-resilient.’
- Pivoting wholesale every six months as new capabilities ship.
- Treating yourself as your job title rather than as your skill stack.
- Becoming the loudest doomer in the office.
Apply this today
Pick one action from the practice block above. Put it on today's calendar at a specific time, in a specific place. If it can't fit in today's calendar, it's too big — shrink it until it can.