Step 7: We Almost Broke Everything

📍 Part 7 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

Let me describe the period just before we built the Garage.

High creativity. Great energy. Agents proliferating across the team.

Underneath it: loose operational foundation at best. Governance ideas and concepts.

Flailing.

Here’s what “flailing” actually looked like:

Seven agents doing roughly the same thing. No design pattern to rationalize them. A delivery team member builds an agent, it works great, she goes on vacation, the model updates, it breaks, nobody knows who to call.

Some agents didn’t log to the dashboard. Some logged multiple entries. Some logged events for failed runs. Agents that hadn’t been through a security review. Agents that got stuck in loops and churned resources. Agents without error handling.

None of it malicious. All of it predictable.

Momentum without infrastructure eventually produces exactly this.

What the Garage is.

The name is intentional. The Garage is where things get built right; maintained properly, run reliably, tuned up occasionally, extended thoughtfully.

The core insight: every agent, regardless of who built it or how fast it came together, needs to meet a consistent baseline.

Usage logged to the central dashboard
Security parameters and data governance verified
Responsible AI framework compliant
Clear ownership with a maintenance plan
No unnecessary overlap with existing agents
Fit into the software development lifecycle

Before the Garage, those things happened by luck. After the Garage, they happen by design. They were all documented in the Garage Green Book.

The thing we were most careful not to break.

The creative momentum from Phase 5.

The worst version of an agent ops team is one that becomes a bottleneck. Submit your agent request here. Six-week review cycle. Fill out this form in triplicate. You missed section 17 of the BRD. How did you come up with that ROI. We need LT buyoff. Thank you for your patience.

That kills everything. Literally everything. Momentum, creativity, usage, passion; everything.

So we designed what we think of as a barbell.

One side is the delivery team: the ideation, the domain expertise, the speed, the ideas born from real work. To quote my mentor “In the business, not on the business”

The other side is the Garage: the rigor, the telemetry, the governance, the scale.

Both sides need each other.

Delivery without ops builds fast and breaks things. Ops without delivery builds carefully and solves the wrong problems. Together: fast and right.

What good agent ops actually enables.

It’s not just about catching problems.

Operational infrastructure is what makes scale possible. When the process for onboarding a new agent is defined, you can move faster. When agents share a common architecture, you can combine them. When the foundation is solid, extensions are fast. When your telemetry is accurate, you get buy in and more funding.

The Garage isn’t friction for innovation. It’s the launchpad.

One more thing the Garage gave us: a real answer to “what agents do we have, what do they do, and who owns them?”

That’s not glamorous. It’s essential. It’s an incredibly valuable asset. You need a library of agents, an agent to search that library, and an agent to simplify the process for getting more agents into the library. That’s agent ops. That’s The Garage.

Agent ops is a real thing. If you’re scaling agents without it, you’re not running a program. You’re running a mess.

Next: What the whole system looks like when it’s actually working.

Step 6: The Phase Nobody Plans For

📍 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.

Part 1: Becoming Agent Native.

📍 Post 1 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

We Started in Our Worst Quarter. On Purpose. Q4. Our busiest quarter. The one where we’re all running flat out and nobody has margin for anything extra.

That’s when we decided to pull a small group off delivery and dedicate them to building AI agents.

People thought we were crazy. The timing was bad. But here’s the thing about timing: there’s never a good quarter to change how you work. If you wait for a slow moment, you’re waiting forever.

Three decisions made Phase 1 work. They’re worth naming clearly, because we got all three right (and had gotten them all wrong in an earlier attempt).

Decision 1: Delivery resources. Not new headcount.

The instinct is to hire specialists. Build a separate AI team. Find people with “AI” in their title.

We did the opposite.

We took people already doing the work – people who knew exactly where the friction was, who understood what “a bad Monday looks like” in our workflow – and we gave them dedicated time. Not 10% time. Not a side project. A real squad with a real mandate.

The people who know the pain are the ones motivated to build the cure.

Decision 2: Low-code or nothing.

We made it a mandate: no code-based solutions. No Foundry builds. No MCP servers. No deep engineering.

Partly practical; code means maintenance, and we didn’t have a team to own that. But mostly strategic. The platforms were moving faster than we ever could. Our edge wasn’t engineering. It was application. Low-code kept us in our lane.

Decision 3: Start embarrassingly small.

We had tried the big project approach before. A large-scale agent initiative run as a hobby by people with other jobs to do.

It failed. Not because the vision was wrong. Because nobody owned it, nobody had real time for it, and the scope was too big to make rapid, visible progress.

This time: small agents. Single tasks. The thing you do six times a day that shouldn’t require a human.

Not a meta-agent. Not a platform. Just: let’s automate that one thing that people hate doing.

Out of Phase 1, we had a handful of agents doing small, specific, daily automations. Unimpressive on a slide. Genuinely useful in a workday.

That was enough to move to Phase 2.

The biggest barrier to starting isn’t technology or budget. It’s the belief that you need a huge, perfect project to justify the investment. You don’t.

Next: What happened when those agents met the broader delivery team, and why it didn’t go the way we expected.