There is a belief that Lean is for factories. Toyota, assembly lines, steel and bolts. A service process has no visible stock and no forklift, so surely the ideas do not carry over. That belief is half right. The tools were born on factory floors, but the thinking behind them, that most elapsed time in a process is not spent adding value, translates well to a back office where “work” is an application form moving between five desks.
Lean names eight kinds of waste, remembered by the letters of TIMWOODS. Let us walk through them using one imaginary process: a lender in Nagpur verifies and approves small business loan files. A file arrives scanned, gets keyed in, verified, checked and sent for approval.
The eight, in a service setting
Transport. Unnecessary movement of work between people or places. In a back office, this is a file passing through four queues when two would do, or a document emailed back and forth across sites.
Inventory. Work piled up and waiting: the pending queue. Every file sitting there ages, and its customer waits. A backlog is stock in the lean sense.
Motion. Extra movement by the worker. For an agent, that is switching between six screens to find a single field, or searching a shared folder for the right template each time.
Waiting. Idle time because something upstream has not arrived: an approval, a system response, a missing document. Note the difference from inventory. Inventory is work waiting for people; waiting is people waiting for work.
Overproduction. Doing more, or earlier, than needed. Producing a daily report nobody reads is the classic. So is preparing a full verification pack for files that will be rejected on a basic check.
Over-processing. More effort than the customer values. Three levels of approval for a small amount. Re-keying data already present in another system.
Defects. Errors that need correction: a wrong field, a missing signature, a wrong disbursement amount. This is rework.
Skills (non-utilised talent). Not using people’s ability. A graduate analyst spending the day copy-pasting, or an experienced agent whose ideas about a broken step are never asked for.
Putting a number on one waste
Defects are usually the easiest to size. Suppose the Nagpur team handles 5,000 files a day, and 6 per cent come back for correction. That is 300 files a day. If each correction takes 12 minutes of someone’s time, that is 3,600 minutes, or 60 hours. With 7.5 productive hours per person per day, the team spends the equivalent of 8 people just fixing what went wrong the first time. That is capacity you pay for and cannot bill to anyone.
Cut the defect rate from 6 to 3 per cent and about four of those eight people are freed. Freed does not mean fired; they can absorb growth or clear the backlog (inventory), which is why these wastes are connected. Defects create rework, rework creates backlog, backlog creates waiting and chasing calls from customers. Fixing one early in the chain pays back in several others.
Where the idea gets misused
The first misuse is treating “waste” as a word for lazy people. In Lean, waste is a property of the process, not the person. The agent switching between six screens is not at fault; whoever designed the screens is.
The second is deleting every non-value-adding step. Some of them are necessary even though the customer would not pay for them: compliance checks, maker-checker reviews, audit trails. Lean calls these “business non-value-add”. They should be done as cheaply as possible, but not removed because a workshop got excited. Cutting a KYC check as “over-processing” is how a lender ends up with a regulator’s letter.
The third is running a one-time clean-up exercise. Lean is a habit. A team that finds eight wastes in a workshop and never looks again will find them back in six months.
How to start looking
Pick one process. Follow one file from arrival to closure and note every handoff, every wait and every touch. Write the touch time (when someone works on it) against the elapsed time (when it sits). In many service processes the touch time is a small fraction of elapsed time, and that ratio itself tells you where the waiting is. Then ask the people doing the work which step annoys them most. Their answers usually point at one or two of the eight letters.
Process maps, root cause tools like the five whys, and Six Sigma’s DMAIC all help after that. But the vocabulary comes first: until you can say “this is inventory” or “this is over-processing”, you tend to describe problems as “the team is slow”, which solves nothing.
Figures and names in the examples are illustrative.
Leave a Reply