The first mistake in agent work is choosing a workflow because it sounds impressive. A team sees an AI agent move through several steps in a demo, then goes looking for something dramatic to automate. The better starting point is quieter. Find the work that already has a shape, already leaves evidence, already repeats often enough to learn from, and already has a person spending attention on coordination rather than judgment.
Workflow discovery is the practice of finding that work before prompts, tools, permissions, and evaluations are designed. It sits before How to Delegate to AI Agents and before AI Agent Task Decomposition . Delegation asks how to assign the job. Decomposition asks how to break it into pieces. Discovery asks whether this is the right job to delegate at all.
Start With The Actual Work
A workflow is rarely the same as the official process name. “Prepare a renewal packet” might include checking contract dates, reading recent support notes, confirming product usage, asking a finance question, drafting a summary, and waiting for a manager to approve the tone. “Review inbound partnerships” might include sorting spam, reading the sender’s site, matching the proposal to company priorities, checking conflicts, and writing a polite decline more often than a green light. If discovery begins with the label, it misses the work.
The useful method is to follow a recent example from start to finish. Look at the inputs that arrived, the systems people opened, the judgment calls they made, the places they waited, and the artifact that finally counted as done. The point is not to create a perfect map. The point is to see where attention is spent. Agents are often useful where people are shuttling context between systems, checking routine conditions, preparing drafts, or preserving continuity across steps. They are weaker where the work depends on tacit authority, fragile relationships, open-ended strategy, or facts that cannot be inspected.
Real examples also reveal the hidden branches. A clean process diagram may show five boxes. A real week of work may show twelve exceptions. A customer record is missing. A source is stale. A manager has a standing preference. A ticket refers to an attachment that never arrived. A policy changed, but the old template still circulates. These details are not noise. They are the material that tells you whether the workflow needs an agent, a better form, a runbook, a narrow tool, or simply a smaller queue.
Look For Judgment Surrounded By Structure
The best early candidates are not pure clerical chores and not pure judgment calls. They are structured workflows with judgment embedded inside them. The structure gives the agent a path. The judgment gives the delegation value.
Consider a research intake workflow. The agent may read a request, identify the topic, search approved sources, collect evidence, summarize the tradeoffs, and prepare a short brief. A person still decides what the organization will do with the answer, but the agent can remove the repetitive source gathering and first-pass synthesis. That is different from asking an agent to “decide our market strategy,” which has too much authority and too little verifiable structure, or asking it to “copy this field into that field,” which may be better handled by deterministic automation.
This middle ground is where AI Agent Tool Contracts matter. If the workflow has stable actions, those actions can become tools with clear inputs and outputs. If the workflow has stable evidence, that evidence can become part of the working set. If the workflow has stable review moments, those moments can become gates. Discovery should notice these handles. A workflow with no handles may still be important, but it is not an easy first agent.
Watch How Context Moves
Agents become useful when context has to move. A human reads a request in one place, checks another system, remembers a rule from a document, looks at a prior example, drafts a response, and then explains the decision to someone else. The task is not hard because any one step is heroic. It is hard because the person has to carry the thread.
During discovery, follow the thread carefully. Which facts are required at the start? Which facts are discovered along the way? Which facts are sensitive? Which facts need to appear in the final artifact? Which facts must be hidden from the final artifact but still influence the decision? This is where workflow discovery overlaps with AI Agent Context Windows and Working Sets and AI Agent Data Boundaries . A promising workflow can become a poor agent workflow if it requires dumping too much private context into every run.
Good candidates usually have a bounded working set. The agent can be given a request, a small group of records, a few approved sources, and a clear output target. Bad candidates tend to require broad personal memory, informal politics, unbounded search, or permission to browse private systems without a precise reason. That does not make the work impossible forever. It means the workflow needs more design before it becomes a delegate’s job.
Name The Authority Boundary Early
Discovery should separate preparation from action. Many workflows look risky because the final step is consequential, but the earlier steps are safe and useful. An agent may be able to inspect an account, gather source evidence, draft a recommendation, and prepare a change request without being allowed to execute the change. That partial delegation can still save time and improve consistency.
This distinction keeps teams from making a false choice between no agent and full automation. AI Agent Permissions describes the ladder from read to act. Workflow discovery decides which rung is appropriate for the first pilot. In a billing workflow, the early agent might prepare a refund memo, not issue the refund. In a publishing workflow, it might assemble a draft and validation evidence, not publish the page. In a software workflow, it might open a small pull request, not merge it.
Authority boundaries also make evaluation possible. A read-and-draft agent can be judged on source use, completeness, tone, and whether it escalated uncertainty. An action-taking agent must also be judged on side effects, rollback, permission, and incident response. Starting lower on the ladder is not timid. It is a way to learn what the workflow really demands before giving the delegate more reach.
Study Exceptions Before The Pilot
The happy path is not enough. If a workflow only succeeds when every input is clean, every source is available, and every decision is obvious, the first production surprise will define the system. Discovery should spend time with awkward examples.
Look for requests that arrived with missing information. Look for tasks that were routed to the wrong team. Look for cases where a senior person corrected a junior person’s first draft. Look for edge cases that required a policy interpretation. Look for work that was abandoned because the next step was unclear. These examples reveal the escalation paths and acceptance criteria the agent will need.
AI Agent Acceptance Criteria is easier to write after exceptions have been seen. “Draft a complete summary” is vague. “Draft a summary that names the source records inspected, flags missing account data, separates facts from recommendations, and stops before proposing a discount above the team’s approval limit” is much more useful. The second version comes from studying the actual workflow, not from imagining a tidy one.
Exceptions also reveal when an agent should not continue. Some workflows need explicit stop conditions. If the source record is missing, stop. If the request asks for a commitment the team does not make, escalate. If the tool returns conflicting records, preserve the conflict. If the action would touch a restricted customer, hand off to a person. These rules are not obstacles to delegation. They are what make delegation inspectable.
Keep The First Pilot Narrow
A workflow discovery pass should end with a pilot small enough to learn from. The target is not a grand automation story. The target is a repeatable slice with a real input, a real output, a clear owner, and a reviewer who cares about the result.
The pilot should have visible costs. AI Agent Cost, Latency, and Queues explains why agent work is not free just because it is delegated. Discovery should estimate where the run will wait, which tools it will call, how much review time it will consume, and how often it will need to retry. A workflow that saves twenty minutes of drafting but creates thirty minutes of review is not yet shaped correctly. A workflow that saves five minutes every time and improves the evidence trail may be an excellent candidate if it happens often enough.
The pilot should also have a measurement plan. AI Agent Operating Metrics becomes more useful when the workflow has been chosen well. Measure whether the agent starts with the right inputs, uses the right sources, stops at the right boundaries, produces an artifact reviewers can inspect, and reduces the actual bottleneck. Avoid vanity measures that only count runs completed. A fast delegate that produces confusing work has not improved the workflow.
Discovery Is A Design Habit
The output of workflow discovery is not a giant requirements document. It is a grounded understanding of one job: what starts it, what evidence it needs, what tools it touches, what judgment it requires, what authority it should not have, what exceptions occur, and what a good handoff looks like.
That understanding changes the rest of the build. Prompts become less theatrical because the task is concrete. Tools become narrower because the actions are known. Review becomes easier because the artifact has a purpose. Evaluations become more realistic because they include the messy examples people already see. Permissions become calmer because preparation and action have been separated.
The strongest agent workflows usually begin this way. Not with a promise that an agent can do everything, and not with a fear that any delegation is reckless. They begin with a careful look at real work. The team notices where human attention is being used as glue, where evidence can be gathered safely, where authority should remain with a person, and where a bounded delegate can make the next run easier to trust.
