AI absorption
An organization's capacity to take in AI capability: to accept, operationalize, own and retire old work. Model capability can rise faster than absorption, which then becomes the binding limit.
AI absorption is the organization's ability to turn capability into operating change. It covers accepting a new output, putting it into a real process, assigning someone to own it, handling its exceptions, and retiring the work it replaces.
Technical capability can grow faster than absorption. When that happens, the limit is no longer what the model can do but how much change the organization can absorb: the queue of accepted work waiting to be operated, managerial time, and clear ownership of exceptions. Treating that queue as observable is the first step toward deciding whether to scale a tool. See capability readiness and binding constraint.
Related terms
Capability readiness
How ready an organization's actions are to be used by AI agents: whether each action is a real business capability, exposed cleanly, with clear permissions, side effects and recovery.
Unit of change
The thing an AI program sets out to change: a tool, a task, a workflow, a decision or the whole operating model. Choosing too small a unit is why adoption rises without value.
Operating model
How an organization actually runs: its workflows, decisions, roles, governance and handoffs. AI creates value when it changes the operating model, not when it is bolted onto the old one.
Binding constraint
The main reason an AI idea was rejected at a given time, recorded so the decision can be reopened only when that specific constraint actually changes.