How to Choose a Business Workflow to Automate First

Business automation works best when it removes a repeated handoff that people already understand. It is tempting to start with a large ERP project or an AI feature, but the safer starting point is usually one workflow with a clear owner, a visible delay, and a result the team can check.

Look for friction, not fashionable features

List the work that staff repeat every day or week. Look for copying the same information between spreadsheets, chasing approvals in chat, preparing the same report by hand, or answering the same status question from several places.

These are useful signals, but they do not automatically justify a new system. First ask whether the process is clear enough to describe. If two people follow different rules, the first task may be agreeing on the process rather than automating it.

A simple way to select the first workflow

1. Follow one request from start to finish

Choose a recent example and trace it from the first request to the final outcome. Write down each handoff, the record created, the decision made, and the evidence needed to continue.

For a school, this might be an enrolment or fee follow-up. For a SACCO, it could be a member request or approval. For logistics, it might be a dispatch update. For an SME, it could be a quotation, purchase request, or customer support case.

2. Identify the part that waits

A workflow is a strong candidate when work regularly waits for a reminder, a spreadsheet update, a manager's approval, or a message from another team. Make the waiting point visible. Do not assume that adding a notification will fix it if no one owns the next decision.

3. Define the business rule

Write the rule in a sentence. For example, a request moves to the next stage only after a named person has approved the required information. If the rule cannot be explained, automation may simply hide the uncertainty.

Include the exceptions. A good system should say what happens when information is incomplete, an approval is rejected, a payment is not confirmed, or an external service is unavailable.

4. Decide which record is authoritative

Choose one source of truth for customers, members, orders, payments, stock, or cases. An automation that copies incorrect data faster is not an improvement. Decide which system owns the record and how other tools receive changes.

This is especially important when the workflow connects an accounting package, M-Pesa, SMS, WhatsApp, a portal, or an existing database.

What the first release should contain

A useful first release normally needs more than a button that starts an action. Consider including:

• the records the team actually needs;
• roles and permissions;
• the main workflow states;
• an approval or review step where required;
• a history of changes;
• notifications that tell a person what to do next;
• a report that can be checked against the records;
• handling for failure, retries, and correction.

AI can help with narrow tasks such as classifying an enquiry, finding an answer in approved documents, or summarising a conversation for a staff member. Keep important permissions and financial decisions in normal application rules. A person should be able to review uncertain results and take over.

Measure the process before changing it

You do not need a complicated dashboard at the beginning. Record a small baseline that the team can understand, such as how long a request usually waits, how many handoffs it needs, how often information is re-entered, or how many items need manual correction.

After the first release, compare the same process with the same definition. If the team cannot explain what changed, the measurement is probably too vague.

When to expand

Expand only after the first workflow is understood, used, and supported. Then connect the next process that shares records or decisions with it. This keeps the system coherent and gives the team time to learn what should be standardised and what should remain flexible.

Statum helps organisations map and build business systems, ERP workflows, integrations, and practical automation. Read the business systems and workflow automation service, review the custom software development service, or start a project conversation.