Using a Fishbone Diagram: Part 2PROG 1026: Logic & Problem Solving

AgendaReview

Workshop IntroductionCause & Effect IntroductionBrainstorming Exercise

Cause & Effect PracticeCause & Effect Follow-upWrap-up and Exam Prep

Workshop IntroductionWhy use C&E?Workshop ScopeObjectives of C&E

Root causesTeamworkProblem SolvingInnovation

Ground Rules

Intro to C&E Definition: A Cause and Effect Diagram is a tool that helps a team to identify,

explore, and display in increasing detail, all of the possible causes related to a problem or condition in order todiscover its root cause(s).

Practice BasicsWeekend Procrastination?

Define/ Assign Cause Categories Brainstorm more detailed causes Choose a cause and ask “Why?”

2-5 times Share lowest level causes and

look for patterns

Problem Statement

Constructing a Fishbone DiagramVelaction Video

Process FlowchartProblem Definition CriticalFormat/ Cause CategoriesBrainstorming!AnalysisAction on Root Causes

Case StudyThe Case of the Missing Deadline

What is the central problem?What are possible causes of the problem?

Take a moment to review and reflect on the case study

ProcessSelect a facilitatorPhrase the problem statement (5 min)Generate causes (10 minutes)Construct the diagram (15 minutes)

Dispersion AnalysisProcess CategorizationBreak down causes to find root causes

Analyse Causes (15 minutes)Follow up on root causes (debrief – 5-10 minutes)

Step 1: Select a Facilitator A facilitator is expected to:

Make sure that the problem is clearly understood by everyone.

Get the team to participate in the current step.Manage the time so that each task is finished in line with

the training schedule.Make sure that any and all ideas are recorded accurately.Summarize the team’s conclusions based on the consensus

of the team and the specific assignment.

Step 2: Problem Statement Facilitator provides opportunity for team to contributeStatement should normally be 4-8 words or lessA problem is an issue that represents a gap between

desired and actual performance/results and is an observable effect of one or more contributing causes

Discuss in team and come up with a statement – write it large on a sticky note and place at far right middle of the chart

5 MINUTES

Step 3: Generate CausesGeneral to specific?Specific to general?Brainstorm

no judgment, just try to get as many ideas as possibleFacilitator, ensure everyone has a chance to participate

10 MINUTES

Next: Major Cause Categories

Step 3: Dispersion Analysis4 Ps

Process/ProcedurePeoplePolicyPlant/Equipment

4 MsMethodsManpowerMaterialsMachinery Equipment

Problem Statement

Process People

Policy Plant/ Equipment

Step 3: Process Classification Define major steps in the ProcessEstablish causes relative to the process

Late Pizza Deliveries on Friday Nights

Assembling Pizza

Baking Pizza

Taking Orders

Delivering Pizza

Step 4: Construct DiagramAssign Causes

Assign to one category if possibleIf not possible, consider rephrasing relative to the causeRepeating causes in multiple categories may be a good sign

of a root causeFacilitator works to ensure consensus of assignment

15 MINUTES

Step 5: Analyse CausesLook for repeating items, patternsIn Process Classification, repeating is rare

Look for items that create bottlenecksAsk “Why?” 2-5 timesEnsure it is cause and effect or it is a new causeFacilitator – manage process to ensure you go far enough

and not too far; build consensus on patterns, root causes

15 MINUTES

Step 6: Next StepsRecommendations DocumentProcess Improvement SuggestionRequest for Decision

Other IssuesWhen do you use a tool?Choosing C&E Format

Dispersion Analysis? 4Ms 4Ps Team Generated

Process Classification Process Driven Team Generated

A Word on GOAL/QPCMemory Jogger

BooksFlash DrivesTraining

www.goalqpc.com orwww.memoryjogger.org

Wrap-upProblem SolvingLogic

Math – the Language of LogicAlgorithms & Programmatic Problem-SolvingTools & Techniques

IPOFlowchartsPseudocodeFishbone/ C&E Diagram

Final Exam20 M/C Questions = 40%

Hint: focus on Class Notes/ slides on site1 Application = 60%

Either 1 programming problem

Flowchart, pseudocode and Ruby procedures Approach is worth more than code

Or, Business Case Complete Fishbone with brainstorm, classification, and analysis Approach is worth more than quality of analysis

Good luck!