Skip to content
MOVEMENT POSSIBILITY ACCOUNTABILITY COHERENCE

Each dimension has its own diagnostic question, its own failure mode, and its own governing toolkit — introduced in the Fabric of Coherence practitioner series and grounded in the DRT research program.

Forecasts get mistaken for futurity. AI use cases are chosen because they are trending, not because they fit this organization’s specific conditions. Pilots multiply without ever converting into durable capability.

Programs proliferate while the organization itself doesn’t move. Translation fails at the handoffs between teams, practices, and platforms — what one group builds, the next can’t recognize or use.

Decisions break at the seams between functions, partners, and regulators. Evidence and obligations don’t travel with the decision. There’s no repair or rollback discipline when something goes wrong.

DRT Into Action — 52-week practitioner series

Three posts a week translating a decade of AI transformation research into board-ready frameworks, diagnostic questions, and operational artifacts. Each week: a Concept Primer that reframes how a problem should be governed, a Boardroom Reframe that converts it into hard executive questions, and a Playbook Build that produces an artifact ready to use immediately.

Most transformation programs fail in a familiar way: the organization does many things, on schedule, with competent project management — and yet the underlying system stays brittle. DRT treats this as a modeling error: we have been trained to treat initiatives as the primary unit of change. But the system itself does not reorganize around initiatives.

Boards can ‘do governance’ while drift accelerates. They govern boxes, while the system runs on seams. The board’s real object of oversight is not the initiative list — it is the system of decision travel: where does authority actually move, where does accountability thin out, where do evidence rules change as decisions cross interfaces?

Most organizations measure event-like material through initiative-shaped proxies: tickets closed, time to resolve, milestones hit, adoption recovered. These metrics are not useless — they are aimed at the wrong object. They track operational closure, not systemic re-stabilization. The Event Ledger treats events as rupture-driven state transitions that propagate across the organization and persist until assumptions have been reopened, couplings redesigned, and stability re-achieved.