Skip to main content

Checklist for conflict resolution

  1. Focus
    • Focus on the issue by separating the person from the problem. No name-calling and no labeling.
    • Be flexible, as the enterprise’s rules and policies to govern employee behavior do not cover every situation. Solutions present themselves in a culture of cooperation and compromise.
    • Encourage responsibility by promoting the importance of raising concerns and addressing them as early as possible. Employees fearing retaliation will only "go underground" with their issues, where they fester and grow out of all proportion.
    • Communication is both the source and solution of many conflicts. When dialogue is subverted conflict, breeds in an atmosphere of tension, misunderstanding and fear.
    • Fairness counts and make sure that all team members are subject to the same guidelines.
  2. Negotiations
    • Avoid defend/attack methods
    • Obtain information by asking questions
    • Attempt to understand all perceptions
  3. Meetings
    • Identify areas of agreement
    • Defer the subject to later in the meeting or document & set aside for discussion at the next meeting
    • Obtain opinion from other meeting participants
    • Create a compromise
  4. Interpersonal relationships
    • Determine existence of problems between individual team members
    • Arrange face-to-face meetings to discuss problems & explain what is the perceived problem
    • Use feedback & don't attack with accusations
    • Listen with open minds & respect each other's opinions
    • Avoid finger pointing & come to a compromise
  5. Transparency
    • Keep it in the open and don't resort to secrecy
    • Avoiding breeding discontent and alienation
  6. Ground rules
    Team members need to be able to express themselves in an atmosphere of respect and consideration.
    Team leaders should promote "attack-free" zones for dialogue.
    Collectively identify behaviors & attitudes that limit conflict & encourage effectiveness. Decide what course of action to take if team members do not observe your team's relational & operational guidelines
    No one likes to see a team go off track. Make sure you have a plan in case it does.

Comments

Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi