Leading AI-Adopting Teams

🚧 Expanding

Adopting AI tools is less a tooling rollout than a change-management problem wearing a tooling costume. Your team is somewhere on a spectrum from “already automating half their job” to quietly worried the tools are coming for theirs — and your job is to move the whole group forward with honesty rather than mandates or hype. Get the norms and the trust right and adoption takes care of itself; get them wrong and you’ll see either reflexive resistance or a slow erosion of the craft you’ve worked to build. This page is a stub, but it’s the people problem at the center of everything else in this section.

What this will eventually cover:

Meeting engineers where they are — enthusiasts, skeptics, and the anxious
Setting norms before tools spread: review, ownership, and what’s okay to delegate to a model
The trust conversation — addressing job-security fear openly instead of pretending it away
Avoiding the two failure modes: mandate-driven backlash and unmanaged free-for-all

💡

The most important thing I did wasn’t picking tools — it was saying out loud, early, that the goal is to make people more capable, not more replaceable, and then backing it with how I evaluate work. Engineers can smell a rollout that’s secretly about headcount. Name the fear, be honest about what you don’t know — the same direct, honest conversation you’d want in any hard moment — and adoption stops being something you have to push.

Where to go next

This is where the arc closes — the human part is the hard part, and the least automatable. Two ways back in:

AI Literacy for EMs — the foundation the whole section is built on, if you skipped ahead.
Claude Code 101 — read the why but haven’t put a tool in your own hands yet? Start here.

📚 Go Deeper

Books

Co-Intelligence — Ethan MollickMollick's framing of working with AI as a collaborator, not a threat — useful language for the conversations you'll have with your team.
One Useful Thing — Ethan Mollick's blogOngoing, grounded writing on how AI is actually changing how people work — good source material for setting realistic team expectations.

Courses

DeepLearning.AIPoint skeptical or anxious engineers here — building real understanding is the fastest cure for both hype and fear.

Last updated on June 25, 2026

BMAD 101