Orgware
We have a word for the physical infrastructure: hardware. We have a word for the logic layer: software. We do not yet have a good word for what AI is now making possible at the level of an organisation.
I wonder if "orgware" could work.
Orgware is the operational intelligence layer of a semi-autonomous organisation. Not a set of tools your team uses, but a layer that actively participates in how the organisation runs — sensing, routing, flagging, briefing, and learning.
Software does what you ask. Orgware does things you haven't thought to ask yet.
Imagine a small team. By 8am, before anyone opens Slack, their orgware has already read the overnight metrics, compared them to last week, flagged one number that is quietly drifting out of range, and drafted a brief for the lead. It has queued three questions for the standup.
The standup takes fifteen minutes. Everyone in the room is already oriented. The flagged metric gets a decision. By nine, people and their AIs are building.
Humans spend their cognitive energy: on decisions, not on gathering information to make them.
That is what semi-autonomous means. AI handles the cadence and the signal; humans handle the judgment and the direction.
The building blocks are already here. Natural agents can hold deep specialist knowledge and engage in rich conversations. Conversational interfaces are already replacing dashboards.
Early orgware looks like a well-configured set of agents with clear roles: one monitoring operations, one drafting communications, one querying your data. Mature orgware will look more like an organism — an organisation that learns from its own patterns, improves its own processes, and surfaces its own blind spots.
This changes what leadership means. A leader in an orgware-enabled organisation spends less time asking "what is happening?" and more time asking "what should we do about it?" The shift is from information gathering to strategic thinking.
It also changes what an organisation is.
Software made orgs more efficient. Orgware makes orgs more intelligent.
We are early. The patterns are not settled. The teams building this now are moving incredibly fast and the gap between those architecting their operational intelligence deliberately and those letting it accumulate by accident is already widening.
The question is no longer whether AI will play a role in operational performance. It is whether you will design that role or inherit it.
What does your orgware look like?
