The Eight Wastes in Services: The Invisible Enemy

The Eight Wastes in Services: The Invisible Enemy

In a factory, when there is waste, it shows. A pile of defective parts in the corner of the shop floor, a box of expired materials, a stopped machine sounding its alarm, a shelf groaning under inventory that will never sell. Waste in manufacturing has a body, a weight, sometimes a smell — and that is exactly why it can be measured, charged, and removed. But in service organizations — government agencies, banks, telecoms, back offices, approval teams — an organization's biggest losses never appear on any financial report. There is no defective pile to see, no warehouse overflowing, no machine alarm warning. The employee sits at their desk, the systems run, the lights are on, and the organization bleeds without feeling it.

This is the thesis of this article: waste in services is more dangerous than waste in manufacturing precisely because it is invisible. The enemy you can see, you can fight; the enemy that disguises itself as ordinary work is the one that drains you quietly. The Lean methodology born on automobile assembly lines gave the world a precise map of eight kinds of waste, but it was designed for a world of metal and motion. The real task before service leaders in Saudi Arabia today — as they build the service economy Vision 2030 aspires to — is to translate these eight kinds from the language of the factory into the language of the office, from tangible material into information, time, and decision. This article is that translation.

Why Does Waste Hide in Services?

At the heart of the difference between manufacturing and services lies a simple, deep truth: the factory's product is physical, the service's product is informational. When a transaction sits forgotten in a drawer, its shape and weight do not change; on day thirty it looks exactly as it did on day one. When an office task is redone three times, its defective copies do not accumulate in a corner to embarrass anyone; the old copies are deleted as though they never existed. When a customer waits in a phone queue, their waiting registers on no scale. Physical waste imposes itself on the senses; informational waste is seen only on purpose.

There is a second reason for the disappearance: in services, waste wears the garb of respectable work. The employee re-entering the same data into three systems looks busy and productive, not wasteful. The meeting that gathers twelve people to discuss a decision concerning three of them looks like sound governance, not a hundred wasted work-hours. The report produced monthly and read by no one looks like a commitment to transparency, not overproduction. In the factory, waste looks like a mistake; in the office, it looks like diligence. That is why resisting it is harder: you are not fighting laziness, you are fighting activity in the wrong place.

The third reason is the absence of the scrap pile. In manufacturing, the scrap pile is the visible piece of evidence that forces the question; but in services there is no pile. The cost is scattered across thousands of tiny, dispersed moments: minutes of waiting here, a re-entry there, an unnecessary signature above, a wasted skill below. Because each small moment stands alone, no one notices it; yet together they form the largest uncounted cost line in the organization. From this springs its double danger: it does not appear in the financial statements because it is buried inside salaries that are paid anyway, and hidden in a cycle time that has come to be counted as 'normal'.

“In the factory, waste looks like a mistake; in the office, it looks like diligence. That is why resisting it is harder: you are not fighting laziness, you are fighting activity in the wrong place.”

Mapping the Enemy: The Eight Wastes and the DOWNTIME Acronym

Before we hunt an enemy, we must know its face. Lean defines eight kinds of waste, each being any activity that consumes resources without adding value that the customer would willingly pay for. They are conventionally remembered by an apt English acronym, DOWNTIME — which itself means a stoppage, a clever hint that all these kinds are, at their core, a stoppage in the creation of value.

The eight kinds, in the order of the acronym, are:

In the rest of this article we will take each of these eight, strip off its factory clothing and dress it in office clothing, with realistic examples from government services, back offices, and customer journeys. The goal is not to memorize the list but to learn to see — to walk our organization's corridors and see what had been hidden.

Defects: When Work Is Redone in Silence

A defect in manufacturing is a part that came out of specification, to be discarded or repaired. A defect in a service is a transaction entered with incomplete data, a request rejected for missing attachments, an invoice miscalculated, or a wrong answer to a customer's query that demands a second answer to correct the first. Here the defect is not thrown in a bin; it returns as rework that consumes double the time: once for the error, and once for its correction.

The danger of the service defect is that it is often invisible to whoever made it. The employee who enters incomplete data moves on to the next transaction and never sees that theirs came back three days later through another route, so it looks to them like a new transaction altogether. Thus a hidden loop forms: the error is made at one point, discovered at another, and corrected at a third, and no one connects the three to see that it is a single transaction handled three times. In the absence of that connection, the organization looks busy while it is in fact reproducing its own errors.

More dangerous than the defect itself is the rework rate when it becomes an accepted part of 'normal'. In many back offices it has become taken for granted that a sizeable share of transactions will 'come back' for correction, and the team's capacity has been built on that assumption. Here the defect turns from an occasional accident into an entrenched structure: we hire people, allocate time, and build systems — all to handle errors that should never have occurred.

How do we see it? We trace a single transaction from birth to closure and count how many times it 'came back'. And how do we remove it? By moving from inspection after the error to prevention at the source: forms that will not submit unless complete, checklists at the point of entry, and simplification of fields so the chance of error drops in the first place. The cheapest defect is always the one that never happened.

Overproduction: The Mother of Wastes in the Guise of Achievement

In Lean philosophy, overproduction is considered the most dangerous of the eight because it breeds the others. In the factory it is producing more units than the market demands, which then pile up as inventory. In services it is producing information and work that no one needs: the report produced weekly because 'it has always been produced' and that no one opens, the paper copies printed just in case, the data gathered because 'we might need it one day', and the slides prepared for a meeting and then abandoned.

Overproduction in services is cunning because it wears the mask of proactivity and diligence. Who objects to 'gathering more data' or 'producing one more report'? It looks like prudence, but it is in truth a consumption of the most precious resource — the expert employee's time — to produce what will never be consumed. And every extra report in turn breeds waiting (someone must review it), transportation (it is passed between departments), inventory (it accumulates in inboxes), and potential defects (wrong data in a report no one needed in the first place). Hence its name: the mother of wastes.

The clearest form of overproduction in government agencies is 'the form that asks for everything'. A single form asks the applicant for twenty fields, while only six are actually used in the decision. The remaining fourteen are overproduction: they consume the citizen's time to fill in, the employee's time to enter, the system's space to store, and serve no decision. Simplifying the form down to what is actually used is not laxity; it is a direct application of the principle of resisting overproduction.

The revealing question here is one: who consumes this output, when, and what do they do with it? If the question has no clear, specific answer, you are facing overproduction. The cure is to produce on real demand (pull) rather than precautionary assumption (push): no report without a reader, no field without a decision, no copy without a need.

Waiting: The Waste Swallowed by Cycle Time

If you mapped a transaction's journey from the moment it is submitted to the moment it is closed, and split its time into two parts — time actually worked on it, and time it spends waiting — the ratio would shock you. In many service operations, the actual working time is minutes and the waiting time is days. The transaction does not wait because working on it is hard, but because it is stuck in a drawer awaiting a signature, or in an inbox awaiting a reply, or in a queue awaiting its turn.

Waiting in services comes in two kinds: waiting endured by the customer, and waiting endured by the work. The first is visible and painful — the customer in the branch queue, on the phone line, or watching for an email that does not come. The second is hidden but far costlier — the transaction itself waiting between one step and the next, between one department and another, between 'I sent it' and 'I received it'. Because the transaction does not complain, its waiting is forgotten; yet it is in reality the largest component of total cycle time.

The source of waiting is usually not the slowness of the employee but the design of the process: too many handoffs between multiple hands, approvals arranged in series rather than in parallel, systems that do not talk so the manual transfer between them is awaited, and routing rules that pile work on one person and starve another. Every handoff between two people is a potential waiting point, and every additional approval is a new queue.

How do we see it? We measure the ratio of value-added time to total cycle time; if the actual work is ten minutes and closure takes five days, the whole gap is waiting. And how do we remove it? By reducing handoffs, converting serial approvals into parallel ones wherever possible, delegating small decisions to whoever does the work rather than escalating them, and connecting systems to eliminate manual transfer. Every day a transaction waits in a drawer is a day whose price the customer alone pays.

Non-Utilized Talent: The Waste Lean Added Late

The original seven wastes in Lean speak of wasting material and time; then an eighth was added that speaks of wasting the human being: non-utilized talent. This kind in particular is the most dangerous and the least visible in services, because the capital of a service organization is the minds of its employees, not its machines. When an employee's skill is wasted, it is not an hour of work that is wasted but the source of value itself.

This waste takes forms familiar to anyone who has worked in an office: the accomplished expert who spends half their day on routine tasks anyone could do; the employee who sees the flaw in the procedure every day but is never asked, or is asked and not heard; the suggestion that is offered and then buried; and the knowledge that walks out the door the day its holder retires because it was never documented and never circulated. All of these are energies that exist, fully paid for, but idled.

The bitterest form of this waste is 'learned helplessness': when the employee, after their suggestion is ignored time and again, learns that silence is safer and that initiative is futile. In that moment the organization loses not a single idea but the source of ideas. The employee who used to see and suggest turns into a silent executor, and the most precious improvement mechanism in the organization goes dark: the eye of the one who works on the ground.

How do we see it? We ask: do we have a real channel where the ideas of those who do the work are heard and acted upon? And what share of our experts' time goes to work that does not require their expertise? And how do we remove it? By moving the decision to the point nearest the work, automating the routine to free minds for the complex, and building a culture that honors suggestions grounded in field knowledge. The largest improvement mine in any service organization is minds that have not yet been asked.

Transportation and Motion: A Journey Without Value

Two kinds that look alike and are often confused, but distinguishing them sharpens the sight. Transportation is moving the object of work — the transaction, the file, the information — between people, places, and systems. Motion is moving the human being themselves to do their work. In the factory: moving the product between shops versus the worker's movement among their tools. In services, both manifest with astonishing clarity once you attend to them.

Transportation in services is the transaction's journey between hands. A request begins at the reception desk, is transferred to review, escalated for approval, returned for execution, sent to archiving. Every transfer in this chain is transportation that adds nothing for the customer; on the contrary, every handoff carries the risk of lost context, delayed delivery, and repeated explanation. The more stations in the transaction's journey, the more transportation waste, and with it more waiting points and defects. A transaction that passes through seven offices to do work that two could handle carries five excess transport stations.

Motion, by contrast, is the journey of the employee, not the transaction. The employee who opens five systems in five windows to complete a single transaction, copying data from one screen to another, is performing office 'motion' with no value for the customer. Searching ten folders for a document, navigating endless tabs, and exiting one system to log into another with a different password — all of it is motion that consumes minutes which accumulate across the day into hours.

How do we see them? We draw a flow map in which we trace the transaction's journey (for transportation) and the employee's journey between systems (for motion) and count the stations. And how do we remove them? By merging steps to reduce handoffs, unifying systems or connecting them into a single window, and bringing information and tools nearer the point of use. The shortest journey, for the transaction and for the employee, is always the most valuable.

Inventory: Pending Transactions Are Our Hidden Warehouse

In manufacturing, inventory is shelves of materials and products waiting. It has a place, so it is seen, counted, and worried about. In services, inventory is the accumulated work awaiting processing: pending transactions, requests in the queue, unanswered emails, and files 'under study'. This is inventory in every sense, but inventory without an embarrassing warehouse, so no one attends to it until it explodes.

The danger of service inventory is that it is the most concealed of all the kinds. The pile of materials in the factory imposes itself on the eye; but a thousand transactions stuck in a system occupy no visible space and make no sound. You do not see it until you look for it on purpose, and many organizations do not even know the size of the stagnant inventory in their systems: how many pending requests? since when? with whom? The absence of that number alone is proof that the inventory is hidden.

Inventory is not a static burden but a cost that grows with time. Every accumulated transaction has aging data, a shifting context, and may require rework when it is reopened after a long wait. The customer sitting behind that pending transaction does not know they are 'inventory'; they see only that their request was not completed, and their trust erodes in silence. A large inventory is not a sign of healthy busyness but a symptom of a flaw in flow: work enters faster than it leaves.

How do we see it? We measure the volume of work in progress and its age: how many transactions are pending, and what is the average duration they remain pending. And how do we remove it? By balancing the entry rate with the processing rate, setting an upper limit on work in progress that prevents pile-up, and handling the oldest first to prevent aging. An organization that knows the size and age of its inventory has covered half the road to removing it.

Extra-Processing: The Effort No One Asked For

Extra-processing is expending more effort than the value actually requires: steps that are not needed, approvals that add no assurance, details the customer did not ask for, and precision beyond what is used. In the factory it is polishing a surface no one will see. In a service it is the fifth signature on a transaction where two were enough, the report detailed across fifty pages when one would do, and the double review of work that does not tolerate error in the first place.

The clearest manifestation of extra-processing in bureaucracy is 'approval loops'. Every signature in the approval chain is supposed to add assurance; but past a certain number, the signatures turn into a ritual in which the signer reads nothing and signs because 'the procedure requires it'. Here approval turns from real oversight into extra-processing: it consumes the time of busy seniors, delays the transaction, and adds no actual assurance. An approval that never changes the outcome is not oversight but a procedural ceremony.

There is another, more concealed form: uniform processing of different cases. When we subject the simple transaction to the same path as the complex one — the same checks, the same approvals, the same documents — we are processing ninety percent of cases with a procedure designed for a rare exception. The applicant requesting a routine service pays the price of safeguards put in place for a special case that may not concern them at all. This is extra-processing on a wide scale.

How do we see it? We ask of every step and every approval: what would the customer lose if we removed it? If the answer is 'nothing', it is extra-processing. And how do we remove it? By aligning the level of processing with the need of the value rather than with the worst case, by classifying cases so that the simple takes a fast track and the complex a deeper one, and by eliminating every approval that does not change the decision. Effort the customer would not willingly pay for is wasted effort, however polished it appears.

How to See the Unseen: From the Acronym to Walking the Corridors

Knowing the eight kinds is a necessary condition but not a sufficient one. The list alone does not reveal waste; what reveals it is an organized method of looking. The first and most powerful of these methods is walking the place of work (Gemba) — for the leader to go down to where the work is actually done, rather than settling for reading reports at their desk. The report shows you the dressed-up numbers; but walking among the desks shows you the transaction as it waits, the employee as they copy between screens, and the queue as it lengthens. Waste is not seen from above but from where it occurs.

The second tool is value stream mapping: drawing the whole process from the customer's request to its delivery, and marking for each step its actual time and the waiting time after it. When we place this map before us, waiting, transportation, and inventory appear naked to the eye, and the shocking truth is revealed: the share of time that adds value for the customer out of the total cycle time is often tiny. That single ratio — value time to total time — is the truest measure of a process's health.

And to translate the eight kinds into a practical lens, it is enough to walk through each step of the process and ask simple but sharp questions:

These eight questions are the lens that turns the abstract list into vision. Whoever walks their organization's corridors carrying these questions will see in a single week what they did not see in years of reading reports.

How to Remove Waste: From Random Hunting to Organized Improvement

Seeing waste is a beginning, but removing it requires a discipline that protects the organization from two opposing traps. The first trap is hunting waste without priority: an eager team attacks every waste it sees and scatters its effort across twenty small improvements whose sum produces no tangible effect. The second trap is local improvement that harms the whole: removing waste at one step in a way that piles waste onto the next, so the department improves and the process worsens.

The cure for the first trap is to focus on the flow, not the station. We do not ask 'where is the biggest waste?' in isolation, but 'where is the bottleneck that governs the speed of the whole process?'. Removing waste at a step that is not the bottleneck does not speed up the final delivery at all; whereas addressing the real bottleneck speeds up the entire process. That is why intelligent removal begins with the flow map that reveals where waiting and inventory actually accumulate.

The cure for the second trap is to view the whole process from the customer's perspective, not the departments in isolation. Waste is measured by its effect on the customer's journey from request to delivery, not by its effect on the productivity of a particular department. The department that 'improves' its performance by dumping its unfinished work onto the next department has not removed waste but moved it — and usually multiplied it, because it added transportation and rework to it.

And because waste in services is invisible, removing it is not a campaign launched once and then ended, but a habit planted. The eight kinds do not vanish forever; no sooner are they removed than they begin to creep back in with every new procedure, every new system, and every exception that turns into a rule. That is why the mature organization does not clean its processes once but builds into them a permanent mechanism that continually sees waste and removes it — and this is the essence of the philosophy of continuous improvement.

“The department that improves its performance by dumping its unfinished work onto the next department has not removed waste but moved it — and usually multiplied it.”

The Invisible Enemy Deserves a Visible Battle

We have returned to where we began: a service organization's biggest losses never appear on any financial report. They are buried in salaries paid for rework that should never have occurred, in a cycle time bloated by waiting until it is counted as 'normal', in the minds of experts consumed by routine that does not require their expertise, and in customers' trust eroding in silence behind pending transactions no one sees. This enemy is not defeated by a financial campaign, because it does not reside in the financial statements at all; it is defeated by an eye that learns to see, a method that learns to measure, and a culture that learns not to accept waste as fate.

Service leaders enjoy one advantage: before them lies a mine not yet excavated. In manufacturing, operational efficiency has been squeezed over decades until wresting one additional percentage point is a battle. In many service organizations, by contrast, waste has not yet been touched, because it was invisible. This means that the first serious journey in exposing and removing the eight wastes often unlocks large and rapid gains: a cycle time that shrinks from weeks to days, transactions completed right the first time, and experts returning to what they were made for.

In the context of Vision 2030, which bets on a highly efficient service economy and an experience worthy of the beneficiary, exposing invisible waste becomes a competitive matter rather than a mere internal improvement. The organization that completes its service in a day while others complete it in a week is not only faster but cheaper, more accurate, and closer to its beneficiary. The difference between them is neither talent nor budget, but the ability to see the invisible enemy.

Begin tomorrow with a single step: choose one process that matters to your beneficiary, and walk with it from birth to closure carrying the questions of the eight kinds, and compute one ratio only — how much of its total time was actually spent adding value the beneficiary can feel. The number you will see will be more eloquent than any report, because it will reveal to you for the first time the size of the enemy that has been living among you without a name. And once the enemy has a name, a face, and a number, it becomes defeatable.