Business process automation

Map the process as it really is

The written version of a process and the way it actually runs are often different. People copy data between spreadsheets, forward emails to colleagues for approval, keep personal checklists and work around system limitations. Mapping the real process, step by step, with the people who do it, reveals where time goes and where errors creep in.

A simple diagram showing each step, who does it, which system it touches and how long it takes is usually enough.

Common automation opportunities

Simplify first

Automating a process exactly as it stands can lock in unnecessary steps. Before building, ask of each step: why does it exist, who uses the result and what would happen if it stopped? Some approvals turn out to be formalities, some reports are never read and some data is entered twice. Removing these first makes the automation simpler, cheaper and easier to maintain.

Designing reliable process automation

Where AI fits

• Reading unstructured input

  Emails, documents and free text that rules cannot interpret.

• Drafting

  First drafts of replies or summaries for a person to check.

• Not for

  Predictable steps that rules handle, or decisions that need human accountability.

Automation changes people's work

When steps become automatic, the people who did them need to know what has changed, what they now do instead and how to handle exceptions. Involving them in mapping and testing builds trust and catches problems early. The aim is to remove tedious work, not to leave people unsure whether something has been done.

Plan for exceptions

Every process has exceptions: an order with a special request, an approval needed while the manager is away, a supplier who sends information in an unusual format. Automation should handle the common path and hand exceptions to a person clearly, rather than trying to cover every possibility. Listing the exceptions during mapping, with how often they happen, shows which are worth automating and which should stay manual.

A good rule is to automate what happens most often and design a clean hand-off for the rest.

Keeping a record

Automated processes should leave a record: when each step ran, what it did and who approved what. This helps when something goes wrong, when customers ask questions and when the business needs to show how decisions were made. Many manual processes have no such record, so automation can improve accountability as well as saving time.

Measure the result

Record how long the process takes and how often errors occur before automating, then compare after a few weeks. Include the time people still spend on exceptions. This keeps expectations honest and shows where further improvement would help.