Skip to content

Blog

Agentic coaching is the new agile coaching

Adopting agentic engineering has the same shape as adopting agile twenty years ago: an organizational change, resistance among senior people, and the same three levers that worked the first time.

Written by

Adoption

Published: 30 June 2026 Updated: 2 min read

I gave a leadership talk recently and watched the room change posture at one sentence. It was not a sentence about models or tokens or productivity gains. It was this one: “Agentic coaching is the new agile coaching.”

Every leader over forty in that room had lived the agile transformation. They knew, in their bones, what that sentence meant: the timeline, the resistance, the cost. They knew it was a change in how people work, not a tool you install. I had not explained agentic engineering yet, and they already understood the scale of what I was describing.

That is the whole value of the parallel, and it is worth being precise about why it holds.

Agile was never a technical project

Twenty years ago, adopting agile was not a technical project. The technology was trivial: a whiteboard, sticky notes, a two-week calendar. The hard part was organizational. Teams had to change how they planned, how they handed off work, how they related to management. Resistance was real, and it was loudest among the most experienced people, the ones who had optimized their working style over a long career and did not want it disturbed.

So companies did a specific set of things. They ran pilot teams instead of a big-bang rollout. They got executive air cover, because a change to how people work dies without it. And they hired coaches, outside people whose whole job was to walk teams through the transition, and for a couple of years, nobody questioned paying for that.

Agentic engineering has the same shape

Introducing agentic engineering has the same shape, point for point:

  • It is an organizational change wearing a technical costume. The agents are the easy part. Changing how the team scopes, reviews, and ships is the hard part.
  • The resistance is real, and again it concentrates among the most senior engineers, who have the most finely tuned way of working to protect.
  • Pilot teams, executive mandate, and outside coaching are the same three levers that worked the first time.
  • And it will not happen on tool budget alone, exactly the way agile never happened on a Jira license alone.

The coach’s job is the change, not the technology

Here is the part I will say plainly. I am an engineer who works with AI, not an AI specialist who wandered into engineering. That is the agentic-coaching stance: the job is not to evangelize a technology, it is to coach an organization through a change it has done once before. The change-management layer for this era, the work hycle.org (opens in a new tab) is building, is exactly this: the organizational scaffolding that turns a capability into a working practice.

How you adopted agile predicts how this goes

If your company adopted agile well, you already know how to adopt agentic engineering. Same playbook, faster clock. If it adopted agile badly (tools without coaching, mandate without air cover), you also already know how this goes.

When your company moved to agile, what made the difference: the process, or the coaching that carried the people through it?

Further reading

  1. When the CEO sits in the developer training AI stopped being a tooling purchase and became an investment in the environment: the harness, the context layer, the trained team, the hiring filter. A CEO doing the exercises next to their staff engineers shows the shift. 1 min readShort post
  2. Agentic adoption is harder than agile, because you can't fake it Agile rollouts could rename roles and keep the waterfall. Agentic engineering returns nothing on half-measures, because every gate sits upstream in architecture, context and the team. 2 min readShort post
  3. Most AI rollouts change the codebase and leave the team untouched In a Multitudes survey, codebase changes made up 85% of what teams changed for AI, and only 13% named a process change. In our experience, that gap is why most rollouts hit the same wall. 1 min readShort post

All 13 posts on Adoption

ClientsCase study: Tegtmeier Internet Solutions

Test the constraint in your system

The Factory Readiness Assessment connects this research to your value stream, your data, and the next decision.

Training on this topic: Agentic Engineering for Engineering and Product Leaders
See the assessment

Want to check one team first? The self-check: twelve yes or no questions, three minutes, instant result, no account. Take the self-check