27
loading...
This website collects cookies to deliver better user experience
Stage | Signals |
Problems to solve | Team members engage openly and constructively. Examples: "I hear what you are saying, have you considered using X or Y?" |
Disagreement | Self-protection becomes important. Picking the best solution might not be the main goal for all team members. Examples: "Yes I know I broke the build. But there are bigger issues than just a broken build we should focus on." |
Contest | The aim is to win. Team members start to pick sides, become personal and focus on building their case. Examples: "He always forgets to test his code!" |
Crusade | Winning the conflict is not good enough. Team members believe people on "the other side" will not change. They believe it can only be resolved by removing the other side from the equation. Examples: "Why should we run this by them? They are not using their brains anyway!" |
World war | Nothing good can come out of this stage of conflict. Winning is not enough, the other side needs to be destroyed! Examples: "It is us or them!" |
Stage | Resolving |
Problems to solve | Collaborate, try to find a win-win situation for both parties. |
Disagreement | Offer support and safety. Make sure everyone is empowered in finding a solution. |
Contest | Since things are getting personal, try to keep it to the actual issue. If things get too personal, damaging the relationship is a liability. Gathering facts or metrics about the actual issue might help keep the discussion not personal. |
Crusade | Use a neutral party to mediate the conflict. Talk to both parties until the conflict is de-escalated so you can use the resolving methods of the previous stages. |
World war | There is no resolving this one. Try anything you can to make sure people don't hurt each other. |
27