Back
The org-chart re-shape

Your org chart in 4 quarters

The framework's biggest unlock isn't AI tools — it's removing the middle-management routing layer that exists only to summarise reports. Here's how the org chart re-shapes into the new four roles.

Old vs new
Today
C-suite
synthesises reports
Middle managers
route status updates
Department leads
manage the routing
Junior staff
do the work, slowly
Be AI-First
AI Founder
reads daily brief, decides
Intelligence Layer
AI-generated synthesis
DRIs
own outcomes end-to-end
ICs + agents
ship work 5-10× faster

The four new roles

IC — Individual Contributor

Replaces: junior staff doing rote work

Builds prototypes, drafts, first cuts — paired with an AI agent. Promotion path is now horizontal: more agents to pair with, not more people to manage.

Today
  • Drafts emails, docs, code by hand
  • Routes to manager for review
  • Limited by personal output speed
Will do
  • Briefs Claude / agent on the task
  • Reviews + ships agent's first draft
  • Output 5-10× current

DRI — Directly Responsible Individual

Replaces: department lead doing status reporting

Owns ONE outcome end-to-end. Has authority to ship. Reviews agent output. Accountable for the result, not for the people doing it.

Today
  • Manages 5-10 reports
  • Spends 40% on status reporting
  • Bottleneck for approvals
Will do
  • Owns one customer-promised outcome
  • Reviews agent escalations only
  • Escalates to AI Founder, not status-reports

AI Founder

Replaces: C-suite synthesising reports

Sets vision. Reads the daily intelligence brief. Makes capital allocation. Doesn't synthesize reports — consumes the AI-generated synthesis and decides.

Today
  • Reads weekly status decks
  • Schedules sync meetings
  • Reviews dashboards manually
Will do
  • Reads 8am AI-generated daily brief
  • Reviews AI Leverage Ratio monthly
  • Decides which agent to upgrade vs retire

AI Ops Lead

Replaces: middle managers (status routers)

Owns the Business Brain, the agent library, and the quality bar. The new Operations Manager / Chief of Staff role.

Today
  • Doesn't exist yet at most companies
  • Closest: Operations Manager
Will do
  • Reviews agent quality scores monthly
  • Retires under-performing agents
  • Prioritises next 10 processes for the Sprint
Roll-out plan

4-quarter org transition

  1. Quarter 1

    Goal: Pilot with one team
    • Identify 2-3 ICs willing to pair with agents daily
    • Designate 1 DRI for the first agent's output (Step 7)
    • AI Founder = whoever signed the engagement (founder/CEO)
    • Status meetings cut by 50% for this team
  2. Quarter 2

    Goal: Department-wide adoption
    • Every department has 1 DRI per agent
    • AI Ops Lead role formalised — full-time owner of vault + agents
    • Daily intelligence brief replaces team standups
    • Hiring spec updated to require AI fluency
  3. Quarter 3

    Goal: Replace middle layers
    • Project managers → DRIs (no more status routing)
    • Operations Manager → AI Ops Lead
    • C-suite reports → daily intelligence brief + monthly leverage review
    • Headcount stays flat; output 2-3×
  4. Quarter 4 +

    Goal: Compound + reorganise around agents
    • New hires arrive AI-fluent (built into JD)
    • Org chart drawn with agents alongside humans
    • AI Leverage Ratio reviewed at every board meeting
    • Promotion path: more agent pairs, not more reports
Pitfalls we've seen
  • Skipping AI Ops Lead. Without a single owner of the vault + agents, quality drifts within 2 quarters.
  • Reorganising before the first agent ships. The new structure follows the work, not the other way around. Wait for Step 7.
  • Asking middle managers to "manage agents". If their job is routing, the framework eliminates it. Help them transition to DRI or AI Ops Lead.
  • Promoting only on team-size growth. Re-write the promotion ladder around AI Leverage Ratio, not headcount.
Wizard
Step 9 — Intelligence Layer goes live
Open Step 9
Adjacent
AI Skills Library
The reusable prompts your team builds