The AI-Era Org Chart: How My Team Got Smaller and Faster (and What Yours Should Look Like in 2026)

The 2019 org chart is dead and most companies are still maintaining a corpse. The headcount math everyone learned in business school assumed humans were the unit of execution. The unit of execution moved. The chart shape that fits the new unit looks nothing like the old one.

This is the operator's deep-dive on what changed in org design — what got smaller, what got bigger, and what the new shape actually looks like inside two operating businesses I run. Sits alongside the discipline-specific flagships (Marketing, People & Culture) — those go deep on specific functions; this one zooms out to the whole shape.

The numbers, because they're the most concrete part

At Gardenpatch in 2023: 11 humans. At Gardenpatch today: 6 humans, plus a fleet of agents across functions. Output is meaningfully higher per dollar — roughly 2.4x revenue per head — and the team's job satisfaction is better, not worse.

At The Cooling Co in 2023: 19 humans across office and field. Today: 12 humans plus agents. Service capacity is up about 70%, customer satisfaction held flat or rose modestly, and we serve a wider geographic radius with the same field crew because dispatch and routing got smarter.

These aren't extraordinary numbers. They're what a competent operator can produce by following the migration honestly. Companies that haven't migrated are running with twice the headcount they need. Companies that overcorrected and tried to fire-and-replace are losing institutional knowledge and customer relationships. The right shape is in between — fewer humans, paid better, doing harder and more valuable work, with agents under each of them.

The four positions that don't exist anymore

1. The coordinator role disappeared

In 2019, "marketing coordinator" / "sales coordinator" / "ops coordinator" / "people coordinator" was the entry-level rung of every function. The work was scheduling, status updates, cross-team comms, formatting decks, organizing meetings. It was rote and it was valuable because somebody had to do it.

The coordinator role isn't a human role anymore. The agent does it. The org charts that still list a coordinator on each function are showing what the company wants to be (an old-shape team) rather than what it actually is. Either delete the role or rewrite the JD entirely — see the People & Culture flagship on JD redesign.

2. The single-skill specialist got rarer

The "I do exactly one thing exceptionally well" specialist — the SEO-only marketer, the cold-outreach-only sales rep, the bookkeeping-only finance person — got rarer because the singular skill they bring is now augmented by an agent that does that one skill well too. The specialist is competing against the agent for the same narrow scope.

The roles that survived narrowing are the ones where the specialty is more nuanced than a model captures today — high-stakes negotiation, complex enterprise sales, deep technical domain. Most "specialist" roles in the middle ground got reshaped into generalist-operator roles that can direct agents across multiple skills.

3. The middle-manager-of-coordinators evaporated

Above the coordinator role was the manager-of-coordinators. "Senior marketing coordinator," "marketing manager," "marketing director" — a stack of roles whose job was largely to manage the people doing the rote work, plus a thin layer of strategy on top.

When the coordinator role disappears, the manager-of-coordinators role disappears with it. There's nobody to manage. The strategy work that used to sit on top of that pyramid got compressed into the operator role itself. Org charts that retain the middle-manager layer when the coordinators are gone are paying for empty seats.

4. The pure-individual-contributor track got narrower

The "I'm an IC, I just want to ship code / write copy / do design / do research" track shrank because the work an IC does is precisely the work an agent does best. The high-value IC roles still exist — the principal engineer who designs systems agents follow, the senior designer who sets the visual system agents implement against — but the middle of the IC range is where agents shine.

The teams that figured this out renamed the IC track to be about system design, not execution. The teams that didn't are watching their IC ranks struggle to articulate what they uniquely contribute, and quietly losing the best ones to operator roles elsewhere.

The three roles that got bigger

1. The operator

The single most important role on the new org chart is the operator. Their job is to design the agent layer that does the work, monitor it, intervene on exceptions, set the rules, and be accountable for the function's output. They're not a coder, not a marketer, not a sales rep — they're a system designer for the agent layer that performs those functions.

The operator role exists at every function. Marketing operator. Sales operator. Ops operator. Service operator. Tech operator. People operator. Each one carries a function that used to require 4–8 humans to staff. Each one has a fleet of agents under them. Each one earns substantially more than the 2019 manager equivalent because the role is harder and the leverage is higher.

If your org chart doesn't have explicit operator roles, you have managers managing humans who are doing work an agent could do. That structure stops working below a certain scale.

2. The exception specialist

The flip side of the operator is the exception specialist. When the agent layer hits a case it can't handle, somebody has to. That somebody is usually a senior IC with deep domain knowledge — the kind of expert who used to be the rare specialist on the old chart, now elevated and central because their judgment is the differentiated input.

Per function, you need fewer of these than the old chart had specialists — maybe one or two per discipline — but each one is paid much more and is much more critical to retention. Lose your exception specialist and the operator's agent layer suddenly produces noticeable errors.

3. The cross-function bridge

The role that grew quietly is the cross-function coordinator at the senior level — the person who makes sure the marketing operator and the sales operator and the ops operator are running compatible agent layers. In the old org, this was the COO or VP of operations and they spent their time in meetings. In the new org, this person spends their time auditing agent rules and exception patterns across functions.

This is a new role most companies haven't named yet. The "Chief of Staff" title has bent toward it. The "VP of operations" title has been pulled toward it. Whatever you call it, the role exists and it's load-bearing.

What this looks like in practice

Gardenpatch's current org chart, simplified:

• Tiago (founder / cross-function bridge)
• Marketing operator + content exception specialist
• Sales operator
• Operations operator (covers ops + customer success)
• Tech operator
• People operator (part-time, shared with TCC)

Six humans. Each one with agent leverage in their function. Output of roughly what a 14-person team produced in the 2019 shape.

The Cooling Co's shape is similar in proportion but different in flavor — there's more field-tech headcount because plumbing and HVAC repair can't be done by agents (yet) — but the office side migrated to the same operator pattern. Three office operators (dispatch + service, accounting + back-office, marketing + customer comms) plus a part-time field-ops operator who works closely with the senior techs.

Neither company will hire back into the old shape. The agents are too good now and the per-output cost of the new shape is too low. What we will hire for: more operators (as we expand into new functions or geographies) and more exception specialists (as the work the agents can't do reveals itself).

What to do this quarter if your chart is still 2019-shaped

Three steps that work in sequence:

Step 1: Identify the coordinator-shaped roles. They're the ones whose JD reads "schedule, coordinate, follow up, manage, organize, route." Don't fire anybody. Talk to each one and assess whether they could grow into the operator role for their function (most can, with support).

Step 2: Promote the strongest coordinators into operator roles. Give them agent budget, training, and explicit ownership of the function's output. Rewrite their JDs. Pay them accordingly — the new role is worth 30-60% more than the old one.

Step 3: Stop hiring into the old coordinator role. When an existing coordinator leaves, replace with an agent layer + a new operator role at a higher level. Net headcount drops. Per-output cost drops. Output rises.

This takes 12-18 months done well. Trying to do it in a quarter creates whiplash and lost institutional knowledge. Trying to drag it out longer than 18 months leaves money on the table while competitors catch up.

Where to start

If your org chart still has coordinator roles and you're not sure where to begin: take the 90-second AI-Era Operator Audit first — it scores you across the six disciplines and tells you which functions are most likely running the old shape.

If you know people-and-org-design is the gap, the People & Culture in the AI Era playbook goes deep on operator-role design, exception-specialist hiring, comp redesign, and the migration sequence. $27. Free 30-minute strategy call with me. Money-back in 30 days.

If you'd rather see the broader thesis first, the AI-Era Operator Manifesto lays out the nine beliefs underneath every playbook. Free, no email gate.

And if you're rebuilding multiple functions at once — the Complete Bundle is $99 for all six playbooks (saves $63 vs buying individually). Org-redesign work cuts across every discipline.

The old org chart fit a team where humans were the unit of execution. The unit of execution moved. The chart should move with it. The frameworks for the new shape are here.