Team Rollout Playbook

The Scenario

You're the head of a 10-person strategy and operations team. After using Cowork yourself for two months, you're convinced it can transform how your team works. Your VP has approved a pilot: 10 seats, 90 days, and a clear success/fail framework. If it works, the department of 60 gets licences next quarter.

The pressure is real. If people fumble the onboarding, hit rate limits on day one, expose client data by pointing Cowork at their entire Documents folder, or produce AI-sounding emails that clients notice — the pilot fails and the broader rollout dies.

You need a playbook. Not a "tips and tricks" guide. A structured programme that gets 10 people from zero to productive within 30 days, with guardrails that prevent the mistakes you made when you were learning.

Prerequisites

• Claude Desktop with Cowork enabled on your own machine (so you can verify recommendations)
• Familiarity with the plan tiers (Pro, Max, Team Standard, Team Premium) and their feature differences
• Knowledge of your team's current workflows, tools, and pain points
• Understanding of your organisation's security and compliance requirements

Step 1: Define the Team Profile

Before choosing plans or configuring anything, document who you're onboarding. Create a file called team-rollout-playbook.md and start with:

Team composition:

• List all 10 roles (e.g., 1 team lead, 3 analysts, 2 project managers, 2 client-facing consultants, 1 coordinator, 1 data specialist)
• For each role, identify the 2-3 tasks they do most frequently that Cowork could handle
• Note their technical comfort level (high/medium/low)

Current tool landscape:

• What tools does the team already use? (Google Workspace, Microsoft 365, Slack, Salesforce, Asana, etc.)
• Which of these have Cowork connectors available?
• Where are the biggest time sinks in current workflows?

Security requirements:

• Does the organisation handle regulated data? (Financial, healthcare, personal data)
• What are the data classification levels? (Public, internal, confidential, restricted)
• Are there existing policies about AI tool usage?

Checkpoint: Your playbook opens with a detailed team profile covering roles, tasks, tools, and security context.

Step 2: Select the Right Plan

Based on your team profile, recommend a plan tier. This isn't straightforward — the wrong plan wastes money or leaves the team without critical features.

Evaluate each option:

10 x Pro ($20/seat/month = $200/month):

• Full Cowork access
• No centralised admin controls
• Each user manages their own privacy settings
• No SSO, no domain verification
• Pro: Cheapest. Con: No admin visibility or control.

10 x Team Standard ($25/seat/month = $250/month):

• All Pro features plus admin console
• SSO and domain verification
• Centralised privacy controls (no-training default)
• Con: Doesn't include Claude Code or full Cowork capabilities on all tiers

10 x Team Premium ($100-150/seat/month = $1,000-1,500/month):

• Full Cowork and Claude Code
• Everything in Team Standard
• Higher rate limits
• Con: Significant cost increase

In your playbook, document:

• Your recommended plan with justification
• Which features drove the decision
• What the team loses by not choosing the tier above
• Budget implications for the 90-day pilot

Checkpoint: Your playbook includes a plan recommendation with cost analysis, feature justification, and limitations noted.

Step 3: Design the Security Framework

This section will make or break your CISO's approval. Document:

Data classification rules for Cowork:

• What data types are approved for Cowork processing? (Internal documents, de-identified data, public information)
• What's explicitly banned? (Client PII, financial records, regulated data, credentials)
• Where's the boundary? (Summarising a contract is approved; uploading the contract with client financials isn't)

Working folder policy:

• Mandatory: All team members must create dedicated working folders for each task
• Banned: Pointing Cowork at Documents, Desktop, or any folder containing mixed data
• Recommended: A standard folder structure everyone uses (e.g., ~/Cowork-Workspace/[project-name]/)

Computer Use policy:

• Enabled or disabled for the pilot? (Recommend disabled unless specific use cases require it)
• If enabled: mandatory clean-desktop policy before each session
• Screen sharing etiquette: no Computer Use during meetings or when sensitive information is on screen

Privacy settings:

• On Team plan: verify that the no-training default is active (check Admin console)
• On Pro plan: provide step-by-step instructions for each user to opt out of training data individually
• Document what happens to conversation data: stored locally, not accessible via audit logs or compliance API for Cowork sessions

Incident response:

• What should a team member do if they accidentally process sensitive data?
• Who do they contact?
• What remediation steps are available?

Checkpoint: Your playbook includes a comprehensive security framework covering data classification, folder policies, Computer Use policy, privacy settings, and incident response.

Step 4: Build Shared Configuration Assets

Create the shared files that every team member will use. These go into a shared-config/ folder in your playbook:

team-context.md — Facts about the team that every Cowork session should know:

• Company name, industry, and key clients
• Team structure and roles
• Reporting standards and formatting rules
• Key dates and deadlines

brand-voice.md — Writing standards (see Domain 3 tutorial for detailed guidance):

• Voice characteristics
• Approved and banned vocabulary
• Formatting rules
• Before/after examples

cowork-usage-guidelines.md — The team's rules for using Cowork:

• Approved use cases (drafting, analysis, file processing, scheduling)
• Banned use cases (processing regulated data, making commitments to clients, final-draft communications without human review)
• Quality gates: "Every Cowork output must be reviewed by a human before leaving the team"
• Rate limit awareness: "Plan your heavy tasks for morning; save simple tasks for afternoon when limits may be tighter"

shared-skills/ — If the team has custom skills (e.g., /humanise, /report-format), include them here with installation instructions.

Checkpoint: You've created shared configuration files covering team context, brand voice, usage guidelines, and any shared skills.

Step 5: Design the Onboarding Curriculum

Structure the 90-day pilot into three phases:

Week 1-2: Foundations (All 10 team members)

Week 3-6: Adoption (Role-specific workflows)

Each person should have 2-3 assigned tasks they complete using Cowork during this phase. Pair advanced users with less confident ones.

Week 7-12: Integration (Independent usage with monitoring)

• Remove training wheels: team members design their own workflows
• Weekly 15-minute check-ins to troubleshoot and share discoveries
• Track usage metrics (see Step 7)

Checkpoint: Your playbook includes a phased onboarding curriculum with specific activities for each week and role-specific workflow recommendations.

Step 6: Create the Training Materials

For each phase, create a one-page reference sheet:

Quick Start Card (laminated desk reference):

• How to open Cowork and select a working folder
• The five rules (dedicated folder, review execution plan, never process regulated data, British English, human review before sending)
• Common prompts for the team's top 3 use cases
• Who to contact for help

Troubleshooting FAQ:

• "Cowork isn't showing the Cowork tab" — Check your plan tier, ensure Claude Desktop is updated
• "My task stopped halfway" — Your computer went to sleep or the app was closed. Keep it running.
• "Cowork used American English" — Check your Project Instructions. Add an explicit British English rule.
• "I hit a rate limit" — Rate limits reset every 5 hours. Schedule heavy tasks earlier in the day.
• "Cowork tried to access files outside my working folder" — Check your folder scope. Report this to [you] as a potential configuration issue.

Checkpoint: Quick Start Card and Troubleshooting FAQ created and ready for distribution.

Step 7: Define Success Metrics

Your VP needs to see data at the 90-day mark. Define what success looks like:

Adoption metrics:

• % of team members using Cowork at least 3x per week by week 6
• Target: 80% (8 out of 10)

Productivity metrics:

• Average time saved per week per person (self-reported, tracked in a shared spreadsheet)
• Target: 2+ hours per person per week by week 8

Quality metrics:

• % of Cowork outputs used with minimal editing (< 5 minutes of revision)
• Target: 70% by week 8

Security metrics:

• Number of security incidents (sensitive data processed, folder scope violations)
• Target: Zero

Satisfaction metrics:

• Team satisfaction survey at day 30 and day 90
• Target: 7+ out of 10 average

Create a simple tracking spreadsheet or document where team members log their usage, time savings, and any issues.

Checkpoint: Success metrics are defined with specific targets, and a tracking mechanism is in place.

Step 8: Compile the Final Playbook

Bring everything together into a single comprehensive document:

1. Executive Summary — One paragraph: what the pilot is, how many people, what plan, what success looks like
2. Team Profile — Roles, tasks, tools, security requirements
3. Plan Selection — Recommendation with justification and cost
4. Security Framework — Data classification, folder policy, Computer Use policy, privacy, incident response
5. Shared Configuration — Context files, brand voice, usage guidelines, skills
6. Onboarding Curriculum — 90-day phased plan with weekly activities
7. Training Materials — Quick Start Card, FAQ
8. Success Metrics — Adoption, productivity, quality, security, satisfaction targets
9. Risk Register — Top 5 risks to the pilot and mitigations
10. Appendix — All shared configuration files included

Checkpoint: The playbook is complete, self-contained, and ready to hand to your VP for approval.

Expected Output

Your deliverable is a ready-to-use team rollout playbook:

• team-rollout-playbook.md — the master document with all nine sections
• shared-config/ folder with team-context.md, brand-voice.md, cowork-usage-guidelines.md
• Quick Start Card and Troubleshooting FAQ
• Success metrics tracking template

This isn't a "how to use Cowork" guide. It's an operational deployment plan that covers technology selection, security, training, configuration, and measurement. The kind of document a VP signs off on.

Extension Challenges

1. Scale the playbook to 60 people — Adapt the 10-person plan for your full department. What changes? (Hint: you'll need champions per team, a self-service onboarding path, and a support escalation structure.)

2. Add a cost-benefit analysis — Calculate the total cost of the pilot (licences + training time + your time as project lead) against the projected productivity gains. Present this as a one-page business case addendum.

3. Create a "Cowork Champion" programme — Identify 2-3 advanced users from the pilot group who'll become peer trainers for the broader rollout. Design their training curriculum and define their responsibilities.