- Describe the expected deliverable before choosing the assistant’s available actions.
- Start with a clearly bounded set of data and tasks.
- Separate preparation, approval and execution in the workflow.
Put enterprise adoption in context
The expanded PwC–Anthropic partnership announcement of 14 May 2026 describes enterprise use of Claude and its tools. It is an announcement by a vendor and partner, not a controlled study that predicts outcomes for another deployment.
For a team considering Cowork, the central question is which workflow to entrust to the assistant. The aim is not to grant every available permission. It is to define useful work, sufficient context and a reliable way to inspect the result. Exact capabilities must be checked in the plan and environment used.
Choose a task with a visible result
A good candidate produces a deliverable the team knows how to evaluate: a preparation note, document comparison, proposed classification or first draft of a dossier. Work needs a beginning, an end and quality criteria. A broad request such as “manage my business” does not provide that structure.
Choose a recent example and describe how it was completed. Identify useful files, information that should not be used and points requiring business judgement. This preparation lets you compare assisted output with expectations and refine instructions without accumulating abstract rules.
Prepare bounded, coherent context
Gather only the sources needed for the scenario. Check versions, names and possible contradictions. Provide the deliverable format, intended audience and essential elements. The assistant should also know how to report missing information.
Accessible sources should match the user’s permissions and role. For an initial trial, use demonstration data or an approved scope. Document granted access and its purpose. A new need may justify expanding context after examining what the expansion enables.
Create a useful approval point
The reviewer should be able to understand the work performed. Ask for a distinction between retrieved facts, assumptions and points to confirm. When an external action is contemplated, its content and destination should be shown before execution.
An assistant may prepare an email or update without automatically sending or applying it. The appropriate autonomy level depends on the process. The pilot identifies common errors and review effort, then informs what can be simplified while retaining control.
Three scenarios to explore
First illustrative scenario: prepare a meeting from approved documents, including context, questions and an agenda. Second: compare dossiers against a provided matrix, flagging missing information. Third: organise recurring work using a template and a list of items still requiring verification.
These examples are needs to test, not a promise that every step is available in every Cowork configuration. Check features, integrations and account conditions before writing an internal tutorial. Keep one simple scenario that can be replayed after an update.
Decide next steps with the team
At the end of the pilot, examine several deliverables and their corrections. Ask users what helps, what slows them down and what they cannot confidently verify. A well-written response may still require substantial work.
The next step might be training, improved source material or expansion to another workflow. Assign ownership of the usage guide and change tracking. Adoption relies on maintaining shared practice beyond the first demonstration.
Sources & methodology
This insight combines cited publications with editorial analysis. Illustrative examples are not client results. Vendor features and terms may change.