📍 Part 6 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
When we started, the model was simple.
Squad builds. Delivery uses.
That division felt right. Clean organizational lines. Clear ownership. A good model.
By Phase 5, it was gone, and it was the best thing that could have happened.
Delivery became builders.
Not because we told them to. Not as a program or initiative.
Organically…as the natural result of everything that came before.
People moved through the anxiety, saw agents make their days better, made the mindset shift from threat to tool to teammate. They started showing up with more than feedback. They showed up with half-built ideas. With sketches of agents they needed. With “I figured out how to make this work”
And with a low-code toolkit they built them. Themselves.
Why this works better than centralized roadmaps.
The people doing the work every day know the friction better than anyone. They know which task is genuinely painful versus just annoying. They know which data lives in the wrong place. They know what “good output” actually looks like for their specific context. They aren’t looking at a PowerPoint slide or a Figma, they are living the experience.
When they build the agent, it fits because it was designed by someone in the workflow it’s automating.
Mona is a great example. She didn’t come from a squad roadmap, she came from a delivery team member who was tired of the back and forth with humans scheduling meetings. She understood the problem completely. She had opinions about exactly what the output should look like. She came to demo days and the engineers said “that’s a great idea but it won’t work” and then she showed them the MVP…working. That day changed our world.
That’s the model. You can’t push it from the top down. It has to grow
The propagation effect.
When everyone in delivery is creating, velocity compounds. One agent spawns an idea for three more. A tool that worked for one person gets adapted for the whole team. The surface area of “problems we’ve automated” expands faster than any squad sitting in an ivory tower could imagine.
There’s not some special team that’s the only one creating. Everyone is. That’s the whole point.
The catch.
There is one. And it’s significant enough to become its own post.
When everyone is building, you get overlap. You get orphaned agents when the person who built them goes on vacation and something breaks. You get agents that don’t log to the dashboard, don’t meet governance requirements, don’t fit the responsible AI framework.
We hit all of this. And more.
Seven agents doing roughly the same thing. Nobody quite sure who owned what. A model update quietly breaking something nobody was watching.
Citizen development at scale without operational infrastructure eventually leads to chaos.
Which is exactly what led us to build the Garage.
Creativity without ops is a mess waiting to happen. Ops without creativity is a very well-governed nothing. You need both.
Next: The mess — and what we built to fix it.
Signal, not Sentiment 