The repetitive task may need a simpler process before automation
A repetitive task may be best removed, simplified, delegated or automated depending on why the repetition exists. Map the work, identify the judgement it requires and compare the ongoing responsibilities of each option. Automating an unnecessary step preserves the step as well as speeding it up.
Put the advice into practice
Build a workflow your team can actually rely on
Connect systems and follow-up with agreed rules, human review and exception handling.
Discuss your workflowThe choice is often framed too early as “person or software”. There is another decision before that: whether the work is still necessary in its current form. A duplicated approval or an unused report can remain wasteful after it becomes automatic.
Ask what the task is meant to achieve
Identify the customer or colleague who needs the output and the decision it supports. If nobody uses it, investigate why it exists before assigning a new tool or person to produce it. Some tasks are necessary for governance or recordkeeping even when they are not visible to customers; record that purpose clearly.
Separate the outcome from the current method. The outcome might be an approved project scope. The method might involve copying details into three places and chasing several people. Redesigning the method can be more useful than accelerating each existing action.
Compare four possible responses
| Option | Suitable question | Responsibility that remains |
|---|---|---|
| Remove | Is the output still needed? | Confirm the consequence and approval for stopping it |
| Simplify | Can steps or duplicate information be reduced? | Agree the revised process and source of truth |
| Delegate | Does the work need a person with clear instructions? | Provide context, authority and review |
| Automate | Are the inputs and rules reliable enough? | Maintain access, exceptions and change control |
The options can combine. A team might remove one duplicate check, simplify the brief, delegate the judgement and automate the movement of approved information. The strongest design does not need to fit a single label.
A hypothetical approval process
Imagine a professional-services organisation prepares a monthly client-status document. An administrator copies project information into a template, a manager checks it and another person transfers the same content into an internal report.
The review first asks who uses each version. If the internal report duplicates an existing system view, that copy may no longer be necessary. The client document may still need a person to explain context and check commitments. Routine preparation could be simplified with a consistent source, while judgement remains with the manager.
Only after those decisions would automation be assessed. Creating a draft from approved fields might help. Sending it automatically without review could create a different risk. This is an illustrative process, not a recommendation about a real client communication.
Make the decision visible to the people involved
ASQ’s flowchart guidance provides a useful basis for documenting a sequence and checking it with the people who do the work. Include the informal decisions, missing information and rework that a tidy ideal process can hide.
Ask which steps are rule-based and which depend on context. “Copy the approved reference number” differs from “decide whether the client should receive a revised commitment”. A single process can contain both, so the design should not assign them to the same level of autonomy by default.
Also ask what happens when a person is absent or the source information changes. Delegation needs clear authority and continuity. Automation needs an owner and an exception route. Neither option removes the need for management.
Compare the complete effort
Include preparation, review, maintenance, exceptions and rework in the comparison. A tool that saves copying time but requires frequent correction may move effort rather than remove it. A delegated task may work well when the instructions are clear and the recipient has the required context.
Use a small, observable trial where appropriate. Define what would count as an acceptable output and what should stop the test. The existing automation savings guide addresses the separate calculation after allowing for human review.
The decision should leave the organisation with a process it can explain and maintain. The most useful improvement may be a smaller workflow, a better brief or a clearer responsibility, with technology added where it has a defined job.
