Org design in the AI era: span of control is doubling. Most companies aren't ready.
If AI eats the bottom 30% of every individual contributor's job, the math on manager span of control breaks. Here's what's actually changing in org structure — and the three mistakes companies are making right now.
Every conversation about AI in the workplace is about the IC role. What gets automated, what gets augmented, what disappears. Almost nobody is talking about what this does to the org chart — and the org chart is where the cost structure lives.
Here's the unspoken consequence: when AI removes 20–30% of the routine work in each IC role, the natural span of control doesn't stay the same. It widens. The companies that recognize this early will run dramatically flatter orgs by 2028. The ones that don't will be carrying a layer of middle management designed for a workload that no longer exists.
Why span of control rises
Manager workload is roughly proportional to: (IC questions per week) + (review work) + (1:1 hours) + (career conversations). AI absorbs the first category dramatically — policy questions, how-to questions, second-opinion questions. It compresses the second (less to review when AI drafts the first version). The third and fourth don't shrink, and arguably should grow. Net effect: the same manager can support significantly more ICs if the work is redesigned. But only if.
The three mistakes I see right now
1. 'Flatten' meaning 'remove one layer at the top'
Most 'flattening' announcements eliminate the VP layer and call it done. The real opportunity is in the M2/M3 layers, but it's politically harder because that's where most of your senior people sit.
2. Wider spans without rebalancing 1:1 quality
Going from 7 reports to 11 without changing how 1:1s work means each report gets less time. The math demands tighter 1:1 cadence, shared agenda templates, and a willingness to skip a 1:1 when there's nothing to discuss. Most managers will refuse to skip without explicit permission.
3. Keeping the same comp bands for IC and M1
If your most senior IC makes less than your weakest manager, every senior IC who wants more money becomes a candidate manager. That was a bad bug at span 7. At span 11 it's existential. Fix the IC ladder first.
Stop doing / start doing
- Treating 'span of control' as a fixed cultural norm
- Promoting your best IC to manager by default
- Adding a layer 'because the team got big'
- Same 1:1 cadence regardless of role complexity
- Manager titles as the only path to higher comp
- Reviewing span every 12 months as work redesigns
- Building a real principal IC ladder with comp parity
- Removing layers when workflows compress
- Tiered 1:1 cadence (weekly / biweekly / monthly)
- Splitting 'people manager' from 'tech lead' explicitly
HR & Operations leader scaling global remote teams across Nepal, the Philippines, Australia, and the US. Tech-leaning writing lives on Medium.