Choose a workflow, not a broad AI ambition
Goals such as becoming AI-enabled or improving productivity are too broad to design against. A first pilot needs a clear starting input, a recognizable sequence of decisions, a defined output and accountable users.
The workflow should also have a business reason to change: excessive manual effort, slow turnaround, repeated rework, fragile dependence on key employees or information that cannot move cleanly between systems.
A strong pilot has six characteristics
Evaluate candidate workflows against a small set of practical conditions.
- The work recurs often enough to observe and test.
- The current inputs and desired outputs can be identified.
- Experienced employees can explain what correct means.
- Exceptions are meaningful but not unlimited.
- The workflow has an owner who can approve decisions.
- A useful first boundary can be completed without replacing the company’s core systems.
Avoid the easiest and the most ambitious extremes
A trivial automation may be inexpensive but reveal little about the organization’s ability to use AI responsibly. An enterprise-wide transformation creates too many dependencies to produce clear evidence quickly.
The useful middle is a costly, judgment-heavy workflow with a bounded first version and a realistic path to expansion if the evidence supports it.
Measure the starting condition
Before building, document elapsed time, manual touches, exception volume, rework, approval delay and other measures relevant to the workflow. The pilot can then be judged against an actual baseline rather than impressions.