AI has moved from answering questions in a chat window to opening folders on your computer and editing documents and spreadsheets directly. As desktop agents like Claude Cowork start handling files, two worries grow at once: the fear that your whole job could be taken over, and the practical question of what to hand off first if that's not quite right. This piece answers both with a single principle: AI doesn't take over a job—it takes over tasks. So the process is simple. Break your job down into individual tasks, then follow the steps below to decide what to hand to Claude Cowork and what to keep for yourself.
Claude Cowork Replaces Tasks, Not Jobs
Let's start by putting the anxiety in perspective. A job is the name for the role one person holds; a task is one of the individual pieces of work that make up that role. The job of "marketer," for instance, contains dozens of tasks: organizing materials, drafting copy, tallying numbers, persuading stakeholders, deciding priorities. AI operates at the level of these individual pieces. If Claude Cowork opens a folder and cleans up a spreadsheet, it has taken over one task—tallying numbers—not the marketer's job.
This leads to an important conclusion. When a task moves to AI, the job doesn't shrink. It actually expands, as tasks AI can't replace get added to fill the space. The form changes, but the work continues. So the question needs to change too. Instead of asking whether your job is disappearing, ask how the task list that makes up your job is being reshuffled.
How to Break Your Job Down into Tasks
Now that we understand the principle, let's put it into practice. The method is simple: write down what you did over the past week, verb by verb. If you write "made a report," that's still closer to a job description. You need to go down to the level of "opened last month's sales file and summed it by region," "looked at the totals and decided which region to look at first," and "explained why to my manager." Once you can see that opening a file, adding up numbers, making a judgment call, and explaining a decision are all separate tasks, you've broken it down correctly.
This list becomes your shortlist of candidates for Claude Cowork. Before you break it down, all you have is the vague question of whether you can hand off "writing the report." After you break it down, you can decide line by line which items to delegate and which to keep.
What to Hand Off to Claude Cowork, and What to Keep
Two questions are enough to decide. First, does the input and output of this task move through files? If it's a matter of reading and editing documents and spreadsheets in a folder, it's the kind of thing a desktop agent can handle. Second, can you describe what makes a result good or bad as a rule? If you can, hand it off and review the output. If you can't—if the task involves reading context, persuading people, or setting priorities—that's work you should keep for yourself. Here's that fork in the road, laid out as a diagram.
The two branches ultimately fold back into a single job. That's what expansion really means: using the time freed up by delegated tasks to add tasks AI can't replace.
Designing the Expansion: What to Add with the Time You've Freed Up
Deciding what to delegate is only half the job. The other half is deciding what to add to the space you've freed up. The common mistake here is spending that extra time doing more of the same task—delegating the tallying, then just running the tally more often. Do that, and your job doesn't expand; it narrows into reviewing AI's output.
Real expansion moves in a different direction. Add to your task list the work you'd previously put off for lack of time: deciding what to do next based on results, coordinating with other teams, interpreting why a number came out the way it did. The spreadsheet Claude Cowork cleans up is raw material; what you decide to do with that material is the new task. Do this, and the name of your job stays the same while what fills it out changes. That's the practical meaning of "the form changes, but the work continues."
A Checklist to Try Today
Last, here's the order to work through.
1. Write down last week's work verb by verb to build your task list. 2. Ask each task the two questions: Does it move through files? Can it be explained by a rule? 3. Start handing off, one at a time, the tasks that answer yes to both, and always review the first results yourself. 4. Decide in advance what task you'll add to the time you free up—judgment, interpretation, or coordination is enough. 5. A month later, write the task list again and see what's dropped off and what's been added.
When you reopen that list, there's just one thing to check: has your job narrowed, or expanded? If it's narrowed, you delegated without adding anything back. If it's expanded, you designed it correctly. Here's the situation in one line: you are someone who keeps rewriting their own task list.
