
Enterprise AI Operating Capability
Start with one real workflow. Use evidence to see what improves and what your team can repeat.
AI Is a Start.
What Can It Improve?
Operating capability improves when work results improve and the method can be repeated reliably.
Where Does Value Come From?
Operating capability begins with the value stakeholders need, not with the use of tools or an increase in output volume.
Read more: from value to results, processes and handoffs
Every business workflow has one or more people who need to use its result. The first questions about value are: who is this result for, and what judgement, action or decision will it enable them to make? Only when this is clear can the process, responsibilities and AI participation have a sound basis.
Value is expressed through results. A result is not simply a file or an output, but a deliverable that stakeholders can actually use. Its content, scope and standards must be clear enough for the recipient to continue working or make a decision. Once defined, the result constrains the entire process: the process exists to produce that result, not merely to complete activities. The local purpose of each process must explain how it contributes to the final result.
Without a prior definition of value, a process can become a continuation of tools or habits. AI can generate materials faster, but unless someone can explain who will use them, the standards by which they will be accepted, and how acceptance enables the next step, greater speed does not automatically become operating capability. Operating capability requires results to be produced consistently and reliably taken up by the next user.
Before introducing any tool or changing any workflow, therefore, this step must come first: name the stakeholders, state the value they need, and translate that value into observable results with clear acceptance criteria. Only then does the process have constraints, the division of work between people and AI have boundaries, and subsequent handoffs and evidence have meaning.
The First Workflow
Read more: why start with one workflow
It contains operating objectives, process interfaces, roles and responsibilities, and evidence at the same time. Operating objectives come from the value stakeholders need and are expressed as results with clear acceptance criteria. Process interfaces require every handoff to distinguish whether the result is acceptable from whether the next process can start. Roles and responsibilities translate result requirements into specific accountability, authority and takeover points. Evidence records execution, acceptance, downstream use and achievement of objectives, and supports testing for reuse. All four elements appear within the same workflow and constrain one another.
Choosing one workflow means testing these four elements within a single observable scope. If a result defined by value cannot pass through the process interfaces, results and handoffs are misaligned. If responsibilities do not establish who is accountable for acceptance or start conditions, accountability is disconnected from the interfaces. If the evidence cannot distinguish a result-quality problem from a start-condition problem, the recording method is insufficient to support judgement. Any inconsistency is exposed directly within that workflow.
A single workflow is the smallest unit because it includes every necessary link from value to capability, while remaining small enough to define its scope, owner, baseline and stopping conditions. Looking at less than a workflow, such as a single action or output, leaves out interfaces and downstream use, so transfer cannot be tested. Changing more than one workflow at once introduces too many variables to identify where the logic fails. At this scale, it becomes possible to test all of the following together: whether value defines the result, whether the result constrains the process, whether handoffs involve separate judgements, whether responsibilities align, and whether evidence supports decisions about reuse.
Before expanding any approach, therefore, this test must first be completed in a real business workflow. Only when its objectives, interfaces, responsibilities and evidence are mutually consistent, and repeat execution confirms this, is there a basis for judging whether the method has become lasting operating capability.
Signs You’re Ready to Review a Workflow

Start With the Business Result
The First Conversation
What we’ll cover
The intended value
The process and the handoff
Roles and authority
AI Skill design
Acceptance and evidence
The pilot and review
Three Working Principles
Value, handoffs and evidence are three interdependent theoretical principles. Together, they determine whether a useful one-off output can develop into repeatable operating capability. Without any one of them, this transformation cannot be completed.
Value
Handoffs
Evidence
Value, handoffs, and evidence must all hold together. Without any one of them, effective practices cannot become repeatable operating capability.
Read more: how value, handoffs and evidence work together
Value
Value comes before tools. Operating capability starts with the value stakeholders need, not with what a tool can do. Value defines the result: who needs it, what they will use it for, and what counts as acceptable. Once the result is explicit, it constrains the process's purpose, scope and acceptance criteria. Without value coming first, processes and the division of work lose direction; however much is produced, it remains activity rather than a usable deliverable.
Handoffs
A handoff requires two separate judgements. The first asks whether the previous process's result meets the agreed standard. The second asks whether the next process has the permissions, resources and dependencies needed to start. These judgements involve different accountable parties and directions for improvement. Combining them makes problems difficult to locate: an unacceptable result may be mistaken for a coordination issue, or missing prerequisites for a quality issue. Without clear handoffs, results cannot reliably reach the next user, and value cannot be realised.
Evidence
Evidence determines whether a method can be retained and expanded. Four kinds of facts must be recorded separately: whether work was performed as designed, whether the result passed acceptance, whether the downstream user actually used it, and whether the operating objective improved as a result. Another person must then repeat the work using the same handbook or Skill to test whether the method no longer depends on its original designer's personal experience. Without this evidence, occasional success cannot be distinguished from repeatable capability, nor can a sound decision be made to retain, adjust or stop the method.
All three principles must hold together.
With value alone, results cannot be passed on consistently; with handoffs alone, there is no basis for judging whether what is passed on is useful; with evidence alone, there is no assurance that what is being tested serves the right value. If any principle is missing, an effective approach remains tied to a particular person and a particular execution, rather than becoming operating capability the organization can call upon again.
When designing or reviewing any business workflow, therefore, check all three at once: has value been defined as a result with clear acceptance criteria; have handoffs been separated into two independent judgements; and can the evidence support a decision about reuse? Only with all three in place can a pilot potentially turn a single improvement into lasting capability.
I’m Amber Liu
About me
My approach connects stakeholder value to processes, role responsibilities, acceptance standards, and evidence. These two research notes show how the approach applies to business workflows.
Rebuilding Enterprise Operating Capability with AI Role Responsibilities, Processes, and Human–AI CollaborationView all research publications →

