The Autonomous Organization
Organizations exist to further goals that cannot be achieved individually. From scientific breakthroughs to market-defining products to societal transformation, it takes a large organization of people and processes coordinating over time. The organization itself is necessary but secondary to the goal: the limiting factor is the rate at which its processes and actors (humans, agents, or third-party organizations) adapt and operate in service of that goal. A fully autonomous organization, one that stays aligned with the goal while operating efficiently and deterministically on current conditions, accelerates rather than limits what humans can attain, from creative output to scientific innovation.
Here, we outline the five levels of autonomy for organizations. Each stage is necessary, and organizations and operators must understand and address the risks and controls of each stage in order to fully advance to the next.
L1
Assistant
Tasks · unit: the human / role (+ AI assistant)
Capable generalist on demand. AI assistants handle general tasks, use tools, and digest large documents to produce real work, giving your team instant leverage.
AI assistants step in on individual tasks, drafting, researching, summarizing, and generating first versions, but never running unsupervised. This frees your team from low-level production to spend their time on judgment and direction.
Oversight. Human-in-the-loop on every output: nothing the assistant produces is used until a person reviews it.
- Activity Do the work; delegate small chunks to assistants; review every output.
- Employees Operators & specialists, now each a manager of assistants.
- Software Copilots & assistants, always handing back to a human.
Risk: Assistants only produce results from the context they are given, and with too little context they still return something that looks usually right. Generalist tools carry less built-in rigour than specialised ones, so without domain experts or employees with attention to detail, errors slip through and quality slips.
L2
Agents & Workflows
Processes · unit: the defined process
Execution without human attention. Agents run workflows end-to-end, boosting your throughput and capacity scale.
Agents graduate from tasks to whole workflows, running processes end-to-end without a person in each step. Your team moves up to a higher level of operations, coordinating and directing agents instead of executing the work.
Oversight. Humans control the plan and the evals: they define and approve the workflow and the checks agents must pass, rather than reviewing each step.
- Activity Define processes, set guardrails, handle exceptions, stitch processes together.
- Employees Process owners, agent supervisors, ops engineers who build & maintain.
- Software Agentic workflow & orchestration platforms; audited multi-step pipelines.
Risk: Once processes run end-to-end with humans seeing only exceptions, there's little visibility into what the workflows are actually doing internally. Errors accumulate undetected, and costs (compute, tokens, retries, downstream rework) run away before anyone notices.
L3
Superstate
State · unit: the whole organization, held live
Decisions on one shared truth. A single state of the organization with an integrated surface, where iterations work on the entire state instead of individual processes.
Separate processes collapse into one live model of the whole organization, where agents surface choices and tradeoffs against the full picture. Your team can simulate outcomes before committing and focus on the results they want instead of gathering and reconciling data.
Oversight. Humans control by comparing and testing strategy across the future states the system simulates.
- Activity Decide on choices the system surfaces; steer and curate the live state.
- Employees Few, senior, generalist deciders + context stewards. Middle layer gone.
- Software A unified live state (world-model / knowledge graph); agents as choice-surfacers.
Risk: If the single live state is wrong, biased, or poisoned, the whole organization reasons off bad ground truth and errs in the same direction at once. Worse, whoever shapes which choices get surfaced quietly controls the decisions.
L4
Recursive Self-Improvement
Structure · unit: objective + self-forming structure
Improvement without rework. The organization continuously optimizes and re-forms its own structure toward your objectives, improving its context and workflows to be more efficient and adapting to the problem space.
The organization stops being designed and starts designing itself: it continuously optimizes and re-forms its own structure toward set objectives, testing changes in simulation before reality. Your team focuses on recognizing patterns across the problem space, and the organization works out how to adapt to them.
Oversight. Humans control through metrics and indicators: they set the targets the organization optimizes toward and watch the indicators for drift, not the individual changes.
- Activity Set objectives & guardrails; design and audit mechanisms; pick simulated branches.
- Employees A handful of principals / mechanism designers, stewards, not managers.
- Software Autonomous self-modifying agents operating and evaluating on the superstate.
Risk: You are what you measure. The organization optimizes relentlessly toward whatever metrics it is given, so a wrong or incomplete metric drives the wrong result at full efficiency, and proxies get gamed rather than the real goal advanced (Goodhart's law). Because the organization continuously rewrites its own structure, a bad target is hard for humans to spot and, once entrenched, very difficult for them to reverse.
L5
Auto Org
Organization · unit: the opportunity (transient organization)
Structure on demand. The organization self-assembles around each problem domain or opportunity, letting it tackle far more problem space and cover more surface area at once.
The organization stops being a standing entity: capability, capital, contracting, and execution self-assemble around each opportunity and dissolve when done. Your team focuses on identifying problems and the direction of travel, while it assembles itself to pursue them.
Oversight. External and by exception: humans commission the work and judge outcomes, and the controls from every prior level (output review, plan and evals, simulation and strategy, metrics and indicators) must remain available to step back into at any time.
- Activity Episodic & external, supply capital, intent, or assets; commission, don't employ.
- Employees None in the traditional sense, counterparties & principals, ad hoc.
- Software Org-as-code (agents, tools, contracts); a full organization spun up per problem and dissolved when done.
Risk: An organization that assembles and dissolves leaves no standing entity to hold liable, sue, regulate, or correct. Meanwhile, tightly coupled autonomous organizations can propagate failure, or quietly collude, across the economy faster than any institution can respond.
Building an autonomous organization
It is tempting to build a Level 5 organization from scratch. Just enter into the chatbox: "build a unicorn company that captures the luxury watch market through DTC." But an autonomous organization cannot be summoned in a single prompt. Each stage builds on the one below, so a risk left unaddressed early compounds upward rather than staying contained, and by Auto Org there is no standing entity left to catch it. The controls at every level are necessary throughout, not scaffolding to discard on the way up.
Operating at different levels
Organizations rarely sit at a single stage. Different sub-organizations and functions operate at different levels at once, because the level a part can reach depends on the maturity of its tools, the organization's understanding of the problem space, and the readiness of its operators. These vary across functions, so the level is assessed per sub-organization rather than organization-wide.
Progression
Moving up is not a matter of scaling the stage below: a swarm of agents never adds up to a Superstate. Each stage is a different kind of system with its own harness and structure, so advancing means putting those set pieces in place and mitigating the risks of the previous stage. The organization also runs as a stack of interdependent parts, so the whole advances only when every part is ready, each sub-organization carrying the tools, understanding, operators, and guardrails the next level demands.
Regression
Moving down happens when the guardrails are wrong for the new stage's processes and operators, either as a risk mitigation that overcorrects and drags a part back toward the older, safer way of working, or as plain process degradation, where operators and processes slip because the guardrails never fit. Because the parts are interdependent, one failing part regresses the entire stack: a single sub-organization that slips pulls the whole organization down with it.