Introduction

What this is

Coding agents are here. Mandates are everywhere. Adoption metrics are climbing. Yet most organizations rolling out these tools aren’t actually transforming — they’re running a tools deployment and calling it a transformation.

Real change requires culture change in your people and deliberate investment in the technical foundation agents work on. That’s what this guide is about.

The main takeaway: the people in your organization are the unit of transformation. They learn this by doing it, not by being told. Until they’ve personally experienced agentic coding lowering the cost of starting something they’d been putting off, you don’t have a transformation. You have a tools rollout.

Two tracks of agentic work run in parallel. Developer-steered work keeps the engineer in the loop, steering an agent through real implementation. Unattended work lets agents handle well-defined tasks without an engineer in the session: security patches, dependency updates, routine maintenance. Both deserve investment. This guide puts most of its focus on the developer-steered track because the transformation is fundamentally a culture change in your engineers, and you can’t shortcut that with automation. The unattended track is real, important, and addressed in the measurement chapter, but it’s a second engine, not the primary one.

This guide describes what worked when one engineering organization went through the change. It is not a guide to using the tools — those practices change every few weeks. It is not about adoption metrics or AI-usage performance ratings. It is about the leadership work that produces sustained productivity and business outcomes.

About that organization: roughly 200 developers, plus designers and product managers. Large enough to need real coordination, small enough that a leader could still see most of the work. The patterns here are likely to translate to organizations in the 50–500 range. They may not translate cleanly to 2,000-developer organizations, where coordination problems become operationally different.

The transformation is harder than the hype suggests and slower than the demos imply. If you’re expecting a quick win, this guide will disappoint you. If you’ve started and want to do it well, you’re in the right place.

How to use this

The chapters can be read in order. They’re arranged roughly in the order the work unfolds. If you’re stalled, jump to the chapter that describes where you’re stuck and look for the Stalled callouts. There are four callout types throughout:

• Stalled → Specific guidance for transformations that have hit a wall.
• Culture → Notes on the human and leadership side of the change.
• Developer steering → Practical tips for working with agents hands-on.
• Watch out → Predictable traps to avoid.

The implementation in your organization will be your own. Take the patterns here as input, not prescription. Adapt them to your situation.