← Back to all postsJune 12, 2026

Write down how the work happens before automating it

A useful process map describes what happens on an ordinary day, including the missing details and handoffs that a demonstration can overlook.

Colleagues document a work step beside the tools needed to perform it.

Before automating a task, ask someone to show you how it happened last time. Write down the real steps, including the missing information, waiting and exceptions.

A process that lives in one person's memory can be difficult to hand over. Connecting an AI tool does not remove the need to decide what the work should do.

A short map gives you a way to examine the process before choosing what to automate.

Follow one real example

Choose a recurring task and walk through a recent completed case with the person who handled it. Ask where the request arrived, what they checked and what happened next.

Keep the description close to the work. If a quote waited for measurements, include that wait. If the office asked the owner to clarify a condition, include the decision.

Use a safe summary when documenting an example. The map usually needs the type of information and its source, rather than a copy of a customer's full record.

Make the important handoffs visible

For each step, identify who is responsible and how they know the work has reached them. A message sent is different from a handoff accepted.

Ask what happens when the usual person is unavailable. Check where missing details are recorded and who follows up.

Here is a hypothetical first map for a local service business:

Part of the taskWhat to record
TriggerA customer submits a quote request.
OwnerThe office coordinator checks the request.
InformationRequested service, job area and details needed for the next assessment.
DecisionIs the request in scope, or does someone need to clarify it?
ExceptionMissing information goes to a named person for follow-up.
Finished resultThe appropriate person has accepted the request and its next step is recorded.

This describes an arrangement to review, rather than a universal service standard. Your own process should reflect the work you actually provide.

Remove unnecessary work before making it faster

The map may show that the same detail is entered twice or that an approval has no clear purpose. Ask whether the step can be removed or simplified.

Check why a control exists before deleting it. A review that looks repetitive may prevent a pricing error or an unauthorised customer promise.

Then identify which steps follow dependable rules and which require interpretation. A conventional form or reminder may be sufficient. AI may be useful for a bounded drafting or summarising task that a person can check.

Test the map with another person

Give the instructions to someone who did not write them. Ask them to explain what they would do with a normal request and an incomplete one.

Revise the places where they need to guess. Add a useful example or point to the person who can decide an exception.

Keep the map where the work happens and name its owner. Update it when the business changes the service, system or handoff.

Use the map to choose the next improvement

You now have a clearer description of the task and a basis for comparing a proposed change. Agree what should improve and how you will check the result.

For help mapping a difficult handoff, tell us where the work starts and where it tends to stall. We can help examine the process before adding another tool.

Free rank audit