How to choose the first process to automate

Find a recurring action

Ask an employee which information they regularly copy, reconcile or request again. Review a few recent operations: where work begins, how often tools change and what needs correcting. This gives a more useful starting point than a general request to ‘automate everything’.

The first area should have clear input, repeatable rules and a verifiable result. For example, move an inquiry to a shared list, assign a responsible person and show the deadline for the next action. If every operation follows a new agreement, clarify the rules first.

• The operation genuinely repeats, rather than having occurred just once.
• Input data is available and someone is responsible for its quality.
• You can describe the normal result and a few common exceptions.
• The trial can be limited while retaining a manual way to do the work.

Describe the process through one example

Below is an illustrative process for handling an estimate request. It is a discussion outline, not a client implementation result. Take a similar real operation from your work and fill it in with specific information.

Work through exceptions before development

Use cases that have already happened: a customer submitted a form twice, left out a required parameter or canceled an order, or an employee went on leave. Decide what should happen next in each case. Not every decision needs automating; sometimes showing the problem to a person is enough.

• What to do with duplicate records and how to distinguish them from a new task from the same customer.
• Who clarifies missing information and where that is visible.
• How responsibility changes when the usual employee is unavailable.
• What is saved if an external system fails and who retries the transfer.
• How to correct an error or cancel an action without losing necessary history.

Keep the first version limited

Choose one data source, one route and a clear outcome. For an inquiry, this could be a form, a shared record and assignment to a responsible person. Multiple branches, complex sales rules and merging the entire history can be considered separately after the basics are checked.

1. Prepare test examples of the normal operation and exceptions.
2. Agree on where each step's result is checked.
3. Walk through the process with a future user and fix unclear statuses.
4. Define who watches the trial and how to return to manual work.
5. Expand usage once the agreed scenarios work and staff understand the steps to follow.

Compare work before and after

Before launch, record how many manual transfers the operation requires, where staff wait for each other and which errors need correcting. After launch, compare similar operations over a comparable period. If there were no records before, collect baseline observations first.

When to expand automation

Choose the next area based on the first version's results. If inquiries are saved but managers do not understand their priority, handling rules need work. If stock information is unreliable, adding notifications will not fix it: first define a reliable data source.

Record what already works, which exceptions remain manual and who is responsible for changes. You can then discuss another source, an additional calculation or a new status. This gives each improvement a verifiable task.