Mostrando las entradas con la etiqueta A3. Mostrar todas las entradas
Mostrando las entradas con la etiqueta A3. Mostrar todas las entradas

sábado, 28 de febrero de 2015

Zero Defects (無欠陥) – Part 1 of 3 - Five Elements of Production and the Five W’s and one H.

This article is intended to describe the sequence for Root Cause analysis, from the point of view of Sensei Shigeo Shingo and is based on my own experiences as an instructor of TPS continuous Improvement also.


Its not intended to describe how a template must be filled or completed, the scope is more conceptual, it talks about the interrelation of the tools Ishikawa diagram, 5 W’ 1 H & the 5 whys?


Write about Zero Defects is not simple, so I have divided in 3 parts and this is the first one.

The below diagram is basic when determining the root cause of a problem. This Diagram, was first described by Sensei Shigeo Shingo in his book; Zero Quality Control: Source Inspection and the Pokayoke System.

Five Elements of Production and the Five W’s and one H.

Fig.


It is very common for beginners in the method of problem-solving, wanting to go directly to the solution, without investing a reasonable time analyzing and finding the true root cause of the problem. Usually when I wonder what part is the most important for problem-solving over 90% of people answer Pokayoke, however are in error and without discrediting the importance of implant a good Pokayoke, the most important thing is to find the root cause problems, however it is extremely difficult.

In my experience this tools sequence have gave me good results, starting from Problem definition, 5W & 1 H, followed by Ishikawa Diagram until answer the 5 Whys that demystify the Root Cause

Five W’s  one H.
Fig.


It’s an Information Gathering method; that helps to define the problem, with data and facts.
5W1H (what, where, when, who, how, why) is a method of asking questions about a process or a problem taken up for improvement. Four of the W’s (who, what, where, when) and the one H is used to comprehend for details, analyze inferences and judgment to get to the fundamental facts and guide statements to get to the abstraction. The last W (why) is often asked five times so that one can drill down to get to the core of a problem.

However many times is not easy to answer directly and we may get stuck in one question Why?.
In other worlds just after the problem have defined and the question Why? Is prompted the team may be in blank, not clue at all; for that situations we should use the Cause and Effect Diagram or Ishikawa Diagram, to discriminate all the possible causes and find the answer, that immediately will carry on a new question, Why?... and so on.


Ishikawa diagram.

Fig.


Depict the Causes of a specific event Common uses of the Ishikawa diagram are Product Design and Quality Defect prevention, to identify potential factors causing an overall effect. Each cause or reason for imperfection is a source of variation. Causes are usually grouped into major categories to identify these sources of variation.
Causes;
Causes in the often categorized, such as to the 5 M's, described below. Cause-and-effect diagrams can reveal key relationships among various variables, and the possible causes provide additional insight into process behavior.
Causes can be derived from brainstorming sessions. These groups can then be labeled as categories of the fishbone. They will typically be one of the traditional categories mentioned above but may be something unique to the application in a specific case. Causes can be traced back to root causes with the 5 Whys technique.

Typical categories are

The 5 Ms (used in manufacturing industry)
    Machine (technology)
    Method (process)
    Material (Includes Raw Material, Consumables and Information.)
    Man Power (physical work)/Mind Power (brain work):Kaizens, Suggestions
    Measurement (Inspection)

The original 5 Ms used by the Toyota Production System have been expanded by some to include the following and are referred to as the 8 Ms. However, this is not globally recognized. It has been suggested to return to the roots of the tools and to keep the teaching simple while recognizing the original intent; most programs do not address the 8Ms.
       Milieu/Mother Nature(Environment)
       Management/Money Power
       Maintenance

The categories typically include
       People: Anyone involved with the process
       Methods: How the process is performed and the specific requirements for doing it, such as policies, procedures, rules, regulations and laws
       Machines: Any equipment, computers, tools, etc. required to accomplish the job
       Materials: Raw materials, parts, pens, paper, etc. used to produce the final product
       Measurements: Data generated from the process that are used to evaluate its quality
       Environment: The conditions, such as location, time, temperature, and culture in which the process operates.

5 Why’s
The 5 why’s typically refers to the practice of asking, five times, why the failure has occurred in order to get to the root cause/causes of the problem. There can be more than one cause to a problem as well. In an organizational context, generally, root cause analysis is carried out by a team of persons related to the problem.
No special technique is required.

Fig.




However in the practice it’s not easy, and like I have mentioned before, there are situations when the team do not have the answers and they will need to do an Ishikawa diagram.


Lets see this example.
As you see the Ishikawa Diagram was used at the right moment, to demystify the answer or answers.

I hope this help you in your next problem-solving event.


jueves, 30 de octubre de 2014

A3 and DMAIC – Improving the Problem Solving Culture at Lean-Six Sigma Deployment.

In my work experience there are times when you need mix Methods of Problem Solving ( A3 and DMAIC), it could be for many reasons.

Some years ago I joined at one company that had none knowledge about Lean Manufacturing, they where expose to Six sigma Deployment  (wrong deployed by the way),  I found several problem one of the most dangerous for Six sigma was the “Certification Hanged on the wall” ; this behavior is explained as follow ; “when the Black or Green Belt , are not continuing doing Six sigma projects; they finished  2 or 1 project  required to get the certification , updates their resumes and hanged the Certification on the wall”.

The Organization suffered of ; excess of Passive Talent or as we call in Lean the 8 waste (Lack of Talent People Utilization). 

This is a System Failure; as I have mentioned the Six sigma Deployment was wrong implemented, therefore as the Lean-Six sigma Director I had to create a new and effective System that promotes the Problem Solving as Culture or DNA of the organization.

However the main problem was “How to modify the old behaviors?,” there is not a perfect formula or answer for this, let me tell you already.

When I faced this situation, I introduced a new Belt Level “Yellow”, and it was mandatory for all the Salary Staff (Supervisors, Technicians, Engineering, Finance etc.) basically the rest of the people that had not certified as Green or Black, that was more than 90% of total population at that time. Yes of course I had the full support of management, otherwise I would have fired lol.  Don't try this if you don't have the full management support.!!!

Even that I followed the Standard for Six Sigma Yellow Belt training, I introduced the A3 problem Solving method (The method more used on Lean Manufacturing) , the idea was create the Problem Solving behaviors that be transform as Culture eventually, the A3 was mixed with DMAIC phases , this allowed easy introduction to that company that was more oriented to Six sigma.

I intentionally deviated of the old paradigms that they had about the Six sigma; “…DMAIC or Six sigma, takes many time and just the scientific-statistic people can do”; that was the old paradigm for Problem Solving or DMAIC of that organization, at that moment.

The Yellow Belt Finished their projects using the next Template, and the project will not take more than 1 week from D to C .
I have not to say that eventually the Green and the Black Belt used this report (Template) to document their projects and obviously they where prompted to do more projects.



A3-DMAIC Problem Solving Template



A3-DMAIC Problem Solving - Example








As I have mentioned this has the purpose to make the Problem Solving, as DNA of the company and the “Templates or formats” should be easy to review at any meeting - time,

I use the A3 problem solving because In Toyota, no problem is a problem!; Problems are seen as opportunities to improve their processes and, ultimately, their products.

 The people assigned to solve the problem, view the assignment as an opportunity to improve their problem-solving skills. They understand that they learn more and become a better problem-solver each time they perform the process. 

A3 is a structured and very useful problem-solving template. To be successful, this template must be supported by a lean culture that changes how we view problems. Otherwise, A3 Problem Solving will just join the list of “programs of the month”.

On the A3 template, the steps are typically laid out like this:




And as I always say on my post, you do not have to follow, copy or implement, what is here; its for your reference only, what worked for me, not necessary will work for you, however if you think that some of this tool or method may help you please don’t hesitate and try it immediately avoiding the procrastination.



PD: Obviously you can Mix DMAIC with 8D or others PS Methods templates.