TL;DR

  • Define the handoffs, owners, and observable states before automating a workflow.
  • Agree on completion evidence and design the path for missing responses or conflicting records.
  • Start with one bounded process and measure accepted outcomes alongside review and recovery effort.

There is a predictable moment in almost every conversation about applying AI to a business.

Someone describes a messy process involving email, spreadsheets, text messages, tribal knowledge, and one employee who knows how everything really works. Then the room jumps directly to an agent that will automate the whole thing.

The instinct is understandable. The technology is exciting, and the current process is painful.

But automation is not a substitute for deciding how the work should operate.

AI can remove friction from a good workflow. It can also make a broken workflow fail faster, more confidently, and at greater scale.

For the ownership layer of this workflow, see how to assign responsibility beyond notifications so every open item has a clear next owner and escalation path.

Once the workflow defines completion, give AI actions verifiable receipts so a person can inspect the result without reconstructing the conversation.

Before granting consequential access, test whether a completed action was authorized using the boundary scenarios in this companion analysis.

Start with the handoffs

Map who owns the work as it moves between people, tools, and stages. For each handoff, name the trigger, required information, next owner, and evidence of acceptance. This makes the dependency visible before an AI agent begins moving work through a process whose responsibilities may still be unclear.

A salesperson believes operations received the details. Operations believes the customer has approved the scope. The technician believes the equipment is already onsite. Billing believes the closeout documents were uploaded. Everyone completed the task visible to them, and the job is still not done.

Before adding AI, draw the handoffs:

  • What event starts the work?
  • Who or what owns the next state?
  • What information must travel with it?
  • What proof is required before it can move forward?
  • What happens when the expected response never arrives?
  • Who is accountable for final closeout?

This does not require a consulting project. A whiteboard and the people who actually do the work are usually enough to expose the gaps.

The important thing is to map the workflow as it exists, not as the standard operating procedure says it exists.

Name the states of the work

Define the states that describe what is true, such as approval pending or documentation accepted. Give each transition an owner and a required confirmation. Activities like calling or uploading remain useful, but the workflow should advance only when the evidence supports the next state.

Automation works better when the system is organized around states:

  • request received;
  • scope verified;
  • customer approval pending;
  • materials confirmed;
  • visit scheduled;
  • work completed;
  • documentation rejected;
  • closeout accepted;
  • invoice eligible.

A state tells the system what is true. An activity only tells it that somebody tried something.

That distinction matters because AI agents are good at generating and routing activity. Without a clear state model, they can create the appearance of motion while the underlying job remains stuck.

A useful automation should move work from one verified state to another. It should not merely produce more messages about the work.

Decide what “done” means

Define completion as an observable result agreed by the people who depend on it. Include required documents, checks, approvals, and exception handling. An agent can then help gather that evidence and identify gaps instead of treating the latest message or completed task list as proof that the job is finished.

The field technician says the work is done because the equipment is installed. The project manager says it is not done because the photos are missing. The customer says it is not done because the old equipment was left onsite. Finance says it is not done because the purchase order does not match.

AI cannot resolve that ambiguity unless the organization does first.

Define completion in observable terms. A field visit might require:

  1. the requested work is physically complete;
  2. required tests pass;
  3. photos and serial numbers are attached;
  4. the customer contact signs off;
  5. exceptions are documented;
  6. closeout is accepted by the client system.

Now an agent can help. It can check for missing documentation, compare the work order to the submitted photos, request a signature, update the customer, and escalate an exception. The workflow gives the intelligence somewhere useful to operate.

Keep humans at the expensive edges

Allocate human review according to consequence, uncertainty, and the ability to recover. Give an agent room to prepare work and perform permitted routine actions with clear verification. Require a specific approval when the next step creates a commitment or risk outside those limits, and preserve the context for that decision.

Good candidates for automation are often reversible and easy to verify:

  • extracting structured details from a work order;
  • drafting a customer update;
  • checking whether required fields are present;
  • comparing a schedule against technician skills and distance;
  • reminding an owner when a response is overdue;
  • summarizing the history of an open issue.

Poor candidates for unsupervised automation are actions with large consequences and weak feedback:

  • committing to scope that has not been verified;
  • promising a service date before dependencies are confirmed;
  • approving unusual spend;
  • closing a customer complaint based only on internal notes;
  • deleting records that may be needed later.

The right boundary will differ by business. The principle is stable: automate where the work is reversible and observable; add approval where the cost of being wrong compounds.

Build the exception path first

Define what happens when a response never arrives, a record conflicts, or an action cannot be verified. Give the exception an owner, a deadline, and a permitted next step. The system should preserve relevant context and pause consequential actions when the evidence or authority required to continue is missing.

What happens when the address is wrong? When the technician calls out? When the customer says the work was never authorized? When two systems disagree? When the model is uncertain? When the input is technically complete but obviously inconsistent?

An operational AI system needs somewhere honest to put uncertainty. It should be able to stop, preserve context, assign an owner, and explain why the work cannot safely continue.

“Needs review” is not a failure of automation. It is a necessary state in any system that interacts with reality.

Automate the operating system, not the chaos

Use AI to execute a workflow whose states, responsibilities, and completion evidence are already explicit. Begin with one bounded process, test its normal and exception paths, and measure accepted outcomes. Expand automation when that evidence supports it, including the human effort needed to review, correct, and recover the work.

That can feel slow compared with launching an agent. In practice, it is the fastest route to something people will trust.

Once the workflow is clear, AI becomes much more useful. It can interpret messy requests, maintain context across handoffs, surface exceptions, draft communications, and complete repetitive work without losing sight of the real outcome.

The best automation does not make a chaotic process invisible. It makes a sound process easier to execute.

Frequently asked questions

Do we need to replace our systems before adding AI?

Not necessarily. Start by checking whether one workflow has usable data, clear ownership, and enforceable permissions across the systems it already uses. Some gaps require remediation; that does not automatically mean replacing the entire application estate.

Which workflow should we automate first?

Choose a recurring process with an identifiable owner, accessible evidence, a clear outcome, and manageable consequences if it fails. Avoid choosing solely because a demonstration is easy. The exceptions and verification path matter as much as the routine steps.

How should we measure whether the automation helped?

Compare accepted outcomes, elapsed time, human review, rework, and total operating cost against a baseline. Keep attempted actions separate from completed work, and record any control violations or unresolved exceptions.