Claude Cowork Setup: The 30-Minute Fix Most People Skip

Most People Use Claude Cowork Wrong. Here's the 30-Minute Fix.

Claude Cowork has been out since January. I've been using it daily — for client work, for content, for managing this business. And the gap between "Cowork out of the box" and "Cowork properly set up" is enormous.

It's not a prompting problem. It's a setup problem.

Nav Toor published a thread this week listing 17 best practices after running 400+ sessions. Some of it is power-user territory. But the core insight is right: the people getting great results from Cowork aren't writing better prompts. They're spending 30 minutes on Claude Cowork setup that most people skip entirely.

Here's what actually matters — especially if you're just getting started.

The Single Biggest Mistake: Treating It Like ChatGPT

Open ChatGPT. Type a question. Get an answer. That's the mental model most people bring to Cowork.

It doesn't work.

Cowork isn't a chatbot. It's closer to a new hire. And a new hire who knows nothing about you, your work, or your preferences is going to produce generic output. Every single time.

The difference is that a human new hire picks things up over weeks. Cowork has no memory between sessions. Every conversation starts from zero. So if you don't give it context upfront, you're onboarding a new employee from scratch every time you open the app.

That sounds like a limitation. It's actually a feature — because it means there's no context bleed, no hallucinated memories from three weeks ago. But it does mean you need to build your context into files.

Step 1: Tell Claude Who You Are (5 Minutes)

Create a folder in your working directory. Call it 00_Context so it sorts to the top.

Add one file: about-me.md.

This isn't your CV. It's the stuff a colleague would know after working with you for a month. What you do. Who you serve. What your current priorities are. What kind of output you expect.

Mine is about 15 lines. It covers my name, my role, the business, the kind of clients I work with, and a note that I write in UK English. That's it.

Without this file, Claude writes for a generic professional. With it, Claude writes for me. The difference shows up in the first output.

Step 2: Set Your Global Instructions (5 Minutes)

Go to Settings → Cowork → Edit next to Global Instructions.

Most people leave this blank. That's like buying a car and never adjusting the mirrors.

Global Instructions load before everything else — before your files, before your prompt, before Claude even looks at your folder. They're your baseline.

Here's roughly what mine says: read context files first. Always ask clarifying questions before executing. Show a plan before taking action. Default to .docx for documents. No filler language. If confidence is low, say so.

This means even a lazy, rushed prompt produces calibrated output. Claude always knows who I am. Always reads the right files first. Always asks before guessing.

Step 3: Give It Your Voice (10 Minutes)

If you're using Cowork for any kind of writing — emails, reports, content, client comms — add a brand-voice.md file to your context folder.

Describe how you write. Not in abstract terms ("professional yet approachable") but with actual rules. Words you use. Words you never use. How long your paragraphs are. Whether you use contractions. Two or three paragraphs of your actual writing as a reference.

I have a full voice guide for this site. It bans phrases like "harness the power of" and "in today's rapidly evolving landscape." It specifies UK English. It says every claim needs a specific example, not a generalisation.

The result: Claude stops writing like a marketing department and starts writing like me. Not perfectly — but close enough that editing takes minutes instead of a full rewrite.

This is the file that compounds the most. Every time Claude produces something that doesn't sound right, I add one line to the voice file. Permanent fix.

Step 4: Define "Done" Instead of Describing the Process

This is the mindset shift that changes everything.

Bad prompt: "Help me with my files."

Good prompt: "Organise all files in this folder into subfolders by client name. Use the format YYYY-MM-DD-descriptive-name for filenames. Create a summary log of every change. Don't delete anything."

The second prompt defines the end state, the naming convention, the output artifact, and the safety constraint. Claude can execute it autonomously. You can walk away.

Every task prompt should answer three questions: What does "done" look like? What are the constraints? What should Claude do when it's uncertain?

That last one is underrated. Most people give clear instructions for the happy path and say nothing about edge cases. Tell Claude: "If you're not sure about a classification, flag it instead of guessing. If a date isn't clear, mark it as VERIFY." This turns Cowork from a tool that sometimes makes errors into a tool that tells you exactly where it needs your judgement.

Step 5: Ask for a Plan Before Execution

Add this to your Global Instructions: "Show a brief plan before taking action on any task. Wait for my approval before executing."

One line. Prevents 90% of disasters.

Without it, Claude reads your prompt and immediately starts executing. Sometimes it's spot on. Sometimes it misinterprets one word and reorganises three months of files in the wrong direction.

With the plan step, you get a 30-second review. "I'm going to create these six subfolders, move these files, rename them using this convention. Proceed?" You scan it. Looks right. Approve. Done.

The cost is 30 seconds per task. The benefit is never having to undo a 20-minute autonomous mistake.

Beyond the Basics: What to Explore Next

Once you've done the Claude Cowork setup above, you've already overtaken most users. Here's what to look at next.

Plugins. These are bundles of skills for specific domains — sales, marketing, data analysis, productivity. Install two or three that match your role. They're free and they give Claude specialised knowledge it doesn't have by default. You can browse them in Settings → Plugins.

Scheduled tasks. Type /schedule in any session. Claude walks you through setting up recurring tasks — a Monday morning briefing, a Friday status report, a daily competitor check. The catch: they only run when your computer is awake and Claude Desktop is open. Plan around that.

Connectors. Link Claude to Gmail, Slack, Google Drive, Notion, Asana, or any of the 50+ available integrations. Scheduled tasks combined with connectors is where Cowork stops being a task executor and starts being an autonomous system. "Every Monday, check my Slack for product feedback and create a summary in Google Drive." That kind of thing. If you've read my comparison of Cowork and OpenClaw, this is where Cowork closes the gap on proactive automation.

Sub-agents. For complex tasks with independent parts, Claude can spin up multiple agents working in parallel. "Research four vendors simultaneously and give me a comparison table." The task that takes 40 minutes sequentially takes 10 in parallel. Use them on Opus 4.6 for best results. For more on where AI agents are heading, see my piece on the future of AI agents.

The Pattern Behind All of This

Every good Cowork practice follows the same principle: invest in setup, reduce prompting.

The people struggling with Cowork are writing long, detailed prompts for every task and getting inconsistent results. The people getting great output spent 30 minutes building their context architecture — and now write ten-word prompts that produce client-ready deliverables.

This is the shift from ChatGPT-era thinking to Cowork-era thinking. ChatGPT rewarded prompt engineering. Cowork rewards system engineering.

If you want help setting this up properly — context files, voice guide, workflows, the lot — that's exactly what I do in a Cowork setup session. 90 minutes. You walk away with everything configured and your first real workflows running.

Credit to Nav Toor's thread for sparking this post. His full 17 practices are worth reading if you want the power-user version. This is the "start here" version.