Lemanskills.com

Team Conflict: Is It Always a Bad Thing?

When we hear “conflict”, we think “trouble”. When we hear “conflict”, we think “dysfunctional team”, where communication doesn’t work, and people have personal issues. Or when we hear “conflict”, we think that leader doesn’t know how to lead his/her team successfully.

Is that really true? Why are we so scared of a conflict? What is the worst thing that can happen when there is a conflict in the team? What kind of experiences we have with the conflict that make us think and behave in a certain way when one appears?

Why do we avoid conflict?

The real question should be: why do we avoid doing things in overall?

  • We have bad experiences from the past. We wanted to share a great idea with somebody, and as a response we got yelling and then being ghosted for a week. We gave feedback, with a good intention so a person can grow, and as a response we got attack and aggression. Based on that kind of experiences we decide (sometimes on the unconscious level) that we are not going to expose ourselves to those reactions. So, we just stop doing it, since it brought us more harm than good in the past.
  • Other people think that we should stay low. How many times did you hear: “stay low, don’t put yourself out there” or “maybe it’s not perfect, but at least you have a peace and quiet of mind”. Or “you should be happy about what you have, don’t risk it”. Speaking up requires putting ourselves in the spotlight and even when we just want to share another point of view, or we want to improve a way of working, there is always a risk of being somehow judged or attacked by people. If others are afraid of that kind of courage of speaking up, they will project this fear on us: just to make sure that nobody gets hurt (twisted logic). And if we trust those people, it’s a huge chance that we will listen to them and resign from making a change.
  • We have our own beliefs about something. What do you think about conflict: is it a good or a bad thing? Or maybe it depends? If we were exposed (as children and then, as adults) to the conversations where other people were discussing that a conflict is the worst thing that can happen and we should avoid it because it never brings anything good, how on Earth can we be open to it? It’s almost impossible, since our brain is soaked with this narrative and doesn’t have any other data that it can rely on to create a new belief. It’s applicable to every single thing that we avoid: we don’t do it, because our brain “protects” us from being hurt by potential consequences of that kind of decision.

In the area of conflicts, it’s extremely visible: we avoid it, because we burned ourselves once or twice. Based on that we make this strategy to not get involved in any kind of “risky” situation: so, we sit quiet and just focus on living through another day. Is it really the best option we can get?

When a lack of conflict is dysfunctional, not the other way around?

One of the biggest experts of team development and leadership, Patrick Lencioni, years ago wrote a book “5 Disfunctions of a Team”. It is a really short story (doesn’t even look like a personal/professional development book), yet it’s very powerful. And there is one part that stopped me when I first read it: Lencioni says that one of the dysfunctions of a team is a fear of conflict.

What?

(On the chart on the left-hand side there are definitions of all disfunctions and on the right-hand side there are solutions, that answer the questions: what is the best thing we can do here for our teams?)

If we stick to our old believe that a conflict is something negative and destructive – that it ruins the trust and good atmosphere in the team, how is it possible that it’s actually the other way around?

When we avoid conflict, not speaking up and be open about what do we really think, feel, or observe in the workplace, there is a huge risk of not being as effective and efficient as possible. It’s also short sided: if we are not sharing it now, it’s going to backfire in the future. So, at the end of the day, it will bring worse result than we imagine now. What’s even worse, people probably will talk behind other colleagues’ or leader’s backs, and not saying anything out loud. We can imagine that it will bring even worse outcomes, like really ruining the atmosphere, creating space for psychological games and in a consequence: lack of trust.

The fear of conflict can be one of the biggest barriers that will stop people from growth, thrive and being the best versions of themselves in a workplace. What can we do to change this mindset?

How can we use conflict that nourishes our team?

The key thing to understand is that a certain kind conflict is something that we can use. Sometimes it is, sometimes it isn’t, it really depends on what we are dealing with.

There are 2 categories of conflicts, I call them functional and dysfunctional.

  • Functional conflicts are when there is a space for people to have a discussion, create a new product, service or idea that can be reshaped in something groundbreaking. It happens when two (or more) people are really passionate about what they do, and they want to create the biggest possible value for others. If you are a manager, you can use this occasion to create a safe environment, where people can discuss with a minimized risk of having a destructive argument. That way you make sure that they have a contract for this discussion, good intention of creating something, not to be mean to each other (or prove the other person that their point of view is worse or not worth anything at all). Be a moderator, guard of the conversation, support when needed and make sure that the conversation nourishes both sides.
  • Dysfunctional conflicts are when they fit into one of the types on the Wheel of Conflict (created by Christopher Moore).

  • Conflict of data is when we miss some pieces of information. It’s like having an Excel spreadsheet where there are blanks in some cells and in consequence formulas don’t work. It can also happen when two people understand one thing in a different way (have different frame of reference).
  • Conflict of structure is when there is a lack of clear scope of responsibilities between people/teams, the processes or policies are not working (or they don’t exist at all). It can also happen when there is a lack of contract (we don’t know who is responsible for what, when and why).
  • Conflict of interest is when one side has their own goals that are contradictory to those that the other side has. A great example is a salesperson and a service person: the first one’s goal is to sale as much as possible, and the second person is responsible for the best quality of service, while taking care of the same customer. The first one has bonus from each customer, and the other has a bonus from not-returning-with-questions clients. Completely different focus.
  • Conflict of values is when we have religious or political differences, that are influencing our ways of living or are a base of what is important and not-negotiable for us. This type of conflict is not solvable, we can only agree to not bring those subjects to the conversation or mediate when it influences our workspace somehow.
  • Conflict of relations is at the end of the cycle. The interesting thing is when we think about conflicts, the first thing that comes to our mind is “people are not communicating well” or “they don’t like each other” – we don’t dig deeper into first four types of conflict. The truth is that conflict of relations is at the very end, mostly as consequence of one (or more) of the previous ones. It’s happening when we communicate badly, we use stereotypes in our way of thinking, can’t deal with strong emotions that we experience, or we repeat other negative behaviors.

What can we do with the dysfunctional conflicts? First and foremost: we need to map and name correctly which conflict is the real one in the situation we are dealing with. Without that, even the most beautiful strategy is not going to work, because we are going to answer to the wrong need. We’ll get frustrated and use all our energy badly. Focus on investigating will bring the best results, since then the solutions will be to the point: it’s more than certain that it’s worth investing time in this process.

The bottom line

The conflict is a huge, hairy, and scary thing that we often have very strong convictions about. We avoid it, by staying low, don’t speak up to not get into any confrontation. We do it because we don’t want to get hurt, expose ourselves to bad emotions, stress or feeling that we do not belong. Perfectly natural, there is nothing to be ashamed of.

When we make a mindset shift: from fixed (focused on avoiding conflict) to a growth one, where we take into consideration that the conflict can be good for us, nourishing and interesting, we can gain more than we think. With remembering about having a good intention, being in OK-OK zone and with a goal of creating something extraordinary as a consequence of a passionate discussion, we can achieve the outcome that won’t be possible to achieve on our own.

It puts old, good conflict in a completely new light. I believe it’s worth trying if it fits.

Udostępnij

Komentarze

0 0 votes
Article Rating
Subscribe
Notify of
0 komentarzy
Oldest
Newest Most Voted
Inline Feedbacks
View all comments

Czytaj także

Leadership

Mastering Problem Solving: How to Save Time and Adapt

As a leader, you’re no stranger to problem-solving. It’s the bread and butter of leadership, the skill that keeps the wheels turning and the team moving forward. But here’s the thing: not all problems are created equal, and neither are the people solving them. One-size-fits-all solutions? They’re a myth. To truly master problem-solving, you need to understand your team, their preferences, and how to flex your approach. Let’s dive into how tailoring problem-solving strategies can transform your leadership game and strengthen your Communication Intelligence (CQ) muscle.     The PCM Lens: Why Preferences Matter in Problem Solving?   The Process Communication Model (PCM) teaches us that people have different personality base types, and those types influence how they prefer to face challenges. Some thrive in solitude, needing quiet time to think through problems on their own. Others prefer the intimacy of a 1:1 discussion, where they can bounce ideas off one person. Then there are those who light up in group settings, energized by collaboration and collective brainstorming. Add in the variables of virtual versus in-person environments, and you’ve got a spectrum of preferences that can make or break your problem-solving efforts. As a leader, recognizing these differences isn’t just nice-to-have—it’s essential. For example, forcing an Imaginer into a high-energy group brainstorming session might literally kill them, and they remain silenced, while expecting a Rebel to solve a problem alone at their desk could leave them disengaged. Understanding these nuances is part of building your CQ muscle—the ability to adapt your communication style and approach based on the needs of others.   The High Stakes of Ignoring Problems   Before we explore tools and strategies, let’s talk about what happens when leaders don’t address problems effectively—or worse, when they ignore them altogether. Unresolved problems rarely solve themselves; instead, they keep getting bigger and bigger. Small issues snowball into larger ones, creating inefficiencies, damaging trust, and eroding team morale. The costs? Missed deadlines, killed relationships, lost revenue, and even high level of voluntary turnover. No to mention toxic atmosphere, people not talking to each other, not exchanging ideas or sharing knowledge. Sounds like a long list of different cost that’s not going to be easy to rebuild. On the flip side, a proactive and tailored approach to problem-solving not only resolves immediate issues but also builds a culture of trust and collaboration. When your team sees that you’re invested in solving problems in ways that work for them, they’re more likely to engage fully and bring their best selves to the table.   Problem Solving as a CQ Superpower   Problem-solving is more than just a technical skill; it’s a core component of Communication Intelligence (CQ). Leaders with high CQ don’t just focus on what needs to be solved—they think about how to solve it in ways that resonate with their team. This means asking questions like: – Who needs to be involved in this process? – What environment will help us tackle this effectively? Which tools and approaches will be the worst? – How can I adapt my approach to fit the preferences of my team members? What can I do to involve them in the process?   By flexing your CQ muscle, you’re not just solving problems—you’re strengthening relationships, building trust, and create a culture where everyone feels heard.   Tailoring Your Problem-Solving Approach   So how do you put this into practice? Here are some tools and strategies for addressing problems in different setups:   Solo Problem Solving For team members who prefer working alone, give them space and time to process independently. It’s not about them being weirdos, it’s just their preference. Provide clear instructions and context, then let them take ownership of the task. Tools like project management software (i.e. Trello or Asana) can help track progress without micromanaging. You can create an online wall (i.e. on MIRO) so people can work together asynchronously in their own time and space. Set some deadlines and time for check ins.   1:1 Problem Solving Some people thrive in 1:1 settings where they can discuss ideas openly without the pressure of a group. Use this time to ask open-ended questions and actively listen to their perspective. If their preference is for you to be more direct, set the sentences straight, clear and transparent so there’s no time wasted in the middle of the process to guess what you aim here for. You can also use tools like 5 (or 7) Why, Problem Framing, Ishikawa Diagram or any other Lean tools or techniques. Make sure that you’re solving the real problem that is a root cause of your current situation.   Group Problem Solving Group settings work well for those who feed off collaboration and collective energy. Facilitate brainstorming sessions or workshops where everyone can contribute ideas. Tools like whiteboards (physical or digital) or platforms like MIRO can help visualize ideas in real time. You can also use the group problem-solving methods, like Action Learning to be as effective and efficient as possible. Action Learning is a method where the group of 4-8 people sit together (online or onsite) for 1,5-hour session where one person brings a problem to solve. The group is responsible for asking questions, share their insights and create potential solutions for the problem presenter. It’s a very intense yet extremely productive session where the group is completely focused on the process of solving the issue, without distractions or doing something else in the same time. The power of this method is that people are all involved in the process, they are learning on the way and support each other. So the pros and more than just problem solved; there’s also a positive influence on knowledge sharing practices, relationship building, trust, psychological safety, reliability within a group or organization, using the variety of points of views, experiences, perspectives and talents. Action Learning is one of the best group methods to solve problems that I know and practice. Groups that I work with within this method are

Czytaj dalej
Leadership

3 Leadership Lessons I Learned from Bad Recruitment Processes

Recruitment is often described as both an art and a science—a delicate balance of intuition, data, and strategy. But sometimes, even with the best intentions, things can go awry. I’ve learned this the hard way. Over the years, my experience in leadership have taught me that recruitment mistakes are not just costly in terms of money but also in terms of time, energy, and efficiency. Today, I want to share with you three of my biggest lessons from bad recruitment decisions that I hope will help you to not repeat those in your leadership practice.   #1 The Rush: When Speed Wins With Strategy   There was a time when I was desperate to fill a position on my team. Aren’t we really in constant situations like that? I remember that we had a critical project coming up, I was drowning under the amount of tasks I had on my list and I convinced myself that having “someone”—anyone—on board quickly was better than waiting for the better fit. I rushed through the process, skipping some of the deeper evaluations and settling for a candidate who seemed “good enough.” The result? It ended up costing me more than I ever anticipated. The person lacked the skills and mindset needed for the role, and within six months, we had to part ways. Not only did this mean starting the recruitment process all over again, but it also disrupted my work, again.     According to research by the Society for Human Resource Management (SHRM), the average cost per hire is around $4,700. However, if you make a bad hire, the costs skyrocket. Studies estimate that replacing an employee can cost anywhere from 8 to 12 months of their salary. For example, if you hire someone with an annual salary of $50,000, replacing them could cost you between $33,000 and $50,000. And that’s just the financial side—what about the lost productivity and influence on yourself? On the team? This experience taught me a crucial lesson: rushing to fill a position is like building a house on quicksand. It may seem like you’re saving time in the short term, but in reality, you’re setting yourself up for long-term instability.   #2 The Bias Trap: Judging by Brands, Not Skills   Another mistake I’ve made is being overly impressed by the organizations listed on a candidate’s CV. When someone came from a big-name company or a well-known brand, I found myself assuming they must be ready to do the job. After all, if they worked at such prestigious places, they must be highly capable, right? Wrong.  One candidate I hired had an impressive resume filled with experience at top-tier organizations. I was so dazzled by their background that I overlooked some red flags during the interview process—things like their lack of enthusiasm for the role or their vague answers about past achievements. It turned out that their success in previous roles was largely due to the systems and teams already in place at those organizations. In my smaller, more dynamic team, they struggled to adapt and contribute effectively. This mistake taught me to focus on the specific person, not just their past affiliations. A brand name on a CV doesn’t guarantee a cultural, personality-based or skill set fit for your organization. Now, I dig deeper during interviews, asking specific questions about their contributions and how they handle challenges in different environments.   #3 Ignoring the Personality Match   As someone deeply invested in Communication Intelligence (CQ) and the Process Communication Model (PCM), I know how critical personality dynamics are in any working relationship. Yet, there have been times when I ignored this knowledge during recruitment—and paid the price for it. I once hired someone who looked perfect on paper: they had the right skills, experience, and even glowing references. But what I failed to assess was how well we would work together on a personal level. Our communication styles clashed almost immediately. Where I value directness and proactive problem-solving, they preferred a more passive approach and avoided conflict at all costs. Data vs emotions. Logic vs relationship care. Nothing wrong about that, don’t get me wrong! But it comes with a cost, especially when you work in a small setup. This mismatch didn’t just affect our one-on-one interactions; it also impacted the overall efficiency. When there isn’t alignment between a leader and their team members, it creates friction that slows down decision-making and execution. According to Gallup research, disengaged employees can cost organizations up to 18% of their annual salary in lost productivity. Imagine what happens when that disengagement spreads across an entire team! Now, I make personality assessments a non-negotiable part of my recruitment process. Tools like PCM are there to use: I’m not saying that you do a questionnaire for every single candidate since it’ll cost a lot (if you can afford it, go for it!). It’s about using the framework in practice. Listen, observe, connect the dots. Everything is there, you just need to know what you’re looking for.   Moving Forward: How to Avoid These Pitfalls    Here’s what I’ve learned to do differently: Prioritize Fit Over Speed: Take the time to find someone who aligns with your team’s needs and culture—even if it means extending your search timeline. Remember that fast recruitment can cost you so much more time in the future. Dig Deeper Into Experience: Don’t be swayed by big names on a CV; focus on understanding what the candidate actually contributed in their previous roles. Assess Personality Compatibility: Use tools like PCM or other personality assessments or knowledge from the framework to ensure alignment between you and your potential hire. Recruitment is never going to be an exact science, but by learning from past mistakes and implementing more thoughtful strategies, you can significantly improve your chances of finding the right person for your team—and avoiding costly missteps along the way.   Final Thoughts    As leaders, we often feel immense pressure to make quick decisions and keep

Czytaj dalej
Leadership

Mastering Tough Conversations: A Tech Leader’s Guide to 1:1s (That Nobody Really Wants to Lead)

As a tech leader, you’re no stranger to challenges—tight deadlines, complex projects, and ever-evolving technology are part of the job. But one of the most delicate challenges you’ll face doesn’t involve code or systems; it involves people. Leading tough conversations with employees is an essential skill that separates good leaders from great ones. Whether it’s addressing underperformance, delivering hard feedback, or navigating team conflicts, these moments can define your leadership. This guide equips you with actionable tools to lead tough conversations effectively, using a structured approach that combines contracting, Communication Intelligence (CQ), including the Process Communication Model (PCM). Let’s dive in.   When Tough Conversations Are Necessary: Scenarios You’ll Encounter   Before we get into the how, let’s identify the when. Here are common situations where a tough conversation might arise: Underperformance: An employee is consistently missing deadlines or delivering work in a quality we agreed on. Behavioral issues: A team member exhibits disruptive behavior, such as frequent conflicts with peers or unprofessional communication. Career Development: You need to inform an employee that they didn’t receive a promotion or that their role is changing. Restructuring: Delivering news about layoffs or departmental changes. Personal Concerns: Addressing sensitive issues like burnout, mental health, or personal struggles impacting performance.   Each of these scenarios requires a thoughtful approach to ensure the conversation is productive and respectful. And none of those are easy: there’s no one-size-fits-all approach so it might sound like a hell to a tech leader. But we have some algorytms that you can use to run the meeting with success.   The Framework: Contracting, CQ, and PCM   To handle these conversations effectively, use three elements to have a success no matter what kind of situation you are facing. Contracting: Establish clear agreements on three levels—administrative, professional, and psychological. You have more about the contracting itself, the levels and what to do to make sure the contract is fully covered in this article. Communication Intelligence (CQ) muscle: Flex your communication style to meet the employee where they are emotionally and mentally. Managing reactions that are always emotional (you like it or not) is our job as leaders: we need to know what triggers which behavior and what to do to overcome or address it when it appears. Process Communication Model (PCM) Framework: Tailor your approach to the employee’s personality base for maximum impact. Match the language and way of communication they need, not your favorite ones. That’s crucial for the conversation to be successful: you’re leading it for them, not for yourself.   Part 1: Contracting—Setting the Stage for Success   Contracting involves creating clarity and mutual understanding before diving into the conversation. What are the essentials of 3 levels that are inside? – Administrative Contracting: Define the logistics. Where will the meeting take place? How long will it last? What’s the agenda? Example: “Let’s meet in my office at 2 PM for 30 minutes to discuss your recent project performance.” Take care of this during and after as well. “What is the deadline to implement what we’re talking about?” – Professional Contracting: Clarify roles and expectations. Emphasize that this is a professional discussion and its goal is to find solutions, not to blame anybody for anything. Example: “My role is to provide feedback and support you in improving; I would like for your role to share your perspective and be engaged in the next steps we are going to create together during this meeting.” – Psychological Contracting: Set the emotional tone by creating a space for a person. Acknowledge that the conversation might be difficult but make sure you are focused on the positive outcome. Example: “I know this might be uncomfortable, but I want you to know this is coming from a place of support and wanting to help you succeed.”   Part 2: Flex Your CQ Muscle   Communication Intelligence (CQ) is your ability to adapt your communication style based on the situation and the other person’s needs and preferences. In tough conversations, this means balancing focus with accountability. What are the easiest 3 things that you can do as a leader to make sure you’re using your CQ muscle? – Listen Actively: Truly hear what the employee is saying without interrupting or jumping to conclusions. Make notes. Paraphrase, check if you understand as your employee intended you to. Don’t assume, ask. – Acknowledge Emotions: If the employee feels upset, angry or defensive, name the emotion without judgment. Example: “I can see this feedback is frustrating for you.” or “I understand that situation is infuriating.” Don’t underestimate the state, let it be, check what kind of information is hidden below this emotion. Use it in the solution creation phase. – Stay Calm and Focused: Keep your tone steady and avoid escalating tension, even if emotions run high. I know that’s one of the hardest things to do: most of the time we go angry when the other person is angry. We mirror each other, that’s how our brain is wired. But by being conscious of that, we can stop the automatic pattern and break it by being more mindful and goal-oriented. When you observe something like that, say to yourself: “What is the goal of this conversation? What I want to achieve here?” That kind of reminder is going to take you back to the OK-OK state and continue with more clear view of mind.     Part 3: Tailor Your Approach with PCM—Speak Their Language   The Process Communication Model (PCM) identifies six personality types, each with unique communication preferences and stress patterns. Understanding these types allows you to tailor your message effectively. Here’s a quick breakdown: Thinker: Logical, organized, values data and structure. – Approach: Be clear, factual, and provide detailed explanations. – Stress Behavior: May become overly critical or perfectionistic, attack others for lack of thinking or logical approach.   Persister: Principled, dedicated, values integrity and commitment. – Approach: Appeal to their sense of purpose and principles. – Stress Behavior: May become judgmental or

Czytaj dalej
0
Would love your thoughts, please comment.x
()
x