Anthropic 的增长营销负责人 Austin Lau 解释了何时使用 Claude Cowork、如何决定将哪些工作流委托给它，以及具体的上手步骤。6 月 4 日，Austin 将分享他如何利用 Claude Cowork 开展营销工作。
注册参加网络研讨会
- 分类企业 AI
- 产品Claude Cowork
- 日期2026 年 6 月 3 日
- 阅读时间5分钟
- https://claude.com/blog/best-practices-for-getting-started-with-claude-cowork
2024 年，我们使用的是聊天窗口中的 Claude。你提出问题，得到答案，但如何将这个答案转化为有用的成果，完全取决于你自己。2025 年，Claude Code 让工程师们以令我们其他人有些羡慕的速度交付成果。
今年，我们都可以通过 Claude Cowork 迎头赶上。
去年，我开始将 Claude Code 用于聊天功能无法处理的、冗长且多步骤的任务。一周之内，我从完全不知道终端是什么，发展到能够构建出在 30 秒内完成原本需要 30 分钟任务的 Claude Code 工作流。我当时之所以用 Claude Code 做非技术性工作，是因为 Claude Cowork 那时还不存在。
现在，我 90% 的工作都在 Claude Cowork 中完成。在这篇文章中，我将向你展示如何判断哪些任务适合放在这里，通过我工作中的真实案例进行讲解，并让你在大约十分钟内完成你的第一个可交付成果。
使用 Chat 与 Claude Cowork 与 Claude Code 的区别
如果你的工作是非技术性的知识型工作——邮件、演示文稿、电子表格、文档、会议，以及“你能整理一份关于这个的摘要吗”——那么 Claude Cowork 就是为你准备的。你不需要懂编程。你不需要知道什么是“智能体”或如何构建一个。
如果你在过去两年里，一直是在 100 多个标签页和文件中打开一个 AI 聊天标签页，把提示词或问题复制粘贴进去，再把答案复制粘贴出来，那么你已经知道如何使用 Claude Cowork 了。它就是这样，只是省去了复制粘贴的步骤。
同一个 Claude 模型为聊天、Claude Cowork、Claude Code、Claude Design 以及 Claude 出现的所有其他场景提供支持。这些是用于不同类型工作的独立工作空间，但内部运行的是相同的模型。以下是一个帮助你思考何时使用哪种工具的框架：
- 聊天通常是知识工作者初次接触 Claude 的方式。你把自己已有的内容交给 Claude：上传文件、粘贴文本、描述当前情况，然后获得答案。聊天适用于获取答案、头脑风暴以及边想边说。
- Claude 桌面应用中的 Claude Cowork 则反其道而行之。它不再让你把工作带到 Claude 面前，而是把 Claude 带到你的工作中。你将它指向电脑上的一个文件夹，把它连接到你已经使用的应用，然后告诉它你想要完成什么。使用 Claude Cowork，你只需描述一个预期结果，然后离开，回来时就能看到已完成的工作。
- Claude Code 专为构建和发布软件的开发者打造。如果你的工作内容存在于代码之中，就从这里开始。
很多人不知道，Claude Cowork 和 Claude Code 在底层运行的是同一个引擎。
什么时候应该使用 Claude Cowork？
理解何时使用 Claude Cowork 与何时使用聊天，是大多数人感到困惑的地方，所以这是我的经验法则：
- 如果你想要的内容只需几次交互就能完成，比如一个问题、一次解释、一场头脑风暴或一次快速验证，那就使用聊天。
- 如果你需要的是一个可交付的成果，例如，一份别人会打开的文件、一份别人会演示的幻灯片、或者一个需要整理排序的电子表格，那就使用 Claude Cowork。它适用于任何涉及多个步骤、或涉及多个文件/文件类型、或多个应用的任务，也适用于那些你将其描述为“任务”而非“问题”的场景。使用 Claude Cowork，你是在把工作委托给 Claude。
以下是一些划分界限的例子：
| 示例问题或任务 | 使用方式 |
|---|---|
| 我们的业务回顾会议应该涵盖哪些内容？ | 聊天 |
| 读取这个 Google Drive 文件夹中过去三个月的会议记录，并使用我们的模板为我制作一份 QBR 演示文稿。 | Claude Cowork |
| 如何用 VLOOKUP 查找数据？ | 聊天 |
| 检查我的所有电子表格，并把所有的 VLOOKUP 函数改为 INDEX MATCH。 | Claude Cowork |
| 为这个页面建议一个更好的标题标签和元描述。 | 聊天 |
| 使用这张表格中这 30 个页面的新标题标签和元描述，并通过 CMS 连接器更新它们。 | Claude Cowork |
最常见的错误是凡事都用聊天，从未体会过 Claude Cowork 能带来的不同。相反的错误则是把一次性问题交给 Claude Cowork，然后干等着，而聊天本可以在五秒内回答。
适合 Claude Cowork 任务的五个要素
如果你刚开始使用，不确定该把哪些项目交给 Claude Cowork，可以用这份清单来检验。你不需要满足全部五个条件，但一个好的候选任务应该符合其中几项：
- 输入不止一项。多个文件、整个文件夹，或者一个文件加上一些连接器。如果只有一个输入，聊天通常就能处理得很好（不过你仍然应该尝试一下）。
- 输出一个文件。你需要一个可以附加、展示、分享或改作他用的交付物：一份文档、一个演示文稿、一张电子表格或一个 CSV 文件。
- 你会再次做这件事。一次性任务没问题，但重复性任务才是最佳选择。你可以把它们安排在上班前自动运行。
- 你清楚什么样的结果才算好。你熟悉输出的形态，所以能在 15 秒内判断出结果是正确、错误，还是完成了 70%。
- 中间部分是最无聊的。思考集中在开始（决定你想要什么）和结束（判断结果是否正确）。中间的一切（提取、编译、核对、重新格式化）才是你交出去的部分。
我在 Anthropic 如何使用 Claude Cowork
我在 Anthropic 负责增长营销，所以我的例子都带有营销色彩。不要指望从中找到可以直接照搬的工作流程——从长远来看，这没什么帮助。你要观察的是每个例子如何命中上面清单中的几项，因为这才是你在自己的 Claude Cowork 工作流中需要寻找的模式。
每日简报
营销人员每天收到的 Slack 频道和邮件数量可能让人应接不暇。我设置了一个"每日简报"任务，每天早上 6 点运行。Claude Cowork 连接了我的 Slack 和 Gmail，我的提示词告诉它查看我未读的邮件和我关注的频道，将它们分类整理，并生成一份简短报告。
这份报告给了我一份需要关注事项的摘要，按类型分组的标记邮件、频道摘要，以及任何可能影响营销的隔夜产品相关事件。任何被 Slack 和邮件淹没的人都可以运行这个工作流的某个版本。
预算进度跟踪
我工作的一部分包括效果营销的预算进度跟踪。这是那种没人愿意干的活，因为它既无聊又繁琐。许多效果营销团队在 Google Sheets 中跟踪每日支出和消耗率，以估算达成目标的进度。你要么手动从每个渠道导出每日支出并粘贴到表格中，要么花钱购买第三方工具来为你提取、转换和加载数据。
使用 Claude Cowork，我连接到 Google Ads 和 Meta Ads，并在桌面应用中创建一个实时工件（基本上是一个 HTML 仪表盘），它会自动拉取我的每日支出并为我计算进度。我还可以直接用通俗易懂的英语告诉 Claude 如何筛选我的广告活动以及需要注意什么。
对照上面的清单来运行：多个数据源输入（每个渠道的支出），一个文件输出（这里是仪表盘），我不断重新运行它，而中间部分就是那种我绝对不想自己做的、毫无灵魂的下载-复制-粘贴苦差事。由于广告平台通过我的连接器集成，我可以随时更新这个仪表盘。
报告
我不再需要导出一堆 CSV 文件、构建数据透视表或手动合并文件，而是将 Claude Cowork 连接到 Google Search Console。它会拉取我关心的数据（查询词、国家、页面），并将其整合到一个单一的表格中，而不是像手动导出数据时 Google 默认的每个维度一个 CSV 文件。
我还为 Claude 提供需要关注哪些内容的上下文，比如查看最近七天与之前七天的对比，仅筛选特定国家，标记任何有显著变化的数据，并按照我想要的模板撰写报告。之后，我可以继续调整任何内容，或向 Claude 提出后续问题。
有了 Claude Cowork 的定时调度功能，这项任务每周都会自动运行。过去写报告每周大约要花我 30 分钟；现在只需 5 分钟，而这 5 分钟我花在了需要我判断的部分：补充缺失的背景信息，以及推敲需要重点强调的内容。
这些只是我使用 Claude Cowork 的一些例子，但远未触及它的全部潜力。请查看我写的另一篇文章，其中详细介绍了另一个复杂用例的完整操作流程，涵盖了插件、技能、本地 MCP 和 Dispatch，以获取更多最佳实践。
你的前 10 分钟：Claude Cowork 快速上手
第一次打开这个应用？以下是入门方法：
- 打开 Claude 桌面应用，切换到 Claude Cowork 标签页。
- 给 Claude 一些可处理的内容。拖入几个文件，指向你电脑上的一个文件夹，或者连接一个你常用的应用（如 Slack、Gmail、Notion、CRM 等）。平庸的 Claude Cowork 输出与出色的输出之间的区别，几乎从来不在你的提示词，而在于你是否提供了足够丰富的上下文供 Claude 处理。
- 告诉 Claude 你想要的结果。描述你最终希望得到的交付物，并提供任何必要的背景信息。
- 从一个你非常熟悉的真实任务开始。你会立刻看到它哪里强、哪里需要你提供上下文，而且你本来就知道什么样的结果才算“好”。
- 让 Claude 在开始前先问你问题。这是我养成的最有用的一个习惯。把它作为你提示词的一部分：在我们开始之前，先复述一遍我的要求以确保我们理解一致，然后尽可能多地向我提出澄清性问题。
这样做能暴露出你没想到要明确说明的事情，比如我们看的是哪个时间段、这里的“好”是什么意思、或者有哪些你知道但 Claude 不知道的边缘情况。陷阱在于，你假设 Claude 已经知道那些对你来说显而易见的事情。一开始回答五个问题只花你 30 秒。事后才发现同样的信息缺口，既费时间又费 token，而且修正起来很麻烦。
还是不确定该交办什么？问 Claude。Claude 有记忆功能，可以搜索你过去的对话，所以你可以问它你最常做哪些任务，以及哪些任务适合在 Claude Cowork 中尝试。
当我仍然会去用聊天功能时
我仍然大量使用聊天功能来探讨定位问题，在做出决定前对某个想法进行压力测试，或者问一些随机问题，比如为什么我的狗老是舔床。
重点不在于聊天是“旧”方式。聊天适用于输出是你脑海中的一个想法，而 Claude Cowork 适用于输出是你要交给别人的东西。
去创造点什么吧
选一件你每周都会做的重复性任务，试着用 Claude Cowork 来完成它，看看结果如何。最初几次任务可能会感觉有点别扭，但尝试几次后，你会很快从“这东西怎么用”转变为“接下来我该交给它什么”。
本文由 Anthropic 增长团队的 Austin Lau 撰写，表达了他对 Claude Cowork 的看法、使用模式和建议。
用 Claude 改变你组织的运作方式
Austin Lau, growth marketing lead at Anthropic, explains when to use Claude Cowork, how to decide what workflows to delegate, and concrete steps to get started. On June 4, Austin will share how he uses Claude Cowork for marketing.
Register for the webinar
- Category
- ProductClaude Cowork
- DateJune 3, 2026
- Reading time5min
- https://claude.com/blog/best-practices-for-getting-started-with-claude-cowork
In 2024, we had Claude in a chat window. You asked a question and you got an answer, but it was up to you to turn that answer into something useful. In 2025, Claude Code let engineers ship at a pace that made the rest of us a little jealous.
This year, we can all catch up with Claude Cowork.
I started using Claude Code last year for long, multi-step tasks that chat wasn’t equipped to handle. Within a week, I went from not knowing what a terminal was to building out Claude Code workflows that completed 30-minute tasks in 30 seconds. I was using Claude Code for non-technical work because Claude Cowork didn’t exist yet.
Now, 90% of my work happens in Claude Cowork. In this post, I'll show you how to tell which of your tasks belong there, walk through real examples from my own work, and get you to your first finished deliverable in about ten minutes.
Using Chat vs Claude Cowork vs Claude Code
If your job is non-technical knowledge work–emails, decks, spreadsheets, docs, meetings, and "can you pull together a summary of this”–then Claude Cowork is for you. You don't need to know how to code. You don't need to know what an "agent" is or how to build one.
If you've spent the last two years with an AI chat tab open among 100 other tabs and files, copy-pasting prompts or questions into it and copy-pasting the answers back out, you already know how to use Claude Cowork. It's that, minus the copy-pasting.
The same Claude models power chat, Claude Cowork, Claude Code, Claude Design, and every other place Claude appears. These are separate workspaces that you use for different types of work, but the same models run inside all. Here’s a framework for how to think about when to use which one:
- Chat is often how knowledge workers get introduced to Claude. You bring what you have to Claude: upload a file, paste some text, describe what's going on, and get an answer. Chat is for answers, brainstorming, and thinking out loud.
- Claude Cowork in the Claude desktop app flips that around. Instead of bringing your work to Claude, you bring Claude to your work. You point it at a folder on your computer, connect it to the apps you already use, and tell it what you want done. With Claude Cowork, you describe an outcome, step away, and come back to finished work.
- Claude Code is made for developers building and shipping software. If your work lives in code, start there.
Many people don't know that Claude Cowork and Claude Code run on the same engine under the hood.
When should you use Claude Cowork?
Understanding when to use Claude Cowork vs chat is the spot where most people get stuck, so here's my rule of thumb:
- Use chat if what you want fits in a few exchanges, like a question, an explanation, a brainstorm, or a gut check.
- Use Claude Cowork if what you need is a deliverable, for example, a file someone will open, a deck someone will present, or a spreadsheet to be sorted. Use it for anything that’s multi-step or touches more than one file/file type or more than one app, or that you'd describe as a task rather than a question. With Claude Cowork, you are delegating work to Claude.
A few examples of where the line falls:
| Sample question or task | Use |
|---|---|
| What should I cover in our business review meeting? | Chat |
| Read the last three months of meeting notes in this Google Drive folder and build me a QBR deck using our template. | Claude Cowork |
| How do I VLOOKUP something? | Chat |
| Go through my spreadsheets and change all the VLOOKUP to INDEX MATCH. | Claude Cowork |
| Suggest a better title tag and meta description for this page. | Chat |
| Use the new title tags and meta descriptions for these 30 pages from this sheet and update them using the CMS connector. | Claude Cowork |
The most common mistake is reaching for chat for everything and never feeling the difference Claude Cowork can make. The opposite mistake is handling Claude Cowork one-off questions, then waiting around for something chat would've answered in five seconds.
The five ingredients of a Claude Cowork-shaped task
If you’re not sure what projects to delegate to Claude Cowork when you’re first getting started, run them through this checklist. You don't need all five criteria, but a good candidate hits a few:
- More than one thing goes in. Multiple files, a whole folder, or a file plus some connectors. If there's only one input, chat probably handles it fine for the most part (you should still experiment).
- A file comes out. You need a deliverable that you can attach, present, share, or repurpose: a doc, a deck, a spreadsheet, or a CSV.
- You'll do it again. One-offs are fine, but recurring tasks are the sweet spot. You can schedule them to run before you're even at your desk.
- You already know what good looks like. You're familiar with the shape of the output, so you can tell in 15 seconds whether the output is right, wrong, or 70% there.
- The middle is the boring part. The thinking lives at the start (deciding what you want) and the end (deciding if it's right). Everything in between (extract, compile, reconcile, and reformat) is what you hand off.
How I use Claude Cowork at Anthropic
I manage growth marketing at Anthropic, so my examples are marketing-flavored. Don't read these looking for a workflow to copy—that's not going to be helpful in the long run. Watch how each one hits a few items from the checklist above, because that's the pattern you'll be looking for in your own Claude Cowork workflows.
Daily briefing
The number of Slack channels and emails a marketer receives every day can be overwhelming. I have a "daily briefing" task that runs every morning at 6am. Claude Cowork is connected to my Slack and Gmail, and my prompt tells it to review my unread emails and the channels I care about, sort them into buckets, and produce a short report.
The report gives me a TLDR of what to look into, flagged emails grouped by type, channel summaries, and any overnight product-related incidents that could have impacted marketing. Anyone drowning in Slack and email can run some version of this workflow.
Budget pacing
Part of my job includes budget pacing for performance marketing. It's the kind of work nobody wants because it's boring and tedious. Many performance marketing teams track daily spend and run rate in Google Sheets to estimate pacing to goal. Either you're manually exporting daily spend from each channel and pasting it into the sheet, or you're paying for a third-party tool to extract, transform, and load data for you.
With Claude Cowork, I connect to Google Ads and Meta Ads and create a live artifact (basically an HTML dashboard) in the desktop app that automatically pulls in my daily spend and calculates pacing for me. I can also just tell Claude in plain English how to filter my campaigns and what to look out for.
Run that against the checklist above: multiple sources in (every channel's spend), a file out (in this case it's the dashboard), I rerun it constantly, and the middle is the mindless soul-sucking download-copy-paste grind I absolutely do not want to do myself. Since the ad platforms are integrated through my connectors, I can update this dashboard at any time.
Reporting
Instead of exporting a pile of CSVs and building pivot tables or combining files manually, I have Claude Cowork connected to Google Search Console. It pulls what I care about (queries, countries, pages) and reconciles it into a single sheet, instead of Google's default of one CSV per dimension when you export data manually.
I also give Claude the context on what to focus on, like looking at the last seven days vs the prior seven, filtering to only specific countries, flagging anything that moved meaningfully, and writing up the report in the template that I want. From there I can go ahead and tweak anything or ask Claude follow up questions.
With scheduling in Claude Cowork, this runs automatically every week. Reporting used to take me ~30 minutes a week; now it takes five and I spend them on the part that needs my judgement: filling in missing context and workshopping the callouts.
These are just some examples of how I use Claude Cowork, but they barely scratch the surface. Check out another article I wrote that highlights a more detailed walkthrough of another complex use case that spans plugins, skills, local MCPs, and Dispatch for more best practices.
Your first 10 minutes with Claude Cowork
First time opening the app? Here’s how to get started:
- Open the Claude desktop app and switch to the Claude Cowork tab.
- Give Claude something to work with. Drop in a few files, point it at a folder on your computer, or connect an app you frequently use (Slack, Gmail, Notion, CRM, etc). The difference between a mediocre Claude Cowork output and a great one is almost never your prompt, but whether you're providing enough rich context for Claude to work with.
- Tell Claude the outcome you want. Describe the deliverable you want at the end and provide any necessary context.
- Start with a real task you know well. You'll see immediately where it's strong, where it needs context from you, and you already know what "good" looks like for it.
- Make Claude ask you questions before it starts. This is the single most useful habit I’ve built. Include this as part of your prompt: Before we begin, repeat my ask back to me so we're aligned, then ask me as many clarifying questions as you have.
This surfaces things you didn't think to specify, like which time period are we looking at, what does "good" mean here, or what edge cases do you know that Claude doesn't. The trap is assuming Claude already knows what's obvious to you. Answering five questions up front costs you 30 seconds. Finding those same gaps afterwards costs you time and tokens, and it's a pain to fix.
Still not sure what to hand off? Ask Claude. Claude has memory and can search your past conversations, so you can ask it which tasks you do most often and which ones to try in Claude Cowork.
When I still reach for chat
I still use chat extensively to talk through a positioning problem, pressure-test an idea before I commit to it, or to ask random questions like why my dog keeps licking the bed.
The point isn't that chat is the "old" thing. Chat is for when the output is a thought in your head, and Claude Cowork is for when the output is something you’ll hand to someone else.
Go build something
Pick one repetitive task you do every week, try using Claude Cowork for it, and see what comes back. The first few tasks might feel a little awkward, but after a few tries you'll quickly go from "how do I use this" to "what do I hand it next."
This article was written by Austin Lau, on the growth team at Anthropic, and expresses his opinions, usage patterns, and advice on Claude Cowork.