Pat Arcady is an agile and executive coach with FreeStanding Agility. In this interview, Pat discusses ways conflict manifests itself in an organization, the importance of nonviolent communication, and a useful four-step protocol for achieving positive outcomes for all parties.
Pat Arcady is an agile and executive coach with FreeStanding Agility, where she coaches leaders and teams in strategies to increase employee engagement, team alignment, and collaboration. She also happens to know a thing or two about conflict management. In this interview, Pat discusses ways conflict manifests itself in an organization, the importance of nonviolent communication, and a useful four-step protocol for achieving positive outcomes for all parties.
Jonathan Vanian: Why exactly does conflict occur on a team?
Pat Arcady: Conflict occurs when we have an attachment to a particular strategy for meeting a need (be it a business need or a personal need) and that strategy isn't acceptable to someone else on the team.
JV: How does practicing agile relate to conflict management? Does practicing agile well essentially lead to good conflict management?
PA: Just the opposite. High-performing teams learn how to manage conflict well so it does not impede their ability to be agile!
JV: What are some individual and team skills one can use to handle conflict so it resolves in an appropriate manner?
PA: Teams benefit when they build trust and expect teammates to speak up about what is important to them. To do this with high impact, anyone can learn how to focus on the core business needs instead of strategy. It never fails; once a team or a couple can agree on the core need(s) at hand, then strategies and solutions are unlimited. The goal of nonviolent communication nonviolent communication (NVC) is to help people focus on what really matters and why it matters to them and hear one another on that. Then together, craft solutions that can work for everyone involved.
JV: What are some examples of good conflict management skills?
PA: Listening is an important skill. Listening for the core need behind the words is what makes the difference. For example, if John says "This meeting is a waste of time," one could wonder what is John signaling? Is it that he wants to have a say in what meetings he attends—he prefers to opt in? Does he want respect for his time, his tight schedule this week? Is he saying he wishes the meeting was better organized or more substantive? Often, I find a statement like this points to an engineer's frustration with not enough blocks of uninterrupted time to write code. So, along with listening, is the skill of being genuinely interested in what the other person is really saying and finding ways to elicit that from them without judgment.
Another important conflict management skill is asking for what you want—making a request of another. To often, I hear someone complain about something without voicing how to improve upon things. So with the example above in which John complains about the meeting being a waste of time, John could follow that with an explanation of what he really needs—be it a meaningful agenda, or uninterrupted time to code—and make a request of the group or the meeting convener, instead of just voicing his unhappiness.
A third skill I find important is developing the capacity to speak in terms of what you want instead of just saying what it is you don't like.
JV: How do these teams learn these skills?
PA: Reading Marshall Rosenberg's book or attending an NVC workshop, and then PRACTICING.
JV: Do you have an example of a company or organization that practices good conflict management?
PA: I find teams that take their retrospectives seriously learn how to be honest and real about what isn't working to make them great and commit to getting better at those things together. But first you have to call out what those things are and do so in ways that are respectful and honest.