Workforce impact and automation exposure
Decomposes a role into tasks, rates each against what a machine still cannot do, and decides role by role: unchanged, redesigned, redeployed, or gone.
The printable canvas and the handoff into Claude Code are part of a paid plan. See what a plan includes. It needs the Claude desktop app on this machine, and your team and the prompt library already installed in that project — we cannot see your disk, so open it there.
What it is
A structural design tool, not a communication one — a distinction the method insists on, because the decisions made here determine what is later communicated rather than the reverse. Each affected role is broken into its component tasks, each task is rated against what current AI genuinely can and cannot do, and a structural decision is made role by role.
- Task decomposition
- A role broken into its component tasks rather than assessed as a whole. A job title can be highly exposed in some tasks and untouched in others, and the job title is the wrong unit of analysis.
- Perception and manipulation bottleneck
- Tasks needing dexterous, real-world physical manipulation in unstructured settings. Narrowing as computer vision and robotics advance, but still a genuine limit.
- Creative intelligence bottleneck
- Genuinely novel idea generation and creative problem-solving. AI can imitate creative output convincingly; whether it originates it is a live and contested question, which is why this rating needs judgement rather than a formula.
- Social intelligence bottleneck
- Negotiation, persuasion, care and the reading of another person's state — tasks where the human relationship is the point, not an obstacle to efficiency.
- The structural decision
- Unchanged, redesigned around the tasks a machine now handles, redeployed to a role where human tasks dominate, or the role no longer exists. Made and approved before any communication starts.
- Sign-off
- Approved by HR leadership, the relevant function heads and the transformation director before any communication to affected teams. Treated as a live document, versioned as the programme progresses.
How you run it
- Decompose each role into its component tasksNot the job title — the actual tasks that fill the working week. This is the unit the rest of the analysis works on.
- Rate each task against the current bottlenecksPerception and manipulation, creative intelligence, social intelligence. Be honest about how fast the bottleneck is narrowing, not just where it sits today.
- Convene HR leadership and the relevant function headsNot the transformation team alone. The people who own the roles need to be in the room for the structural decision to hold.
- Decide the structural outcome per roleUnchanged, redesigned, redeployed, or gone — a specific decision for every role in scope, not a general statement about the function.
- Get steering group sign-off before any communicationThe decisions determine what is communicated, not the other way round. Communicating before sign-off risks announcing something the steering group has not actually agreed.
The prompt
Run this tool in your own Claude
The short prompt starts your partner against the library on your disk. The long one carries everything with it and needs nothing installed.
Your playbook
It lands in the earliest stage this tool suits. Move it on the Playbook page.
You’ll need
- The specific roles in scope, described by task rather than by job title
- An honest, current read of what AI or automation can and cannot do for each task
- HR leadership and the relevant function heads in the room, not just the transformation team
You’ll end up with
- Every role decomposed into its component tasks
- Each task rated against the current automation bottlenecks
- A structural decision per role, made before any communication begins