Claude and Cowork merge: what changes in everyday work

A rollout does not mean access for every account

The new experience starts gradually with Pro and Max across web, desktop and mobile. Team and Free are planned to follow; Anthropic says Enterprise changes receive at least 30 days’ notice. Check the account actually being used. One colleague may already see the new interface while another workstation still offers separate chat and Cowork options.

This matters when introducing the tool at work: training material should show the observed experience and its verification date. Avoid instructions that explain only one particular button. Also document the task, expected deliverable and necessary permissions. Those descriptions remain understandable when the navigation changes.

Describe the task through its intended deliverable

A recurring report with a manageable set of sources is a useful starting point. For a trades business, approved project lists might feed a Friday overview of delayed jobs. Specify the reporting period, responsible people, deviations from plan and unanswered questions. Ask for an editable table and a short narrative for an internal meeting.

Also explain how missing information should be handled: an unknown completion date stays unknown, and a suspected cause becomes a question. The first run should leave original files untouched. You can then compare the output directly with the source and establish whether the process has sufficiently clear inputs in the first place.

A useful brief could read: turn these three approved meeting records into one page of decisions, owners and deadlines; flag unclear ownership; leave source files unchanged. Review the result against those same three categories. If the task later needs another system, reassess its scope. The initial goal is not blanket authorization to search every reachable folder or business application.

Distinguish cloud work from local dependencies

The new experience can continue substantial tasks in the cloud. Work involving files or applications on your computer still needs the desktop app open. Assigning a task from a phone does not remove that dependency. For the pilot, list which inputs are available online and which exist only on a particular device.

Test these situations separately. A report using connected online data should be able to continue after you close the page. A task involving a local customer folder should visibly wait or fail when the computer cannot be reached. The team needs an understandable status and must not mistake an old report for the current result.

Choose documents, presentations and design deliberately

Claude Docs, Slides and integrated Design are part of the new way of working. In practice, retain three distinct acceptance criteria: a document must be clear and complete, a presentation must support a decision, and a design must meet the agreed visual requirements. A shared conversation does not make these reviews interchangeable.

In the project-report example, review the table first. Then create a short meeting brief and only afterwards the slides. If an important number changes, trace it through every output. Save the accepted version with its date, responsible person and underlying sources. That is the operational handoff point.

Connected work still needs clear handoffs

Give the first task a narrow working scope. Reading a project list and sending a customer update are different decisions. Identify who accepts business changes and when Claude should ask questions. An instruction such as “take care of the projects” provides too little guidance.

Measure elapsed working time from the brief to the reviewed output and count manual corrections. Record whether friction came from a missing connection, unclear data or a model mistake. Improvements can then target the actual cause: sometimes the team needs a better template, sometimes cleaner reference data, and only afterwards an additional integration.

Questions about the new Claude experience

Will existing Cowork tasks disappear? Anthropic describes continuity for existing conversations, projects, artifacts and connections. Still check important ongoing work in your own account.

Does every employee immediately need new training? A short walkthrough of a real, bounded task is usually more useful than a tour of every menu. Can everything run without a computer? No: local files and desktop tools remain device-dependent. The System Check helps identify a suitable process and its data paths first.

Can new users start with Dispatch? Current help says no. Existing users can keep using Dispatch for now. Instructions for new tasks should therefore start from capabilities actually available in the account.