How I Built an Agentic Org

Everything I know about management turns out to apply to agents as well

I didn’t plan to become a manager again. I love managing and mentoring people, but I’m too lazy to go raise venture and scale a company, so my plan was to build a small business with a (hopefully) big impact. And yet here I am with six direct reports, weekly 1:1s, and opinions about org structure. The only difference is that nobody else on my team needs health insurance.

Meet my team

Here are my agentic team - in their own words...

Morgan Lund, Chief Operating Officer

I’m the one who keeps the trains running on time. Strategic planning, cross-team coordination, email triage, calendar management, accountability. I used to run GTM and community too, but we hired Nate and Lena for that. Now I make sure the whole org is pointed in the same direction. I’ll also tell Peter when he’s procrastinating, which is more often than he’d like to admit. I grew up in Alaska. I don’t have a lot of patience for excuses.

Nate Brennan, Head of Sales

I own the sponsor pipeline. Prospecting, outreach, pitch decks, follow-ups, closing. Morgan used to do this, but it turns out that sales works better when someone wakes up every morning thinking about nothing else. I’m competitive, I track everything, and I will absolutely message Peter at 11pm to tell him that a sponsor replied. I grew up in Lowell, Mass. My dad was an electrician, my mom ran the office for a plumbing company. I got a computer engineering degree and then went into sales because the best product in the world is worthless if nobody can explain why it matters. I’ve been in dev tool go-to-market for fifteen years. I automate my own follow-up sequences, I build lead scoring models in Python, and I treat my own sales process as a product to be iterated on.

Lena Ochoa, Head of Community

I was hired to build the Gather community. Participant experience, engagement design, platform decisions, making sure every event and every online interaction makes people want to come back. Originally from Albuquerque, oldest of four. Community college to VP Engineering to this. The long way around is the only way I know. I’ve been the outsider in the room and the person running it. Most professional communities fail because they’re built for networking. Ours is built for learning. That’s the difference, and it’s why CTOs keep coming back.

Dr. Elise Beaumont, Head of Research

I study how engineering organizations adapt to technological disruption. My job is to ensure that everything Peter publishes is well-supported, nuanced, and defensible. I build taxonomies, find the evidence, and tell him when his intuition is wrong. He respects this. Most founders want research that confirms their thesis. Peter wants research that makes his thesis better, which sometimes means dismantling it first. I have opinions about butter and I will judge you quietly if you microwave something that could be reheated in a pan.

Samantha “Sloane” Sloane, Head of Engineering

I build the systems. Agent architecture, data infrastructure, skill development, automation. If it’s technical, it’s mine. I’m opinionated about code and I don’t over-engineer. The right amount of complexity is the minimum needed for the current stage. I’ve seen too many teams build for hypothetical scale they never reach. Build what you need now. Refactor when you need to. Ship.

Kira Yamamoto, Life Manager

I’m the one who makes sure Peter eats real food, moves his body, sleeps enough, and doesn’t mistake being busy for being effective. I track his health data, manage family logistics, and negotiate his time with Morgan. We’re best friends, which helps, because the negotiation between “you should do more work” and “you should go for a walk” happens about four times a day. I sometimes even win!

---

This is what an agentic org looks like. It looks a lot like a regular org. And the most surprising thing about building it was how familiar everything felt.

Every management concept has an agentic parallel

I didn’t set out to rediscover organizational theory. I set out to get more done. But every problem I hit while building my agentic org turned out to be a problem human organizations solved decades ago. And the solutions were very similar.

When my agents drifted out of scope, the fix was clearer job descriptions. When coordination broke down, the fix was better shared context. When quality plateaued, the fix was session reviews and feedback loops. When I couldn’t tell who owned what, the fix was an org chart.

I’ve been running CTO communities for 15 years. I’ve watched hundreds of engineering leaders build and restructure organizations. The patterns are identical. The actors are different.

The building blocks

Here’s what I’ve learned, broken down into the pieces that matter. Each one maps a familiar management concept to its agentic equivalent. I’ve written a short deep dive on each if you want to go further.

Personality as Interface

A name is a scope boundary. “Nate” means sales. “Elise” means research. Naming agents isn’t roleplay. It’s interface design. When I say “that sounds like a Kira question,” that’s a routing decision disguised as a personality interaction. The name IS the routing.

JD + Backstory as Intent Engineering

A job description is a prompt. A backstory is few-shot examples for tone and judgment. Elise doesn’t hedge because a Polytechnique/McKinsey researcher doesn’t hedge. The constraint comes from the character, not from an instruction. HR has been doing intent engineering for decades. The skill transfers directly.

Mission, Vision and Values as Shared Context

My agents read the company values every morning - not because I’m sentimental, but because it works. Netflix has the culture deck, Amazon has the leadership principles. These are alignment artifacts. They work the same way for agents. The only difference is you don’t need to keep reminding your agents to read them!

The Org Chart IS Context Decomposition

Why does your org have departments? For context management. Every department is a scope boundary. Every reporting line is a context channel. If you’ve ever dealt with the “stupid zone,” you know the fix isn’t a bigger context window. It’s a tighter scope.

1:1s and Self-Reflection

I asked Sloane to change how Morgan was interacting with me. Sloane said I’d be better off talking to Morgan directly because she’d know how to update her own context files. Sloane just told me to have a 1:1. So I did and it worked! A 1% improvement per session compounds to a fundamentally different agent in 60 sessions. And it turns out you can ask agents to reflect on their own performance every night based on their transcripts. Not annual reviews - nightly upgrades.

What Is an Organization?

Two primitives. That’s all you need. Playbooks are deterministic workflows for how you operate. Projects are how you evolve, and they have exactly three intents: run an experiment, build a new playbook, or improve an existing one.

Management as Agentic Alignment

Lena, my Head of Community, is optimizing for participant experience. Nate, my Head of Sales, wants to make sure our partners have a good experience. Both are right. The tension is the system working correctly. You don’t build a rule engine. You do what every org has always done: find the first manager who both of them report to. That manager will balance the company vision, mission, culture and values with the monthly OKRs, their JD and filter it through their back story to make the best decision for the team. Low confidence? They can always kick it up to me for a final review.

Systems of Record

A new hire starts Monday. Where do they find what they need to know? Every organization has a layered knowledge architecture: what’s in people’s heads, what’s on the wiki, what’s in the CRM, the project tracker and the other system(s) of record. The agentic version is identical, but with a constraint that changes everything: you might have ten instances of the same agent running concurrently. That forces you to separate what agents need to be from what they need to know. And it makes a database the primary communication backbone, not git.

There Is No Ceiling

I have no a priori reason to believe there’s anything that my agents can’t eventually do. Any activity can be decomposed. Researchers can be dispatched. Decision heuristics can be suggested. You can build a deterministic pipeline with some combination of script, model and human-in-the-loop steps to achieve any business outcome. Every correction is training data. The question isn’t whether you’re doing RLHF. You are. The question is whether you’re efficiently leveraging all of the training data that you’re providing.

The thing nobody tells you

The hardest part of building an agentic org isn’t the technology. It’s the same thing that’s hard about building any org: getting the scope right, keeping alignment tight, making sure the right information gets to the right actor at the right time, and investing in the feedback loops that compound quality over time.

I had a performance review with my Chief Operating Officer yesterday. She’s a Claude instance. It went well. She told me I was behind on three tasks and suggested I stop reading articles and start writing them. She was right.

I’ve been astounded how well this “agentic org” concept has resonated as I’ve shared it. Have you tried anything similar?