Problems solving
Problems solving
Embedded Files
The teams that survive are those that solve their problems. Successful teams are those that kill their problems before they get big.
The teams that survive are those that solve their problems. Successful teams are those that kill their problems before they get big.
What is the problem ?
What is the problem ?
A problem is a gap between reality and our expectations
The 5 steps of problem solving
The 5 steps of problem solving
The 5 steps > use this file
1. Describe the Symptoms
Alert, out of stock, reduced productivity, waiting
.
2. Describe the Problem
What facts do we have? What, Who, Where, When, How ?
What is the gap between the current and expected situation ?
.
3. Identify the root causes
The "5 Why" method
Ishikawa diagram (6 M)
The problems will come from the 6 M’s
The problems will come from the 6 M’s
Mother -Nature
Mother -Nature
Means
Means
Machine
Machine
Method
Method
Men
Men
Measure
Measure
The "5 Why" to identify the root causes :
The "5 Why" to identify the root causes :
Real example with the lincoln memorial (US)
Real example with the lincoln memorial (US)
The monument is deteriorating rapidly.
I renovate the building regularly and it costs a fortune !
The building is deteriorating rapidly, I look for the root cause through the 5 why
1_Why does the building deteriorate?
Because too many chemicals are applied
2_Why are too many chemicals used?
To clean pigeon poop
3_Why are there so many pigeons?
Because they eat the insects on the building !
4_Why are there so many insects?
Because of the light!
Solution: do not light the building at night
Solution that is ecological, economical and definitive thanks to the 5 Why
the 4 attitudes that facilitate problem solving
the 4 attitudes that facilitate problem solving
Don’t judge too quickly
Be Curious
Be Logical
Be Concrete
Workshop Problem Solving
Workshop Problem Solving
To solve : PDCA Method
To solve : PDCA Method
PLAN DO CHECK ACT (PDCA) works well in all types of organizations.
It can be used to improve any process or product, by breaking them down into smaller steps or development stages, and exploring ways to improve each one.
It's particularly helpful for improving business processes generally
However, going through the PDCA/PDSA cycle can be much slower than a straightforward, "gung ho" implementation. So, it might not be the appropriate approach for dealing with an urgent problem.
STEP 1 > PLAN
1_The target to be reached is etablished
2_Planning a solution to a problem
STEP 2 > DO
3_Implement the solution
4_Learn by doing to capitalise later
5_Ideas for adjustements
STEP 3 > CHECK
4_Evaluate the result of the implemented solution
5_Formalise our learning
STEP 4 > ACT
7_A decision has been made
it works > duplication
it doesn't work > new iteration
DPS Approach
DPS Approach
DPS is a collaborative work based on the experience of each and the collective intelligence.
It works as a project: there is a team, a leader and a planning.
When do you use this method ? Mainly for the customers risk
--> To go further HERE
DMAIC Approach
DMAIC Approach
To capitalize : why create or update a standard ?
To capitalize : why create or update a standard ?
Thanks to it, good gestures become permanent. It is the "wedge" that allows us to progress, to move forward step by step without ever going backwards.
Thanks to it, good gestures become permanent. It is the "wedge" that allows us to progress, to move forward step by step without ever going backwards.
The lack of work standards at certain points in a process is the main cause of variability in the performance of a team.
The standard is not set in stone, it evolves iteratively as problems are solved and therefore over time. It is a document that is subject to change, to be optimised by the team that designed it and uses it.
DPS is used when there is a client risk. Three actions are added to solve a problem
Page updated
Report abuse