DRT Into Action — a 52-week practitioner series.
Three posts a week translating a decade of research on AI transformation into board-ready frameworks, diagnostic questions, and operational artifacts. Started January 2026.
How the series works
Each week follows a stable three-part structure that makes the work cumulative rather than merely informative.
A — CONCEPT PRIMER
Reframes a managerial object — what a decision is, what an event is, what a seam is — so it can be governed rather than merely managed
B — BOARDROOM REFRAME
Converts the concept into the hard questions and decision gates executive teams can actually use in a leadership session or board meeting
C — PLAYBOOK BUILD
Produces a concrete artifact — a register, a diagnostic test, a drill, a dashboard — ready to apply immediately and revisit as the system evolves
Grounded in the Dynamic Relationality Theory trilogy, the co-creation research program, and the REAL governance framework. By the end of 52 weeks, readers have a complete operating system for governing AI-enabled organizational transformation.
Featured posts
Concept Primer · Week 8
Events vs. Initiatives: The Unit of Change Is the Event
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.
Boardroom Reframe · Week 11
From Boxes to Seams: The Governance Object You’re Probably Not Governing
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?
Boardroom Reframe · Week 6
From “Move Fast” to “Learn Safely”
In Timeline A, the board hears ‘we must move faster.’ Speed amplifies hidden coupling, governance becomes retrospective narration, and trust becomes a demand rather than a property. In Timeline B, the board reframes speed: the rate at which we can learn without violating invariants. That sentence does two things the ‘move fast’ story cannot: it forces explicit invariants, and it turns change into an observable, classifiable event that can be authorized, monitored, and reversed.
Playbook Build · Week 8
The Event Ledger and the Reopen → Redesign → Re-stabilize Loop
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.
Recent posts
- The risk story everyone tells
- Why interoperability beyond APIs requires meaning + obligation transport
- Making authority measurable, not rhetorical
- Same company, two timelines
- Why “who decided?” is the first GSI question
- A patterns library for governing risk-bearing units
Join practitioners and researchers receiving three essays per week on AI transformation governance.
Want the framework in practice, not just in writing?
The advisory work puts this diagnostic directly to work in your organization’s specific situation.