From Proxy.Me: Agentic AI Digital Apprentices
Six maturity levels describing how work moves through organizations, where judgment resides, and how much human effort is required to convert intent into action.
The Kinetic Maturity Model describes how work moves through organizations, where judgment resides, and how much human effort is required to convert intent into action. Each maturity level represents an observable operating state defined by behavior under load rather than by aspiration, branding, or stated strategy.
The model is neither a taxonomy of tools nor a forecast of technology adoption. It exists to make complex organizational problems concrete, operational, and economically legible.
"AI produces a durable return only when it reduces the ongoing cost of coordination by relocating judgment and continuity from people into structure. Tools that accelerate execution without altering this structure improve local productivity but do not change enterprise economics."
Most organizations do not experience themselves as static. Calendars are full. Messages flow constantly. Activity levels are high. Yet when examined closely, almost every meaningful piece of work requires a sequence of human interventions before execution can begin: someone must notice the request, decide who owns it, reconstruct context, confirm priority, and coordinate the next step.
This effort happens before the work itself. It is not execution. It is activation. Structural inertia is the accumulation of this activation effort.
AI can accelerate execution inside this structure. But when activation energy remains unchanged, faster execution produces more artifacts that queue at the same coordination points. Output increases. End-to-end progress does not.
Four questions define each level and its economic implications:
Technology adoption alone does not move an organization between levels. Behavior changes first. Structure follows.
Knowledge work exists primarily in informal channels and personal memory. Email, chat, documents, spreadsheets, and meetings serve as the coordination fabric. There is no durable representation of work in motion that persists beyond individual participation.
Roles are defined by responsibilities and tasks rather than decision authority or judgment structure. Knowledge accumulates in people rather than in roles.
Under pressure: The organization tightens control. Leaders add approvals. Escalations rise. Performance depends on a small group of experienced individuals who act as informal routers, creating hero dependency.
Metrics that appear important: Task completion rate, utilization, meeting volume. These reinforce activity, not motion.
AI is adopted at the individual level. Knowledge workers use digital assistants, copilots, coding agents, and analysis tools to draft documents, write code, search information, and summarize material more quickly. This level often produces genuine early gains and tends to lift staff with weaker baseline skills more than senior peers.
Despite faster execution, the flow structure remains unchanged. Humans still decide what to work on, carry context between steps, interpret decisions made elsewhere, and route work manually.
Under pressure: Artifact production accelerates. Messages multiply. Dashboards fill. Coordination overhead grows faster than execution speed. This is the AI productivity trap.
"Many organizations will remain at Levels 1 and 2, not because they fail, but because these levels are politically comfortable. They allow visible investment, measurable activity, and incremental improvement without forcing changes to authority, role design, or decision ownership. The economic ceiling of these levels is not a technological limit. It is a structural choice."
Metrics that appear important: Time to draft, volume of artifacts, AI tool adoption rates. These measure acceleration rather than throughput.
The organization introduces a system of record for knowledge work. Requests, cases, or initiatives are captured explicitly rather than living only in inboxes and threads. This is the first structural shift: work becomes observable beyond individual participation.
Work now has a visible lifecycle. Bottlenecks can be seen. Aging work can be identified. However, routing remains manual. People still decide where work goes next and when.
Under pressure: The system holds together better. Backlogs become visible. But prioritization still requires negotiation. Humans remain the routing layer.
Metrics that matter: Percentage of work captured, average age of work items, manual handoffs per case. Visibility improves diagnosis, not motion.
Proxies are activated for a limited set of Roles, typically in pilot areas where judgment is critical and coordination costs are high. These pilots are not technology experiments. They are structural experiments. The organization is testing whether it can relocate continuity and routing from human effort into a persistent digital actor.
These Proxies are trained on Role-specific logic, including lenses, constraints, and early decision heuristics. They do not replace humans. They learn from them. In their initial form, they operate as digital assistants: retrieving context, filtering noise, preparing materials for decisions, and tracking the state of active work. The human steward teaches the Proxy by correcting its interpretations, refining its lenses, and guiding its reasoning through real cases.
Over time, the most successful pilots see Proxies begin to route work between Roles without human intervention. This is the first appearance of the mesh, though it is small and bounded. The organization begins to experience something unfamiliar: work that continues to move even when specific people are unavailable.
Flow characteristics: Proxies begin to handle intake, gather and preserve context, apply basic routing rules, and surface ambiguity early. Humans shift from moving work to shaping how work should move. Within the pilot, context no longer resets between handoffs. A case that moves from one Role to another arrives with its history, its reasoning, and its current state intact. Outside the pilot, the old pattern persists. The contrast becomes visible quickly.
Under pressure: Pilot teams behave differently under stress. Work continues to move. Context does not reset with every interruption. Decision latency drops. When a team member is sick or on leave, the Proxy preserves the Role's continuity, and the work does not stall. The contrast between pilot and non-pilot areas becomes visible, and often uncomfortable. This discomfort is productive: it creates demand for structural change rather than requiring it to be imposed.
Governance at this level: Proxy governance at Level 3 is primarily observational. The human steward watches how the Proxy interprets situations and corrects its reasoning directly. Connections are minimal and tightly scoped. What matters most is establishing governance habits that will become essential later: regular review of the Proxy's decision logs, deliberate curation of its lenses, and a clear understanding of the boundary between what the Proxy knows and what it can touch. Organizations that skip these habits during the pilot will struggle to govern a larger mesh later.
Transition preconditions (from Level 2): Work must already be visible (Level 2 is a prerequisite). At least a few Roles must be defined as decision-making structures with explicit lenses and boundaries. The pilot area must have a human steward willing to invest in teaching the Proxy. This is an apprenticeship, not a technology rollout.
Metrics that matter: How much work is routed or contextualized by Proxies rather than by humans? How many clarification cycles have been eliminated? Has the pilot area reduced its dependence on specific individuals for continuity? This is the point where judgment begins to compound. Each case strengthens reasoning; each correction refines lenses; each successful routing builds the first strands of the mesh.
The Proxy model extends across the organization. Roles are consistently defined as decision-making structures rather than task lists. The Work Graph serves as the primary representation of how value flows. Scenarios are introduced to dynamically reconfigure behavior based on conditions.
This is the level where the mesh becomes real. Proxies coordinate with one another across organizational boundaries, routing work, negotiating shared scenarios, and flagging dependencies without waiting for human intermediaries. The organization begins to operate as an integrated system rather than a collection of managed teams.
Humans do not disappear. They shift. Instead of carrying work from step to step, they shape how work should move. They refine lenses, adjust scenario definitions, review the mesh's behavior, and intervene when situations require judgment the Proxy cannot provide. The human role becomes architectural rather than operational.
Flow characteristics: Work flows primarily through the mesh of Roles and Proxies. Context travels with the work. Handoffs preserve history, reasoning, and state. Flow becomes resilient rather than brittle. When a Role is overloaded, the mesh can reroute work through alternative pathways. When a scenario changes, Proxies adjust without waiting for instructions. The organization begins to experience a phenomenon difficult to describe without living through it: work moves faster when pressure increases.
Under pressure: The organization accelerates rather than freezes. Work reroutes around bottlenecks. Scenarios tighten oversight where risk is high and relax it where routine work can continue. Speed and safety reinforce each other. Because governance is embedded in how work moves rather than applied as an external check, the organization does not need to choose between moving fast and moving carefully.
Governance at this level: Governance is systemic. Constraints are enforced continuously across the Work Graph. Mesh governance becomes essential: cumulative operational authority of multi-Proxy flows must be measured and managed. Authorization lists, mesh partitions, and coordination pattern reviews become standard mechanisms. Points of View are shared across Proxies, versioned, and audited. See Appendix D for detailed treatment.
Transition preconditions (from Level 3): Sufficient Roles defined as Kinetic Roles with explicit lenses, scenarios, and boundaries. The Work Graph established as the shared representation of work motion. Governance matured beyond individual Proxy oversight to systematic mesh governance. Most importantly, leadership must have shifted from managing execution to shaping the conditions under which execution occurs.
Metrics that matter: End-to-end flow time, decision latency, frequency of coordination meetings. The defining characteristic is that throughput increases without proportional increases in human effort. If the organization is getting faster but people are working harder, it is still at Level 2 or 3 with better tools.
The Kinetic operating model extends beyond knowledge work into physical operations, field activity, and customer-facing systems. The distinction between digital and physical coordination dissolves.
Proxies at this level do not just route knowledge work. They coordinate across domains that were previously managed independently: supply chain decisions inform customer commitments, field operations data reshapes resource allocation, regulatory signals propagate through the Work Graph to every Role they affect. The organization operates as a single sensing and responding system rather than a collection of functional units.
This level is not theoretical. It describes the operating state that highly mature organizations will approach as agentic technology, sensor networks, and real-time data infrastructure converge.
Flow characteristics: The entire value chain is orchestrated through a shared Work Graph. Signals propagate across domains without manual translation. A disruption in one part of the system triggers scenario adjustments throughout the mesh. Work is not just flowing. It is self-correcting. The mesh identifies bottlenecks before they become visible to humans, reallocates capacity, and detects when a scenario definition is no longer adequate.
Under pressure: The organization adapts its shape in real time. Resources shift. Priorities rebalance. Under extreme pressure, governance tightens automatically: scenarios escalate, veto lenses activate more frequently, human oversight intensifies in areas of highest risk while routine work continues flowing. The response to crisis is a coordinated, system-wide adjustment that happens faster than any human coordination network could achieve.
Governance at this level: Governance operates at the system level. Policy spans digital and physical domains. Cumulative operational authority is measured continuously across the entire mesh. Governance is no longer experienced as friction. It is experienced as stability. See Appendix D for the governance implications of cross-domain deployment contexts.
Transition preconditions (from Level 4): Technical infrastructure supporting real-time signal propagation across physical and digital domains. Data from sensors, field operations, and customer interactions flowing into the Work Graph. Regulatory acceptance: organizations must demonstrate that their governance architecture provides equivalent or superior accountability to traditional human-driven controls.
Metrics that matter: System resilience under stress, speed of resource reallocation across domains, total coordination cost as a percentage of operating expense. At this level, coordination cost should be declining even as organizational complexity increases.
One of the most common traps in organizational transformation is measuring the wrong things at the wrong time. Metrics meaningful at one maturity level become misleading at another.
The progression from activity to visibility to structure to throughput to system behavior reflects the underlying shift in where judgment and continuity reside.
The maturity levels are experienced differently across executive roles. While the underlying structure is the same, the risks, constraints, and signals that matter most vary.
Appendix D provides a detailed treatment of how Proxy governance operates in practice, including the distinction between governing reasoning and reach, measuring cumulative operational authority, mesh partitions and authorized node lists, and the governance implications of different deployment contexts. This model describes when governance capabilities become necessary; Appendix D describes what those capabilities look like in practice.
The pace of technological change will continue to accelerate. Language models are improving rapidly. New classes of models, including world models and systems designed to maintain longer-term memory and intent extraction, are already emerging.
None of these developments alters the core constraints described in this model. More capable intelligence does not, by itself, reorganize how work moves through an enterprise. Even the emergence of artificial general intelligence would not eliminate this reality. Such systems may reason better than humans, but unless organizational judgment, flow, and continuity are made explicit and structural, that intelligence will still be forced to wait at the same coordination boundaries.
"As intelligence becomes cheaper and more abundant, structure becomes the limiting factor. The organizations that benefit most from future advances will not be those that adopt more capable models, but those that have already reduced activation energy, made judgment explicit, and embedded continuity into how work flows."
Each maturity level reflects a different answer to the same question: Where does judgment live, and who carries motion?
A free set of online self-assessments is available to help you diagnose your organization's current maturity level and identify feasible next steps.
Browse ResourcesDownload free sample chapters or learn about the complete book.
Browse Resources About the Book