Skip to content

How to automate a business without automating the wrong work

Start with one repeated process that your team can explain. The aim is not to automate everything. It is to make one valuable route more reliable, observable and easier to own.

Use the practical checklist Discuss one business process

Choose a process, not a platform

The best first candidate is specific enough to map and frequent enough for the team to notice the difference.

  1. 01

    Start with a visible operational leak

    Look for a repeated missed hand-off, duplicate entry, unanswered follow-up or review queue. A vague ambition to use AI is not a process to automate.

  2. 02

    Name one desired outcome

    Define what the owner should receive at the end of the route, such as a complete enquiry, an assigned task or a review-ready record.

  3. 03

    Keep the first route narrow

    Select one team, one trigger and one source of record. A narrow first route makes the exception pattern visible before it becomes expensive.

Map the route people actually follow

A process map needs to include the workarounds and decisions that a simple happy-path diagram often hides.

  1. 01

    Record the trigger and source record

    State what starts the process and where each material field should come from. This avoids an automation acting on an incomplete or duplicate record.

  2. 02

    List hand-offs and approval points

    Show who checks, changes or depends on the information. Keep customer, commercial and high-consequence decisions with the named person who owns them.

  3. 03

    Make exceptions explicit

    Capture the cases that need more information, a different route or a human decision. The exception queue is part of the design, not a failure after launch.

Work through one illustrative pattern

The pattern below shows the level of detail that makes a first test discussable and reviewable.

  1. 01

    Manual starting point

    An enquiry arrives in a shared inbox and the follow-up depends on someone noticing it. The team has no common queue for unanswered messages or record of the next owner.

  2. 02

    Controlled first route

    A new enquiry creates a task from the approved inbox or CRM record, sends an approved acknowledgement and assigns a named person to review the next commercial response.

  3. 03

    Human exception and measure

    A missing contact detail, duplicate record or unclear request stays in a review queue. The owner checks whether complete enquiries reached the right person and whether the exception pattern is becoming smaller or clearer.

Choose the lightest workable route

The right answer may be a platform setting, a connected workflow, a controlled manual queue or an AI-assisted information step.

  1. 01

    Check the current system first

    Review the existing platform, its available settings and its authorised integration routes before adding another tool.

  2. 02

    Use AI for a bounded information task

    AI can help prepare, extract, classify or draft material when the input, review standard and failure route are clear. It does not replace accountable judgement.

  3. 03

    Agree the evidence for a decision

    Before building, decide which records, hand-offs, exceptions and acceptance checks will show whether the first route is worth continuing.

Test, hand over and review

A live workflow needs an owner and a way to recover when the route does not fit the real case.

  1. 01

    Test a bounded set of cases

    Use an agreed batch, period or sample. Check that the right record is used, the expected action happens and exceptions reach the right person.

  2. 02

    Give the exception queue an owner

    Make clear who sees an unclear case, who can pause the workflow and who can approve a change to the operating boundary.

  3. 03

    Decide what to improve next

    Review completion, routing quality, rework and the pattern of exceptions. Expand only when the team can explain why the route is working.

A practical checklist before an automation conversation

Bring these answers for one process. They make a useful first scoping discussion possible.

  1. 1.What repeated task is currently being missed, delayed or done twice?
  2. 2.What event starts the process and where is the authoritative record?
  3. 3.Who owns the business outcome and who handles an unclear case?
  4. 4.What action could be prepared or completed without taking away a consequential decision?
  5. 5.What would the team need to see to judge the first test a success?
  6. 6.Which system access and information can be authorised for a narrow first route?

Choose the next useful route

Use the page that best matches the decision you need to make next.

Bring one repeated process to the conversation

Describe the trigger, source record, owner and exception that matter most. We can establish whether a controlled first route is viable.

Discuss one business process How we work