Pass 01
Understand the bottleneck
- Question
- Where does the work actually get stuck?
- Output
- A plain-language workflow map.
Method
A build process for inspected work.
The engagement starts with an observed bottleneck and ends with a working agent, review loop, and operating limits.
Start a Workflow Intake01Overview
The first question is not which model to use.
The first question is what work should move, what evidence exists, which tools are available, and where human review must stay.
02The Field Method
Seven inspection passes.
Pass 02
Inventory available resources
- Question
- What tools, data, examples, permissions, and owners already exist?
- Output
- A resource list with gaps marked.
Pass 03
Map what agents can actually do
- Question
- Which parts can be drafted, recommended, checked, acted on, or escalated?
- Output
- An operating boundary.
Pass 04
Build the workflow-specific agent
- Question
- What is the smallest useful system around this workflow?
- Output
- A working agent for one defined job.
Pass 05
Test against real cases
- Question
- Where does it fail, miss context, or need review?
- Output
- Observed failures and corrections.
Pass 06
Deploy with guardrails
- Question
- What can it touch, who reviews, and what happens when it is unsure?
- Output
- Permissions, logs, review points, and failure paths.
Pass 07
Improve from usage
- Question
- What changed once the system met real work?
- Output
- A maintenance path based on actual misses and new needs.
03Bring the Evidence
The better the evidence, the better the first build.
Bring
- Prior cases
- Good outputs
- Bad outputs
- Edge cases
- Tool access constraints
- Approval rules
Examples
- Needed
- Prior cases, good outputs, bad outputs, edge cases, and review notes.
Tool context
- Needed
- The systems involved, access constraints, owners, and current process.
Decision rules
- Needed
- Where judgment lives, what cannot be automated, and who approves action.
04What You Get Back
The output is more than a prompt.
Workflow map
Steps, inputs, owners, and failure points.
Agent interface
A form, command, report, queue, or small interface people can use.
Operating notes
Known limits, review rules, and maintenance tasks.
05Fit Criteria
Good candidate workflow.
A strong candidate workflow has repeated cases, available inputs, reviewable outputs, a known owner, and a clear reason the current manual version is expensive.
Good signs
- Repeated cases
- Available inputs
- Reviewable outputs
- Known owner
- Clear cost to the manual version