📍 Part 3 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
I wrote about this in August Agents: Names Matter and it was the right instinct. Now, on the other side of the full journey, I understand why it worked even better than I thought at the time.
Reese. Casey. Nabha. Elliot. Gibbs. Mona. George. Winston. Axel. Lily.
These aren’t product names. They’re teammates.
That distinction (which can sound like fluff the first time you hear it) turned out to be one of the most operationally significant decisions we made.
Here’s the simple version of why it works.
When something is a tool, your relationship to it is passive. You use it or you don’t. You don’t give a shovel feedback. You don’t coach a dashboard. Tools sit in a drawer until someone reaches for them.
With a teammate, your relationship is active.
You onboard them. You give them context. You tell them when they’re missing the mark. You notice when they improve. You advocate for them when someone else doesn’t understand what they do.
When your team has a stake in an agent’s success, they do something invaluable: they give feedback. Quality feedback. The kind that makes agents genuinely better.
We did regular performance reviews with our agents. More frequent right after onboarding or a new capability release (just like a new hire or after a promotion), less frequent as they found their footing. Same discipline as the rest of the team.
George is the clearest example.
Before George, Friday afternoon meant pulling together the week’s work, surfacing the key insights, formatting it, and getting it to the right people. Valuable. Tedious. The first thing that got cut when Friday got busy.
George does it automatically. He looks across everything you have produced, finds the biggest insights, and delivers them without anyone asking.
But here’s what made George good: feedback. Lots of it. Specific feedback from people who saw George as a teammate they were invested in making better.
That feedback loop exists in part because of the naming. Because of the personification. Because of the decision to onboard rather than launch.
There’s a governance benefit too, which we didn’t anticipate.
Naming forces clarity. When Mona graduated from a personal helper to a team-level role, we treated it like a promotion. Clarified scope. Assigned an owner. Eliminated overlap with other agents who’d been doing adjacent things.
Without that discipline, you get what I’ll describe in Part 6: seven agents doing roughly the same thing, disjoint responsibility, things slowly breaking.
Personas force you to think like an org designer, not just a builder. And be very clear, you are building an org.
The question your team will stop asking once agents have names:
“Do we need this?”
The question they’ll start asking:
“How do we help them thrive?”
That’s a completely different organization.
Giving your agents personas isn’t just adoption strategy. It’s how you build a team that includes humans and agents and actually functions like one.
Next: How we knew any of this was working — and what happened when we looked at the data.
Signal, not Sentiment 