What happens to organizations as AI makes coordination radically cheaper? The Exponential Organizations community has spent more than a decade exploring how technology reshapes organizations. When Salim Ismail, Michael Malone, and Yuri van Geest’s Exponential Organizations (2014) described companies whose reach grows far beyond their headcount, their thinking grew into a movement: OpenExO. Today, some 20,000 ExO coaches help organizations put its ideas into practice.
Now The Organizational Singularity, led by Ismail, extends the argument into ExO 3.0: an organization built around what they call an Intelligence Stack, with governance running through it. More execution passes to agents while people retain responsibility for purpose, judgment, and consequential decisions. The firm becomes, increasingly, an accountability shell.
How to implement this Intelligence Stack? It turns out that Engaging OS is uncannily suited.
The original ExO framework grouped ten attributes into S•C•A•L•E and I•D•E•A•S. ExO 3.0 introduces D•R•I•V•E and S•H•A•P•E, but the earlier attributes remain a useful way to see the fit:
ExO attribute | Its expression in Engaging OS |
|---|---|
Autonomy | Positions carry explicit authority to act. They get instantiated by Roles at various bodies; people or agents in turn hold roles. |
Dashboards | The resulting authority determines which items appear in each Role’s Console, and which consoles appear. |
Algorithms | Agents hold Roles and act through the same permission system as people. |
Staff on Demand | Employees, contractors, and agents can fill Positions. |
Interfaces | Outside contributors enter through defined Positions and work on the same items. |
Experimentation | A process can be modeled and up and running in a single session; the modeling method is called Business Operations Notation/Development, the slash signifying that the notation constitutes the development. |
To borrow from Steve Jobs, these are not separate things; they all stem from the role-based paradigm.
Consider each ExO attribute:
Autonomy and Dashboards
ExO’s Autonomy attribute describes self-organizing teams with authority pushed down to them. Dashboards give those teams shared, current information to steer by. Together, these let work proceed without waiting for a manager to direct each step.
In Engaging OS, authority and visibility come from the same definition.
A Position holds Operations, which are the right to take a particular action on an item in a particular status. A Role is the assignment of a person or agent to that Position at a particular Body for a defined period. The role’s various Consoles appear on its dashboard, showing the items that the user can act on now.
When an item is moved from draft to submitted status, it may leave the drafter’s actionable list and appears on the approver’s. Once approved, it likely moves yet again to a console held by another user’s console. Nobody routed it; its status did.
The process needs to be designed, but then need only be articulated. Autonomy supplies the authority; the Dashboard provides conduits to where it is exercised. And with Statuses and Operations constituting the workflow, there is no need to produce a separate routing diagram to keep aligned with the permissions; the specs are complete enough to be executable, so can generate on-the-fly business process (BPMN) diagrams.
Note that this means the organization is not defined by who has authority over whom; rather, it is about who can do what to various objects (among which, it is true, are Persons). Autonomy as a value is baked in to the Engaging OS model of what an organization actually is.
Biologists call coordination through changes in a shared environment stigmergy. An ant leaves a pheromone trail; a Wikipedia editor leaves an edit for others to inspect and develop. Here, the trace is an item’s status; each change makes available the next authorized action.
Algorithms and Staff on Demand
ExO’s Algorithms and Staff on Demand expand what an organization can accomplish with its permanent staff. Software and outside talent take on work the firm would once have hired people to perform internally.
Engaging OS gives each contributor a defined place in the operation. A Position can be filled by an employee, a contractor, or an agent. The holder may change; the Position’s authority remains explicit.
For an agent, that authority is its permission envelope.
Take the process of sales outreach: three Positions might participate — the Drafter, the Approver, and the Sender. The Drafter and Sender are agents; the Approver is a person.
The Drafter’s envelope is small:
It drafts outreach for a qualified Lead.
It submits the draft for approval.
It revises and resubmits a returned draft.
The Drafter finds a qualified Lead in its Console, writes the outreach, and submits it. The item leaves its actionable list and enters the Approver’s queue.
Ask the Drafter to approve its own work and it cannot; that Operation simply isn’t available to its Position. The refusal comes from the platform, rather than an instruction the agent must remember to obey.
The Approver returns the draft with a requested change. The Drafter revises and resubmits it. The Approver approves. Only then does the outreach become available to the Sender.
Each step records who acted, what changed, and when. Meanwhile the organization has gotten agent execution, a human review queue, separation of authority, and a record of the work — all from one set of operational definitions. The accountability shell has acquired a working interior.
Interfaces
ExO’s Interfaces connect outside resources to the organization’s internal work. Without them, access to a crowd or a pool of specialists can create another coordination job.
Among the core values of Engaging OS is Frank Lloyd Wright’s notion of organic architecture, where the outside and inside are clearly defined as different, yet each is of the other.
In Engaging OS, an outside contributor enters through a Position. Their Operations define what they can see and do, and their work lands on the same items used by everyone else.
Interfacing with the system occurs one of two ways: humans get screens, while AIs get the the industry-standard MCP protocol.
A contractor’s submission becomes an employee’s approval item. An agent can prepare something for an external specialist to review. The shared process continues across the boundary.
Experimentation
ExO treats Experimentation as an organizational habit: try an idea, observe what happens, and adjust.
Experimentation is easier when changing a process begins with sentences the business can read.
Engaging OS uses BON/D—Business Operations Notation/Development—to express Operations. Its questions make the actor, action, item, conditions, and context explicit:
A Guest can book a Room, provided that Room has availability on that date.
Anyone involved can read that, challenge it, and agree on the intended rule. The sentence specifies the Operation the platform enforces.
A process can be modeled during a discussion and, be running before the meeting ends. People can then inspect actual work: what appears in each Console, where an item waits, whether a Position has enough authority, and whether an approval is necessary. The model becomes something to try.
Purpose and the people around it
ExO begins with a Massive Transformative Purpose. Purpose attracts people, gives their effort direction, and helps a community form around the organization. While the domain analysis discussions can be inspiring, software obviously cannot supply that commitment.
Nor does assigning someone a Position create trust, engagement, or a productive community. Engaging OS can give contributors a way to act once those relationships exist. Leaders and coaches still have to build them.
ExO supplies a language for the organization people want to become. Its coaches help them make the choices that entails. Engaging OS makes several of those choices executable: authority becomes Operations, responsibility becomes a Role, and a change in an item’s status brings the next participant into the work.
The match is particularly useful as agents join the organization. Human and agent contributions can share a process while retaining distinct permissions. Autonomy can expand without leaving its boundaries implicit.
Coase explained the firm through the cost of coordination. As that cost falls, the firm still needs a clear account of who may act and who answers for the result.
ExO describes the emerging organization; Engaging OS provides the backbone for its realization.
For more about the rise of the Exponential Organization, see:
“The Rise of the Exponential Organization with Peter Diamandis and Salim Ismail” at the A16Z podcast