AI used to live in a chat window, answering questions you typed in. Now it has moved a step further: desktop agents like Claude Cowork can open folders on your computer and edit documents and spreadsheets directly. The moment an agent starts touching files, two worries surface at once — is my entire job about to be handed over, and if not, what exactly should I hand over first? This piece answers both with a single principle. AI doesn't take over a job wholesale; it takes over one task at a time. So the fix is straightforward: break your job down into individual tasks, then follow a clear sequence for deciding what goes to Claude Cowork and what stays with you.
Claude Cowork Replaces Tasks, Not Jobs
Let's deal with the anxiety first. A job is the name of the role one person holds; a task is one of the individual pieces of work that make up that role. The job of "marketer" 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 tallying task — not the marketer's job.
This leads to an important conclusion. Handing a task to AI doesn't shrink the job. If anything, the job expands, absorbing the tasks AI can't handle. The work continues; only its shape changes. So the question needs to change. 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 have the principle, let's put it into practice. The method is simple: write down what you did last week, verb by verb. "I made a report" is still too close to a job description. You need to go further down — "I opened last month's sales file and totaled it by region," "I looked at the totals and decided which region to review first," "I explained my reasoning to my manager." Once you can see that opening a file, adding up numbers, making a judgment call, and explaining your reasoning are all separate tasks, you've broken it down correctly.
This list becomes your shortlist of candidates for Claude Cowork. Before you break things down, all you have is a vague question — can I hand off report writing? 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 this task's input and output move as files? If it involves reading and editing documents and spreadsheets in a folder, it's the kind of thing a desktop agent can handle. Second: can you state, as a rule, what separates a good result from a bad one? 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 — it's one you should keep. The diagram below maps out that fork in the road.
The two branches eventually converge back into a single job. What expansion really means is using the time freed up by delegated tasks to take on the tasks AI can't replace.
Designing Job Growth Around the Tasks You Keep
Deciding what to delegate is only half the job. The other half is deciding what to put in the space that opens up. A common mistake here is spending that freed-up time doing more of the same kind of work — delegating the tallying, then just running tallies more often. Do that, and your job doesn't expand; it shrinks into being AI's proofreader.
Real expansion runs in a different direction. Add to your task list the work you never had time for before: deciding what to do next based on the results, coordinating with other teams, interpreting why a number came out the way it did. The spreadsheet Claude Cowork cleaned up is raw material; deciding what to do with that material is the new task. Do this, and the job's name stays the same while its internal mix of tasks changes. That's the practical meaning of "the shape changes, but the work continues."
A Checklist to Try Today
Finally, here's the sequence to put this into action.
1. Write down last week's work verb by verb to build a task list. 2. Ask each task the two questions: does it move as files, and can the rule be stated? 3. Starting with the tasks that answer yes to both, hand them to Claude Cowork one at a time, and always review the first results yourself. 4. Decide in advance what task will fill the time you free up — judgment, interpretation, or coordination is enough. 5. A month later, write the task list again and see what dropped off and what got added.
When you reopen that list, there's only one standard that matters: has your job narrowed, or has it expanded? If it narrowed, you delegated without adding anything back. If it expanded, you designed it right. Sum up where that leaves you in one sentence: you are the person rewriting the task list.
