The short answer
Start with one repeatable task whose rules are clear. A workflow is the sequence of steps used to finish a task. Automation means having software carry out steps that people would otherwise do. Check whether it reduces the total work, including checking results and fixing mistakes.
Still choosing a task? Use our worksheet to compare what to automate first.
Get these three things clear first
The work
What starts the task? What steps happen next? What counts as finished?
Ask someone to show you a recent example, including any spreadsheet or email steps.
The rules
Which decisions follow a clear rule? Which unusual cases need a person?
If staff disagree about the right answer, settle that before asking software to repeat it.
The owner
Who checks failed tasks, changes the rules and keeps the connections working?
Write down how to stop the automation and finish the work by hand if needed.
Count checking time, too
Record how often the task happens and how many minutes someone spends doing it. Track waiting time separately: waiting two days for approval does not mean two days of work.
This shows the arithmetic, not a client result or promised saving.
Difference: 2 hours 40 minutes a week before time spent monitoring and fixing the automation. Subtract that time before judging the benefit.
Check what the tools can actually do
- Choose where the correct record will be kept.
- Check whether the tools have a supported way to share information.
- Confirm that needed details are complete and consistent.
- Check subscription limits and any extra usage charges.
- Decide who can give or remove access to each tool.
Test with made-up records or remove names and identifying details. Do not put passwords or private customer details in a project brief.
Run a small trial that includes mistakes
Try a normal task, missing information, a repeated request and a broken connection. For each one, agree what the software should do and who will see a failure.
Example decision path
- A request arrivesCheck that the needed details are present.
- The usual rules applyLet the software complete the agreed steps.
- Something is unusualFlag it for a named person to review.
For payments, customer messages or changes to important records, decide what a person must approve and how a mistake can be corrected before switching on automatic action.
Continue only if the trial helps. Compare all handling, review and repair time with the old process. Change or stop the trial if it simply moves work to someone else.
Keep this checklist
Your one-page project brief
- Task: what starts it and what finishes it?
- Current effort: how many tasks, minutes and corrections?
- Tools: where is the information kept?
- Unusual cases: when should a person take over?
- Success: what result would make the trial worth continuing?
- Ongoing care: who handles failures, changes and costs?
Be clear about what support includes. Do not assume it covers unlimited changes or help at every hour.
Common questions
Does every repetitive task need automation?
No. A task that rarely happens or has constantly changing rules may take more effort to automate and maintain than to do by hand.
Do we need AI?
Not always. Moving information from a form can follow a fixed rule. Reading varied documents or drafting text may benefit from AI (artificial intelligence, including software that generates or interprets information). Test its answers on realistic examples and decide what a person must check.
Must we replace our software?
Check whether you can adjust or connect your current tools first. If an important step is still missing, compare existing software with a custom business app.
Does automation mean removing people?
No. The aim may be less copying and fewer forgotten tasks, with people still making the decisions that need judgment.