The 7 wastes of lean and how to spot them

Most companies are bleeding profit and don’t even realize it. I’m not talking about dramatic stuff - embezzlement or bad deals. I’m talking about the quiet, slow drain of waste baked into everyday operations.

Taiichi Ohno, the engineer behind the Toyota Production System, identified seven categories of waste - called “muda” in Japanese - that kill efficiency. He wrote about them in his 1978 book, and they’re just as relevant now as they were then. Probably more so.

Cut through the noise - in the age of AI, defining and fixing your processes matters more than ever. If you automate a wasteful workflow, you just get wasteful results faster. So let’s understand what waste looks like before we talk about fixing anything.

TIMWOOD framework

People use the acronym TIMWOOD to remember the seven wastes. It’s a bit clunky, but it works. Let’s break each one down.

Transportation

Moving stuff around that doesn’t need moving. In a factory, that’s shuttling materials from one end of the building to the other for no good reason. In an office, it’s forwarding emails through five people before someone can act on them.

Any movement that doesn’t directly add value is dead weight.

Think about your own workflows. How many handoffs happen between teams? Each handoff is a transportation cost - time lost, context lost, errors introduced. Based on hundreds of implementations we’ve supported at Tallyfy, the handoff between teams is where most processes break down. Not because people are bad at their jobs, but because the process itself forces unnecessary movement.

Inventory

Capital sitting in a warehouse isn’t earning interest. It’s gathering dust.

Inventory waste goes beyond physical goods. Think about all the half-finished projects sitting in your team’s backlog. Those unfinished tasks represent invested time that hasn’t produced value yet. Same principle.

Toyota pioneered JIT (Just in Time) inventory management specifically to tackle this. The goal is simple: have just enough materials to keep things moving, just enough finished product to meet demand. Nothing more.

Motion

Transportation is about moving materials. Motion is about moving people.

Picture this: a technician walks from one workstation to another six times a day. Each trip takes three minutes. That’s 18 minutes of walking. Across a five-day week, that’s 90 minutes. Across a year? Over 75 hours of just… walking.

Here’s one that’ll resonate with office workers - when the printer sits across the building from your desk. Every trip to grab a printout is wasted motion. Even at a single workstation, poor ergonomics force unnecessary movements that add up.

Fun fact: pedal bins and fitted kitchens were originally designed as motion-reduction solutions. Someone looked at a kitchen and thought, “why are we walking so much?” That’s lean thinking in everyday life.

Waiting

This one’s easy to spot. One process grinds to a halt because another process is stuck. Bottleneck. Dead time. Money burning.

Monitor your process flows from start to finish. Where do things pile up? Where do people sit idle waiting for approvals, inputs, or handoffs?

In our experience with workflow automation, waiting is often the biggest waste by sheer volume. We’ve seen approval steps that take 45 minutes of actual work but sit in someone’s inbox for two weeks. The work isn’t hard. The waiting is a nightmare.

Overproduction

Making more than you need, before you need it. Sounds obvious, but turns out it happens everywhere.

Unreliable suppliers push companies to build safety stock. Bad demand forecasting leads to excess. A “more is better” mindset creeps in. And suddenly you’re storing, insuring, and managing inventory that nobody asked for.

Overproduction feeds transportation waste (stuff has to go somewhere) and inventory waste (stuff has to be stored). Well, that simplifies it a bit. It’s basically the domino that tips the others.

Over-processing

What does the person receiving your output actually value? Anything beyond that’s over-processing.

I see this constantly in professional services. Teams spend hours polishing reports that nobody reads past page two. Designers add finishing touches that don’t change purchase decisions. Engineers build features nobody requested.

Find out what matters to the people you serve. If those extra finishing touches make a meaningful difference they’re willing to pay for, great. If not, redirect that energy somewhere useful.

Defects

Every defect means rework, scrap, or worse - a product that makes it through to the end user.

If you catch defects internally, you lose materials and time. If you don’t catch them, you’re looking at replacements, recalls, and reputation damage. Neither option is pleasant. Is zero defects realistic? Probably not.

The fix isn’t better inspection at the end of the line. It’s tracking defects back to their source. Are people trained properly? Are the process steps themselves creating errors? Are materials from suppliers up to standard?

The 8th waste nobody wants to admit

Have you asked your teams how to improve the design of their workspace? Their processes? Their tools?

Feedback we’ve received from operations leaders consistently highlights this: there’s a massive pool of improvement ideas sitting in the heads of the people doing the work every day. Most organizations never bother asking.

This drives me a bit crazy. Your teams know where the waste is. They trip over it daily. They’ve probably already figured out workarounds. But if nobody creates a channel for those ideas to surface, all that creativity goes to waste.

In discussions we’ve had about process improvement, one professional services team stands out. They reduced headcount from 65 to 15 people while simultaneously increasing revenue 4x - simply by documenting their processes and eliminating the redundant work their staff had already identified as wasteful. The ideas were there all along. Someone just needed to listen.

Identifying waste is only the first step - you need a system to track and eliminate it over time. That’s exactly why we built Tallyfy the way we did. Make the process visible first, then improve it continuously.

Morgan vs. Toyota - two very different choices

These two case studies sit at opposite ends of the spectrum, and both are fascinating.

Morgan chose tradition

Morgan Motor Company, based in Malvern, England, has been hand-building cars since 1909. In 1990, BBC’s Troubleshooter program (hosted by Sir John Harvey-Jones) examined their operations. What he found was textbook waste.

Over-processing showed up as Morgan’s insistence on hand tools for everything. Would the people buying these cars really mind if an artisan used a hand-held power tool? Probably not. But Morgan balked at changing.

Transportation was a mess. Vehicles moved from one end of the facility to the other and back again during production. Waiting happened constantly as processes ground to a halt waiting on earlier steps.

Inventory ran on an old-fashioned card system, and unnecessary volumes of materials sat in storage. Finished cars were parked on a gravel lot where they risked damage. Defects were rare thanks to craftsmanship, mind you, but all inspections were manual and visual - hidden problems could slip through.

Harvey-Jones recommended modernizing. Morgan rejected almost everything, arguing that tradition was the appeal and their years-long waiting list proved the model worked.

Honestly, whether that dedication adds real value is debatable. But they made a conscious choice. That’s the key distinction.

Toyota chose elimination

Toyota didn’t just talk about waste reduction. They built an entire production system around it.

They stopped trying to produce more cars and then stimulate demand. Instead, they gauged market demand and only produced what they could immediately sell. That took courage.

They streamlined production flows so steps flowed smoothly into each other, cutting waiting. They designed facilities to minimize transportation between processes. They chose equipment that did the job well - not the flashiest or most automated option - reducing over-processing.

Their JIT system tackled inventory head on. Improved workstation ergonomics reduced wasted motion. And instead of catching defects at final inspection, they tracked problems to their source and fixed them there.

The results speak for themselves. Toyota became one of the most respected automakers on the planet, known for quality and reliability at reasonable prices. Not bad for a company obsessed with waste.

Templates to reduce waste in your processes

Example Procedure

Inventory Management

1Receive and check incoming goods

2Sort, label, and store your inventory

3Monitor your stock levels

4Place stock orders

5Get stock orders approved

+8 more steps

View template

Example Procedure

Print Production & Quality Control Workflow

1Initial Print Job Setup

2Configure Print Properties

3Submit Print Request

4Review File and Specifications

5Get Cost Approval If Needed

+2 more steps

View template

Example Procedure

Warehouse Order Picking and Fulfillment Workflow

1Generate warehouse picklist from pending orders

2Assign warehouse picker to order batch

3Prepare picking cart and warehouse equipment

4Scan totes and verify item barcodes for accuracy

5Review and verify customer order details

+4 more steps

View template

Lean waste isn’t just for factories

Here’s where I think most lean content gets it wrong. They talk about manufacturing floors and assembly lines. But the seven wastes show up everywhere. Ray Kroc’s McDonald’s uses JIT inventory management to reduce food waste, and you could argue that’s still manufacturing in a different form, but even purely service-based operations deal with these wastes. Duplication is over-processing in disguise. Delays in service delivery are waiting waste. Routing people from department to department is transportation waste applied to human beings instead of materials. At Tallyfy, we believe the key to eliminating waste is making your processes visible first. You can’t improve what you can’t see. And once you see it - once you map out exactly how work flows through your organization - the waste becomes painfully obvious.

I think that’s what makes the seven wastes framework so powerful. It’s not complicated. It’s a lens. You hold it up to any process and suddenly the problems jump out. Will it fix everything overnight? No.

The question isn’t whether your organization has waste. It does. Every organization does. The question is whether you’re willing to look for it, listen to the people who already see it, and do something about it.

That’s where most companies stall. Not because the waste is hard to find, but because fixing it requires changing how people work. And change, as Morgan showed us, isn’t always welcome - even when the evidence is right there.

Start small. Pick one process. Map it out. Ask the people who run it where the waste is. Then fix it. Then do it again. That’s lean in a nutshell - not a one-time project, but a habit of continuous improvement that compounds over time.