Org Design in the Age of AI

I've been talking to companies — startups to megacaps — about AI and organizational design. Everyone is adding AI to their workflows. Almost no one is rethinking why the workflow is shaped that way in the first place. The org chart is next thing AI disrupts.

---

The hidden function of hierarchy

Strip a company down to first principles and it’s really three things: people, hierarchy, and information flow. We tend to think of hierarchy as being about authority — who reports to whom, who approves what. But that’s the surface. The deeper function of hierarchy is information routing. The org is too large for any single person to see the whole picture, so you install layers of managers to aggregate signals from the front lines, synthesize them, and pass them up — and to translate strategic intent from the top and distribute it down.

Most of the organizational machinery we take for granted exists to solve this problem. Meetings, status updates, steering committees, quarterly business reviews — these are all information-routing mechanisms. They exist because moving knowledge between people is expensive.

---

The real bottleneck was never speed

Consider how a typical product gets built. A PM spends weeks writing a PRD. Design interprets it into mocks. Engineering interprets the mocks and estimates “eight weeks” — at which point the requirements shift and the PRD gets rewritten. Dev takes two to three months. QA spends weeks on regression testing. GTM prepares launch materials and trains sales. End to end, a mid-sized feature easily takes three to six months.

The real bottleneck is translation cost. PM’s intent gets encoded into a document. A designer decodes that document and re-encodes it as a visual. An engineer decodes the visual and re-encodes it as code. QA decodes the intended behavior and re-encodes it as test cases. Every translation loses fidelity. Every translation requires alignment meetings. Every translation generates wait time — not because people are slow, but because the act of making one person’s understanding legible to another person is genuinely hard.

This is what AI collapses.

---

What it actually changes

When a PM can go from idea to interactive prototype in a day using AI, the translation layer between PM and engineering compresses to near-zero. When AI generates tests alongside code as it’s being written, the handoff between dev and QA disappears. When an intelligence layer can synthesize customer signals, usage data, and business metrics in real time, the middle manager whose job was to aggregate that information weekly has to find a different source of value.

This isn’t about any single role getting faster. It’s about the gaps between roles — the translation layers, the handoff queues, the alignment meetings — evaporating.

And once you see it that way, the implications for org design get serious:

• The relay race becomes a basketball game. The sequential handoff model — PM then design then eng then QA then GTM — gives way to small squads of 3–5 people with all the necessary skills, moving simultaneously, making most decisions themselves. Only big directional bets escalate up.

• Departments decompose into capability atoms. Instead of teams organized by function, the org becomes a set of independent, composable capabilities — collections, identity verification, risk scoring, savings — each self-contained, each combinable.

• PMs become product creators. The old PM spent most of their energy making ideas legible to other people. The new PM validates directly — prototyping, running data analyses, generating first-pass implementations.

• Middle management compresses. The managers who thrive will be the ones whose real contribution was always judgment, coaching, and navigating ambiguity — not routing information.

• QA embeds into development.

• The system starts generating the roadmap. This is the most radical shift. The example Jack Dorsey used - A restaurant’s cash flow tightens ahead of a seasonal dip. The system detects the pattern, packages a short-term loan with adjusted repayment, and pushes it to the merchant — before they even thought to look for financing. No PM decided to build that. The system recognized the moment and composed them.

• Release cycles give way to continuous flow. No more “v2.0 ships in Q3.” Ship small improvements daily. This requires CI/CD infrastructure, but more importantly it requires letting go of the big-launch identity — trading the dopamine of a major release for the discipline of relentless, quiet value delivery.

---

The deeper shift

Competitive moat changes: It used to be execution speed — who could ship fastest. Now it’s learning speed — how quickly the org can absorb what AI makes newly possible and restructure around it.

Most companies today are using AI the way you’d use a faster horse — to make the existing structure run a little better. The companies that pull ahead will be the ones willing to ask a harder question: what would we build if we were designing this organization from scratch, today, knowing what AI can do?