The Doctrine
A structural account of why large organisations freeze under sustained speed, and what it takes to operate differently.
Most large organisations are operating with models designed for a world that no longer exists. The industrial operating model, built for stable, predictable environments, optimises throughput by centralising control. Within its valid domain, it is effective. The problem is that most enterprises are no longer operating within that domain.
Modern organisations face environments defined by continuous change, software-mediated coordination, and speed that outpaces the control cycles the industrial model was built to manage. When you apply a stability-oriented model to a volatility-defined environment, you do not get failure. You get something more insidious: sustained underperformance that looks like an execution problem, a talent problem, or a technology problem, when the actual cause is structural.
AI is the most acute current expression of this incompatibility. Organisations invest in AI capability and find that the constraint is not the technology. It is the decision architecture through which the technology must operate. But this is not an AI problem. The structural mismatch predates AI. AI simply makes it impossible to ignore.
The Kinetic Enterprise is a structural description of enterprise behaviour under sustained speed and uncertainty. It names the mechanisms by which organisations generate decision latency, lose coordination coherence, and fail to convert capability into execution. It explains why these outcomes are structural rather than incidental, and what a different operating architecture looks like.
The doctrine treats the enterprise as a system. Outcomes emerge from structure, interfaces, and feedback loops rather than from individual intent or organisational culture. When coordination fails at scale, the cause is almost always in the architecture of decision-making, not in the quality of the people executing within it.
It is not a consulting offering, a best practices catalogue, or a change management guide. It will not tell you how to restructure your organisation in eight steps. The doctrine is analytical and structural. It gives senior leaders and technologists a way to see what is actually happening and why, not a prescriptive roadmap for fixing it.
The value of the doctrine is diagnostic precision. Most organisations already have enough frameworks for execution. What they lack is an accurate account of why their current structure produces the outcomes it does.
The intended reader is a senior technologist or executive operating in a large, complex organisation where structural constraints are the dominant friction. CTOs, CIOs, and board members who have invested significantly in technology and still find that execution does not match capability. Leaders who have run the standard playbooks and found them insufficient.
The doctrine is particularly relevant to organisations operating in regulated environments, where governance overhead is significant and the tension between control requirements and execution tempo is acute.
Start with the Model if you want the analytical framework first. The model explains decision latency as a governing variable, flow as a system property, and governance as constraint rather than control.
Start with the Lineage if you want the intellectual foundations. The doctrine draws from three independent traditions: systems thinking, flow and constraint theory, and decision and manoeuvre doctrine. Understanding where it comes from clarifies what it is trying to do.
Get the Book for the full articulation. The book is the canonical form of the doctrine in its current stable version. It covers the complete analytical framework with worked examples from regulated enterprise environments.