Top Banner
Non-violent Communication Toolbox of Agile Practicioners How to turn personal conflicts into trust and deeper compassion Ari-Pekka Lappi (@ilmirajat) CC-BY Andrew Magill
67

Agile toolbox for nonviolent communication

Nov 22, 2014

Download

Flowa Oy

Non-violent
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Agile toolbox for nonviolent communication

Non-violent Communication Toolbox of Agile Practicioners

How to turn personal conflicts into trust and deeper compassion

Ari-Pekka Lappi (@ilmirajat)

CC-BY Andrew Magill

Page 2: Agile toolbox for nonviolent communication

Goal After this presentation everyone has at least 3 useful NVC tools they can use in their everyday work.

NVC is a great framework, but also difficult apply in practice. My goal is to make it a natural part of your agile toolbox.

•About me•A real life story• 7 NVC tools for agile

practitioners•Discussion (limited time)•After session: ~3 weird

advanced tools (ask!)

Outline

Page 3: Agile toolbox for nonviolent communication

Who am I?• Hybrid philosopher-engineer

• Developer, ScrumMaster, architect• M.A. majoring theoretical philosophy

from Helsinki University• Entrepreneur

• Big fan of functional programming (F# and Clojure) - and philosophy of Nietzsche• There is surprisingly much

similarities between NVC and Nietzsche’s philosophy

Thus Spoke Zarathustra by Atanas Botev.Oil on canvas/collage 2004

Page 4: Agile toolbox for nonviolent communication

Story

Page 5: Agile toolbox for nonviolent communication

Once opon time there was a developer, who had gotten an opportunity to develop awesome software with the coolest available technologies at that time.

CC-BY 2.0 JD Hancock

Page 6: Agile toolbox for nonviolent communication

The first demo

Finally all the main pieces were there: Database, business logic, services and service calls, UI... There was still a lot of work to do, but nonetheless our developer hero was satisfied and proud.

CC-BY 2.0 JD Hancock

Page 7: Agile toolbox for nonviolent communication

UX specialist was disappointed and angry

”This doesn’t look at all what it should, and its not functioning as I have planned. There’s missing a lot of thing from UI. And this is ugly. I’m very disappointed!”

CC-BY 2.0 JD Hancock

Page 8: Agile toolbox for nonviolent communication

BANGMy great plan is ruined. They don’t respect me and my work. This is simply ugly!

The other person does not understand but thinks only her own narrow domain of speciality.

She is undue and expects too much from me!

What was the moment things turned awry?

Page 9: Agile toolbox for nonviolent communication

Afterthoughts

This was a proof of concept for the overall architecture. It makes a lot of sense to validate that before finalized UI.

In web site development it was common at that time to start from visual appearance and implement backend stuff last.

CC-BY 2.0 JD Hancock

Page 10: Agile toolbox for nonviolent communication

A solution? Let’s educate each other and add

information

Hasty, volatile interpretation

”I was right! HAH!””I was wrong, sorry!”

Being right become more

important that the other

as a person

Page 11: Agile toolbox for nonviolent communication

The conflict was mostly about…• Valuation and respect• Ownership and authority• Value of own work• Reputation and gratitude

It was more only little about information per se.

CC-BY 2.0 Steve Evans; CC-BY-NC 2.0 Michael Kappel

Page 12: Agile toolbox for nonviolent communication

Frustration #0: This is insane!

I want to do cool stuff with competent and motivated people!Why collaboration is so damn hard every now and then?

Page 13: Agile toolbox for nonviolent communication

Solution? • Non-violent communication (NVC) is

psychological framework developed by Marshall B. Rosenberg. • It aims to:• Improve our ability to listen and

understand the other• Clearer and more accurate expression

of (own and other’s) needs and values

Page 14: Agile toolbox for nonviolent communication

It was surprisingly hardto make NVC work for me!

CC-BY 2.0 Alex Proimos

Page 15: Agile toolbox for nonviolent communication

Tool #7: OFNR-loop

O

F

N

F

Observation without evaluation

Clearly expressed feelings

Needs and values

Actionable request

CC-BY 2.0 Lee Nachtigal

Page 16: Agile toolbox for nonviolent communication

Tool #7: OFNR-loop – The basics

3. Need 1. Observation

2. Feelings

4. Requests

1. Need 1. Observation

1. Feeling

2. Demand, violence…

No clear distinction Collision,Danger of radiation sickness

Strongly influence by:- Fear- Unsafety (protection)- Distrust- Constraints- Injustice & unfairness

Clear distinction Connections,Self-awareness

Strongly influenced by:- Needs & values- Trust- Opportunities- All emotions

Page 17: Agile toolbox for nonviolent communication

Lets add then another person to the picture…

1. Observation 3. Need

2. Feelings

4. Requests

1. Need 1. Observation

1. Feeling

2. Demand, violence…

Page 18: Agile toolbox for nonviolent communication

…and the actual communication loop

O O

RNN

F

R

F

Page 19: Agile toolbox for nonviolent communication

O

OR

N

N

F R

F

Tool #7: OFNR-loop as a whole

N O

F

D

O N

F

R

N O

F

D

N O

F

R

Me You

Page 20: Agile toolbox for nonviolent communication

There must be a shortcut!

It cannot be this complex!

Page 21: Agile toolbox for nonviolent communication

O

OR

N

N

F R

F

Tool #7: OFNR-loop as a whole

N O

F

D

O N

F

R

N O

F

D

N O

F

R

Me You

16 boxes (each enclosing a complex algoritm)2 potentian nuclear blasts

A lot of asyncronous processing.3 vague background workflows

Insanely thight schedule & presure

Page 22: Agile toolbox for nonviolent communication

Frustration #1: Usability

As such NVC might be a bit too complex to everyday life. CC-BY 2.0 Lee Nachtigal

Page 23: Agile toolbox for nonviolent communication

O

OR

N

N

F R

F

N O

F

D

O N

F

R

N O

F

D

N O

F

R

Me You

(Conflict stress hormones negative impact verbal skills)

+ Framework that requires linguistic sensitivity

Bandwidth limits

Page 24: Agile toolbox for nonviolent communication

O

OR

N

N

F R

F

N O

F

D

O N

F

R

N O

F

D

N O

F

R

Me You

(Conflict stress hormones usually negative impact to memory)

+ A lot to remember in overall+ A framework to remember

Memory overflow

Page 25: Agile toolbox for nonviolent communication

O

OR

N

N

F R

F

N O

F

D

O N

F

R

N O

F

D

N O

F

R

Me You

(Conflict stress negative impact to analytical thinking)

+ complex psychological framework + some problem solving

110% Processor utilization

Page 26: Agile toolbox for nonviolent communication

Frustration #2: Scale

Small conflicts are potentially as devastating as big ones but in the long run. Because they are small, they are often ignored and let unresolved.

”By the book NVC” is often overkill.

Page 27: Agile toolbox for nonviolent communication

O

OR

N

N

F R

F

Tool #7: OFNR-loop

N O

F

D

O N

F

R

N O

F

D

N O

F

R

Me You

Good start but I need something more

Page 28: Agile toolbox for nonviolent communication

Tool #5: NVC templatesWhen/as <observation without evaluation> I feel <clearly expressed feeling> because <expression of need or value>.

Do you feel <clearly expressed feeling> because <observation without evaluation> and because <expression of need or value>?

OR

I-template

You-template

Page 29: Agile toolbox for nonviolent communication

Tool #5a: I-TemplateWhen/as <observation without evaluation> I feel <clearly expressed feeling> because <expression of need or value>.

“As you say “its’ not going to work” I feel annoyed and sad because this idea really inspires me and in my opinion we have not yet tried all options. I would like to use some time in exploring other way to implement this.”

Page 30: Agile toolbox for nonviolent communication

Tool #5a: You-templateDo you feel <clearly expressed feeling> because <observation without evaluation> and because <expression of need or value>?

”Do you feel angry and frustrated because the demo didn’t look like what you expected to see at this phase of project and because it’s important to you that you can be proud of the solution we deliver to the customer?”

Page 31: Agile toolbox for nonviolent communication

Frustration #1½: Usability

NVC has great potential, but NVC may make you talk like a book.

CC-BY 2.0 Lee Nachtigal

Page 32: Agile toolbox for nonviolent communication

Tool #3: NVC Canvas as a Kata – An observationHow systematically you have practiced non-violence?

How systematically you’ve been trained for violence (incl. critical attitudes, blame, judgement, resentment, martyrdom…)?

Page 33: Agile toolbox for nonviolent communication

It takes thousands of repetitions to learn technically correct right jab.

Why would non-violence be any easier?

Prepare! Pratice!

Page 34: Agile toolbox for nonviolent communication

Tool #3: NVC Canvas as a Kata4. Possible requests (person A) 4. Possible requests (person B)

1. Observations2. Feelings (A) 2. Feelings (B) 3. Needs (B)3. Needs (A)

Clues (A & B)

Page 35: Agile toolbox for nonviolent communication

Tool #3: NVC Canvas as a Kata - in action

4. Possible requests (Developer) 4. Possible requests (UX Specialist)

1. Observations2. Feelings (A) 2. Feelings (B) 3. Needs (B)3. Needs (A)

Clues (A & B)

UX specialist said this is uglyand asked are you going to follow my plan

Developer wanted to demoa “successful” PoC of new technology

AngryDissatisfiedConfused?

ConfusedProud (in the beginning)Frustrated

Appreciation &respect

Appreciation &respectValuation of own workRelatednessReputation

Would you like to help me to tweak details in UI whenWe have a bit more finalized version of it?

I feel confused because this demo was not what I expected.I want you to clarify what is happening and are you going to follow my plan?

Business unit director and many other persons with high status attended the demo

Page 36: Agile toolbox for nonviolent communication

Tool #3: NVC Canvas as a Kata – Getting started

Kata A:Employees don’t trust managers.Management don’t trust employees.

Kata B: A manager tries to do his/her best to improved things. Employees still keep on complaining.

Kata C: I person in team don’t like agile patterns and practices and refuse to participate.

Page 37: Agile toolbox for nonviolent communication

Conflicts are not the point in NVC. The goal is to get beyond conflicts,

toward win-win-mindset

Frustration #3: Focus

CC-BY 2.0 Ada Be

Page 38: Agile toolbox for nonviolent communication

You don’t want to resolve conflicts!You want a better community!

You want to achieve your goals!

Frustration #3: Focus

CC-BY 2.0 Ada Be

Page 39: Agile toolbox for nonviolent communication

Tool #1: Attend to folks’ needs!*

Dev UX

”But this is the first demo and…”

* Antimatter principle by Bob Marshall

”This does not look what is should look like! This is ugly!”

Page 40: Agile toolbox for nonviolent communication

O

OR

N

N

F R

F

Tool #1: Attend to folks’ needs!*

N O

F

D

O N

F

R

N O

F

D

N O

F

R

Dev UX

”But this is the first demo and…”

”This does not look what is should look like! This is ugly!”

KEEP IT SIMPLE* Antimatter principle by Bob Marshall

Page 41: Agile toolbox for nonviolent communication

O

OR

N

N

F R

F

Tool #1: Attend to folks’ needs!*

N O

F

D

O N

F

R

N O

F

D

N O

F

R

N N

Dev UX

”But this is the first demo and…”

”This does not look what is should look like! This is ugly!”

START HERE* Antimatter principle by Bob Marshall

Page 42: Agile toolbox for nonviolent communication

Tool #1: Attend to folks’ needs!*

Dev UX

”But this is the first demo and…”

”Yes. In this first demo we haven’t paid much attention to UI yet. May I ask your comments when we have a bit more finalized UI? And are you interested in hearing why?”

Why she feels angry?What is important for her?

* Antimatter principle by Bob Marshall

”This does not look what is should look like! This is ugly!”

Page 43: Agile toolbox for nonviolent communication

O

OR

N

N

F R

F

Tool #1: Attend to folks’ needs!*

N O

F

D

O N

F

R

N O

F

D

N O

F

R

N N

Dev UX

” Yes. In this first demo we haven’t paid much attention to UI yet. May I ask your comments when we have a bit more finalized UI? And are you interested in hearing why?”

”This does not look what is should look like! This is ugly!”

LEVEL UP!* Antimatter principle by Bob Marshall

Page 44: Agile toolbox for nonviolent communication

Using ”Attend to folks’ needs”in non-conflict situation

• Problem: • Sharing information is very important, but not the most important• Time is the most scarce resource• How to use time in meetings in optimal way?

• Solution:

An agenda item by X

How to fulfil X’s needs? Why discussion is important…?

DiscussionDid everyone got what they

needed?

Page 45: Agile toolbox for nonviolent communication

Tool #2: Who-what distinction

”Mice are ugly!” ”An elephant thinks that mice are ugly”

In all interpretations there is an observed thing and an observer!

Vs.

Page 46: Agile toolbox for nonviolent communication

Tool #2: Who-what distinction

”Dear Elephant!

Your claim that mice are ugly is completely absurd! What is wrong with you?Mice are tasty and good for playing!

Best regards,Cat”

By being able to see clearly who observes helps you to see beyond criticism!

Page 47: Agile toolbox for nonviolent communication

Tool #2: Who-what distinction

”UI is simply ugly!” ”An UX specialist thinks that UI is ugly.”

Vs.Reality

Page 48: Agile toolbox for nonviolent communication

Tool #2 Who-what distinctionBad feedback is injustified criticism

I’m good in this

Feedback

I suck

Feedbacksucks

I’m good in this

Feedback

I learn!An alien mindset

Bad feedback is a learning puzzle

Page 49: Agile toolbox for nonviolent communication

Tool #4: Yoda Principle

Do a change in the system or do not. There is no try!

CC-BY 2.0 angelo - Yoda Franklin Institute Museum, Phialdelphia

Page 50: Agile toolbox for nonviolent communication

’Try’ smells…• Obsession• Fear• Dishonesty• Denial of

ignorance• Dismissal of

discussion

© A. Lipson 2003 http://www.andrewlipson.com/escher/relativity.html

Page 51: Agile toolbox for nonviolent communication

Proposal

Won’t Try Will

Didn’t

It’s complicated

Did

Request

Won’t Will

Didn’t Did

ProposalActionable,clear &real options

Complex, slow and nasty Simple, painfully honest and straightforward

Page 52: Agile toolbox for nonviolent communication

Actionable, clear & real optionsNo real options! “I want you to stop drinking”

Real options “I want you to tell me what needs of you are met by drinking and discuss other ways to meet those needs.”

Page 53: Agile toolbox for nonviolent communication

Actionable, clear & real optionsNo real options! “I want you feel free to express yourself around me.”

Real options “I like you to tell me what I might do to make it easier for you to feel free to express yourself.”

CC-BY 2.0 Jessica Flavin

Page 54: Agile toolbox for nonviolent communication

Actionable, clear & real optionsNo real options! “Lets try this-and-that, because we have to do something…”

Real options ”I don’t know what to do. The only option I see is this-and-that. Doing nothing is not a real option. Shall we experiment this or do you have other options?

CC-BY-SA 3.0 Sven Dirks

Page 55: Agile toolbox for nonviolent communication

Request

Won’t Will

Didn’t Did

Proposal • Only real options• ”Try” smells a failure• ”Try” may postpone a

resolution to problemsDo a change in the system Or do not There is no try

Tool #4: Yoda Principle

Page 56: Agile toolbox for nonviolent communication

Tool #6: Language smells• Identify violent “Jackal’s language”• Absolutes: Always, never, all the time,

necessity, no options• Judgemental language: right, wrong,

evil…• Vague expression (e.g. “I feel like a

failure…”)• Feelings white list

• Etc.

• Worked only partially for me

Read the book

Lucas van Valckenborch (1535 or later–1597)

Page 57: Agile toolbox for nonviolent communication

NVC Toolbox for Agile PractitionersTool #1: Attend to folks’ need! (i.e. Antimatter principle)Tool #2: Who-what distinctionTool #3: NVC canvas as a kataTool #4: Yoda principleTool #5: NVC templates (I-version and You-version)

May work for you (did not work for me):Tool #6: Language smellsTool #7: OFNR-loops

Page 58: Agile toolbox for nonviolent communication

Tool #1: Attend to folks’ needs!

It’s not hard. (1) Stop. (2) Identify the needs. (3) Address

them.CC 2.0 BY-SA Adriagarcia - Superman @ Saló del Cómic

Page 59: Agile toolbox for nonviolent communication

Tool #2: Who-what distinction

Observation = Observer + Observed

Page 60: Agile toolbox for nonviolent communication

Tool #3: NVC canvas as a Kata

Prepare! Practice!

Page 61: Agile toolbox for nonviolent communication

Tool #4: Yoda Principle

Embrace ”YES” and embrace ”NO”It’s “TRY” that hurts you most!

CC-BY 2.0 angelo

Page 62: Agile toolbox for nonviolent communication

Tool #5: NVC templates (I- and You-template)

My feelings and needs. Your feelings and needs?

CC 2.0 BY José Luis Mieza - Lovers of Teruel

Page 63: Agile toolbox for nonviolent communication

Tool #6: Language smells

Words without empathy are empty, empathy without

concepts is blind.Lucas van Valckenborch (1535 or later–1597)

Page 64: Agile toolbox for nonviolent communication

Tool #7: OFNR-loop

“Ill seen, ill said” –BeckettCC-BY 2.0 aussiegall

Page 65: Agile toolbox for nonviolent communication

Build-Measure-Learn

Was there at least 3 NVC tools you find useful in your work and for your organization?

Page 66: Agile toolbox for nonviolent communication

NVC Toolbox for Agile PractitionersTool #1: Attend to folks’ need! (i.e. Antimatter principle)Tool #2: Who-what distinctionTool #3: NVC canvas as a kataTool #4: Yoda principleTool #5: NVC templates (I-version and You-version)Tool #6: Language smellsTool #7: OFNR-loops