Seven salaries for work nobody needs
Your team is busy. That is not the same as productive.
Asana's Anatomy of Work research found that people spend 58% of their day on work about work: chasing updates, asking for approvals, copying information from one place to another, searching for the latest version of a file. The same research found that better processes alone would give each knowledge worker back 4.9 hours a week.
Run that on a 60-person company. That is almost 300 hours every week, the work of more than seven full-time people, spent on activity no client asked for and no client pays for. You are not hiring those seven people. You are already paying them.
There is a bigger number, too. An IDC (International Data Corporation) estimate, repeated so often it has become folklore, puts the revenue companies lose to inefficiency at 20 to 30% a year. Treat it with caution. Then pick a tenth of it, and ask yourself whether you would notice.
What waste looks like in an office
Lean thinking was born on factory floors, where waste is easy to spot: a pile of half-finished parts, a worker walking across the hall for a tool, a batch thrown away because one setting was wrong. Offices have exactly the same waste. It just doesn't pile up where you can see it.
Waiting is a request sitting in someone's inbox until they come back from a meeting, an approval that needs the one manager who is travelling, a client onboarding that stalls for a week because nobody knew it was their turn. Every day of waiting is a day of delivery, and often of revenue, pushed into the future.
Duplicate processing is the same order typed into the CRM (customer relationship management system), then into the planning sheet, then into the accounting tool. IDC found that 43% of workers regularly copy, paste or rekey information between systems. Each retype is paid time, and each one is a new chance to get it wrong.
Defects are what those chances produce: the wrong date sent to a client, the trainer booked twice, the shipment sent to last year's address. Defects cost twice, once to fix and once in credits, refunds and the client who quietly decides not to renew.
Unused talent is the most expensive waste and the least visible. When your best account manager spends Thursday afternoon reconciling a spreadsheet, the cost is not only her hourly rate. It is the client she didn't call and the deal she didn't grow.
Notice the pattern. Some waste shows up as cost: paid hours, rework, the hire you make because the team is overloaded. The rest shows up as revenue you never see: slower delivery, capacity sold to nobody, clients lost to small, repeated mistakes. Lean is usually sold as cost cutting. In operations, it is at least as much about growth.
You cannot remove waste you cannot see
On a factory floor, you can walk the line. In an office, the line runs through inboxes, calendars, spreadsheets and the heads of three people who have been there longest. Nobody owns the process end to end, so nobody sees where it leaks.
Try this. Take one ordinary request from last month, a new client order or a booking, and follow it from the moment it arrived to the moment it was done. Count the handoffs. Count the tools it passed through. Count the days it spent waiting. Then estimate how many hours someone was actually working on it.
It is common to find a request that needed two hours of work and took two weeks to finish. The difference between those two numbers is your waste, and it repeats with every request, every week.
Now the harder question: could you answer any of this from data, or did you have to ask around? If it took asking around, you are not short of effort. You are short of a map.
From map to lean process
OpsOlive starts where lean starts: with seeing the work. You describe in plain language how a process runs in your company, what arrives, who acts on it, what happens next. Our mapper turns that description into a map of the process as it really runs, not as the onboarding deck says it does.
The map makes the waste visible. Waiting shows up as statuses where work sits with no owner. Duplicate processing shows up as the same data entered in three places. Defects show up as loops where work goes back a step. Once you can see them, you can decide what to remove.
Then the platform configures itself from the cleaned-up map. The data lives in one place, so nobody types it twice. The workflow knows whose turn it is, so nothing waits in silence. The repetitive steps run as automations, so your people do the work only people can do. No consultant, no workshop series, no code for you to maintain.
The money comes from both sides. Hours come back to the team, and the hire you were about to make for coordination can wait. Requests move faster, clients get what they paid for sooner, and fewer of them leave over avoidable mistakes. The same team serves more clients, which is the only kind of growth that improves your margin instead of your headcount.
If the follow-one-request test left you uneasy, tell us how that process runs today. We'll map it with you and show you where it leaks.
Every company runs lean on paper. The map shows how it runs on a Tuesday afternoon.
Sources
- Asana: Anatomy of Work Global Index 2023
- Entrepreneur: How inefficient processes are hurting your company (citing IDC)
Describe how your business process works. We turn it into your system.