Agentic operating-model design
Assign accountability for work shared by people and agents
Agents are introduced into processes designed entirely around human roles. The decision is how to assign accountability for work shared by people and agents. The work begins with your actual workflow and looks for the evidence that separates intended behaviour from a consequential exception. It is particularly relevant to COOs and operating-model leaders. A useful outcome is an explicit account of what was examined, what remains uncertain, and which decision the evidence can support.
The operating choices relationship
- Process ownership
Establish the basis for production owner.
- Control reviewer
Define challenge and approval responsibilities.
- Agentic operating model
Retain the scoped finding and its unresolved dependencies.
Decision
Frame the decision around production owner
Questions and the evidence they need
- Production owner
- Inspect process ownership for the relevant constraint or observation.
- Control reviewer
- Inspect decision rights for the relevant constraint or observation.
- Intervention route
- Inspect service responsibilities for the relevant constraint or observation.
The decision is how to assign accountability for work shared by people and agents. This is relevant to COOs and operating-model leaders when agents are introduced into processes designed entirely around human roles. Name the affected workflow, the consequence of a wrong decision, and the owner who can act on the result. The initial discussion should establish which evidence is already available and which uncertainty is material enough to investigate.
The specific failure hypothesis is that the agent performs work but no team owns exceptions, corrections or changing its authority. It remains a hypothesis until examined in the deployment. Existing internal tests or operating records may already resolve it; identify the uncovered question before commissioning additional work.
Mechanism
The operating model must name who owns live decisions
Relationships within operating choices
- Production owner
- Assign responsibility for useful completed work.
- Control reviewer
- Define challenge and approval responsibilities.
- Intervention route
- Resolve exceptions and lifecycle changes.
What this specialty examines
An agentic operating model should assign responsibility throughout the lifecycle. Separate ownership of business outcomes, technical operation, control review, exception handling and authority changes. Agents can execute tasks, but accountability for the process still needs a named human role.
The review should map production ownership, control review, human intervention and lifecycle decisions. Identify the normal route, relevant exceptions and the authoritative record of the outcome. Inspect the relevant business-system record, enforcement event or process evidence alongside any reported status. Keep incomplete cases visible, with an explanation of what their absence prevents the owner from concluding.
The tradeoff to make explicit
For this decision, central control promotes consistency while local workflow ownership preserves operational context. Compare the available design or operating choices against the same intended outcome. If one option removes a required control or changes the task boundary, describe that difference before treating its apparent simplicity, speed or lower effort as an improvement. The decision should expose the tradeoff instead of burying it in an aggregate score.
Preparation
Connect the working inputs to the boundary being examined
Evidence packet for production owner
Illustrative working format
- Process ownership
- Identify the accountable role and verify its decision rights or availability.
- Decision rights
- Check its relationship to the relevant workflow and expose missing context.
- Service responsibilities
- Identify the accountable role and verify its decision rights or availability.
- Escalation paths
- Identify provenance and the specific decision this material can inform.
Start with process ownership, decision rights, service responsibilities and escalation paths. Identify the owner, revision and operating context of each source. Sanitised examples may support initial design, but differences from actual conditions should remain explicit. Where direct access is unsuitable, a customer-controlled evidence or execution route may be considered, with agreed handling and retention.
The scope also needs the business sponsor, agreed expectations for a representative business hypothesis, and the authority to inspect the relevant boundary. Specify what evidence would distinguish the failure in which the agent performs work but no team owns exceptions, corrections or changing its authority from acceptable behaviour. If stakeholders disagree about intended behaviour, resolve the interpretation before classifying the observed difference as a defect.
How the work proceeds
Carry production owner through to an accountable finding
From the scoped material to a decision record
- Process ownership
Establish the existing process and its constraints.
- Control reviewer
Apply the scoped check to intervention route.
- Agentic operating model
Record the evidence, open dependencies, and the owner’s next decision.
Establish the problem and comparison baseline
Bring process ownership, decision rights, service responsibilities and escalation paths into a working session with COOs and operating-model leaders. Separate observed process conditions from stakeholder preferences and future estimates. Describe the current approach and at least one credible alternative, including simpler process improvement where relevant. The preparation output is a comparison brief with the unresolved assumptions, accountable owner and observations that would justify advancing or rejecting the proposed option.
Examine options and challenge assumptions
Map interactions between product, engineering, operations and control teams. Test ambiguous cases through tabletop walkthroughs, especially incidents and contested outcomes. A responsibility chart is useful only if participants understand what decision they are expected to make.
Choose the next bounded commitment
Develop a proposed agentic operating model with role interfaces and accountability gaps from the examined alternatives. Distinguish immediate dependencies from questions that a bounded experiment can answer, and name who owns the operating or benefit measure. Recommend an advance, hold, revise or stop decision with a specific next observation. Any later expansion should depend on the agreed learning result and available capacity, rather than the completion of planning activities alone.
Indicative artefact
Make the agentic operating model usable by its owner
Agentic operating model
Illustrative working format
- Agentic operating model
- Identify the assessed workflow, revision, and decision boundary.
- Role interfaces
- Record accepted inputs, task meaning, and incomplete or failed outcome semantics.
- Accountability gaps
- Name the missing evidence, responsible owner, and condition for revisiting the decision.
A useful decision artefact is a proposed agentic operating model with role interfaces and accountability gaps. Supporting material may include selected cases, configuration or process records, evidence references, a disagreement log and prioritised actions. Retain the case selection rationale and material disagreements alongside the result; otherwise the result may be mistaken for complete coverage.
Illustrative scenario
Examine intervention route through a constructed exception
A constructed case and its decision paths
Illustrative scenario
- Production owner
An agent incident falls between the product owner and the platform team.
- Control reviewer
Walk the incident across product and platform responsibility boundaries.
- Intervention route
Assign the unresolved operating decision to an accountable role.
Consider a fictional situation: a customer-service team assumes engineering handles agent mistakes while engineering assumes operations owns every exception. The scenario is illustrative, with no client engagement, executed test or measured improvement implied.
For disputed support ownership, agree who corrects business records, who diagnoses implementation faults and who communicates with users. Those responsibilities may sit in different teams. The model should coordinate them rather than assign every issue to a generic AI owner.
Scope and next action
Keep the conclusion within the stated business hypothesis
Confirm fit before the next commitment
- Production owner
- This review is limited to the stated business hypothesis.
- Process ownership
- The relevant owner must confirm access and the intended operating conditions.
- Agentic operating model
- Commitment depends on the sponsor’s evidence review.
A strategy or business-case model is decision support. It does not establish demand, guarantee financial returns, commit staffing or authorise organisational changes. Any engagement depends on an agreed scope, qualified team, authorised access and confirmed availability. Bring the affected workflow, its current configuration or process, the triggering change and the evidence already available. The immediate scope question is prompted by the situation in which agents are introduced into processes designed entirely around human roles; confirm which missing observation would change the owner’s next action.
Ways to engage
Related engagement scopes
AI Readiness Assessment
Find what must change before an agent belongs in your workflow. Review the data, ownership, controls and operational dependencies together.
AI Agentic Vendor Selection
Choose against your workflow requirements. Compare agent platforms through agreed scenarios, integration constraints and operating responsibilities.
AI Transformation Sprint
Move from an interesting use case to a deliberate adoption decision. Connect workflow value, organisational readiness and the changes needed to take the next step.
Continue exploring
Related insights and resources
Choose the work before the agent
Compare agentic work with simpler alternatives, expose the dependencies behind a promising demonstration, and fund a bounded experiment with a clear decision at its end.
Measure the work that improves
Connect agent activity to accepted business outcomes, establish a credible comparison, and distinguish useful capacity from realized financial value before deciding whether to scale.
Before the pilot: five questions for agent readiness
A compelling demo leaves important questions open. Use a five-dimension rubric to examine the data, authority, evidence, ownership and people behind your next agent initiative.