conflict management

Full: The Conflict Fuel Tank

gas-pump-1914310_640.jpg

As I coach tenured and new managers, one of the many recurring themes I hear about is the rampant interpersonal conflict within organizations. If there is conflict, the organization is not unique; in fact, if business owners believe there is little conflict among their team members, I am comfortable telling them they are wrong. 

Conflict avoidance is something we learn from a young age. Rather than addressing the way we feel, we look to our caregivers to fix the discomfort. While I am not suggesting you leave your young children to fight their battles on the playground without guidance, I do think there is validity in fighting our own battles from a young(ish) age. We were conditioned to have the parent, the sitter, the teacher, and then the boss, help fix our problems. Yes, I am a proponent of assisting employees in sorting through issues, but it is not about “doing it for them.” The enablement concept is closely linked with employee entitlement (and let’s make sure we are not encouraging that). 

The key here: do not avoid the topics that cause tension (employees often want to go around the issues) but instead we need to work through them. 

Avoidance of conflict, which mainly is attributed to our golden conditioning of thinking conflict is terrible, only fills the gas tank. Rather than simple disagreement, conflict is stored and builds upon itself. The person with whom you had a conflict now appears only to be or bring bad news. Typically, this is not the case – but we have filed it in our brain bank as “bad.” 

If you reach this point, it is probable you think addressing conflict is too exhausting and time-consuming. But the truth is: you need to face conflict as it rises. When you do not, it becomes overwhelming. You end up anxious, overly angry, and unsure as to why you despise a person so vehemently. 

If your conflict fuel tank is overflowing, it is time to start addressing (through), not avoiding (around) it. 

This article was first published on LinkedIn.