learnaiwithrafa
Multi-ToolWorkflows

Audit Your Own Job for AI (the Prompt I Run on My Role)

AI won't take your whole job — it takes tasks inside it. Here's the audit prompt I paste into Claude to score every weekly task for delegation, plus the EM rule I use to decide what stays human.

4 min read3 sources
  • #workflows
  • #delegation
  • #productivity
  • #claude

Stop asking "will AI take my job." Ask "which tasks inside my job should it already be doing." The data backs the reframe: Anthropic's Economic Index found that as of November 2025, 52% of Claude.ai conversations are augmentation (AI helps, you decide) and 45% are automation (AI does it) — and augmentation just overtook automation again. People aren't handing over careers; they're handing over tasks. As an EM, that's exactly how I think about delegation with humans, so I run the same audit on myself.

Why task-level, not job-level

Most roles are a small slice of the thing you were hired for, buried under a mountain of overhead. Salesforce's State of Sales puts a number on it: reps spend only about 30% of their week actually selling — the other 70% goes to admin, research, and internal meetings. Your ratio is different but the shape is the same. The automation win isn't your job; it's the 70%.

The three-bucket rule I use

I score every recurring task on two axes: the judgment it demands, and the damage if it goes wrong.

  • Automate fully — repetitive, low cost of error (formatting reports, first drafts of routine messages, sorting inputs). AI owns it end to end.
  • AI assists — needs some judgment. AI drafts/researches/preps; you approve. Your time drops from an hour to five minutes.
  • You stay in control — it moves a relationship or a real decision (performance conversations, negotiations, final calls). AI briefs you; it doesn't act.

Copy this prompt

Paste it into Claude with five quiet minutes. It interviews you, then sorts and ranks.

You are my automation auditor. Interview me, then sort my work week into three
buckets and hand me a ranked plan. Be decisive: most people under-automate out of
habit. Push back when I claim a task "needs me" without a real reason.

STEP 1 — INTERVIEW (one question at a time, wait for my answer):
1. My role, and a rough hour-by-hour normal week.
2. What I do every single day without fail.
3. Weekly/monthly work: reports, reviews, planning, 1:1s.
4. Tasks I procrastinate on most.
5. Where I copy info from one place to another.
6. Tasks that touch another person's feelings, money, or trust.

STEP 2 — SORT each task into exactly one bucket:
- AUTOMATE FULLY: repetitive + low error cost. AI does it end to end.
- AI ASSISTS: needs some judgment. AI drafts/researches/preps, I approve;
  my time on it must drop >=70%.
- I STAY IN CONTROL: moves a relationship or needs real judgment. AI only briefs.
If I push a task to "control" with no relationship/judgment reason, challenge me
once with the honest counter-argument, then respect my call.

STEP 3 — DELIVER:
1. A table: task | bucket | hours/week | one-line "how" (scheduled prompt, saved
   Claude skill, a connector, or an agent) for every AI-touched task.
2. Top 3 to automate first, ranked by (hours saved) x (ease of setup). For each:
   plain setup steps I can do this week + the first ready-to-paste prompt.
3. Honest total hours/week I get back from just the top 3, and the bucket-three
   work I should reinvest that time into.
4. One task I probably think is automatable but isn't yet — and why.

Do this today

Run the prompt, then ship only the #1 item this week — a single working automation is worth more than three you never finish. Re-run the whole audit every six months; tasks migrate from "assists" to "automate" as your trust and the tools grow.

Sources