Lean Manufacturing Wastes: Muda
Larger profit margins can be boiled down to two actions – increasing output and improving efficiency. Frequently, businesses choose to increase their capacity to drive output, hiring staff and investing in new tools. They can also look for ways to work more efficiently with their existing resources. Reducing waste is essential in order to make processes more efficient.
Costs from wastes are ultimately passed on either to your customers or your business. Putting prices up can mask waste costs to a certain extent, but the market determines what your customers will pay. When customers find your product too expensive – or when a competitor tries to undercut your price – waste directly attacks your profit margins. Lean Manufacturing defines three wastes that must be reduced or eliminated: Muda (not adding value), Mura (unevenness), and Muri (overburden). In this article, we’ll take a look at the first waste, Muda.
What is Muda?
Muda is the Japanese word for waste. One way to describe a wasteful process or activity is “something that adds no value”.
And why should customers pay for waste? If you purchase a faulty product, should you be charged the cost of a replacement? If a table you buy has been in storage for twice as long as usual, should that extra storage cost be passed on to you? The concept can (and should) be applied to any line of business.
In some cases, determining what adds value and what does not is not so cut and dry. Business activities can be split into the three following categories:
The steps that turn your raw material or concept into finished products, services and applications. Designing, developing, constructing, manufacturing are all value-adding activities.
- Non-value-adding, but necessary
There are some business activities that your customers will not want to pay for, but are nevertheless essential. Activities related to compliance with government and law regulations fall into this category. These are not wastes, and cannot be eliminated – they can only be made more efficient.
Activities that do not produce value and are unnecessary are classed as wastes. These are what you need to reduce and eliminate to make your business more profitable.
Lean Manufacturing Mudas
The Toyota Production System, the precursor of Lean Manufacturing and Kanban, identified 7 Mudas or Wastes: Transportation, Inventory, Motion, Waiting, Overproduction, Overprocessing, and Defects. As the system has evolved and been adopted in knowledge work sectors, an 8th Muda has been added to the list: the waste of human potential.
Let’s take a look at how each Muda affects your business and what steps you can take to reduce waste and increase the profitability of your business.
Unnecessary movement between stages of a process
In a manufacturing environment, this means the literal movement of raw material and stock from one place to another. Nevertheless, the concept still applies to knowledge work. Consider how a task moves from development to testing, or from writing to editing. What triggers the move from one state to the next?
Signing documents, reviews, sending emails – could any of these steps be made more efficient or even automated? One example could be setting up Trello notifications to notify other collaborators rather than manually sending emails. Another source of transportation waste is tasks moving back and forth due to miscommunication, unclear requirements, or poor quality of execution.
Idle materials, products or work in progress
Inventory is the accumulation of work in progress. It can also mean an accumulation of finished product that has not been sold or delivered to your customer yet. In Kanban processes, this primarily appears in the form of WIP items splitting your team’s focus and causing a bottleneck. Inventory build-up indicates that your flow is being hampered. This waste is reduced by adhering to Just In Time principles and only pulling a task through when your team has the capacity to work on it.
Unnecessary movement within process stages
Whereas transportation focuses on unnecessary movement between stages of a process, motion waste seeks to reduce unnecessary movement within it. Making each motion as small and ergonomic as possible is crucial in a manufacturing setting. But how can you reduce motion in knowledge work? There are hundreds of wasted motions – manually inputting data, chains of emails, searching, and filing. Document management systems and business process automation are some methods used to reduce the waste of motion.
The Muda of waiting is easily the most obvious form of waste in a Kanban process. It frequently appears in two forms. First, tasks are idle because team members can’t handle all of the WIP. Secondly, tasks are queueing to enter the next process stage because there is not enough capacity to pull them through. Some methods to reduce waiting waste are making sure WIP limits are suitable for your team and establishing explicit Kanban rules and pull policies in your process.
Producing too much
This waste can negatively affect your business in multiple ways. Your customer may not need all of the product features developed – the effort spent on a high throughput is wasted! Overproduction equally ties up time, effort, and money that could be better spent on other value-adding activities, and leads to further waste by increasing Inventory/Work In Progress. Matching delivery to demand in timing as well as quantity is the core principle of Just in Time production.
Doing more than is necessary
Overdelivering can be seen as a virtue, but in most cases, your customer will not be happy to shoulder an extra cost or wait additional time. The overprocessing Muda often comes from defining the specification or scope with your client too loosely – team members strive to deliver 100% when your client might only need 75% to reach their goals. This often comes from a misunderstanding of why customers buy your product, and what looks better to the product owner might look worse to the customer if the necessary market research and customer satisfaction data aren’t present.
Doing things wrong
The Muda of defects has costs which increase proportionally to how long it takes for the defect to be noticed. A defect that makes it through to your final product leads to poor customer satisfaction. Other costs include redoing the work correctly. Reducing this waste requires testing and quality assessments at each stage of your process to ensure defects are caught immediately after they occur.
Underused talent, ingenuity, and creativity
Kanban strives to make processes more efficient and productive. All too frequently the human factor is overlooked. Your team members work on your process every single day – they will have many insights to contribute. Encouraging your team to give their input and help solve problems is a key part of Kaizen culture.
The Kanban method relies on the cumulative effect of multiple small changes. There will be hundreds of opportunities across your business to reduce waste a little bit at a time. However, to quantify the effect of a change, you must make sure you are accurately tracking your Kanban metrics. Rigorous measuring and analysis ensure you know which actions make the biggest difference to your customer satisfaction and your bottom line.
Which wastes are the biggest problems for your process? What steps have you taken to reduce them? Tell us about your experience in the comments!
Meet the Author
Sonya Siderova is a passionate product manager and a driving force behind Nave, a Kanban analytics suite that helps teams improve their delivery speed through data-driven decision making. When she's not catering to her two little ones, you might find Sonya absorbed in a good heavyweight boxing match or behind a screen crafting a new blog post.
Our digital course Sustainable Predictability is listed for $397 until Nov 30th. Take advantage of the 60% discount… https://t.co/8bBbiaWPa3Follow
Start making reliable decisions and eliminating the bottlenecks caused by unclear priorities with a dynamic priorit… https://t.co/hVpa8sCtR9Follow
Take your team to a whole new level with Nave's Kanban analytics for Trello. Picture what's going on behind your da… https://t.co/BhnrABnsPBFollow
In our latest article, we’ll take you through the key steps to reducing the impact that blockers have on your deliv… https://t.co/10L6MoruB4Follow
30% discount on all annual plans until the 30th November! Subscribe now with a coupon code NAVEBLACK20… https://t.co/dnSM2KzS5cFollow
The dotted horizontal lines on the Cycle Time Scatterplot are called percentiles. We use percentiles to define the… https://t.co/nlUcIGRDm3Follow
High pressure over long time periods leads to your team suffering from burnout and its symptoms. Learn more about w… https://t.co/hcYg29OE3YFollow
Successful project managers are effective leaders whose decisions will drive a business forward. Here are the top 5… https://t.co/gDVZffzmDbFollow
Rely on data, not instincts. Nave Power-Up for Trello builds immersive analytical charts over your Trello boards. T… https://t.co/4wgoF3Sy2aFollow
Optimizing workflow efficiency is about eliminating bottlenecks and improving the predictability and stability of y… https://t.co/VmsnvqEH9kFollow
Use the percentiles on the Throughput Histogram to define the number of tasks you can commit to on a daily, weekly… https://t.co/9LcMvOs0U6Follow
Businesses that are truly fit for purpose are positioned for long-term survival and success. Here's an in-depth rev… https://t.co/k8vtaiHc6sFollow
Learn more about how to become more efficient with our expert tips and guidelines for Kanban teams.… https://t.co/wFrpIWBLyxFollow
Businesses with higher levels of team motivation perform better for a simple reason: they appreciate their employee… https://t.co/aFpd3fLT6tFollow
The Cycle Time Breakdown Chart can be of great help when it comes to bottleneck analysis. Identifying the root caus… https://t.co/TkASBXrTuMFollow
WIP limits can become a challenge without first considering the maturity of your team and the current state of your… https://t.co/Ly2oe23XwhFollow
Measure and improve your delivery performance with our advanced Kanban analytics for Asana projects. See a dashboar… https://t.co/3GfshR3MeJFollow
Product teams often argue which is better, but the focus should be on how to merge Kanban and Scrum together to del… https://t.co/kSUCdCTA9tFollow
Using a probabilistic approach of making future predictions enables us to define service level agreements with more… https://t.co/BhFmeeWt1DFollow