The Six Ways Work Gets Wasted

Everyone was busy last month. The diary was full, the work went out, and at the end of it the margin was thinner than it should have been.

That's the signature of wasted work. It isn't visible as idleness - nobody's doing nothing. It's visible as effort that produces nothing a client would pay for.

Lean thinking came out of manufacturing, which makes it easy to dismiss if you run a services business. The principle survives the translation perfectly: any resource you spend that the client doesn't value is waste. Factories counted it in materials. You count it in hours.

The six that show up in services

• Waiting - work that sits because something upstream hasn't happened. A job approved but not scheduled, a quote sent but not followed up, information requested but not received
• Over-processing - doing more than the client asked for because that's how it's always been done. Extra revisions, longer reports, checks nobody requires
• Motion - people moving information between systems by hand. Copying, re-entering, reformatting, reconciling
• Rework - doing a thing twice because the first time was wrong. Usually caused upstream by unclear requirements, not by the person who did it
• Overproduction - doing work before it's needed, or delivering more of it than was asked for. Output that isn't wanted yet is still cost
• Underused skill - experienced people spending their week on work a junior, a template or a system could do

The last one is the most expensive and the least visible. It doesn't show up as a problem at all. It shows up as a well-paid person having a bad week.

Why waste survives so long

Because every piece of it was once a sensible decision. Copying data between two systems was quicker than fixing the integration. Rechecking someone's work was faster than training them. Doing it all yourself was more reliable than delegating.

The part most people miss: a workaround doesn't announce when it stops being temporary. Nobody sits down and decides that the spreadsheet they built in 2023 is now load-bearing. It just quietly becomes how the business runs, and the cost gets absorbed into everyone's week instead of appearing on anything.

That's why waste is a measurement problem before it's an efficiency problem. If you can't see it, you can't argue it's there.

How to find it without a consultant

This is the Discovery & Clarity phase of our Operational Excellence Framework, in its simplest form.

1. 1

   Pick one process that runs often. Invoicing, quoting, onboarding, scheduling. Something that happens weekly and involves more than one person.

2. 2

   Map it as it actually happens. Every step, including the waiting, the chasing and the rework. Not the version in your head - the version that took place last time.

3. 3

   Mark each step: does the client pay for this? Not "is it useful" - would the client pay for it? Waiting, motion and rework all get a no, and usually they're most of the map.

4. 4

   Count the handoffs. Every time work changes hands, time and accuracy both take a hit. Fewer handoffs is worth more than any amount of handoff improvement.

5. 5

   Fix the biggest one, not all of them. One change to one process, measured. A small fix that holds beats a transformation nobody maintains.

6. 6

   Measure before and after in hours. Hours is the currency that makes this real to everyone. Dollars abstract it; hours make people argue about it, which is the point.

What this looks like in practice

A civil contractor we work with was running timesheets outside the system they already had. Crews recorded hours one way, the office transcribed them another, and someone spent real time each week reconciling the two before anything could be invoiced.

The waste wasn't the transcription - it was the waiting for it, the rework when the two versions disagreed, and the invoicing that couldn't start until the reconciliation finished. We set up timesheets inside the system they were already paying for, so hours went straight to the job. Same work, most of the waiting gone.

Quick self-check

If you answer "yes" to more than one, you're likely losing more hours to waste than to not having enough work.

Your task for this week

Take your most repeated weekly process and time the whole thing end to end - including waiting and rework. Then split it into steps the client would pay for and steps they wouldn't. The second column is your improvement list, and it's usually longer than people expect.