2.problem Solving and Decision Making Presentation
2.problem Solving and Decision Making Presentation
Decision Making
LEVEL – PRACTITIONER
Session Rules
3
About the Facilitator
• Awards • Contributions
– Most Valuable Professional (MVP) – – Facilitates leadership, behavioral and
Business Solutions (Microsoft) project management topics
– Global Trainer of the Year Award – Editor of “Forecast Scheduling with
(Cognizant) Microsoft Project 2010 & 2013” book
– Delivery Excellence Award 2011- .
2012, 2012-2013 (PMI India)
• Outreach
– Past Champion Advisory Committee
• Certifications member, PMI India Champion
– Microsoft Certified Technology – President, MPUG Chennai Chapter
Specialist: Microsoft Project 2010 (http://chennai.mpug.com)
– PMI-certified Project Management
Professional (PMP) ®
– PMI-certified Scheduling Professional
(PMI-SP)®
– Certified Six Sigma Green Belt
4
A BAD DAY
Your team missed to complete the design on time. You need to find
out the reason why this happened. Six team members were involved
at different stages of designing the product.
You discuss this issue with three of this team. One team member
says by his past experience this issue is due to lack of planning.
Second team member says a recent research published by reputed
magazine states only five of 100 projects had this issue, and we
don’t need to worry about. Third team member says we had
frequent changes in requirements and this caused this delay.
6
Overview
7
Problem Solving and Decision
Making: Objectives
After completing this course, you will be able to:
– Identify the difference between symptom, problem and cause
– Learn techniques for problem solving and decision making
– Systematically identify the root cause and make better decisions
8
What is the difference
between Problem
Solving and Decision
Making?
Problem Solving and Decision
Making
Problem Decision
Solving Making
Problem Solving and Decision
Making
Problem Decision
Solving Making
Problem Solving and Decision
Making
Problem Decision
Solving Making
Symptom, Problem, and Cause
15
Solve This
16
Angry Client
Case Study
The client needs this transaction report on the last Friday of every month.
This report is used by them to generate the bills and give rewards points.
These transactions are usually in thousands of dollars.
All the team members in the team are trained on this process of
creating this report. This report is usually generated in 5 hours.
Today, you received a call from the Client. She was furious. She
complained their premium customers were billed incorrectly because the
transaction report has errors.
Angry Client (Contd.)
19
Process
20
Define the problem
22
Identification of Causes
Tools
Identification of Causes
Tools
Some more information …
Process
document is
not accurate
Team not
Did not Follow the
motivated Work load of
Steps Prakash
Version
Macro Version Customer
upgrade issue
Issues Expectation
was different
Cause and Effect Diagram
Advantage Disadvantage
Place the pointer tool in Annotate toolbar on this slide. Then, select T (text) and write your
response next to your name
27
When to use fish bone diagram?
29
Let Us Investigate
Tools
Advantage Disadvantage
Place the pointer tool in Annotate toolbar on this slide. Then, select T (text) and write your
response next to your name
31
When to use root cause analysis?
32
Drawbacks of Root Cause
Analysis
• It is least scientific. It is based on ones opinion
• Five Why analysis done by two people can yield to different
findings
• It assumes each symptom/problem has only one cause
• This method requires a skilled person
33
Process
34
Decision Making Interactive
Activity
Solutions
36
What are the Options?
Tools
Weightages
Weightages 3 3 3 2 1
Weightages 3 3 3 2 1
70%
automation
with review
100%
Automation
Weightages 3 3 3 2 1
70%
automation 2 2 2 1 1
with review
100%
Automation
3 3 3 3 3
Solutions Score
Cost Time Quality Scalability Integration
Sum(Wi*Si)
70%
automation 2 2 2 1 1 21
with review
100%
Automation
3 3 3 3 3 36
“100%
Automation”
Force Field Analysis
Tools
52
53
Summary
54
Congratulations!