← All field notes

Before You Automate a Workflow, Draw the Exceptions

The routine steps are only part of a business process. Map the missing information, unusual requests and decisions that need a person before choosing an automation tool.

Product Strategy

The easiest part of a workflow to explain is often the part that runs smoothly. A request arrives, someone checks it and the next person gets the information. The harder work is hidden in the exceptions: the missing detail, the unusual request or the decision made in a conversation.

Before choosing an automation tool, draw what actually happens. Include the work people do to keep the process moving when the expected path does not fit.

Follow one item from beginning to end

Choose a repeated task and identify its starting point, the information it uses and the result someone needs. Speak with the people doing the work. Ask them to describe a normal item and a difficult one, using fictional examples where the details are sensitive.

In a hypothetical purchasing workflow, an ordinary request might follow a simple approval path. An urgent replacement, an incomplete supplier record or an amount outside someone's authority could each need a different decision. Putting every request through the ordinary path would miss those distinctions.

The GOV.UK guidance on learning user needs supports starting with the people, their tasks and their existing difficulties. Apply that discipline before treating a diagram of the ideal process as a description of the real one.

Mark decisions, handoffs and waiting

Beside each step, note who owns it, what information they require and where the result goes. Distinguish an automatic rule from a judgement call. Ask what the next person needs to know before taking over.

Then add the exceptions:

  • What if the information is incomplete or contradictory?
  • What if the same request arrives twice?
  • What if an approver is unavailable?
  • What if a connected system stops responding?
  • What if the request changes after work has started?

An exception does not always need another automatic branch. Sometimes the right response is to stop safely, explain what is missing and put the item in front of an authorised person.

Choose a first step with a clear boundary

Look for a repetitive task with understandable inputs and a result someone can check. Drafting an internal reminder or copying a verified status between systems may be a more manageable start than automating an entire approval process.

Agree what the automation is allowed to change and which decisions stay with people. If it connects two systems, define how staff will see incomplete work and correct it. Our integration failure guide explains why retries and repeated messages need explicit handling.

Rehearse the exceptions before expanding

Use a suitable test environment and fictional records to try both the routine path and the unusual cases. Confirm that staff can see an item waiting for review, understand why it stopped and resume it without repeating completed work.

After release, assign someone to review exceptions and decide whether the process or the automation needs changing. Do not measure success only by how many actions ran; consider whether the intended work reached a correct, useful outcome.

You may find that a simpler form, clearer responsibility or a revised approval rule solves the immediate problem without more software. If automation is still useful, start the discussion with the process map, including its exceptions and decision owners.