Before You Automate: The Questions That Decide Whether It Works

Most automation projects do not fail because of technology. They failed because the organisation automated a process nobody fully understood, and the software simply made the confusion run faster.

For senior leaders, which is an expensive outcome. You pay for the system, your teams lose confidence in it, and the old workarounds quietly return. Within a year, people are back to email, spreadsheets, and phone calls to get things done. The cost is not only financial. Every failed rollout makes the next change harder to sell to your people.

The fix is rarely a better tool. It is a better set of questions, asked before anyone builds a workflow. These six questions decide whether your automation delivers real value or simply digitises the problems you already have.

1. Map the process as it really runs, not as the policy says

Every organisation has two versions of each process: the one written in the procedure manual and the one your people actually follow. Automation must start with the second. If you digitise the official version, you automate a process that does not exist.

Sit with the people who do the work and trace one real transaction from start to finish. Listen for the steps nobody mentions in meetings. Ask them:

• Where does the work start, and what triggers it?
• Who touches it, in what order, and why?
• Where does it stop and wait, and for how long?
• Which steps happen off the record, in email, on WhatsApp or on paper?

2. Fix what is broken before you make it faster

Mapping will expose duplicated checks, unnecessary approvals and steps that exist only because something went wrong years ago. Automating those steps locks them in and makes them harder to remove later. Clean them out first.

Look for these warning signs:

• Rework loops: documents that return to the same person more than once.
• Duplicate capture: the same information typed into two or more systems.
• Legacy approval: approval steps nobody can justify, but nobody is willing to remove.
• Incomplete input: requests that missing key details arrive and stall while someone chases them.

3. Give every step a clear owner

A workflow without owners is just a diagram. Each step needs one named role accountable for completing it, not a department, a shared inbox or “the team.” When everyone owns a step, nobody does.

Ownership also defines escalation. If a step stalls, your teams should know exactly who acts next and by when. For every step, clarify:

• Who completes the work?
• Who reviews or approves it if anyone?
• Who steps in when the owner is unavailable?
• What turnaround time you expect

4. Decide what visibility you need before you need it

Leaders often discover the limits of a process during a crisis: delayed payment, an audit query, or an escalated customer complaint. By then, the simple question “where is this sitting?” has no fast answer.

Define upfront what you want to see at any moment, and who needs to see it. Good workflow visibility answers four questions:

• Status: where every item sits right now.
• Age: how long it has been waiting.
• Ownership: who is holding it.
• History: who did what, and when.

5. Agree on the exceptions, not just the ideal route

Most process maps describe the ideal route. Real operations are full of exceptions: missing documents, rejected requests, urgent cases and approvals above a certain value. If your workflow cannot manage them, your teams will simply route around it.

List your most common exceptions and decide how each one should flow. Keep the rules simple. Too many branches create a process nobody can follow, automated or not. Exceptions are also where risk concentrates, so they deserve deliberate design rather than improvisation.

6. Define what success looks like, then measure it

Automation is a business decision, so treat it like one. Before you build, agree on the two or three measures that will prove the change worked. Without a baseline, you cannot show the value, and you cannot spot the process drifting back to old habits.

Useful measures include:

• Turnaround time from request to completion
• Number of items stuck beyond the agreed time limit.
• Volume of rework or returned documents.
• Time your managers spend chasing status updates.

Your checklist before you automate.

If any answer is no, you are not ready to automate yet. Before you digitise any process, confirm that you can answer yes to each of these:

• We have mapped the process as it runs today.
• We have removed duplicate, redundant, and unexplained steps.
• Every step has one named owner and a clear escalation route.
• We know what visibility we need and who needs it.
• We have agreed how the common exceptions flow.
• We have a baseline and two or three measures of success.

Automation amplifies whatever you give it. A clear, owned, and measured process becomes faster and more reliable. A confused one becomes confusion at scale, with a bigger budget attached.

The leaders who get real value from workflow automation do the thinking first. They treat technology as the final step rather than the first, and they insist on clarity before they spend.

If you are planning to digitise a process, or a workflow you already automated is not delivering, start with these questions and work through them with a partner who has done it before.

BCM Transform helps organisations across Africa turn clearly defined processes into structured BCMFlow workflows, where every step has an owner and every item is visible. Ready to get it right before you build? Talk to BCM Transform.