Week 2: Pepsi Case, Trigger Words, Root Cause (5 Why's) Flashcards
When looking at a case, you should be spending _____ of your time on analysis
2/3
So if you have 3 hours, two hours should just be reading and understanding the material
If a case has one clear cut question, it is not a case, just a ________
Question
A case should always have multiple solutions fam
Coke and Pepsi Case Following these slides
Title: The Shifting Landscape of the Carbonated Soft Drink Industry
CSD
carbonated soft drink (CSD)
The largest costs for CSD manufacturers, including Coca-Cola and Pepsi, were
advertising, promotional materials, market research, and support for bottlers, including local advertising and negotiating with the bottler’s raw material suppliers and their primary customers, retail stores
Fountain accounts
companies that distributed CSD products through fountains (mixing concentrate and carbonated water on the spot) rather than in cans or bottles.
Restaurant chains, such as McDonald’s or Burger King, were important fountain customers
For the majority of Coca-Cola and Pepsi’s histories, independently owned,__________ were the companies’ primary source of distribution and sales
franchised bottlers
The strong rivalry between Coca-Cola and Pepsi throughout the twentieth century became known as the ________
cola wars
The 5 Whys Slide’s beyond this
The 5 Whys Slide’s beyond this
Brief overview
The 5 Whys is a technique that can help you to find the root cause of a problem.
By understanding the root cause of the problem, you can solve it in such a way that it doesn’t reoccur.
The 5 Why’s outline
1) Define the problem
2) Why is it happening
3) Why is that
4) Why is that?
5) Why is that?
6) Why is that -> Root Cause
Who invented the 5 WHys
The 5 Whys Technique was developed within the Toyota Motor Corporation in the 1930s
The 5 Whys outline example
Let’s take a look at what might have caused your website to go down
Problem: Website went down.
Why did it happen? It ran out of memory.
Why? Because it was incorrectly configured.
Why? Because the site admin made a mistake.
Why? Because development hadn’t provided adequate instructions.
Why? Because they assumed it was obvious
Countermeasure
The corrective action you take to the problem
Countermeasure to the 5 Whys Website down example
Cause 1: The website ran out of memory.
Countermeasure: Get the site up and running again.
Cause 2: Incorrect configuration.
Countermeasure: Create a Standard Operating
Procedure to verify configuration before every update.
Cause 3: Site admin made a mistake.
Countermeasure: Make sure site admin knows how to run the new verification test.
Cause 4: Development hadn’t provided adequate instructions.
Countermeasure: Train dev team to provide sufficient instructions.
Cause 5: Assumed it was obvious.
Countermeasure: Have a word with dev team manager to ensure they speak to their team about the importance of being precise no matter how obvious it seems.
Rule of Thumb
Asking why five times is a rule of thumb. You may have to ask “Why?” just three times or even ten times to get to the real root cause of the issue you’re investigating.
How to Run a 5 Whys Meeting
Step 1: Organize a 5 Whys Meeting Step 2: Define the Problem Statement Step 3: Ask the First “Why?” Step 4: Ask “Why?” Four More Times Step 5: Determine your Countermeasures Step 6: Assign Responsibilities Step 7: Monitor Progress Step 8: Close the Meeting
Step 1: Organize a 5 Whys Meeting
Organize for everyone who might be affected by the problem or have input to its solution to attend a 5 Whys Meeting
If you are not leading the session then make sure that someone is. It is the session leaders responsibility to lead the 5 Whys process and assign people as being responsible for countermeasures.
Step 2: Define the Problem Statement
At the start of the session, you should define the problem you are trying to solve. Write the problem on a whiteboard if you can
It’s essential to keep the problem statement focused only on the problem. Do not state any possible reasons for the problem or make any assumptions
Step 3: Ask the First “Why?”
Ask your assembled team why the problem is occurring.
Try to avoid entertaining answers that are guesses – stick to facts. If there is more than one reason given for the problem, then ask your team to vote on the most likely cause
Step 4: Ask “Why?” Four More Times
Ask why another four times, each time using the previous answer to base your question on. Once you have done this, you will have five reasons, one for each “why?” question.
As previously mentioned, you may need to ask why more times than five if you haven’t got to the root of the problem.
Step 5: Determine your Countermeasures
Agree what countermeasures you will take to address each of your five reasons that are now on the whiteboard.