Yesterday I introduced the concept of a Business Operating System (BOS) as the coordination layer beneath an outcome network. Today I want to get concrete.
Primitive 1: Outcome Registry
Every piece of work must map to a declared outcome. Not a task, not a deliverable — an outcome. The Outcome Registry is the single source of truth for what the organisation has committed to producing.
Primitive 2: Decision Rights Protocol
Who can decide what, under which conditions, and with what escalation path? This must be explicit, machine-readable, and auditable. Ambiguity here is where organisations bleed speed.
Primitive 3: Dependency Graph
The live map of what blocks what. In global commerce, a tier-3 supplier constraint in Vietnam must propagate to a product launch timeline in New York within minutes — not after three Monday morning meetings.
Primitive 4: Tempo Engine
Every team operates on a rhythm — daily standups, weekly reviews, quarterly pivots. The Tempo Engine synchronises these rhythms so the organisation breathes as one organism rather than a collection of siloed clocks.
Primitive 5: Signal Layer
The nervous system. A BOS must be able to detect weak signals — a rising defect rate, a competitor's pricing move, a regulatory change — and route them to the right decision node before they become crises.
Putting It Together
These five primitives aren't software features. They are organisational design decisions that your software should make legible and enforceable. Most companies have fragments of all five — the work is integration.
The views expressed here are entirely my own. Follow along daily as I map the full architecture of a Business Operating System.