20121216 1327 conflictresolutiondiagramtutorial-published-100912040222-phpapp02

74
Resolving Conflicts without Compromise also known as “I want to have my cake and eat it!” Pascal Van Cauwenberghe & Portia Tung

description

Resolving Conflicts without Compromise also known as “I want to have my cake and eat it!” by Pascal Van Cauwenberghe & Portia Tung

Transcript of 20121216 1327 conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Page 1: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Resolving Conflicts without Compromisealso known as

“I want to have my cake and eat it!”

Pascal Van Cauwenberghe & Portia Tung

Page 2: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

About us

Her Blog: www.selfishprogramming.org His Blog: blog.nayima.be

NAYIMA

We make play work

Consultant.Storyteller.Games Maker. Consultant.

Project Manager. Games Maker.

Page 3: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

About this session

1. What do we mean by “Conflict” ?2. Name a conflict you’d like to resolve3. A conflict we prepared earlier4. Patterns of Conflict5. Ideas for resolving your conflict6. Further reading7. Session feedback

Page 4: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

1/7WHAT DO WE MEAN BY CONFLICT?

Page 5: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

“I want to live in the city...” “... AND in the country”

Page 6: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

“I want to eat what I want...” “... AND be fit and healthy”

Page 7: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Manager: “We need to go faster to deliver more features”

Developers: “We need to go slower to increase quality.”

Page 8: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

What do we need to resolve conflicts?

1. Willingness to find a solution– Refuse to compromise – Common goal

2. Articulate the conflict3. Explore solutions– Surface assumptions– Challenge assumptions– A dash of creativity

Page 9: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

The Shallow Thinking Process

Root Cause Analysis

Why don’t we have what we need?

A problem

Magic Happens

Here

THE SolutionThis is what we needed all along!

Happy Days

Page 10: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

The Logical Thinking Process

Page 11: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

The Logical Thinking Process

Intermediate Objectives

Map

Current Reality Tree

Conflict Resolution

Diagram

Future Reality Tree

Prerequisite/Transition

TreeWhat is our goal?What are we missing?

Why don’t we have what we need?

What could be done to resolve the underlying fundamental conflict?

Would that work?What could possibly go wrong?

How do we get there?In small steps.

Magic Happens

Here

That’s what this session is

about

Page 12: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

The Conflict Resolution Diagram

Objective

Prerequisite 1Requirement 1

Prerequisite 2Requirement 2

Page 13: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

3 Types of Conflict

Page 14: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

“I want to live in the city...” “... AND I want to live in the country”

Type 1:“I want X and the opposite of X”

That’s not possible, is it?

Page 15: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

“I want to eat what I want...” “... AND be fit and healthy”

Type 2:“I want X and Y”

But I have to choose, right?

Page 16: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Manager: “We need to go faster to deliver more features”

Developers: “We need to go slower to increase quality.”

Type 3:“I want X. They want Y. We can’t both be right”

Only one of us can win, at best.

Page 17: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

2/7 NAME A CONFLICT YOU’D LIKE TO RESOLVE

Page 18: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Three types of Conflict

1. I want X and the opposite of XThat’s not possible, is it?

2. I want X and Y but I can’t have bothI have to choose, don’t I?

3. I want X. They want Y.Only one of us can win, at best.

Page 19: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

3/7 HERE’S ONE WE PREPARED EARLIER

Page 20: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Define products

Sales

Operations

Billing

Invoicing

Story #1

• Consultants audited business unit => FAIL• We have to build a system to support the

whole value stream

• Conflicts between sales and operations• And between finance/audit and the rest– More than a month of “shuttle diplomacy”

Page 21: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

• One of the conflicts is about product definition• Lots of confusion about what products mean– Ask 5 people, you get 6 different answers

• 2 previous attempts failed• We have a hard deadline because of new EU

regulations

Story #1

Page 22: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Step 1: Articulate the conflict

Objective

Prerequisite 1Requirement 1

Prerequisite 2Requirement 2

Page 23: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Step 1: Articulate the conflict

Sales:Customised Products

Operations:StandardisedProducts

Page 24: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Step 2: Find the common objective

Objective

Prerequisite 1Requirement 1

Prerequisite 2Requirement 2

Page 25: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Tip: Don’t continue until you agree on a common, concrete and motivating goal

If there’s no common goal, there’s no incentive to solve the conflict

Page 26: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Step 2: Find the common objective

Sell more

Be more efficient

Customised Products

StandardisedProducts

SurvivingBusiness

Page 27: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Tip: Strive for clarity first,then for correctness

Precise and crisp definitions to ensure everyone has the same

understanding

Page 28: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Step 2: Find the common objective

Increase salesIncrease margin

Reduce costsDeliver on SLA

Customised Products

StandardisedProducts

Profitability in ashrinking market

Page 29: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Step 3: Review clarity and logic

Increase salesIncrease margin

Reduce costsDeliver on SLA

Customised Products

StandardisedProducts

Profitability in ashrinking market

Page 30: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Step 3: Find the assumptions

Objective

Prerequisite 1Requirement 1

Prerequisite 2Requirement 2

1

2

3

5

4

Page 31: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Tip: Brainstorm assumptions

Go for quantityInclude “obvious” assumptions

Page 32: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Tip: Use “Extreme Assumptions”aka “Throw a tantrum”

X is the ONLY way to have YX is the BEST way to have Y

X guarantees Y

Page 33: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Step 3a: Find the assumptions

1

Increase salesIncrease margin

Reduce costsDeliver on SLA

Customised Products

StandardisedProducts

Profitability in ashrinking market

Page 34: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

3a. Our assumptions

• We can’t have both customised and standardised products because– Product == Product– Standardised != Customised– As soon as sales starts to customise we end up

with an infinite number of products (again)– Sales doesn’t understand delivery– Operations doesn’t understand business

Page 35: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Step 3: Find the assumptions2

Increase salesIncrease margin

Reduce costsDeliver on SLA

Customised Products

StandardisedProducts

Profitability in ashrinking market

Page 36: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

3b. Our assumptions

• To increase sales and margin we need to customise products because– We can only compete by having an offer that’s

different from our competitors– Customers are becoming more demanding– We must react quickly to customer demands– We can never compete on price

Page 37: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Step 3: Find the assumptions

3

Increase salesIncrease margin

Reduce costsDeliver on SLA

Customised Products

StandardisedProducts

Profitability in ashrinking market

Page 38: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

3c. Our assumptions

• To reduce costs and deliver on SLA we need to standardise products because– Having low variation is the only way to have

predictable production schedules– Standardised products are the only way to flexibly

allocate people according to demand– Product variation always costs more (changeover,

setups, switches, training, bottlenecks)– Lean only works with low variation production

Page 39: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Step 3: Find the assumptions

4 Increase salesIncrease margin

Reduce costsDeliver on SLA

Customised Products

StandardisedProducts

Profitability in ashrinking market

Page 40: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

3d. Our assumptions

• To be profitable in a shrinking market we need to increase sales and margin because– We can’t expand the market– The only way to increase profitability is to sell

more or increase the margin on each sale

Page 41: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Step 3: Find the assumptions

5

Increase salesIncrease margin

Reduce costsDeliver on SLA

Customised Products

StandardisedProducts

Profitability in ashrinking market

Page 42: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

3e. Our assumptions

• To be profitable in a shrinking market we need to reduce costs and deliver on SLA because– We are penalised for not hitting SLAs– Our competitors have lower costs– This is a price sensitive market, so the only way to

increase profitability is to reduce costs– This is a quality-sensitive market, so the only way to

increase or keep market share is to increase quality– Quality is hitting the SLA

Page 43: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Step 4: Challenge the assumptions

Objective

Prerequisite 1Requirement 1

Prerequisite 2Requirement 2

1

2

3

5

4

Page 44: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Step 4: Challenge the assumptions

1

2

3

5

4 Increase salesIncrease margin

Reduce costsDeliver on SLA

Customised Products

StandardisedProducts

Profitability in ashrinking market

Page 45: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

4a. Challenge our assumptions

• We can’t have both customised and standardised products because– Product == Product– Standardised != customised– As soon as sales starts to customise we end up

with an infinite number of products (again)– Sales doesn’t understand delivery– Operations doesn’t understand business

Page 46: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

4b. Challenge our assumptions

• To increase sales and margin we need to customise products because– We can only compete by having an offer that’s

different from our competitors– We must react quickly to market demands– We can never compete on price

Page 47: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

4c. Challenge our assumptions

• To reduce costs and deliver on SLA we need to standardise products because– Having low variation is the only way to have

predictable production schedules– Standardised products are the only way to flexibly

allocate people according to demand– Product variation always costs more (changeover,

setups, switches, training, bottlenecks)– Lean only works with low variation production

Page 48: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

4d. Challenge our assumptions

• To be profitable in a shrinking market we need to increase sales and margin because– We can’t expand the market– The only way to increase profitability is to sell

more or increase the margin on each sale

Page 49: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

4e. Challenge our assumptions

• To be profitable in a shrinking market we need to reduce costs and deliver on SLA because– We are penalised for not hitting SLAs– Our competitors have lower costs– This is a price sensitive market, so the only way to

increase profitability is to reduce costs– This is a quality-sensitive market, so the only way to

increase or keep market share is to increase quality– Quality is hitting the SLA

Page 50: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

The assumption we challenged

Product == Product

Increase salesIncrease margin

Reduce costsDeliver on SLA

Customised Products

StandardisedProducts

Profitability in ashrinking market

Page 51: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

What if....

Sales and Operations were talking about different products?

That would explain the confusion

Page 52: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

The resolved conflict

Customise Sales

Product

StandardiseOperational

Product

Sales Product != Operational Product

Increase salesIncrease margin

Reduce costsDeliver on SLA

Profitability in ashrinking market

Page 53: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

There was another conflict

Operations:Coarse Products

Finance & audit:DetailedProducts

Low input andtrackingoverhead

Detailed auditingCost analysis

Lower costsReduce cycletime

How would you solve this conflict?

Page 54: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

The Solution

Finance & Audit“Products”

Operations“Products”

Sales & Marketing“Products”

Page 55: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

The Result

• Built and deployed the system– Took two years, including refactoring of product

catalog• Business unit has been profitable since• Market share grows• Among top 5 in the world meeting industry

SLAs• Continuously improving

Page 56: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

4/7 PATTERNS OF CONFLICT

Page 57: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Three types of Conflict

1. I need X and the opposite of XThat’s not possible, is it?

2. I need X and Y but I can’t have bothI have to choose, don’t I?

3. I want X. They want Y. We can’t both be rightOnly one of us can win, at best.

Page 58: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Using the Conflict Resolution Diagram

• You can’t solve your own conflict– Ask for help

• The biggest obstacle is willingness to find a solution without compromise– Need to believe that a solution exists– Use examples to show that solving the problem is possible

• First look for clarity, then for correctness– A clear problem statement often leads to “evaporation” of the

problem• The CRD is a collaborative tool

– Don’t use it to “prove” the other party is wrong– Sometimes you have to provide “shuttle diplomacy”

Page 59: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Typical conflict patterns

• The false conflict– We’re talking about different things

• Assuming we have no options– We always have options

• Today against tomorrow– We can repay debt in small steps

• Not enough resources– There are ways to do more with the same resources

• Conflating means and ends– There’s another way to achieve the goal

Page 60: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

5/7 DID YOU GET ANY IDEAS TO LOOK AT YOUR CONFLICTS DIFFERENTLY?

Page 61: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

6/7 FURTHER READING

Page 62: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Recommended Resources

• Summary from www.agilecoach.net• “The Logical Thinking Process” – H.W. Dettmer• “It’s not Luck” – E. Goldratt• “Thinking in Systems” – D. Meadows

Page 63: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Summary

Page 64: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

About this session

1. What do we mean by “Conflict” ?2. Name a conflict you’d like to resolve3. A conflict we prepared earlier4. Patterns of Conflict5. Ideas for resolving your conflict6. Further reading7. Session feedback

Page 65: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Three types of Conflict

1. I need X and the opposite of XThat’s not possible, is it?

2. I need X and Y but I can’t have bothI have to choose, don’t I?

3. I want X. They want Y. We can’t both be rightOnly one of us can win, at best.

Page 66: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

What do we need to resolve conflicts?

1. Willingness to find a solution– Refuse to compromise – Common goal

2. Articulate the conflict3. Explore solutions– Surface assumptions– Challenge assumptions– A dash of creativity

Page 67: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

The Shallow Thinking Process

Root Cause Analysis

Why don’t we have what we need?

A problem

Magic Happens

Here

THE SolutionThis is what we needed all along!

Happy Days

Page 68: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

The Logical Thinking Process

Intermediate Objectives

Map

Current Reality Tree

Conflict Resolution

Diagram

Future Reality Tree

Prerequisite/Transition

TreeWhat is our goal?What are we missing?

Why don’t we have what we need?

What could be done to resolve the underlying fundamental conflict?

Would that work?What could possibly go wrong?

How do we get there?In small steps.

Magic Happens

Here

Page 69: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

The Conflict Resolution Diagram

1. Articulate the conflict2. Find the common objective3. Review clarity and logic4. Find the assumptions5. Challenge the assumptions6. Explore potential solutions

Objective

Prerequisite 1Requirement 1

Prerequisite 2Requirement 2

1

2

3

5

4

Page 70: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

We can have our cake AND eat it!

Page 71: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

7/7 SESSION FEEDBACK

Page 72: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Session Retro

What Went Well (WWW) What Went Wrong (WWW)

Puzzles Lessons Learned

Thank You!for your Gift of Feedback

Page 73: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02

Thank you!

Introductions

Her Blog: www.selfishprogramming.org His Blog: blog.nayima.be

NAYIMA

We make play work

Consultant.Storyteller.Games Maker. Consultant.

Project Manager. Games Maker.

Page 74: 20121216 1327   conflictresolutiondiagramtutorial-published-100912040222-phpapp02