Roll out Claude
For managers running adoption and enablement leads.
Adopting Claude as a team is mostly an organization problem, not a model problem. These posts cover the patterns that decide whether week-four adoption looks different from week-one: how to onboard skeptical engineers, how to corral mixed Claude Code fleets, how to turn a CLAUDE.md file into shared team standards, and how to know when a workshop will land and when it'll bounce.
Posts in the Roll out Claude track
How to Train AI on Your Company's Knowledge: A Field Guide for Non-Engineers
Teach your AI how your best people decide, not just what documents say. A field guide to training AI on company knowledge across eight business roles.
Deep diveStop Loading UX Research Reports Into Claude One at a Time. Build a Corpus Your Whole Team Can Query.
Most UX research repository AI setups fail because the structure blocks retrieval. Here's how research teams build a corpus any LLM can query on demand.
Deep diveHow to Onboard Engineers to Unfamiliar Codebases in Week One With Claude Code
Claude Code codebase onboarding is ending the 30-day ramp. The bottleneck was never reading speed; it was senior-engineer translation capacity. Here is what changes when new engineers hold the tool, and where the new /team-onboarding command fits.
Deep diveThe Engineering Manager's Guide to Governing Agentic Development
Govern agentic development by encoding team standards into tooling, not mandating keystrokes. A framework for engineering managers adopting Claude Code at scale.
Deep diveYour Team Bought AI Licenses Three Months Ago. Why Aren't They Using Them?
AI adoption stalls after license purchase because teams default to training when they should be redesigning workflows. The research is clear on what works instead.