title: "Team Adoption" last_updated: 2026-03-21 status: experimental difficulty: advanced prerequisites: [07-session-architecture]

Team Adoption

Coming in V3. This module is scaffolded with an outline.

How does my team adopt agentic workflows?

The adoption curve — Most teams have a champion, a few early adopters, and a skeptical majority. Each group needs different things.
Shared configuration — Creating team-wide CLAUDE.md / AGENTS.md files that encode team conventions. The config becomes a living style guide.
The onboarding path — A structured sequence for new team members: install → first task → team config → team workflows.
Standardized workflows — Defining team patterns for common tasks: PR review, bug triage, feature development, documentation updates.
Knowledge sharing — How to capture and share what works: team pattern libraries, internal case studies, retrospectives.
Governance — Who can modify team configs? How do you handle conflicting preferences? What's the review process for new patterns?
Measuring impact — Metrics that matter: cycle time, defect rates, developer satisfaction. Metrics that mislead: lines of code, token usage alone.
Common adoption failures — Mandating tools without training, ignoring security concerns, over-automating too fast, not measuring.

Claude Code: Team settings, shared hooks, org-level CLAUDE.md, enterprise features
Codex CLI: Team configuration, shared AGENTS.md, organization patterns

Audit your current team's development workflow for agentic opportunities
Create a team CLAUDE.md/AGENTS.md that encodes your team's top 10 conventions
Design an onboarding guide for a new team member's first week with agentic tools
Run a team retrospective after 2 weeks of agentic workflow adoption