Unnecessary tasks at work: how to identify and eliminate them

The work nobody questions

In a company, tasks rarely appear for no reason. A report may have been created to solve a specific problem, an approval step to prevent an error and a spreadsheet to make up for a system limitation. The problem starts when circumstances change and those activities stay in place. Over time, new procedures are added without reviewing the old ones, and the organization ends up accumulating work that consumes resources without a proportional benefit.

This happens in offices, shops, warehouses, restaurants and service companies alike. A store manager fills in checklists nobody reviews, a salesperson updates information that already exists in another system, or a supervisor prepares reports with data management already has. Everyone is doing their job, but that doesn't prove every activity is still necessary. Sometimes the first possible improvement isn't doing something faster, but stopping it altogether.

What counts as an unnecessary task

An unnecessary task is an activity that consumes resources without delivering enough value to justify it under current conditions. That doesn't mean everything that doesn't directly generate revenue should go: safety checks, quality controls, mandatory documentation and much of the administrative workload serve essential purposes.

Telling one from the other requires understanding why each task exists, who uses its output and what would happen if it were changed or removed. Take a company that asks its branches for a daily sales report. If that information is already available in the central system and the report adds no analysis, it's probably a duplication. But if it includes incidents, sales observations or data the system doesn't capture, eliminating it without understanding its purpose could harm the operation.

Five signs a task is worth reviewing

1. Nobody can explain why it's done

When the usual answer is "we've always done it this way," it's worth looking into. A task may have been useful for years and lost its purpose after a change in systems, structure or procedures. The fact that an activity has been around for a long time doesn't prove it's still needed.

2. The same information is entered several times

It's common for a transaction to be recorded in one system and then copied into a spreadsheet or document. Sometimes there's a reason for it; in other cases, the duplication persists because nobody has reviewed the procedure as a whole. Depending on the situation, the solution may be to remove one of the entries, change how information flows or connect tools that are already in place.

3. Some reports don't lead to decisions

A report can take hours to prepare, review and distribute. If nobody uses its findings, it's worth asking why it's still produced. It may also turn out that only part of it is useful, in which case simplifying it is a better option than eliminating it.

4. A task requires too many people

Imagine a customer return that has to go through a salesperson, a store manager, the admin team and a supervisor, even when it meets predefined conditions. Some checks may be necessary, but some approvals could be handled with clear rules. Each additional step adds waiting time and queries that affect both the customer and the team.

5. The task exists to make up for another problem

A parallel spreadsheet may exist because the system doesn't provide the necessary information, a daily meeting may compensate for unclear responsibilities, and an extra check may be the result of a process that frequently produces errors. Eliminating these activities without addressing the cause can make things worse, because in these cases the task is a symptom, and the improvement lies in the process that makes it necessary.

What a small activity really costs

A ten-minute task seems insignificant when viewed on its own, but its impact changes when it's repeated every day and involves many people.

As an illustrative example, suppose 25 employees spend ten minutes a day filling in a duplicate record over 20 working days. The calculation (25 × 10 × 20 ÷ 60) comes to 83.3 hours a month of capacity consumed.

If that record serves no necessary purpose and can be eliminated entirely, that time becomes available. It doesn't automatically translate into financial savings: if the company keeps the same structure, what it recovers is working capacity that can go toward customer service, sales, order picking or other needs. Keeping that distinction clear helps assess the benefit of any change realistically.

How to decide which tasks to eliminate

The first step is to choose a specific process and observe how it's carried out in practice, whether it's receiving goods, preparing a quote, closing out the register or approving a purchase. Then break it down into its component activities and ask four questions about each one: why it exists and what need it meets, who uses its output, what risks or errors would arise if it stopped, and whether there's a simpler way to achieve the same result, such as removing a duplication, cutting steps or using information that's already available.

Not every answer will lead to eliminating something. Some activities will stay, others will be simplified and others can be automated. What matters is that the decision responds to a verifiable operational need, not simply a desire to save time.

Eliminating, simplifying and automating are not the same

Consider a restaurant that fills in an incident report by hand. If nobody uses it and there's no obligation to keep it, it should be eliminated. If the information is needed but the form asks for too much data, it can be simplified. If the record has to be kept and the data already exists in other systems, automation is worth considering. These are three different solutions for an activity that looks the same at first glance.

That's why the order of analysis matters: automating an unnecessary task doesn't fix the decision to keep doing it. And as peripheral work decreases, people whose work depends on judgment and focus can spend more time making decisions, serving customers or solving problems, which is where they add the most value.

The risk of eliminating without understanding the operation

Cutting activities indiscriminately can have consequences that aren't visible at first. A check may be preventing costly errors, an approval may respond to a contractual obligation and a record may be needed to ensure traceability.

Before changing a procedure, talk to the people who carry it out and those who depend on its results, and then check what effect the change had. Eliminating a task isn't an improvement if it later leads to more errors, queries or rework. The success of an intervention is measured by how the process performs afterward, not by how many steps were removed.

Recovering capacity starts with questioning the work

Many companies try to improve by adopting new tools, training teams or asking for more speed. These measures can help, but they don't replace a review of what the organization does every day. Before investing in a solution, it's worth asking which work needs to continue, what can be simplified and what no longer makes sense.

At DeepWork, we analyze processes and operations to identify where capacity is being consumed unnecessarily and which improvements to prioritize. The starting point is the DeepWork Assessment, which looks at how work actually gets done before deciding what to change.

Learn about the DeepWork Assessment