What makes a workflow ready for an agent (the readiness checklist)
Most processes fail an agent handoff for the same few reasons. Here is the checklist to run before you pick a first workflow.
Most processes fail an agent handoff for the same few reasons
A ranked wish list, picked on instinct
- You have a list of processes you would like to hand off, and no reliable way to rank them.
- The obvious candidates are usually the loudest ones: the month-end scramble, the inbox nobody owns, the report someone rebuilds every Friday.
- Loud and ready are different properties.
- A process can consume half your week and still resist a handoff, because the rules live in one person's head, the inputs arrive in six shapes, and nobody has written down what a correct result looks like.
- Picking wrong costs you a quarter and a good deal of internal credibility.
Six checks, run before you pick a first workflow
- You choose on evidence.
- Preparation stops being invisible.
- The first handoff is survivable.
The readiness checklist
Readiness is a property of the process, and you can inspect it before you commit to anything. Run the workflow you are considering against these six checks.
A workflow that passes all six is a candidate. One that fails a check is not disqualified; the failing check names the preparation work.
Stable inputs
Written decision rules
A definition of correct
Observable state
A bounded blast radius
A human gate on the consequential step
What changes when you run the checklist first
You choose on evidence
Preparation becomes a scoped task
The first handoff is survivable
Where this fits
This is the sorting step ahead of a Tier 1 engagement. One process, end to end, is the lowest-commitment way to see the pattern work, and the checklist tells you which process to pick. Once a workflow runs and holds, the question becomes what else follows the same shape, which is the path toward a full role.
Read more on Automate a Workflow, and on how gates and review surfaces are built in How It Works.
