Lexicon · IV · The organization
Agentic workflow
A business process redesigned so that agents own entire steps of it, under defined oversight, rather than a chat bolted onto the side of the existing process.
The analogy
You do not drop a robot into the middle of a workshop designed for humans: it would get in everyone's way. You redesign the line around what the robot does well, and reposition the craftsmen where their hands are irreplaceable. The agentic workflow is that redesign, applied to office processes rather than the shop floor.
Redrawing the process
Toggle between yesterday and today, then tap each step: watch who does what, and where the controls sit.
Scenario: handling a customer claim
7 human steps, 6 queues in between; typical delay: 5 days.
Tap a step to see who owns it and what changes.
Intake · Human step
An advisor reads the claim and records it. Queue: a few hours.
The process was not augmented. It was redrawn.
The redesign, step by step
The path fits in five moves. Map the real process: not the official one, but the one actually practiced, with its queues. Spot the delegable stretches: repetitive, tool-equipped, verifiable, where an agent can own the step end to end. Define the controls before plugging in: thresholds, approvals, samples; oversight is designed together with the flow, not bolted on after the incident. Instrument: readable logs, traceability for every case. Widen by increments: delegate small, measure, raise the thresholds as the controls keep holding.
A concrete example
Claims processing: yesterday, seven steps held by humans. Today, an agent qualifies the request, retrieves the history, checks the contract and prepares the response and the goodwill gesture; an advisor decides and signs; an audit samples every week. The process was not "augmented": it was redrawn around the delegation and its control points.
Where to place the humans
Three places, one rule: the human goes where their judgment is the product. Hard-to-reverse decisions: committing money, answering publicly, terminating a contract. Exceptions: the case that fits no pattern, which the agent must know how to escalate rather than force into the mold. The relationship: the moments when the customer must hear a person, not a process. The classic mistake of "the old process plus a chatbot": keeping humans as form-carriers between two automated steps. What you want is the opposite: fewer humans in the flow, placed at the points where their signature truly commits.
What it is NOT
It is not "the old process, plus a chatbot": if nobody redefines the roles, AI remains entertainment at the margins of the real flow of work. And it is not the disappearance of the human: it is their explicit repositioning. The oversight points are part of the process design itself, not an appendix.
Often confused with
The distinction that changes the conversation.
- Classic workflow (BPM)
- The classic workflow moves forms between humans along fixed steps. The agentic workflow hands entire stretches to agents and reserves for humans the decisions that matter. The first optimizes how work circulates; the second redefines who does it.