How should an engineering manager roll out Claude Code across a development team?
Claude Workshop teaches an engineering manager to roll out Claude Code with Delegate, Review, Own, a small champion group, and a 30/60/90 plan. The first 90 days prove one workflow on real pull requests before the rest of the team copies it. Large-rollout cohorts stay at 30-35 engineers.
How should an engineering manager roll out Claude Code?
Claude Workshop installs Delegate, Review, Own first. Name a small champion group from the mastery enablement model. Train the first cohort on the team's repository, then copy the same CLAUDE.md and review gates. For a large rollout, keep each cohort at 30-35 engineers.
What should the first 30 days install?
Days 1 to 30 put CLAUDE.md in the repo, pick champions, and run one bounded Claude Code workflow with a review gate. The manager scores review time and the share of AI-assisted work with explicit verification on a short pull-request sample. The methodology guide is the written method the team follows.
What changes at 60 and 90 days?
By day 60, champions teach the same workflow to the next group and MCP stays on an allowlist. By day 90, a large rollout can open a 30-35 person cohort once review evidence is consistent. Do not expand seats until reviewers can reject unreviewable agent work without a debate.
How the champion model scales
Mastery includes internal enablement and a champion model. Champions keep the standard short, update it after real runs, and sit in review until the rest of the team can apply Delegate, Review, Own without them. That is how a manager rolls out Claude Code without turning every squad into a private experiment.
Should the whole team start on the same day?
No. Start with champions, then a first cohort, then a 30-35 person large-rollout cohort. Mixed-experience groups fit the intermediate shape (usually 12-35). Experienced groups fit mastery (usually 8-24). The sequence matters more than a company-wide kickoff.
Selected research
Representative field notes connected to this topic.
Spotify Portal Cut Claude Tokens 90%
Spotify’s Portal post sparked a real debate about saving Claude Code tokens by delegating bulk work to helper models.
Claude Ported a 1993 Amiga Game
A 1993 Amiga-to-Godot port shows how Claude can read old assembly, and why evidence matters more than a clean diff.
Claude Code 2.1.139 team conventions
Claude Code 2.1.139 team conventions: a CLAUDE TOC, red-folder approvals, data-class tags on MCP connectors, and a weekly retro note.
claude_code_stop_hook_block_cap in Claude Code 2.1.143
What claude_code_stop_hook_block_cap searchers need: the Claude Code 2.1.143 hook change handled as convention, with rollback paths and receipts.
Claude Code 2.1.142 team conventions
Claude Code 2.1.142 team conventions for parallel agent streams: a skill index, a hook budget, a CLAUDE TOC, and red-folder approvals.
Claude Code 2.1.141 team conventions
Claude Code 2.1.141 team conventions: a CLAUDE TOC, red-folder approvals, data-class tags on MCP connectors, and a weekly retro note.
Related training topics
Bring this into your team
We tailor the training to your codebase, adoption stage, and review standards.
Book a 15-minute sync