How to brief Claude Cowork
like an operator.
Most disappointing Claude Cowork output traces back to a vague ask, not a weak model. Here's the structure that gets you a usable first pass instead of a generic guess.
The five rules of a good Claude Cowork brief
Briefing Claude Cowork well is the same discipline as briefing a capable assistant, just written down instead of assumed. Five things separate a brief that produces something you'll actually use from one that produces a generic first guess.
Name the task, not the tool
Not "help me with this spreadsheet", but "turn this weekly sales export into a one-page summary my manager can read in two minutes". Claude Cowork works towards an outcome far better than towards a vague request for help.
Hand over the actual inputs, not a description of them
The real spreadsheet, the real email thread, the real document, not your summary of what's in them. Claude Cowork works from the source; a description loses the details that decide the output.
Say what "done" looks like
A specific format (a table, a one-paragraph summary, a message), a specific length, a specific audience. "Done" left undefined gets you Claude's best guess at done, which may not match yours.
Ask for the first pass before you ask for the polished version
See the structure and the approach before refining tone and formatting. Correcting direction on a first pass is far cheaper than re-explaining after a polished version went the wrong way.
Turn what works into a repeatable prompt
Once a task is running well, save the exact instruction that produced it. Most of the value in Claude Cowork comes from turning one-off wins into a workflow you reuse every week without re-explaining it.
Want to see this method run against a real recurring task, start to finish? Read a full session walkthrough, or if you don't have a dedicated ops specialist, see what you can produce yourself with it.
Coaching designed
to end.
Reading the method is one thing; having someone check your first attempts against your actual recurring tasks is another. Three promises, in writing, if you bring it to a session:
Independence Guarantee
On the Deep Dive Programme you'll be working independently inside six sessions, or we'll keep going: up to two further sessions free.
24-Hour Match
Tell us what you do; we'll match you with the right specialist within 24 hours. Guaranteed.
Things people
usually ask.
The task in plain language, the real files or data it needs, and a clear picture of what "done" looks like: format, length, audience. Claude fills gaps you leave open with guesses, so the fewer gaps, the closer the first pass lands.
No. Plain language about the task and the outcome works, as long as it’s specific. "Help me with this spreadsheet" invites a guess; "turn this export into a one-page summary my manager can read in two minutes" doesn’t.
Experimenting works eventually, but it’s slow, and most of the value gets lost if you don’t save what worked. This teaches the structure that gets a usable result faster, and the habit of turning a win into a workflow you keep using.
This guide covers the method. Boffin Hub’s Claude Cowork coaching applies it live to your real, recurring tasks, with someone checking your first attempts, which is where most people get unstuck faster than reading alone.