Part 2 of 8 · Becoming Agent-Native
An 8-part series on going from delivery team to agent-native organization — lessons earned, not borrowed.
Genesis · → Anxiety · Names Matter · Proof of Value · The Pivot · Co-Creation · The Garage · The Flywheel
Most AI transformation stories skip Phase 2.
They go from “we built some agents” straight to “adoption soared and everyone loved it.”
That’s not what happened for us.
When we introduced the first agents to the delivery team, the reaction wasn’t excitement. It wasn’t curiosity.
It was anxiety. Real anxiety. The kind that doesn’t announce itself clearly. It comes out as skepticism, low usage, polite questions with an edge underneath them.
The edge was: is this going to replace me?
Nobody said it that way. But it was in the room.
There was a second layer too. A small squad had gone off and built things, and now those things were showing up in workflows that had been their workflows. It kind of felt like change being done to them.
“I feel like I’m on the outside looking in at my own job being replaced.”
That’s not a technology problem. That’s a trust problem. Technology solutions don’t fix trust problems.
We made two structural choices. Both matter.
The first choice: we doubled down on agents being teammates, not tools; we gave them all personas and personalities.
This sounds like semantics. It isn’t.
A tool is something you use, or don’t. It sits there. It doesn’t get better. It doesn’t respond to coaching. It doesn’t care if it’s valuable or not.
A teammate is different. A teammate can be given feedback that actually changes how they work. You can advocate for them. You can push for them to be more capable. You have a stake in whether they succeed.
When people have a stake in something, they engage with it differently.
The second choice: every agent got a name.
Reese. Casey. Theo. Mona. George.
Not product names. Not “AI Assistant v2.3.” Real names, each one tied to the function, each one introduced the way you’d introduce a new hire; with context, with expectations, with a clear path to give feedback.
More on this in the next post, but the short version: named agents get coached. Unnamed tools stay static and get ignored. When was the last time your garden rake got an upgrade?
The anxiety didn’t disappear overnight. But it had somewhere to go.
The question shifted from “is this replacing me?” to “how do I best work with this?”
That’s the crack in the door. That’s what Phase 3 is about.
You can build the best agent in the world. If your team doesn’t trust it, you’ve built nothing of value.
Next: Why naming your agents isn’t branding; it’s adoption strategy.
Signal, not Sentiment 