There are 7 wastes in Lean which are referred to as Muda (in Japanese). Let us quickly go through each one.
Waiting:
It talks about the non-productive time period due to lack of equipment, material , human beings. This can talk about any delayed arrival of materials or persons, or delay due to equipments broken. So resources would be idle till such time.
Eg: Waiting for a human resource to be available to fix an issue
Over Production: It refers to manufacturing an item before it is actually needed. It relates to excessive accumulation of WIP of finished goods inventory. It is the worst form of waste because it contributes to all the others.
Eg: Preparing unnecessary reports which may not be read at all
Rework (or Defects): This talks about the correction needed for fixing the mistakes, normally. These activities are waste of time.
Eg 1: Fixing the bugs created in software code Eg 2: Correction on made on the word documents – typo errors/spelling mistakes
Motion: It tells about the unnecessary movement of people and equipment
Eg: Extra data entry, extra steps ...
Over Processing: This refers to non-value added tasks which customer would not be interested. This could be because of poor design of the product/process.
Eg1: Any gold-plating work , like beautification of software code which is not required or not asked by customer Eg:2 Sending unnecessary mails doing extra communication Eg:3 Sending some data in multiple reports – duplicate effort
Inventory: To keep stock of items , often in excess, than what is required .
Eg 1: Keeping stock of raw materials, in plenty (abundance) than what is needed for use.
Transportation: It refers to the unwarranted movement of materials, information.. Process Steps should be closely located to one another for minimal movement.
Eg 1: Mail Forwarding to another persons , after missing to loop in those persons in the original email Eg:2 Movement of files/papers from one place to another place
Now as we have seen the 7 wastes of Lean , there is also another type of waste , which is often called as the 8th waste. It talks about the underutilization of talent and skills. If we happen to address this waste, there is a chance that we can do well with the rest of the waste types.Having said that, let us see how we can make good use of these wastes .
Let us take some of the wastes discussed above
Waiting: Some IT applications might be quite complex and can involve multiple technologies. In a typical enterprise based web application, the technologies involved could be relational database(s), server-side programming languages, application servers (which host the application), front-end/User Interface languages and programming scripts, messaging tools etc.,. Assume this application is in the development stage.
Now we see a potential problem in the way how application is designed. This requires a technical architect to do a course correction as he is the technical Subject Matter Expert (SME).The design change is critical in ensuring application scalability does not impact. Now assume that this architect is shared/utilized across multiple projects within a business unit of the organisation (which owns this application). When he is needed for this project(application) to provide optimal design, he is not available as he is held up in another project for production implementation and would not be available for 2 days. Now the project needs to wait for his presence and its worth waiting 2 days, since the architect would change the shape of the project (application) so that many users (Scalability) can be able to visit post the go-live period
2.Rework: There are scenarios, where this may be required.
1.There could be changes on product /process design due to environmental conditions, government statutory
2.There could be rework due to a design flaw on product. Eg: A product might have sharp edges on it. A consumer would have put a consumer case against it , after getting affected (hurt) by that. So consumer court would have instructed the company which produced the product to blunt the product’s edges. This is a legal issue which definitely needs rework of the design.
3.Inventory: Why this is needed?
i).In Software, the developers will always have a copy of the code that they had developed. Those codes would be available in a Version control system (Configuration management). But still developers retain that because they would like to see if that can be used in some other projects. Also they want to see how their code looks changed when compared with the code in the version control system
ii). A Supermarket can operate in Push (having Inventory) and Pull type (Just-In-Time). Some items can be fast moving and some items can move slow or have less demand. So the super market can stock fast moving items which do not degrade over a period of time or for a considerable amount of time.
Conclusion:
This goes to show how different type of wastes can be made use of!!