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

Why Habits Are Better Than Goals: A Guide for Leaders

As technology leaders, we live in a world driven by deadlines, KPIs, and ambitious goals. We’re taught to set objectives and measure progress. But what if I told you that focusing on habits rather than goals might be the game-changer you’ve been looking for? Especially if you’re struggling to find time for your own professional development or noticing low engagement within your team, shifting your mindset to prioritize habits could transform not only your leadership but also your entire organization. Let’s explore why habits are more powerful than goals and how they can help you lead with greater impact. The Problem with Goals   Goals are seductive. They promise a future where everything is better: you’ve mastered a new skill, your team is more engaged, or you’ve finally achieved that elusive work-life balance. But here’s the catch: goals are outcome-focused. They emphasize the “what” rather than the “how”. For example, let’s say your goal is to improve team engagement. You might set metrics like increasing participation in meetings or boosting employee satisfaction scores. But once you hit those targets, what happens next? Without a system in place, the progress often stalls or even reverses. Goals also have an inherent flaw: they’re temporary. Once achieved, they leave a void. This is why so many of us experience the post-goal slump: a sense of “what now?” after crossing the finish line. Moreover, as busy technology leaders, goals can feel overwhelming. When your calendar is already packed with back-to-back meetings and project deadlines, adding another goal to the mix can feel like just another task on an endless to-do list.   Why Habits Are the Better Alternative?   Habits, on the other hand, focus on the process. They are small, consistent actions that compound over time to create meaningful change. Instead of chasing a distant outcome, habits anchor you in the present and guide your daily behavior. Here’s why this matters: Habits Build Identity. While goals are about achieving something external, habits shape who you are. For example, instead of setting a goal to “become a better communicator,” you could develop the habit of asking open-ended questions during one-on-one meetings. Over time, this habit reinforces your identity as a leader who listens and connects deeply with their team. Habits Are Sustainable. Unlike goals, which have an endpoint, habits are ongoing. They create a foundation for continuous improvement without requiring constant resets. A habit like setting aside 15 minutes every day for professional reading or reflection becomes part of your routine:no extra mental energy required. Habits Reduce Decision Fatigue. As a leader, you make countless decisions every day. Habits automate certain behaviors, freeing up mental bandwidth for higher-priority tasks. For instance, if you establish a habit of starting each morning by reviewing your team’s priorities, you don’t have to waste time deciding how to begin your day: it’s already decided for you. Habits Drive Engagement. When it comes to team dynamics, habits can be contagious. If you consistently model behaviors like active listening or celebrating small wins, your team is likely to adopt those practices as well. Over time, these shared habits create a culture of engagement and collaboration without requiring constant top-down interventions.     How to Build Habits That Stick?   Now that we’ve established why habits are so powerful, let’s talk about how to build them effectively. Here are some practical steps tailored for busy technology leaders: #1 Start Small One of the biggest mistakes people make is trying to change their entire routine overnight. Instead, focus on one small habit at a time. For example, if you want to prioritize professional development, commit to reading just one article or watching one TED Talk per week. Once this becomes second nature, you can build on it. #2 Anchor New Habits to Existing Routines Habits are easier to establish when they’re tied to something you already do regularly. For instance, if you want to foster better communication with your team, make it a habit to ask for feedback during your weekly check-ins. The check-in is already part of your routine; now it has an added layer of intentionality. #3 Focus on Systems, Not Outcomes Instead of obsessing over results, concentrate on creating systems that support your desired behavior. For example, if you want to encourage innovation within your team, implement a habit of dedicating 10 minutes at the end of each meeting for brainstorming new ideas. #4 Track Progress and Celebrate Small Wins While habits don’t rely on external validation like goals do, tracking your progress can still be motivating. Use apps or simple checklists to monitor consistency and celebrate milestones along the way. #5 Be Patient and Consistent Habits take time to form: research suggests anywhere from 21 days to several months depending on the complexity of the behavior. Don’t be discouraged by setbacks. Focus on consistency over perfection.   The Ripple Effect of Habits in Leadership   When you embrace habits as a leader, the benefits extend far beyond your personal growth: they ripple out to your entire team and organization. Here are some examples: Improved Team Engagement. By modeling habits like regular recognition or transparent communication, you create an environment where team members feel valued and motivated. Greater Innovation. Small habits like encouraging questions or dedicating time for creative thinking can spark breakthroughs that drive your projects forward. Stronger Relationships. Consistent habits like active listening or showing empathy build trust and strengthen connections with both colleagues and stakeholders. Most importantly, focusing on habits helps you lead by example. It shows your team that growth isn’t about chasing lofty goals but about showing up every day with intention and purpose.   A Challenge for You!   As you reflect on this article, I want to leave you with a simple challenge: choose one habit that aligns with your leadership vision and commit to practicing it consistently for the next 30 days. It could be as simple as starting each day with five minutes of mindfulness or ending each meeting

Czytaj dalej
Leadership

Communication Intelligence (CQ): A Key to the Effective Leadership

In the ever-evolving landscape of work, where collaboration and innovation are necessary to survive on the demanding market, one skill stands out as a game-changer: Communication Intelligence (CQ). As a tech leadership expert and someone deeply invested in helping leaders and teams create environments where people thrive, I cannot stress enough the importance of mastering CQ. It’s not just about talking or listening; it’s about understanding, tailoring, and connecting. Let’s dive into what CQ is, why it matters, and how we can build this skill: both as leaders and team members.   What Is Communication Intelligence (CQ)?   At its core, Communication Intelligence (CQ) is the ability to adapt your communication style to connect effectively with others. It’s about being aware of your own communication tendencies while recognizing and responding to the diverse preferences of those around you. Think of it as emotional intelligence (EQ) but focused specifically on how we exchange information, ideas, and emotions. CQ involves empathy, adaptability, and clarity. It’s not just about what you say but how you say it—and how it’s received. Mastering CQ means being intentional in your interactions and ensuring that your message resonates with the person or people on the other side.   Why Is CQ Essential for Leaders and Team Members?   In my work with leaders and teams, I often see how miscommunication can ruin even the best intentions. A lack of CQ can lead to misunderstandings, conflict, and disengagement. On the flip side, strong CQ fosters trust, collaboration, and alignment: key ingredients for both thriving teams and great business results. Here’s why CQ is crucial: #1 For Leaders: they set the tone for communication within their teams. If a leader lacks CQ, they risk alienating team members, failing to inspire, or unintentionally creating a culture of fear or confusion. Leaders with high CQ can tailor their messages to motivate diverse individuals, navigate difficult conversations with grace, and build an environment where everyone feels heard and valued.   #2 For Team Members: in a team setting, CQ helps individuals collaborate more effectively. When team members understand each other’s communication styles, they can avoid unnecessary friction and build stronger relationships. High CQ also empowers individuals to voice their ideas in ways that resonate with others, fostering innovation and mutual respect. Understanding what high CQ looks like (and what it doesn’t) is key to developing this skill. Let’s explore some examples and anti-examples.   Examples of High CQ Behaviors: – active listening: truly hearing what someone is saying without interrupting or jumping to conclusions to soon, – tailoring messaging: adapting your tone, language, or delivery based on the audience. For instance, explaining a technical concept in simple terms for a non-technical stakeholder, – understanding in action: acknowledging someone’s emotions and needs before moving to problem-solving. For example, saying, “I can see this situation has been frustrating for you” before diving into solutions, – clarity in feedback: providing constructive feedback that is specific, actionable, and framed positively. And what’s even more: giving people space to take it in and make a decision what they want to do with it (take or discard), – proactive negative conflict resolution: addressing misunderstandings early rather than letting them grow and eat people alive. And remembering that not all conflicts are bad (actually a fear of conflict is one of the 5 Dysfunctions Of The Team by Patrick Lencioni).   Anti-Examples of Low CQ Behaviors: – interrupting or talking over others: this signals a lack of respect and can shut down meaningful dialogue. It also means that you don’t care about the other person, or anything they say or think, – one-size-fits-all communication: using the same approach for everyone without considering individual preferences or needs. There’s only 17% of chances that the person next to you prefers your communication base. That’s why listening and tailoring is so important: to get the stakes higher than that, – ignoring non-verbal cues: overlooking body language or tone that suggests someone is uncomfortable or disengaged. We have 4 things we can observe: mimics, ton of voice, gestures and posture. Ignoring those non-verbal imformation is going to cost us a lot, – defensiveness in feedback: reacting negatively when receiving constructive criticism instead of seeking to understand, ask more questions, be curious about what the other person wants to say to me, – avoiding difficult conversations: failing to address issues directly, leading to confusion or resentment. And the further it goes, the worse it becomes: it’s really difficiult to stop the huge snowball. So what we can do to avoid those anti-examples?   Use PCM to Build it!   One of the most effective tools I use when working with leaders and teams on CQ is the Process Communication Model (PCM). PCM provides a framework for understanding different personality types and their communication preferences. It’s like having a map that helps you navigate the complexities of human interaction. So why PCM is a good idea to support buildling a high CQ level? It gives you bigger self-awareness: start by identifying your own dominant personality type. This helps you understand your natural communication style and potential blind spots. With whom it’s super easy to go with and when it will be a bigger challenge. It equips you with higher ability of observation: pay attention to the verbal and non-verbal cues of others to identify their preferred communication style. For example: – A Thinker might appreciate detailed agendas and logical arguments. – A Harmonizer may respond better to warmth and emotional connection. It gives you a reason to adapt more: tailor your communication to match the other person’s style. If you’re a Promoter speaking with an Imaginer, slow down and give them time to process rather than pushing for immediate action. It shows you how to practice under stress: PCM also teaches us how stress impacts communication. For instance, under stress, a Thinker might become overly critical, while a Rebel might resort to sarcasm and manipulation. Recognizing these patterns helps us respond constructively rather than

Czytaj dalej
Leadership

3 Lessons on How I’ve Wasted Time as a Leader

As leaders, time is one of our most valuable resources, yet it’s one we often misuse without even realizing it. Reflecting on my own leadership journey, I’ve identified three significant ways I’ve wasted time (at least, so far). These lessons and the things I’ve started to do differently as a positive consequence of them have not only shaped how I lead today but have also helped me become a more effective and focused person. My goal by sharing these lessons is to help you avoid some of the same pitfalls and grow as a leader. Regardless of where you are on your leadership path.   Lesson 1: Waiting for Perfection   One of the earliest and most persistent mistakes I made as a leader was waiting for perfection before making decisions or moving forward. Whether it was launching a new product, rolling out a process change, or even sending an email to the team or organization, I would delay action until I felt everything was flawless. My belief was that perfection equaled success. However, especially in tech world, where innovation moves at lightning speed, waiting for perfection often means missing opportunities or waisted time. I remember one situation vividly when my team had developed a very promising growth program for the leadership team. Instead of releasing an MVP and iterate based on peoples’ feedback, I insisted on refining every detail before launch. By the time we released it, some of the needs where already covered and part of the program was pointless. Solution? My turning point came when I embraced the concept of “progress over perfection.” I began to prioritize speed and adaptability over getting everything right the first time. One of the tools that helped me was implementing agile tools within my team. By breaking projects into smaller, iterative cycles, we were able to deliver value faster and make improvements based on real-world feedback. I also adopted a mindset shift: I stopped seeing imperfection as failure and started viewing it as an opportunity to learn and grow. Now, I encourage people I work with to release early and often, knowing that we can course-correct along the way. This approach has not only saved us time but has also fostered a culture of innovation and showing people that adaptability is the most important thing when we want to achieve a lasting success.     Lesson 2: Looking for an Ideal Candidate   Another way I wasted time as a leader was obsessing over finding the “perfect” candidate for open roles on my team. I would spend months searching for someone who checked every box on the job description: SME skills & knowledge, cultural fit, growth potential. It was only to realize that this person rarely exists. I recall one hiring process where I was looking for a senior facilitator to lead a critical growth project. I turned down several qualified candidates because they didn’t meet my impossibly high standards. In the meantime, the project has begun, I needed to deliver most of the things on my own. I was exhausted, my other tasks were put on hold since it was impossible for me to do everything. I finally made a hire, and it became clear that many of the “must-have” qualities I’d been fixated on weren’t as critical as I thought. Solution? I learned to focus on potential rather than perfection when hiring. Instead of searching for someone who ticks every box, I now look for candidates who demonstrate a growth mindset, strong problem-solving skills, and the ability to adapt to the changing needs of the business.  To make this shift, I changed a little the hiring process to include scenarios and problem-solving exercises that reflect real challenges that we face. This gives me better insight as a leader into how candidates think and approach problems rather than just their resume qualifications. Additionally, I started investing more in onboarding and training. By providing new hires with the tools and support they need to succeed, we’ve been able to develop talent internally instead of waiting for the “perfect” external hire. This not only saves time but also builds loyalty and engagement within the team.   Lesson 3: Focusing on the Wrong Things   As leaders, it’s easy to get caught up in tasks that feel urgent but don’t actually move the needle. For me, this often-looked like micromanaging or spending too much time on operational details rather than strategic priorities. I remember a period when my calendar was packed with meetings about minor issues: approving small budget requests, troubleshooting technical things on the e-learning platform, or reviewing every slide of the training deck. While these tasks felt important in the moment, they distracted me from higher-level responsibilities that nobody can do, but me. The result? Burnout for me and frustration for my team, who felt stifled by my constant involvement in their work. Solution? The first step to breaking this cycle was learning how to delegate effectively. Even if I teach others how to delegate, I sometimes struggle with giving things away since I know exactly how to do them on my own. I realized that by holding onto tasks that others could handle, I was not only wasting my own time but also robbing my team of opportunities to grow and take ownership. I started by identifying tasks that didn’t require my direct involvement and assigning them to team members who were capable (or could become capable with some guidance). To ensure success, I provided clear expectations and allowed space for mistakes. The real space, not only on the paper. If team doesn’t make mistakes that means that they never try doing something new or different. And I don’t want that kind of stagnation and fear in my team. I also adopted a strong system for prioritization. Always using the check point on how this task makes an impact on our goals, we all know how to choose when the task list is endless. This helped me stay aligned

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

New Leadership Online Course!

Do you want to be a leader that people don’t quit?

Check out a Brand New Leadership Online Course!