Welcome to  Whole-brain problem-solving Alan Barker Kairos Training Limited
Problems cannot be solved by thinking within the framework in which the problems were created. Albert Einstein
Whole-brain problem-solving This presentation summarizes the first part of a training course.  Further modules in the course are indicated at the end of this presentation.
What is a problem? Answer this question on flipchart paper, in as many ways as possible – without using words
You know you’ve got a problem when: you want to do something, but you don’t know what to do
Problem-solving: two approaches Traditional Problem: something is not   as it should be Solution: a ‘fix’ that stays   fixed  Whole-brain Problem: we are stuck Solution: moving;    becoming ‘ unstuck’; a course of action
Problem-solving: two approaches Traditional What’s the problem? What’s the cause? Why? (five times) What’s in the way? How do we put it right? What can we measure? How do we break the problem into manageable parts? Whole-brain What do I want to achieve? What if…? What if the problem were a solution? Why not? What else could we do? What rules can we break? What is the problem like?
Who owns the problem? Problems without owners tend to become unmade decisions. Somebody has to be responsible for tackling the problem.  The problem owner: defines the problem at the outset; decides how to think about it; chooses the course of action to tackle it; and commits to dealing with it.
Is it your problem? Everybody’s responsibility has boundaries. It’s counter-productive to try taking responsibility for problems that we have no authority to manage.
Where is the problem? Circle of Influence
Two stages of thinking reality 1 Perception sensation; intuition Representation:  language, models, images 2  Judgement reason evaluation Action
Two stages of thinking We do first-stage thinking to work out  what we are thinking about . We do second-stage thinking to work out  what to do about it .
Two stages of thinking Perception determines what we know. Judgement determines what we know about what we know.
First-stage thinking First-stage thinking uses perception: the five senses, and intuition (our sixth sense, or perception using the unconscious).
Representation The output of first-stage thinking is language. =  dog
Second-stage thinking Second-stage thinking uses judgement: reason and evaluation. Second-stage thinking manipulates language to reach its conclusions. The dog is healthy.  The dog is alert. The dog is looking at its owner. (etc.)
Two stages of thinking We tend to be better at second-stage thinking than first-stage thinking. We can even build machines to do it. Computers are second-stage thinking devices.
Two stages of thinking We tend to be much less good at first-stage thinking. We have very few technologies to help us do it. (Can you think of any?)
Two stages of thinking In fact, we may not regard first-stage thinking as thinking at all.
Two stages of thinking But the quality of our second-stage thinking  depends  on the quality of our first-stage thinking. No amount of excellent second-stage thinking will make up for poor first-stage thinking.
Leaping to judgement:  the dangers of ignoring first-stage thinking Product development Engineering the product rather than seeking to satisfy the customer’s needs Contractual negotiations Addressing perceived ‘issues’ rather than questioning assumptions about what the issues are Corporate strategy Re-engineering structures rather than asking ‘What business are we in?’
To improve your problem-solving skills: Improve your first-stage thinking
First-stage thinking: two questions How is the problem  structured ? Is the problem  presented  to us  or   constructed  by us?
Structuring a problem Initial conditions  [Where am I?] Goal conditions  [Where do I want to be?] Operators  [How do I get from where  I am to where I want to be?] Constraints  [What limits my action?]
Structuring a problem Assess: initial conditions;  goal conditions;  operators;  constraints. If all four are clear,  the problem is well structured.  [WSP] If any or all are unclear,  the problem is ill-structured.  [ISP]
Two types of problem presented constructed
Presented problems Express as a statement of what is wrong Happen to us Not our fault but we are responsible for solving them Obstacle in our path Perceived gap: what is/what should be Cause stress Solution: fight or flight
Presented problems: examples The photocopier breaking down A new product invading our market Being stuck in a traffic jam Delays in a production process
Constructed problems Express as a phrase beginning ‘how to…’ Made by us We are responsible for creating them The reason for taking the journey Perceived gap: what is/what could be Cause creative tension Solution: dispel tension by releasing energy
Constructed problems: examples Gaining a qualification Improving quality Innovating a new product or service Increasing market share
Four types of problem presented constructed Well structured (WSP) Ill structured (ISP) 4 dream 2 headache 3 plan 1 puzzle
1 Puzzles (presented; WSP) A deviation from the norm.  One right answer.
1 Puzzles (presented; WSP) Archetypal examples are technical: a fault in a machine, an interruption in the power supply, a piece of equipment that won’t work properly. The classic problem-solving process – diagnose the cause of the problem, remove the cause, solve the problem – will work only for this type of problem.
1 Puzzles (presented; WSP): techniques Ishikawa Analysis Asking ‘Why?’ (five times) Tree diagrams (why/why) Apollo Root-cause Analysis Control charts
Ishikawa Analysis   Use for Type 1 problems (puzzles). Many forms To complete Forms not  Complete Inability to access  supplier website Supplier loses  the file Supplier has varying processing times  depending on circumstances Friendly supplier on leave Executive u nderpromises the delivery date Executive not realistic in estimating time Not in office in training Procedures People Equipment Approving Authority Inability to estimate accurately processing  time Missing Data New  change in  policy Hard to establish  strong working relationship with supplier
Apollo Root Cause Analysis Use for Type 1 problems (puzzles). Primary effect Action cause Conditional cause evidence evidence http://www.apollorca.com/
2 Headaches (presented; ISP) A deviation from the norm.  No single or obvious right answer.  The problem may have no identifiable cause, or have many causes.
2 Headaches (presented; ISP) Much traditional problem-solving spends a lot of time and effort trying to turn Type 2 problems into Type 1 problems.  Unfortunately, Type 2 problems often have a habit of reverting to type.
2 Headaches (presented; ISP): techniques Live with it: suppress the pain Use a sticking plaster (hide the problem) Transform the problem into another type of problem (move the problem into another quadrant)  Walk away
Aspirin Use for Type 2 problems (headaches). Use sparingly.
3 Planning problems (constructed; WSP) A challenge to be achieved. One clear goal.
3 Planning problems (constructed; WSP) Mapped out in terms of  objectives, targets, milestones  and  measures of success .  Examples include working out objectives after an appraisal, setting a budget, giving the team a sales or quality target, or organizing a project.
3 Planning problems (constructed; WSP): techniques Action plans Gantt charts Force Field Analysis Solution Effect Analysis Tree diagrams (how/how)
Gantt chart Use for Type 3 problems (plans).
Force Field Analysis Use for Type 3 problems (plans). With thanks to Fred Nickols,  whose work on problem solving  is inspirational. His discussion of Force Field Analysis is at: http://home.att.net/~nickols/changing.htm
4 Dreams (constructed; ISP) Objective: to find something new: a product or service, a new process, a new territory, a new set of goals. No obvious answer.
4 Dreams (constructed; ISP) Demands creative or lateral thinking. Cannot be tackled operationally. Examples: creating new products or sources of customer satisfaction.
4 Dreams (constructed; ISP): techniques Brainstorming ‘ How to’ Metaphorical analysis Reversal Synectics
Oracle Use for Type 4 problems (dreams).
Using the problem grid Take a problem that you currently face at work. Where would you currently place the problem in the grid? (Type 1, 2, 3 or 4)? Why? Where would you  like  the problem to be in the grid? Why? How could you transform the way you look at the problem to put it in that quadrant? What can you do  right now ?
To continue the journey: Look at these presentations at http://www.slideshare.net/alanbarker Operational thinking and innovative thinking How to Thinking creatively
Kairos Training Limited www.kairostraining.co.uk

001 Wholebrain Problem Solving Slides

  • 1.
    Welcome to Whole-brain problem-solving Alan Barker Kairos Training Limited
  • 2.
    Problems cannot besolved by thinking within the framework in which the problems were created. Albert Einstein
  • 3.
    Whole-brain problem-solving Thispresentation summarizes the first part of a training course. Further modules in the course are indicated at the end of this presentation.
  • 4.
    What is aproblem? Answer this question on flipchart paper, in as many ways as possible – without using words
  • 5.
    You know you’vegot a problem when: you want to do something, but you don’t know what to do
  • 6.
    Problem-solving: two approachesTraditional Problem: something is not as it should be Solution: a ‘fix’ that stays fixed Whole-brain Problem: we are stuck Solution: moving; becoming ‘ unstuck’; a course of action
  • 7.
    Problem-solving: two approachesTraditional What’s the problem? What’s the cause? Why? (five times) What’s in the way? How do we put it right? What can we measure? How do we break the problem into manageable parts? Whole-brain What do I want to achieve? What if…? What if the problem were a solution? Why not? What else could we do? What rules can we break? What is the problem like?
  • 8.
    Who owns theproblem? Problems without owners tend to become unmade decisions. Somebody has to be responsible for tackling the problem. The problem owner: defines the problem at the outset; decides how to think about it; chooses the course of action to tackle it; and commits to dealing with it.
  • 9.
    Is it yourproblem? Everybody’s responsibility has boundaries. It’s counter-productive to try taking responsibility for problems that we have no authority to manage.
  • 10.
    Where is theproblem? Circle of Influence
  • 11.
    Two stages ofthinking reality 1 Perception sensation; intuition Representation: language, models, images 2 Judgement reason evaluation Action
  • 12.
    Two stages ofthinking We do first-stage thinking to work out what we are thinking about . We do second-stage thinking to work out what to do about it .
  • 13.
    Two stages ofthinking Perception determines what we know. Judgement determines what we know about what we know.
  • 14.
    First-stage thinking First-stagethinking uses perception: the five senses, and intuition (our sixth sense, or perception using the unconscious).
  • 15.
    Representation The outputof first-stage thinking is language. = dog
  • 16.
    Second-stage thinking Second-stagethinking uses judgement: reason and evaluation. Second-stage thinking manipulates language to reach its conclusions. The dog is healthy. The dog is alert. The dog is looking at its owner. (etc.)
  • 17.
    Two stages ofthinking We tend to be better at second-stage thinking than first-stage thinking. We can even build machines to do it. Computers are second-stage thinking devices.
  • 18.
    Two stages ofthinking We tend to be much less good at first-stage thinking. We have very few technologies to help us do it. (Can you think of any?)
  • 19.
    Two stages ofthinking In fact, we may not regard first-stage thinking as thinking at all.
  • 20.
    Two stages ofthinking But the quality of our second-stage thinking depends on the quality of our first-stage thinking. No amount of excellent second-stage thinking will make up for poor first-stage thinking.
  • 21.
    Leaping to judgement: the dangers of ignoring first-stage thinking Product development Engineering the product rather than seeking to satisfy the customer’s needs Contractual negotiations Addressing perceived ‘issues’ rather than questioning assumptions about what the issues are Corporate strategy Re-engineering structures rather than asking ‘What business are we in?’
  • 22.
    To improve yourproblem-solving skills: Improve your first-stage thinking
  • 23.
    First-stage thinking: twoquestions How is the problem structured ? Is the problem presented to us or constructed by us?
  • 24.
    Structuring a problemInitial conditions [Where am I?] Goal conditions [Where do I want to be?] Operators [How do I get from where I am to where I want to be?] Constraints [What limits my action?]
  • 25.
    Structuring a problemAssess: initial conditions; goal conditions; operators; constraints. If all four are clear, the problem is well structured. [WSP] If any or all are unclear, the problem is ill-structured. [ISP]
  • 26.
    Two types ofproblem presented constructed
  • 27.
    Presented problems Expressas a statement of what is wrong Happen to us Not our fault but we are responsible for solving them Obstacle in our path Perceived gap: what is/what should be Cause stress Solution: fight or flight
  • 28.
    Presented problems: examplesThe photocopier breaking down A new product invading our market Being stuck in a traffic jam Delays in a production process
  • 29.
    Constructed problems Expressas a phrase beginning ‘how to…’ Made by us We are responsible for creating them The reason for taking the journey Perceived gap: what is/what could be Cause creative tension Solution: dispel tension by releasing energy
  • 30.
    Constructed problems: examplesGaining a qualification Improving quality Innovating a new product or service Increasing market share
  • 31.
    Four types ofproblem presented constructed Well structured (WSP) Ill structured (ISP) 4 dream 2 headache 3 plan 1 puzzle
  • 32.
    1 Puzzles (presented;WSP) A deviation from the norm. One right answer.
  • 33.
    1 Puzzles (presented;WSP) Archetypal examples are technical: a fault in a machine, an interruption in the power supply, a piece of equipment that won’t work properly. The classic problem-solving process – diagnose the cause of the problem, remove the cause, solve the problem – will work only for this type of problem.
  • 34.
    1 Puzzles (presented;WSP): techniques Ishikawa Analysis Asking ‘Why?’ (five times) Tree diagrams (why/why) Apollo Root-cause Analysis Control charts
  • 35.
    Ishikawa Analysis Use for Type 1 problems (puzzles). Many forms To complete Forms not Complete Inability to access supplier website Supplier loses the file Supplier has varying processing times depending on circumstances Friendly supplier on leave Executive u nderpromises the delivery date Executive not realistic in estimating time Not in office in training Procedures People Equipment Approving Authority Inability to estimate accurately processing time Missing Data New change in policy Hard to establish strong working relationship with supplier
  • 36.
    Apollo Root CauseAnalysis Use for Type 1 problems (puzzles). Primary effect Action cause Conditional cause evidence evidence http://www.apollorca.com/
  • 37.
    2 Headaches (presented;ISP) A deviation from the norm. No single or obvious right answer. The problem may have no identifiable cause, or have many causes.
  • 38.
    2 Headaches (presented;ISP) Much traditional problem-solving spends a lot of time and effort trying to turn Type 2 problems into Type 1 problems. Unfortunately, Type 2 problems often have a habit of reverting to type.
  • 39.
    2 Headaches (presented;ISP): techniques Live with it: suppress the pain Use a sticking plaster (hide the problem) Transform the problem into another type of problem (move the problem into another quadrant) Walk away
  • 40.
    Aspirin Use forType 2 problems (headaches). Use sparingly.
  • 41.
    3 Planning problems(constructed; WSP) A challenge to be achieved. One clear goal.
  • 42.
    3 Planning problems(constructed; WSP) Mapped out in terms of objectives, targets, milestones and measures of success . Examples include working out objectives after an appraisal, setting a budget, giving the team a sales or quality target, or organizing a project.
  • 43.
    3 Planning problems(constructed; WSP): techniques Action plans Gantt charts Force Field Analysis Solution Effect Analysis Tree diagrams (how/how)
  • 44.
    Gantt chart Usefor Type 3 problems (plans).
  • 45.
    Force Field AnalysisUse for Type 3 problems (plans). With thanks to Fred Nickols, whose work on problem solving is inspirational. His discussion of Force Field Analysis is at: http://home.att.net/~nickols/changing.htm
  • 46.
    4 Dreams (constructed;ISP) Objective: to find something new: a product or service, a new process, a new territory, a new set of goals. No obvious answer.
  • 47.
    4 Dreams (constructed;ISP) Demands creative or lateral thinking. Cannot be tackled operationally. Examples: creating new products or sources of customer satisfaction.
  • 48.
    4 Dreams (constructed;ISP): techniques Brainstorming ‘ How to’ Metaphorical analysis Reversal Synectics
  • 49.
    Oracle Use forType 4 problems (dreams).
  • 50.
    Using the problemgrid Take a problem that you currently face at work. Where would you currently place the problem in the grid? (Type 1, 2, 3 or 4)? Why? Where would you like the problem to be in the grid? Why? How could you transform the way you look at the problem to put it in that quadrant? What can you do right now ?
  • 51.
    To continue thejourney: Look at these presentations at http://www.slideshare.net/alanbarker Operational thinking and innovative thinking How to Thinking creatively
  • 52.
    Kairos Training Limitedwww.kairostraining.co.uk