PAT-380 · Pattern

When Your Business Wants Agents but Has No Defined Workflow

When a business wants AI agents before it can clearly describe how work should move, agent adoption may expose an operating-model problem rather than a prompting problem.

Mellorca Patterns·AI Readiness, Agents & Intelligent Operations·2 September 2026

Observable condition

The organization wants an agent to “handle onboarding,” “manage customer requests” or “run the reporting process.” But when the team tries to explain the work, every case seems different. Ownership changes depending on the customer. Exceptions live in people's heads. Approvals happen in chat. The next step is often “ask Sarah” or “check with finance.”

The desired automation is clear at a high level. The operating logic underneath it is not.

Realisation

An agent cannot reliably execute a workflow the organization itself has not defined. The more autonomy an agent receives, the more important it becomes to specify outcomes, boundaries, decision rules, escalation paths and human review.

Microsoft's 2026 Work Trend Index describes leading AI users as more likely to document agent workflows, human handoffs and quality standards. Its broader conclusion is that capturing AI value requires rearchitecting work, not simply adding an agent to the existing mess.

Realisation promptCould two experienced employees independently describe the same workflow, including exceptions and escalation rules, without disagreeing about how it actually works?

Identification

This is a workflow-definition and agent-readiness problem. The visible ambition is AI adoption. The structural issue is that the business has not yet translated its operating knowledge into a sufficiently explicit system for an autonomous actor to follow safely.

Diagnosis

Agent initiatives struggle when:

  • the process has no clear owner or outcome;
  • handoffs depend on messages and individual judgement that is not codified;
  • exceptions are frequent but not classified;
  • required data is fragmented or unreliable;
  • approval and escalation boundaries are undefined;
  • nobody has specified what the agent may do versus what a human must decide.

In that environment, the agent does not remove ambiguity. It inherits it.

Commercial impact

The Commercial Value Wrapper is productivity, margin, scalability, innovation and competitive advantage. A well-designed agent can absorb repetitive execution and expand capacity. A poorly defined one can create review overhead, inconsistent outcomes and new exceptions that consume more human attention than the original process.

The commercial opportunity is therefore not “use agents everywhere.” It is to identify workflows where explicit operating logic, reliable data and sensible human control make autonomy economically useful.

Common misidentification

The common response is to improve prompts or switch models. Better models and prompts matter, but they cannot define the business's approval policy, ownership model or exception rules on its behalf.

If the workflow is ambiguous, technical sophistication can automate ambiguity faster.

Possibility

A better state defines the outcome, common path, exceptions, required data, permissions, quality checks, escalation rules and human accountability before significant autonomy is granted. The agent operates inside that design and produces traceable work that people can review and improve.

Intervention

Choose one bounded workflow rather than a broad job description. Map how work actually moves, identify decision points, separate deterministic steps from judgement, define exception classes and specify human handoffs. Then determine what data and tools an agent needs and what authority it should not have.

The intervention may combine process redesign, integration, data cleanup, agent orchestration, evaluation, permissions and human-review controls. The agent is one component of the operating model.

Practical diagnostic questions

  • Is the workflow documented from trigger to outcome?
  • Which steps require judgement and which follow stable rules?
  • What exceptions occur most often and who owns them?
  • What data must be trusted before the agent can act?
  • Where must a human approve, review or take over?
  • How will the organization know whether the agent is performing well?

Bottom line

Wanting AI agents before defining the workflow is a readiness signal. The opportunity is real, but durable agent value comes from combining capable models with explicit operating design, trustworthy data and clear human accountability.

Sources and further reading

Related Mellorca reading

Article summaryIf an agent initiative cannot be described as a clear workflow with defined data, ownership, exceptions and human handoffs, the business may not have an AI problem yet—it may have a workflow-definition problem. Fixing that foundation can determine whether agent adoption creates leverage or merely new supervision work. If this condition is familiar in your business, explore Mellorca's solutions or start a conversation with us. We can examine where agentic automation is viable and what needs to be designed first.