Count exceptions, not just steps
Write the normal path, then list the cases that cause staff to pause, ask a question or change the rule. The frequency and consequence of those exceptions matters more than how neat the flowchart looks.
Separate judgement from administration
A person may spend most of a task copying information but still make one important decision. Automate the copying without pretending the judgement is repetitive.
Identify missing-information behaviour
Many fragile automations fail because they assume clean inputs. Decide what happens when a field is absent, contradictory or outside an expected range. The safe answer is often to stop and ask.
Use thresholds deliberately
Some judgement can be bounded with thresholds, but those thresholds need an owner and review. A rule that nobody owns becomes hidden policy.
Design for escalation
A good workflow makes uncertainty visible. Define who receives an exception, what context they need, and how the workflow resumes after a decision.
Classify the exceptions
Not all exceptions deserve the same response. Some are missing data, some are commercial judgement, some are policy limits, some are safety or compliance issues, and some are simply rare variations.
Classifying them helps decide whether the workflow should ask for more information, route to a specialist, require approval, or stop entirely. It also prevents one unusual case from making the whole process seem impossible to improve.
Sample real cases before automating
Review a meaningful batch of recent examples and mark which ones followed the normal path. If the supposed “standard” process only describes half of the work, the automation design is based on wishful thinking.
Use the sample to estimate exception frequency and consequence. A rare exception with high financial or customer impact may still justify a human checkpoint even if most cases are routine.
Keep judgement with an accountable role
When the workflow escalates, the human decision should have a clear owner. Avoid routing every uncertain case back to the business owner by default. That recreates the original bottleneck in a new interface.
Where possible, define which role can make the decision, what information they need, and when the case genuinely requires senior judgement.