What Should I Automate, and What Should a Person Still Handle?

When businesses begin looking at automation, one of the most important questions is not what technology can do. It is where people still need to be involved.

A process does not have to be completely automated to become significantly easier. In many cases, the better approach is to automate routine work while making sure a person is involved when judgment, communication, approval, or an unusual situation requires attention.

Start with routine work

Some tasks do not benefit much from human judgment.

If a customer submits a form, the information may need to be stored, a confirmation may need to be sent, and an employee may need to be notified. If an appointment is approaching, a reminder may need to go out. If a document reaches a particular stage, it may need to move to another part of the process.

These are predictable actions. When the same conditions lead to the same outcome every time, automation can often handle the work without requiring someone to initiate each step.

Removing those tasks does not remove people from the process. It reduces the amount of routine work they have to perform before they reach the parts where their involvement is useful.

Keep people involved when judgment matters

Other parts of a process are less predictable.

A customer may have an unusual request. A document may contain conflicting information. An order may require an exception. An employee may need to consider information that cannot be reduced to a simple rule.

In these situations, the system can still help without making the final decision.

It might collect the relevant information, organize it, identify something that appears unusual, or present the employee with what they need to review. The employee can then make the decision without spending as much time gathering information first.

This can be especially useful when most cases are routine but a smaller number require attention. Instead of treating every case as if it were unusual, the process can be designed to bring the unusual cases to the right person.

Consider the customer experience

Efficiency is important, but it should not come at the expense of the person interacting with your business.

Customers generally do not need an employee to personally perform every routine action behind the scenes. An appointment confirmation, order update, receipt, or acknowledgement that a request was received can often happen automatically.

Other conversations may deserve more care. A customer with a complicated problem, an unusual request, a complaint, or a situation requiring flexibility may benefit from speaking with someone who can understand the circumstances and respond appropriately.

When deciding what to automate, consider not only how much employee time you can save but also what the customer needs at that point in the process.

Think about what happens when something goes wrong

A well-designed process should also account for situations where the expected path does not work.

Information may be missing. A system may not recognize a request. A customer may provide something unexpected. An automated step may fail.

Someone should know when these situations occur and have enough information to resolve them.

This is one reason partial automation can be so useful. Routine work can continue without unnecessary involvement, while exceptions are directed to someone who can determine what should happen next.

Design around people’s attention

The goal of automation should not be to remove people simply because technology can perform part of their work. It should be to use people’s time where it provides the most value.

If an employee is copying information between applications, repeatedly checking for updates, or performing the same predictable action throughout the day, automation may be able to handle that work. If the employee is evaluating an unusual situation, helping a customer, reviewing an important decision, or handling an exception, their involvement may be exactly what the process needs.

A useful way to evaluate any workflow is to ask what the system should handle on its own and what deserves someone’s attention.

That creates a better goal than trying to automate everything. The system handles the routine work, while people remain involved where their experience, judgment, and communication matter.