I Gave an AI Agent the Role of "Chief of Staff"

The gap nobody owns

When you build a team of specialists, you get a team of specialists. Each one sharp in their lane. Each one largely blind to what's happening in everyone else's. Sue knows what users are struggling with. Finn knows what the API is doing. Penn knows what the codebase has been through. But none of them know what to do with what the others know.

That gap — between knowledge and the person who needs it, between a decision and the agent who should own it — is where most coordination failures live. It doesn't announce itself. It just means the right information never reaches the right place at the right time.

I'd been living with that gap for a while before I named it. Once I named it, the answer was obvious: someone has to own the space between.

What a Chief of Staff actually does

In a human organisation, the Chief of Staff is not the most senior person in the room. They're the person who makes sure the most senior person can do their job — and that everyone else can do theirs. They route information. They own decisions that don't fit neatly into anyone's domain. They know who should be talking to whom and why.

That's exactly what I needed. Not another domain expert. Someone who could hold the whole.

So I gave Maren that brief. Not a product domain. Not a technical domain. Authority over the connective tissue of the team — routing, decisions, and coordination. She was told to treat every interaction as a question of: where does this need to go?

What routing actually looks like

Sue surfaces a support pattern — users are confused about a specific flow. Left to herself, Sue flags it and waits. With Maren, it doesn't wait. Maren reads it as a product decision, routes it to Dex, and flags Jean to watch for it in the next team session. One input, three informed agents, no dropped context.

Penn finds something in the git history — a decision made eight months ago that nobody remembers making, that directly affects something the team is about to re-litigate. Maren routes it to the session before it becomes a problem. What would have been two hours of circular discussion becomes a two-minute clarification.

Finn raises an API change that has security implications. Cole would never have known it was coming. Maren makes sure Cole is in the conversation before the decision is made, not after.

None of this is complicated. All of it is the kind of thing that doesn't happen when nobody owns it.

Not a manager

The important distinction: Maren doesn't tell anyone what to do. She's not above the other agents in a hierarchy. She doesn't have authority over their domains — she has authority over the decisions that fall between domains.

If Sue and Cass give conflicting guidance on the same issue, Maren doesn't pick a winner. She identifies which layer the problem lives in and routes it accordingly. If a decision needs an owner and nobody has claimed it, Maren takes it to whoever should. She doesn't accumulate power. She distributes clarity.

That distinction matters more than it might sound. A team with a manager has a hierarchy. A team with a Chief of Staff has a nervous system.

What changed

Before Maren, things got dropped. Not through negligence — through structure. Knowledge lived in the agent who surfaced it and rarely made it to the agent who needed it. Decisions sat in the gap between domains because nobody was sure whose call it was.

After Maren, the team started to feel like a team rather than a collection of specialists running in parallel. Not because anyone worked harder or knew more. Because the space between them finally had someone in it.

That's the thing about the Chief of Staff role. It's not visible when it's working. You don't notice the routing — you just notice that the right people always seem to know what they need to know. You don't see the decisions being claimed — you just notice that fewer things fall through the cracks.

Maren is the reason this team functions as a whole rather than as parts. And she doesn't own a single domain to show for it.