SlideShare a Scribd company logo
1 of 6
Download to read offline
Agile 2012




Leading Conflict:
A Systems Intelligence Approach to
Conflict Facilitation for Leaders
Lyssa Adkins & Michael K. Spayd, Agile Coaching Institute
@lyssaadkins @mspayd



1. Take a Systems Leadership View of Conflict
What is the leader’s role with conflict? What would it mean to take a human systems
leadership orientation? If we can see our job as leader as one of building, nurturing, and
‘holding’ the container within which work (and conflict) occur, we make a strong move
towards human systems leadership. 

Start with right view of conflict. From a human systems perspective, conflict is not
something to be managed or merely tolerated; it is a manifestation of the system’s
diversity (and therefore its intelligence) and is emblematic of a positive change urge
within the system (of something trying to happen).

Focus on the container. As leader, our most important job is to setup, nurture and
maintain the container. This includes helping create an environment of positivity resulting
in positive sentiment override, minimizing toxic conflict, and creating agreements
between team members about how to work with conflict. 

Become a conflict facilitator, not an arbiter, to process conflict. In part, this means
realizing that conflict is a challenge for us and our egos (e.g., getting ‘triggered’), both as
leaders and as team members. Our job as leader is not to “resolve” conflict, nor arbitrate
between team members, but to facilitate and help the team navigate it. Conflict
facilitation involves helping the team apply their conflict protocols, using deep
democracy practices, helping the team separate individual interests from positions, and
generally seeing conflict as an urge to change something within the human system.

Source: copyright 2012 Michael Spayd, “Coaching the Agile Enterprise” (book in progress - do not
distribute)




      ©2012 Agile Coaching Institute             Page 1                     www.AgileCoachingInstitute.com
Agile 2012




2. Build the Container
Educate about Conflict & Build Positivity
Create an “emotional bank account” to strengthen
the team’s resiliency. When the balance in this bank
account is positive, the team has a “positive
sentiment override” that helps them work with
conflict.

“Deposits” into the account are appreciations/
shutouts, acknowledgements, and more inquiry/ less
advocacy.

“Withdrawals” from the account are toxic conflict
patterns of blaming, defensiveness, stonewalling,
contempt, and excessive advocacy.

The importance of positivity on team performance
has been strongly supported by research. Losada and
Heaphy looked at 60 teams and divided them into
high, medium and low performance. They found
that high performance teams had a positivity ratio of
5.6, medium performance teams 1.8 and low
performance teams a positivity ratio of .36.

A high-performance team’s bank account
“Balance” is 5:1.

This research has been independently verified by
other scientists, including Dr. Barbara Frederickson
and Dr. John Gottman.


Adapted from CRR Global, Organization & Relationship Systems Coaching Handbook
Original Sources: Marcial Losada And Emily Heaphy, “The Role Of Positivity And Connectivity In
Business Teams,” American Behavioral Scientist 2004: 47: 740; John Gottman, The Relationship Cure;
Barbara Frederickson, Positivity




     ©2012 Agile Coaching Institute             Page 2                     www.AgileCoachingInstitute.com
Agile 2012



Establish Conflict Protocol Agreements
An idea originally developed by Howard Guttman in his book Great Business Teams, and
expanded by CRRGlobal, a conflict protocol is a set of agreements teams make when
they are cool and rational for how to act when they are hot and emotional. They codify
key principles for helping conflict go well:
maximize team learning and diversity, while
limiting harm to team relationships. They need
to be agreed to by true consensus (think deep
democracy) and enforced by the team itself.

CONFLICT PROTOCOL
QUESTIONS
Think about your ideal team. How would that
team handle conflicts and disagreements?



What are some behaviors you want to have happen when conflict occurs? (For example:
speak to the person directly, get all parties together rather than triangulating.)



What are some things you do not want to happen when conflict occurs?



It takes 6-9 months to change a behavior:

How will you hold one another accountable for following these agreements?



What will you do if someone breaks an agreement?




Adapted from CRR Global, Organization & Relationship Systems Coaching Handbook



     ©2012 Agile Coaching Institute           Page 3                   www.AgileCoachingInstitute.com
Agile 2012




3. Become a Conflict Facilitator
Before you can help the team successfully process conflict, you must first develop (or
dust off) you facilitation skills and get into the Conflict Facilitator mindset. Practices for
personal mastery in this area are:
    • Learn facilitation skills                • Mind Training: Repeat the Right
    • Get you facilitator hat on                 View beliefs until they become true
    • Know your triggers: What “sets           • Actively practice seeing everyone
      you off”?                                  as right (partially)




Source: copyright 2012 Michael Spayd, “Coaching the Agile Enterprise” (book in progress - do not
distribute).




4. “Process” the Conflict
The leaders job is to help the team process the change urge. Aligned with the Right View,
there are several ways to do this:

•    Use conflict protocol agreements
•    Use Deep Democracy practices
•    Move from positions to interests
•    Frame conflict as an urge to change; it’s natural and normal




        ©2012 Agile Coaching Institute           Page 4                     www.AgileCoachingInstitute.com
Agile 2012



Deep Democracy Practices
Deep democracy is a philosophy developed by Jungian psychologist and physicist Arnold
Mindell. He observed that human systems create dysfunctions when they only favored
the voices or perspectives they could tolerate well. We all know the experience of having
people on teams who we cannot stand. Mindell found, however, that when we examine
this phenomenon more deeply, we find that the annoying person often has important
information for the team. Groups or teams, which are naturally self-organizing, are not
able to effectively self organize unless all the information in the system is represented
amongst the group.

Source: Arnold Mindell, Deep Democracy Of Open Forums & Leader As Martial Artist

Deep democracy practices are:
 • Constellations                     • Round Robin
 • Fist of Five                       • Writing on stickies before talking
 • Roman Vote                         • Making space for unpopular or minority voices



Move from Positions to Interests
When people are locked into different positions, conflict is unresolvable. “This is perfect
for Java!” says one developer. “No way, man, Ruby on Rails is what we need!” says
another. As long as the conversation stays on that level, we’ll just hear argument after
argument, going nowhere. When the leader helps the two developers recognize their
common interest; however, the conflict can
“unknot” and movement toward a better solution
occurs. Asking questions such as, “Why is it
important to resolve this?” and “What’s important
to you?” helps them see where there is already
common ground. In this case, the developers may
come to recognize that what they *really* want is a
flexible, yet robust technology. With this new
“frame” on the problem, they can have a richer
discussion and come up with the best solution
(which may or may not be Java or Ruby on Rails).

Source: Roger Fisher and William Ury, Getting to YES
Adapted from CRR Global, Organization & Relationship Systems Coaching Handbook


     ©2012 Agile Coaching Institute                 Page 5                   www.AgileCoachingInstitute.com
Agile 2012




     ©2012 Agile Coaching Institute   Page 6   www.AgileCoachingInstitute.com

More Related Content

More from drewz lin

Chuck willis-owaspbwa-beyond-1.0-app secusa-2013-11-21
Chuck willis-owaspbwa-beyond-1.0-app secusa-2013-11-21Chuck willis-owaspbwa-beyond-1.0-app secusa-2013-11-21
Chuck willis-owaspbwa-beyond-1.0-app secusa-2013-11-21drewz lin
 
Appsec usa roberthansen
Appsec usa roberthansenAppsec usa roberthansen
Appsec usa roberthansendrewz lin
 
Appsec usa2013 js_libinsecurity_stefanodipaola
Appsec usa2013 js_libinsecurity_stefanodipaolaAppsec usa2013 js_libinsecurity_stefanodipaola
Appsec usa2013 js_libinsecurity_stefanodipaoladrewz lin
 
Appsec2013 presentation-dickson final-with_all_final_edits
Appsec2013 presentation-dickson final-with_all_final_editsAppsec2013 presentation-dickson final-with_all_final_edits
Appsec2013 presentation-dickson final-with_all_final_editsdrewz lin
 
Appsec2013 presentation
Appsec2013 presentationAppsec2013 presentation
Appsec2013 presentationdrewz lin
 
Appsec 2013-krehel-ondrej-forensic-investigations-of-web-exploitations
Appsec 2013-krehel-ondrej-forensic-investigations-of-web-exploitationsAppsec 2013-krehel-ondrej-forensic-investigations-of-web-exploitations
Appsec 2013-krehel-ondrej-forensic-investigations-of-web-exploitationsdrewz lin
 
Appsec2013 assurance tagging-robert martin
Appsec2013 assurance tagging-robert martinAppsec2013 assurance tagging-robert martin
Appsec2013 assurance tagging-robert martindrewz lin
 
Amol scadaowasp
Amol scadaowaspAmol scadaowasp
Amol scadaowaspdrewz lin
 
Agile sdlc-v1.1-owasp-app sec-usa
Agile sdlc-v1.1-owasp-app sec-usaAgile sdlc-v1.1-owasp-app sec-usa
Agile sdlc-v1.1-owasp-app sec-usadrewz lin
 
Vulnex app secusa2013
Vulnex app secusa2013Vulnex app secusa2013
Vulnex app secusa2013drewz lin
 
基于虚拟化技术的分布式软件测试框架
基于虚拟化技术的分布式软件测试框架基于虚拟化技术的分布式软件测试框架
基于虚拟化技术的分布式软件测试框架drewz lin
 
新浪微博稳定性经验谈
新浪微博稳定性经验谈新浪微博稳定性经验谈
新浪微博稳定性经验谈drewz lin
 
无线App的性能分析和监控实践 rickyqiu
无线App的性能分析和监控实践 rickyqiu无线App的性能分析和监控实践 rickyqiu
无线App的性能分析和监控实践 rickyqiudrewz lin
 
网易移动自动化测试实践(孔庆云)
网易移动自动化测试实践(孔庆云)网易移动自动化测试实践(孔庆云)
网易移动自动化测试实践(孔庆云)drewz lin
 
天猫后端技术架构优化实践
天猫后端技术架构优化实践天猫后端技术架构优化实践
天猫后端技术架构优化实践drewz lin
 
天猫大促性能测试实践 耿电
天猫大促性能测试实践 耿电天猫大促性能测试实践 耿电
天猫大促性能测试实践 耿电drewz lin
 
互联网海量运维 20130807
互联网海量运维 20130807互联网海量运维 20130807
互联网海量运维 20130807drewz lin
 
阿里自研数据库 Ocean base实践
阿里自研数据库 Ocean base实践阿里自研数据库 Ocean base实践
阿里自研数据库 Ocean base实践drewz lin
 
T4 淘宝私有云
T4 淘宝私有云T4 淘宝私有云
T4 淘宝私有云drewz lin
 
I os与android多平台开发心得
I os与android多平台开发心得I os与android多平台开发心得
I os与android多平台开发心得drewz lin
 

More from drewz lin (20)

Chuck willis-owaspbwa-beyond-1.0-app secusa-2013-11-21
Chuck willis-owaspbwa-beyond-1.0-app secusa-2013-11-21Chuck willis-owaspbwa-beyond-1.0-app secusa-2013-11-21
Chuck willis-owaspbwa-beyond-1.0-app secusa-2013-11-21
 
Appsec usa roberthansen
Appsec usa roberthansenAppsec usa roberthansen
Appsec usa roberthansen
 
Appsec usa2013 js_libinsecurity_stefanodipaola
Appsec usa2013 js_libinsecurity_stefanodipaolaAppsec usa2013 js_libinsecurity_stefanodipaola
Appsec usa2013 js_libinsecurity_stefanodipaola
 
Appsec2013 presentation-dickson final-with_all_final_edits
Appsec2013 presentation-dickson final-with_all_final_editsAppsec2013 presentation-dickson final-with_all_final_edits
Appsec2013 presentation-dickson final-with_all_final_edits
 
Appsec2013 presentation
Appsec2013 presentationAppsec2013 presentation
Appsec2013 presentation
 
Appsec 2013-krehel-ondrej-forensic-investigations-of-web-exploitations
Appsec 2013-krehel-ondrej-forensic-investigations-of-web-exploitationsAppsec 2013-krehel-ondrej-forensic-investigations-of-web-exploitations
Appsec 2013-krehel-ondrej-forensic-investigations-of-web-exploitations
 
Appsec2013 assurance tagging-robert martin
Appsec2013 assurance tagging-robert martinAppsec2013 assurance tagging-robert martin
Appsec2013 assurance tagging-robert martin
 
Amol scadaowasp
Amol scadaowaspAmol scadaowasp
Amol scadaowasp
 
Agile sdlc-v1.1-owasp-app sec-usa
Agile sdlc-v1.1-owasp-app sec-usaAgile sdlc-v1.1-owasp-app sec-usa
Agile sdlc-v1.1-owasp-app sec-usa
 
Vulnex app secusa2013
Vulnex app secusa2013Vulnex app secusa2013
Vulnex app secusa2013
 
基于虚拟化技术的分布式软件测试框架
基于虚拟化技术的分布式软件测试框架基于虚拟化技术的分布式软件测试框架
基于虚拟化技术的分布式软件测试框架
 
新浪微博稳定性经验谈
新浪微博稳定性经验谈新浪微博稳定性经验谈
新浪微博稳定性经验谈
 
无线App的性能分析和监控实践 rickyqiu
无线App的性能分析和监控实践 rickyqiu无线App的性能分析和监控实践 rickyqiu
无线App的性能分析和监控实践 rickyqiu
 
网易移动自动化测试实践(孔庆云)
网易移动自动化测试实践(孔庆云)网易移动自动化测试实践(孔庆云)
网易移动自动化测试实践(孔庆云)
 
天猫后端技术架构优化实践
天猫后端技术架构优化实践天猫后端技术架构优化实践
天猫后端技术架构优化实践
 
天猫大促性能测试实践 耿电
天猫大促性能测试实践 耿电天猫大促性能测试实践 耿电
天猫大促性能测试实践 耿电
 
互联网海量运维 20130807
互联网海量运维 20130807互联网海量运维 20130807
互联网海量运维 20130807
 
阿里自研数据库 Ocean base实践
阿里自研数据库 Ocean base实践阿里自研数据库 Ocean base实践
阿里自研数据库 Ocean base实践
 
T4 淘宝私有云
T4 淘宝私有云T4 淘宝私有云
T4 淘宝私有云
 
I os与android多平台开发心得
I os与android多平台开发心得I os与android多平台开发心得
I os与android多平台开发心得
 

Leading conflict handout agile 2012

  • 1. Agile 2012 Leading Conflict: A Systems Intelligence Approach to Conflict Facilitation for Leaders Lyssa Adkins & Michael K. Spayd, Agile Coaching Institute @lyssaadkins @mspayd 1. Take a Systems Leadership View of Conflict What is the leader’s role with conflict? What would it mean to take a human systems leadership orientation? If we can see our job as leader as one of building, nurturing, and ‘holding’ the container within which work (and conflict) occur, we make a strong move towards human systems leadership.  Start with right view of conflict. From a human systems perspective, conflict is not something to be managed or merely tolerated; it is a manifestation of the system’s diversity (and therefore its intelligence) and is emblematic of a positive change urge within the system (of something trying to happen). Focus on the container. As leader, our most important job is to setup, nurture and maintain the container. This includes helping create an environment of positivity resulting in positive sentiment override, minimizing toxic conflict, and creating agreements between team members about how to work with conflict.  Become a conflict facilitator, not an arbiter, to process conflict. In part, this means realizing that conflict is a challenge for us and our egos (e.g., getting ‘triggered’), both as leaders and as team members. Our job as leader is not to “resolve” conflict, nor arbitrate between team members, but to facilitate and help the team navigate it. Conflict facilitation involves helping the team apply their conflict protocols, using deep democracy practices, helping the team separate individual interests from positions, and generally seeing conflict as an urge to change something within the human system. Source: copyright 2012 Michael Spayd, “Coaching the Agile Enterprise” (book in progress - do not distribute) ©2012 Agile Coaching Institute Page 1 www.AgileCoachingInstitute.com
  • 2. Agile 2012 2. Build the Container Educate about Conflict & Build Positivity Create an “emotional bank account” to strengthen the team’s resiliency. When the balance in this bank account is positive, the team has a “positive sentiment override” that helps them work with conflict. “Deposits” into the account are appreciations/ shutouts, acknowledgements, and more inquiry/ less advocacy. “Withdrawals” from the account are toxic conflict patterns of blaming, defensiveness, stonewalling, contempt, and excessive advocacy. The importance of positivity on team performance has been strongly supported by research. Losada and Heaphy looked at 60 teams and divided them into high, medium and low performance. They found that high performance teams had a positivity ratio of 5.6, medium performance teams 1.8 and low performance teams a positivity ratio of .36. A high-performance team’s bank account “Balance” is 5:1. This research has been independently verified by other scientists, including Dr. Barbara Frederickson and Dr. John Gottman. Adapted from CRR Global, Organization & Relationship Systems Coaching Handbook Original Sources: Marcial Losada And Emily Heaphy, “The Role Of Positivity And Connectivity In Business Teams,” American Behavioral Scientist 2004: 47: 740; John Gottman, The Relationship Cure; Barbara Frederickson, Positivity ©2012 Agile Coaching Institute Page 2 www.AgileCoachingInstitute.com
  • 3. Agile 2012 Establish Conflict Protocol Agreements An idea originally developed by Howard Guttman in his book Great Business Teams, and expanded by CRRGlobal, a conflict protocol is a set of agreements teams make when they are cool and rational for how to act when they are hot and emotional. They codify key principles for helping conflict go well: maximize team learning and diversity, while limiting harm to team relationships. They need to be agreed to by true consensus (think deep democracy) and enforced by the team itself. CONFLICT PROTOCOL QUESTIONS Think about your ideal team. How would that team handle conflicts and disagreements? What are some behaviors you want to have happen when conflict occurs? (For example: speak to the person directly, get all parties together rather than triangulating.) What are some things you do not want to happen when conflict occurs? It takes 6-9 months to change a behavior: How will you hold one another accountable for following these agreements? What will you do if someone breaks an agreement? Adapted from CRR Global, Organization & Relationship Systems Coaching Handbook ©2012 Agile Coaching Institute Page 3 www.AgileCoachingInstitute.com
  • 4. Agile 2012 3. Become a Conflict Facilitator Before you can help the team successfully process conflict, you must first develop (or dust off) you facilitation skills and get into the Conflict Facilitator mindset. Practices for personal mastery in this area are: • Learn facilitation skills • Mind Training: Repeat the Right • Get you facilitator hat on View beliefs until they become true • Know your triggers: What “sets • Actively practice seeing everyone you off”? as right (partially) Source: copyright 2012 Michael Spayd, “Coaching the Agile Enterprise” (book in progress - do not distribute). 4. “Process” the Conflict The leaders job is to help the team process the change urge. Aligned with the Right View, there are several ways to do this: • Use conflict protocol agreements • Use Deep Democracy practices • Move from positions to interests • Frame conflict as an urge to change; it’s natural and normal ©2012 Agile Coaching Institute Page 4 www.AgileCoachingInstitute.com
  • 5. Agile 2012 Deep Democracy Practices Deep democracy is a philosophy developed by Jungian psychologist and physicist Arnold Mindell. He observed that human systems create dysfunctions when they only favored the voices or perspectives they could tolerate well. We all know the experience of having people on teams who we cannot stand. Mindell found, however, that when we examine this phenomenon more deeply, we find that the annoying person often has important information for the team. Groups or teams, which are naturally self-organizing, are not able to effectively self organize unless all the information in the system is represented amongst the group. Source: Arnold Mindell, Deep Democracy Of Open Forums & Leader As Martial Artist Deep democracy practices are: • Constellations • Round Robin • Fist of Five • Writing on stickies before talking • Roman Vote • Making space for unpopular or minority voices Move from Positions to Interests When people are locked into different positions, conflict is unresolvable. “This is perfect for Java!” says one developer. “No way, man, Ruby on Rails is what we need!” says another. As long as the conversation stays on that level, we’ll just hear argument after argument, going nowhere. When the leader helps the two developers recognize their common interest; however, the conflict can “unknot” and movement toward a better solution occurs. Asking questions such as, “Why is it important to resolve this?” and “What’s important to you?” helps them see where there is already common ground. In this case, the developers may come to recognize that what they *really* want is a flexible, yet robust technology. With this new “frame” on the problem, they can have a richer discussion and come up with the best solution (which may or may not be Java or Ruby on Rails). Source: Roger Fisher and William Ury, Getting to YES Adapted from CRR Global, Organization & Relationship Systems Coaching Handbook ©2012 Agile Coaching Institute Page 5 www.AgileCoachingInstitute.com
  • 6. Agile 2012 ©2012 Agile Coaching Institute Page 6 www.AgileCoachingInstitute.com