Automation

Work about work: where your team's time goes

delpra™ team5 min read

Ask someone on your team how their day was and the likely answer is "hectic". Ask what got finished and the list is usually much shorter than the rush suggests. The gap between the two answers has a name: work about work.

What work about work is

It is everything a person does around the task without it being the task itself: looking for the right information, asking where an order stands, copying data from one system to another, building a report by merging three spreadsheets, sitting in a meeting to align on what should already be clear.

Asana measures this every year in its Anatomy of Work Index. In the 2021 edition, the conclusion was that about 60% of people's time in office work goes to this kind of activity, and not to the work they were hired to do. The survey covers several countries and companies with profiles different from yours, so the exact percentage in your operations may be different. The order of magnitude, however, tends to surprise people who measure it for the first time.

In sales the picture is similar. Salesforce's State of Sales research (2022) indicates that sales reps spend about 28% of their week actually selling. The rest is split between record keeping, administrative tasks and internal meetings.

Why it is expensive and nobody sees it

Work about work does not appear on any budget line. It sits inside payroll, diluted in hours everyone considers "part of the job". Three effects deserve attention:

  • The company hires to handle the volume, when part of the volume is rework and checking.
  • Errors increase. Every time data is retyped, there is a chance it comes out different. Gartner estimated, in a 2020 survey, that poor-quality data costs the organizations it surveyed an average of US$ 12.9 million per year. Those are large companies, and the figure for a smaller company is different, but the mechanism is the same: wrong decisions and rework.
  • Good people wear out. Nobody was hired to copy and paste. The most capable people feel it the most.

How to measure it in your operations

You do not need to install anything to get a first measurement. A simple one-week survey already shows where to look.

  1. Pick one area (customer service, finance, sales) and explain to the team that the goal is to improve the process, not to evaluate people. Without that clarity, the numbers come back dressed up.
  2. Ask for a log in 30-minute blocks for five days, with four categories: doing (the work itself), searching (information, files, history), chasing or aligning (status messages and meetings) and transferring (copying, retyping, building reports).
  3. Add it up by category and by person. What matters is the proportion, not minute-level precision.
  4. List the five activities that repeat the most in the searching, chasing and transferring categories.

Imagine, as an example, a six-person administrative team that discovers each person spends two hours a day checking orders against a spreadsheet. That is sixty hours a week on a single activity. This kind of finding is what turns a vague conversation about "productivity" into an objective list of priorities.

Where to cut

Each category has a typical cause and a typical fix.

Searching: no single source

When customer information is partly in the CRM, partly in the salesperson's WhatsApp and partly in a spreadsheet, everyone wastes time asking. The fix is to define where each type of information lives and have the systems feed that place automatically.

Chasing and aligning: no visibility of progress

If finding out where an order stands requires asking someone, the process has no visible status. A simple board with stages, owner and date takes care of a good share of the messages and many of the meetings.

Transferring: systems that do not talk

This is the category where automation delivers results fastest. Integrating two systems so the data goes in only once eliminates the retyping and the checking that came after it. Reports built by hand every week also belong here: a dashboard that updates itself gives hours back and ends the argument about which number is right.

The useful question is not "how do we get the team to work more", but "how much of the team's day is real work".

What not to cut

Not every conversation is waste. Aligning on a new problem, a hard decision or a delicate negotiation is real work and needs people. The target is the exchanges that exist only because the information is not where it should be. Cutting a meeting without solving the lack of visibility just swaps the meeting for twenty messages.

The order also deserves care. Before automating the transfer of a piece of data, check whether that step needs to exist. We cover that in map the process before you automate it.

What to expect from the result

The report "A Future That Works", from the McKinsey Global Institute (2017), estimates that about 60% of occupations have at least 30% of activities that can be automated with existing technology, and that fewer than 5% could be automated entirely. In practice, this means the gain comes from removing the repetitive part of many roles, not from eliminating roles.

Well-organized processes and well-built automation reduce costs and make room for margin, but the size of the gain depends on the starting point. What can be said is that measuring first changes the quality of the decision: you stop automating what feels annoying and start automating what consumes hours.

If you want a quick view of how your operations are doing, delpra™'s Operational Maturity Assessment estimates, from your answers, how many hours a year the team spends on manual work. It takes four minutes. To see how we tackle this problem in projects, explore our services.

Written by the delpra™ teamProcesses, automation and AI so operations scale efficiently.

How mature are your operations?

The Operational Maturity Assessment takes 4 minutes and shows where to start.

Take the free assessment

Read next