# Man and Machine: The Org Chart Becomes a Codebase

![Man and Machine: The Org Chart Becomes a Codebase](/writing/man-and-machine/the-org-chart-becomes-a-codebase/assets/hero.jpg)

I used to think about my team as an org chart: boxes, reporting lines, and span of control\.

Now I think about it like a codebase\.

Here's what changed: When you start running autonomous agents alongside people, you realize pretty quickly that the org chart model breaks down\. An org chart assumes every node is a person who needs a manager, a career path, and a Monday standup\. An agent needs none of that\. What it needs is a clear domain, clean inputs, and a defined output\.

Sound familiar? That's a microservice\.

My operating system today has a content engine, an editorial intelligence layer, a metrics collector, a briefing generator, and an overlay pipeline\.  
Each one has a single responsibility\. Each one has a defined interface\. When one breaks, the others keep running\.

So that isn't an org chart, but it is a bounded context architecture\.

The interesting part is what happens to the humans in this model\. They don't disappear\. They move up the stack\. Instead of being the nodes that do the work, they become the architects who design the system\. The people who decide which domains exist, how they talk to each other, and what "good" looks like\.

The CEO becomes the systems architect\. The org chart becomes the codebase\.

If you're still thinking about your team in boxes and lines, you're designing a monolith\. And monoliths don't scale\.

How are you thinking about your own org structure as AI changes what's possible?

\-dg

\#ManAndMachine \#AIOperator \#AutonomousAgents \#Microservices \#BoundedContext \#PaymentsInfrastructure \#Dwolla \#CEOasArchitect Dwolla \#FutureOfWork \#AIinBusiness \#MoneyMoveMedia

## Sources

- [Original LinkedIn post](https://www.linkedin.com/feed/update/urn:li:activity:7449396006082908162/)