Chapter 1 — The Aha Moment
Every AI tool you've used so far probably worked like this: you type something, it responds, you copy the response somewhere, and move on. Useful — but you're still doing the job. The AI is helping you; you are running the show.
Cowork is different. Not a little different. The whole logic is reversed.
Instead of you asking Claude to help with a task, you hand Claude the task — the outcome you want, where your files are, what the result should look like — and Claude goes and does it. You step back. You come back to something finished.
This is the shift: from asking to delegating.
The Colleague Test
Here's the clearest way to understand it.
Imagine you have a capable colleague sitting next to you. If you ask them "Can you take a look at this paragraph?", they look at the paragraph. But if you say "Can you put together a summary of everything that came out of our client calls last month? The notes are in the shared folder, I need it as a Word document by end of day" — they go and do that. Start to finish. You don't hover over their shoulder and narrate each step.
That second kind of request — describe the outcome, point to the materials, let them handle the rest — is exactly how you work with Cowork.
What This Looks Like in Practice
Let's make it concrete. Say your manager has asked you for a summary of everything discussed in your team's weekly meetings over the past month. You have a folder with a separate document for each meeting — four or five files, written in the hurried way meeting notes usually are.
If you tried to do this with a regular AI chat tool, you'd probably paste in one meeting's notes, ask for a summary, copy it somewhere, then do the same for the next meeting, and the next. You're the one moving things through the process, one piece at a time.
Here's the same task written two different ways:
Asking for help (regular AI chat): "Can you summarize these meeting notes? [paste notes]" Handing it off (Cowork): "In my May Meeting Notes folder, there are documents from each of our weekly team meetings. Please read through all of them and create a single summary document with three sections: key decisions made, action items by person, and open questions still to be resolved. Save it as a Word document in the same folder, called May Team Meetings Summary."
The first gets you help with one piece. The second gets you the finished thing: Claude reads every file, writes the document, and saves it. Done. You described the result. Claude handled the rest.
What makes the second version work? It says where the files are, what the output should look like, and where to save it. It doesn't tell Claude how to read the files or how to do its thinking — just what the result should be. The more clearly you describe the outcome, the better the result. Vague instructions produce vague outputs, the same as with any colleague.
A Word on Trust
The first time you watch Cowork go through your files without you managing each step, it might feel a little strange. That's completely normal.
Claude only ever has access to the folders you've explicitly opened to it. Think of it like handing a colleague a specific drawer to look through — not the keys to the whole filing cabinet. It works within the space you give it, nothing more.
There's also a setting called "Ask before acting" that lets Claude pause and show you what it's about to do before each step, rather than running straight through a task. If you're just getting started, it makes the whole thing feel a lot less like a leap of faith. You'll find it in your Cowork settings, and it's covered in more depth later in this course.
Pick one real task from your current week — something that involves files you already have. Maybe it's pulling together notes from several documents, tidying up a folder, or drafting something based on source material you've collected.
Write the delegation prompt for it, using this structure:
- What do you want as the output?
- Where is the source material?
- What format should the result be in, and where should it be saved?
Then open Cowork, start a new task, and type it in. Don't overthink the wording — good enough is fine for a first attempt. The goal is simply to see what it feels like to hand something off and get something finished back.