welcome to how to solve (almost) any problem

72
Welcome to How to solve (almost) any problem Alan Barker Kairos Training Limited 23 May 2013

Upload: zazu

Post on 23-Mar-2016

59 views

Category:

Documents


0 download

DESCRIPTION

Welcome to How to solve (almost) any problem. Alan Barker Kairos Training Limited. 23 May 2013. Problems cannot be solved by thinking within the framework in which the problems were created. Albert Einstein. What is a problem?. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Welcome to  How to solve  (almost) any problem

Welcome to How to solve

(almost)any problem

Alan Barker

Kairos Training Limited

23 May 2013

Page 2: Welcome to  How to solve  (almost) any problem

Problems cannot be solved by thinking within the framework in which the problems were created.

Albert Einstein

Page 3: Welcome to  How to solve  (almost) any problem

What is a problem?

Answer this question on flipchart paper, in as many ways as possible – without using words

Page 4: Welcome to  How to solve  (almost) any problem

You know you’ve got a problem when:

you want to do something, but you don’t know what to

do

Page 5: Welcome to  How to solve  (almost) any problem

Stuck. No answer. Honked. Kaput.

This is the zero moment of consciousness.

It’s a miserable experienceemotionally. You’re losing time.You’re incompetent. You don’t knowwhat you’re doing.

You should be ashamed of yourself.

Page 6: Welcome to  How to solve  (almost) any problem
Page 7: Welcome to  How to solve  (almost) any problem

Why don’t we get stuck every second?

Page 8: Welcome to  How to solve  (almost) any problem

Mental models organize our reality.

Without them, no world would exist for us.

[Joe Griffin and Ivan Tyrell]

Page 9: Welcome to  How to solve  (almost) any problem

Human beings are not so much problem-solvers as solution-seekers.

Page 10: Welcome to  How to solve  (almost) any problem

Human beings are not so much problem-solvers as solution-seekers.

Page 11: Welcome to  How to solve  (almost) any problem

Intuitive problem-solving

Understanding the problem and solving it are the same thing.

The match of information to mental model is the solution.

Page 12: Welcome to  How to solve  (almost) any problem

Sometimes, our mental

models won’t work.(Can you

see what it is?)

Page 13: Welcome to  How to solve  (almost) any problem

And when that

happens, we get stuck.

Page 14: Welcome to  How to solve  (almost) any problem

Stuckness affects our

limbic system

(where we respond

emotionally to external stimuli...)

Page 15: Welcome to  How to solve  (almost) any problem

The result can be the

fight-or-flight response...

Page 16: Welcome to  How to solve  (almost) any problem

... which can cause all sorts of stress – and

lead to a longer-term

stress response.

Bad news.

Page 17: Welcome to  How to solve  (almost) any problem

Part of problem

solving, then, has to be emotional

intelligence.

Page 18: Welcome to  How to solve  (almost) any problem

Solutions unstick our thinking....

Page 19: Welcome to  How to solve  (almost) any problem

problem solution

Stuckness opens a gap

in our problem-solving

response...

Page 20: Welcome to  How to solve  (almost) any problem

... into which

rational problem-

solving can enter.

Page 21: Welcome to  How to solve  (almost) any problem
Page 22: Welcome to  How to solve  (almost) any problem

Problem-solving: two approaches

Rational

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

Page 23: Welcome to  How to solve  (almost) any problem

Problem-solving: two approaches

RationalWhat’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?

Page 24: Welcome to  How to solve  (almost) any problem

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.

Page 25: Welcome to  How to solve  (almost) any problem

Where is the problem?

Circleof

Influence Some problems are in our Circle of

Influence, and some in our Circle of

Concern.

Page 26: Welcome to  How to solve  (almost) any problem

Circle of concern

Circle of influence

Steven Covey says that we

should aim to deal with problems that are in our Circle of Influence, and put aside problems in

our Circle of Concern.

Page 27: Welcome to  How to solve  (almost) any problem

Circle of influence

Stephen Covey

Circle of influence

Effective problem solvers strive

continually to increase their Circle

of Influence.

Page 28: Welcome to  How to solve  (almost) any problem

blame

Four levels of ownership

Page 29: Welcome to  How to solve  (almost) any problem

resistance

Four levels of ownership

Page 30: Welcome to  How to solve  (almost) any problem

responsibility

Four levels of ownership

Page 31: Welcome to  How to solve  (almost) any problem

commitment

Four levels of ownership

Page 32: Welcome to  How to solve  (almost) any problem

Two stages of thinking

reality

1:Perceptionsensation; intuition

Representation: language, models, images

2: Judgementreason

evaluation

Action

Page 33: Welcome to  How to solve  (almost) any problem

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.

Page 34: Welcome to  How to solve  (almost) any problem

Two stages of thinking

Perception determines what we know.

Judgement determines what we know about what we know.

Page 35: Welcome to  How to solve  (almost) any problem

First-stage thinking

First-stage thinking uses perception: the five senses, and intuition (our sixth sense, or perception using the unconscious).

Page 36: Welcome to  How to solve  (almost) any problem

RepresentationThe output of first-stage thinking

is language.

= dog

Page 37: Welcome to  How to solve  (almost) any problem

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.)

Page 38: Welcome to  How to solve  (almost) any problem

We have all sorts of

technology to help us

do second-stage

thinking...

Page 39: Welcome to  How to solve  (almost) any problem

...but not so many to do first-stage thinking.

(Mind maps are good stage-one thinking

tools.)

Page 40: Welcome to  How to solve  (almost) any problem

Leaping to judgement: the dangers of ignoring first-

stage thinkingProduct developmentEngineering the product rather than seeking to satisfy

the customer’s needsContractual negotiationsAddressing perceived ‘issues’ rather than questioning

assumptions about what the issues areCorporate strategyRe-engineering structures rather than asking ‘What

business are we in?’

Page 41: Welcome to  How to solve  (almost) any problem

To improve your problem-solving skills:Improve your first-stage thinking

Page 42: Welcome to  How to solve  (almost) any problem

First-stage thinking:two questions

1. How is the problem structured?

2. Is the problem presented to us

or

constructed by us?

Page 43: Welcome to  How to solve  (almost) any problem

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?]

Page 44: Welcome to  How to solve  (almost) any problem

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]

Page 45: Welcome to  How to solve  (almost) any problem

Two types of problem

presented

constructed

Page 46: Welcome to  How to solve  (almost) any problem

Presented problemsExpress 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

Page 47: Welcome to  How to solve  (almost) any problem

Presented problems: examples

The photocopier breaking down

A new product invading our market

Being stuck in a traffic jam

Delays in a production process

Page 48: Welcome to  How to solve  (almost) any problem

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

Page 49: Welcome to  How to solve  (almost) any problem

Constructed problems: examples

Gaining a qualification

Improving quality

Innovating a new product or service

Increasing market share

Page 50: Welcome to  How to solve  (almost) any problem

planpuzzle

headache dream

Page 51: Welcome to  How to solve  (almost) any problem

1Puzzles (presented;

WSP)

• A deviation from the norm. • One right answer.

Page 52: Welcome to  How to solve  (almost) any problem

1Puzzles (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.

Page 53: Welcome to  How to solve  (almost) any problem

1Puzzles (presented; WSP): techniques

• Ishikawa Analysis• Asking ‘Why?’ (five times)• Tree diagrams (why/why)• Apollo Root-cause Analysis• Control charts

Page 54: Welcome to  How to solve  (almost) any problem

Ishikawa Analysis Use for Type 1 problems (puzzles).

Many formsTo 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

Executiveunderpromises the delivery date

Executive not realisticin estimating time

Not in officein training

Procedures People

EquipmentApproving Authority

Inability to estimateaccurately processing

time

MissingData

New change in policy Hard to establish

strong working relationshipwith supplier

Page 55: Welcome to  How to solve  (almost) any problem

Root Cause AnalysisUse for Type 1 problems (puzzles).

Primary effect

Action cause

Conditional cause

evidence

evidence

Page 56: Welcome to  How to solve  (almost) any problem

Solving puzzles strengthens the urge to find the

correct answer...

...which is sometimes unhelpful...

...because not every problem has a single

correct answer.

(Which shape is the odd one

out?)

Page 57: Welcome to  How to solve  (almost) any problem

2Headaches (presented;

ISP)

• A deviation from the norm.

• No single or obvious right answer. The problem may have no identifiable cause, or have many causes.

Page 58: Welcome to  How to solve  (almost) any problem

2Headaches (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.

Page 59: Welcome to  How to solve  (almost) any problem

2Headaches (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

Page 60: Welcome to  How to solve  (almost) any problem

Aspirin

Use for Type 2 problems (headaches).Use sparingly.

Page 61: Welcome to  How to solve  (almost) any problem

3Planning problems (constructed; WSP)

• A challenge to be achieved.

• One clear goal.

Page 62: Welcome to  How to solve  (almost) any problem

3Planning 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.

Page 63: Welcome to  How to solve  (almost) any problem

3Planning problems

(constructed; WSP):techniques

• Action plans• Gantt charts• Force Field Analysis• Solution Effect Analysis• Tree diagrams (how/how)

Page 64: Welcome to  How to solve  (almost) any problem

Gantt chartUse for Type 3 problems (plans).

Page 65: Welcome to  How to solve  (almost) any problem

Force Field AnalysisUse for Type 3 problems (plans).

Page 66: Welcome to  How to solve  (almost) any problem

4Dreams (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.

Page 67: Welcome to  How to solve  (almost) any problem

4Dreams (constructed;

ISP)• Demands creative or lateral

thinking.

• Cannot be tackled operationally.

• Examples: creating new products or sources of customer satisfaction.

Page 68: Welcome to  How to solve  (almost) any problem

4Dreams (constructed;

ISP): techniques

• Brainstorming• ‘How to’• Metaphorical analysis• Reversal• Synectics

Page 69: Welcome to  How to solve  (almost) any problem

OracleUse for Type 4 problems (dreams).

Page 70: Welcome to  How to solve  (almost) any problem

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?

Page 72: Welcome to  How to solve  (almost) any problem

Kairos Training Limited

www.kairostraining.co.uk