Problem Solving Techniques
This single day course provides an introduction to the various methods and techniques that can be utilised to go about problem solving in a structured and organised way.
We talk you through a number of different scenarios, looking at the main aspects of the techniques, covering areas such as:
Cause and Effect Diagrams with Added Cards - CEDAC
Paretto analysis and different methods of information management
Brainstorming/Mind Showers
Root Cause Analysis
Stopping it from happening again
CEDAC is a process for solving problems. The ‘CED’ part of the name refers to a ‘Cause and Effect Diagram’, a basic plan if you like of the problems encountered, the interaction between them and their contribution to the problem. The ‘AC’ refers to ‘Added Cards’, highlighters of possible solutions and the state of play of analysis of those solutions.
A problem occurs when what is happening differs from what should be happening.
With the use of a few simple bits of paperwork, we can identify the main problems and from there implement solutions to eliminate these problems.
Pareto analysis and Graphing the Process
Pareto analysis is very simple, so simple in fact that they teach it to us all in Primary school. It is really no more than gathering information and plotting it on a bar graph, giving an indication of areas where problems are occurring and/or what those problems are.
The methods used to visualise the information can be one of the single most important aspects of solving the problem, and we display a number of different methods for gathering and providing this information for others.
Brainstorming/Mind Showers
Throughout the problem solving process we emphasise the importance of using hard and accurate information, however in this instance we are using unproven ideas and relying of creativity and experience. We go through methods of gaining feedback from the team members and using that feedback to create a working plan.
5 Whys and Root Cause Analysis
This is simply asking questions that get to the heart of the problem. Although the number 5 is used, you should keep asking until you are sure that you have found the root cause.
There is no point in identifying a problem only to take one step back down the line to rectify it if the root cause is four steps away – the problem will just raise its head somewhere else.
Why did the customer complain?
The finished product was incorrect.
Why was the finished product incorrect?
The incorrect ingredients were used.
Why were the incorrect ingredients used?
The Standard Operating Procedure was not followed.
Why was the Standard Operating Procedure not followed?
It was not available.
Why was the Standard Operating Procedure not available?
Was not stored in the correct location.
In this instance the solution might be to attach the Standard Operating Procedure to the wall so it cannot leave the work area.
Poka Yoke = Mistake Proofing
Poka Yoke is designed to initially compliment quality inspection and control within the workplace, as it is impractical to alter a complete quality system overnight, however the ultimate goal of poka yoke is to replace the need for quality inspection – defects should be either designed out or should highlight themselves.
Systems are generally designed so that if the first operation is faulty then it will be impossible to start the next operation. This is achieved through a combination of careful planning of the order in which operations are completed and good engineering innovation. For this reason it tends to be used in machining operations and assembly rather than areas where there is a need for fine finishes or aesthetics.
This single day course provides an introduction to the various methods and techniques that can be utilised to go about problem solving in a structured and organised way.
We talk you through a number of different scenarios, looking at the main aspects of the techniques, covering areas such as:
Cause and Effect Diagrams with Added Cards - CEDAC
Paretto analysis and different methods of information management
Brainstorming/Mind Showers
Root Cause Analysis
Stopping it from happening again
CEDAC is a process for solving problems. The ‘CED’ part of the name refers to a ‘Cause and Effect Diagram’, a basic plan if you like of the problems encountered, the interaction between them and their contribution to the problem. The ‘AC’ refers to ‘Added Cards’, highlighters of possible solutions and the state of play of analysis of those solutions.
A problem occurs when what is happening differs from what should be happening.
With the use of a few simple bits of paperwork, we can identify the main problems and from there implement solutions to eliminate these problems.
Pareto analysis and Graphing the Process
Pareto analysis is very simple, so simple in fact that they teach it to us all in Primary school. It is really no more than gathering information and plotting it on a bar graph, giving an indication of areas where problems are occurring and/or what those problems are.
The methods used to visualise the information can be one of the single most important aspects of solving the problem, and we display a number of different methods for gathering and providing this information for others.
Brainstorming/Mind Showers
Throughout the problem solving process we emphasise the importance of using hard and accurate information, however in this instance we are using unproven ideas and relying of creativity and experience. We go through methods of gaining feedback from the team members and using that feedback to create a working plan.
5 Whys and Root Cause Analysis
This is simply asking questions that get to the heart of the problem. Although the number 5 is used, you should keep asking until you are sure that you have found the root cause.
There is no point in identifying a problem only to take one step back down the line to rectify it if the root cause is four steps away – the problem will just raise its head somewhere else.
Why did the customer complain?
The finished product was incorrect.
Why was the finished product incorrect?
The incorrect ingredients were used.
Why were the incorrect ingredients used?
The Standard Operating Procedure was not followed.
Why was the Standard Operating Procedure not followed?
It was not available.
Why was the Standard Operating Procedure not available?
Was not stored in the correct location.
In this instance the solution might be to attach the Standard Operating Procedure to the wall so it cannot leave the work area.
Poka Yoke = Mistake Proofing
Poka Yoke is designed to initially compliment quality inspection and control within the workplace, as it is impractical to alter a complete quality system overnight, however the ultimate goal of poka yoke is to replace the need for quality inspection – defects should be either designed out or should highlight themselves.
Systems are generally designed so that if the first operation is faulty then it will be impossible to start the next operation. This is achieved through a combination of careful planning of the order in which operations are completed and good engineering innovation. For this reason it tends to be used in machining operations and assembly rather than areas where there is a need for fine finishes or aesthetics.
Oils - Defence - Health Service - Engineering - Chemicals - Food and Drink - Manufacturing - Business Improvements - Casting
Ferryport Ltd., 112 Canada Drive, Cherry Burton, East Yorkshire, HU17 7RH. 07903 189865, contact@ferryport.org
Registered in England and Wales. Registration number 07644480
Ferryport Ltd., 112 Canada Drive, Cherry Burton, East Yorkshire, HU17 7RH. 07903 189865, contact@ferryport.org
Registered in England and Wales. Registration number 07644480
