Enterprise AI Operating Capability
Write roles, playbooks and review criteria from one process definition. Check for gaps between authority and responsibility.
Discuss a Pilot( 01 )
Start with the Use Case
Keep purpose, inputs, outputs and authority in a single process definition so a change in acceptance criteria tells you what must update across roles, playbooks and review.
Break Down the Work
Set a Shared Acceptance Standard Define what counts as acceptable first. Give each step a purpose and an output. When connecting steps, name who consumes the earlier output and under what conditions the next step may start.
Use the same process definition for role responsibilities, playbooks and performance criteria. Describe who handles exceptions, what authority they have and how decisions are reviewed.
Check two things at handover: whether the upstream output passes, and whether the next step is ready. Recording both shows whether work needs correction or is waiting on a dependency.
Discuss a PilotAfter producing the work, check whether the recipient can actually use it.EXAMPLE 01 · PILOT OBSERVATION
( 02 )
Pilot One Workflow
Log waiting and rework separately so the right owner can address each.
EXAMPLE 02 · PILOT OBSERVATION
Give the method to someone who did not design it and see whether the result still passes.
EXAMPLE 03 · PILOT OBSERVATION
Passing upstream review does not mean the next step has authority or resources.
EXAMPLE 04 · PILOT OBSERVATION
Knowing when to stop is part of a good pilot.
EXAMPLE 05 · PILOT OBSERVATION
After producing the work, check whether the recipient can actually use it.
EXAMPLE 06 · PILOT OBSERVATION
Log waiting and rework separately so the right owner can address each.
EXAMPLE 07 · PILOT OBSERVATION
( 03 )
Connect the Steps
Use four levels to describe results: business outcomes, processes, functional responsibilities and individual actions. Then verify that the work at each level contributes to the overall goal.
Compare quality, time, rework and cost before and after the change. Track manual intervention and exceptions alongside generation speed.
An AI skill brings together the knowledge, tools and rules for a task. The human playbook and the skill share acceptance criteria and specify when a person must take over.
Set the scope, owner, baseline and stop conditions before the pilot. Continue observing if evidence is unclear, and roll back if risk grows.
Define what counts as acceptable first.
Give the method to someone who did not design it and see whether the result still passes.EXAMPLE 08 · PILOT OBSERVATION
( 04 )
Make the Method Reusable
Ask another colleague to repeat the task using the playbook or skill. Note gaps that still need verbal explanation. Expand only when the process can be repeated reliably.
Compare on the Same Basis Define what counts as acceptable first. Set rules for data scope, access and retention before using sensitive information. Escalate to an authorised person when access, inputs or risk limits are unclear.
Agree on interfaces, delivery, acceptance and dispute handling with external partners. Each organization can keep its own process while sharing a standard at the handover.
Bring one live workflow to the discussion. Describe the desired outcome, the bottleneck, the roles involved and the samples available for comparison.
Define what counts as acceptable first.
Discuss a Pilot( 05 )
Keep a Record and Review
Possible deliverables include a process map, a human–AI responsibility matrix, acceptance criteria or a pilot review. Confirm deliverables and timing after discussing scope.
01
Shared Criteria
V2.0 is an interim research framework. Test implementation conditions and business impact on real work, then use the evidence to decide whether to expand.
02
Review
Use four levels to describe results: business outcomes, processes, functional responsibilities and individual actions. Then verify that the work at each level contributes to the overall goal.
03
Comparison Samples
Name the operating goal and the people who use the result. Choose one workflow with observable outputs and manageable risk.
04
Authority
Trace a real deliverable back through the workflow. Record its inputs, owner, acceptance criteria and downstream recipient.
05
Human Takeover
Give each step a purpose and an output. When connecting steps, name who consumes the earlier output and under what conditions the next step may start.
1
One
Workflow
4
Four
SOP Levels
2
Two
Handover Checks
4
Four
Evidence Checks
( 06 )
Use the same process definition for role responsibilities, playbooks and performance criteria. Describe who handles exceptions, what authority they have and how decisions are reviewed.
Connect the Steps
Discuss a Pilot( 07 )
Compare on the Same Basis
An AI skill brings together the knowledge, tools and rules for a task. The human playbook and the skill share acceptance criteria and specify when a person must take over.
Set the scope, owner, baseline and stop conditions before the pilot. Continue observing if evidence is unclear, and roll back if risk grows.
Ask another colleague to repeat the task using the playbook or skill. Note gaps that still need verbal explanation. Expand only when the process can be repeated reliably.
Use four levels to describe results: business outcomes, processes, functional responsibilities and individual actions. Then verify that the work at each level contributes to the overall goal.
Discuss a Pilot( 08 )
Break Down the Work
Set rules for data scope, access and retention before using sensitive information. Escalate to an authorised person when access, inputs or risk limits are unclear.