Conflict Resolution in Project Teams

Stuck in an endless loop of client changes? Lost track of what revision this constitutes? Yeah. Been there. Done that. The secret? It's not about saying no. It's about saying yes to the right things upfront. Every project that goes sideways starts the same way: Vague agreements. Fuzzy boundaries. Good intentions. Six weeks later you're bleeding money and everyone's frustrated. Here's my framework after 30 years of running two 8-figure businesses: The SOW is your salvation. Not some boilerplate template. A real document that covers: • Exact deliverables (not "design work" but "3 homepage concepts, 2 rounds of revisions") • Hours of operation ("We respond M-F, 9-5 PST. Weekend requests get Monday responses") • Revision rounds spelled out ("Round 1 includes up to 5 changes. Round 2 includes 3.") • Feedback cycles defined ("48-hour turnaround for client feedback or the project may be delayed or additional fees may be incurred") But here's what most people miss— Don't work on client notes immediately. Client sends 37 pieces of feedback at 11pm Friday? Producer sends conflicting notes from the CEO? Marketing wants one thing, sales wants another? Stop. Collect everything first. Resolve the conflicts. Get on the phone and discuss it with your client to get alignment. Separate the "have to haves" from the "nice to haves". Then present unified changes. "Based on all feedback received, here are the 8 changes we'll implement. This constitutes revision round 2 of 3." Watch how fast the random requests stop. No extra work that goes unappreciated. No more feelings of being taken advantage of. Communicate before the crisis, prevents the crisis from happening. "Just so you know, we're entering round 2. You have one more included. After that, it's $X per additional round." No surprises. No awkward money conversations. No resentment. Scope creep isn't a them problem. It's a you problem. And that's good news, because that means you are in control. They're not trying to take advantage. They just don't know where the boundaries are because you never drew them. Draw the lines early. Communicate them clearly. Everyone wins. What's your most painful scope creep story? What boundary would've prevented it? Small Business Builders #projectmanagement #clientmanagement #businessgrowth

Conflict is inevitable. How we manage it is both an art and a science. In my work with executives, I often discuss Thomas Kilmann's five types of conflict managers: (1) The Competitor – Focuses on winning, sometimes forgetting there’s another human on the other side. (2) The Avoider – Pretends conflict doesn’t exist, hoping it disappears (spoiler: it doesn’t). (3) The Compromiser – Splits the difference, often leaving both sides feeling like nobody really wins. (4) The Accommodator – Prioritizes relationships over their own needs, sometimes at their own expense. (5) The Collaborator – Works hard to find a win-win, but it takes effort. The style we use during conflict depends on how we manage the tension between empathy and assertiveness. (a) Assertiveness: The ability to express your needs, boundaries, and interests clearly and confidently. It’s standing your ground—without steamrolling others. Competitors do this naturally, sometimes too much. Avoiders and accommodators? Not so much. (b) Empathy: The ability to recognize and consider the other person’s perspective, emotions, and needs. It’s stepping into their shoes before taking a step forward. Accommodators thrive here, sometimes at their own expense. Competitors? They might need a reminder that the other side has feelings too. Balancing both is the key to successful negotiation. Here’s how: - Know your default mode. Are you more likely to fight, flee, or fold? Self-awareness is step one. - Swap 'but' for 'and' – “I hear your concerns, and I’d like to explore a solution that works for both of us.” This keeps both voices in the conversation. - Be clear, not combative. Assertiveness isn’t aggression; it’s clarity. Replace “You’re wrong” with “I see it differently—here’s why.” - Make space for emotions. Negotiations aren’t just about logic. Acknowledge emotions (yours and theirs) so they don’t hijack the conversation. - Negotiate the process, not just the outcome. If you’re dealing with a competitor, set ground rules upfront. If it’s an avoider, create a low-stakes way to engage. Great negotiators don’t just stick to their natural style—they adapt. Which conflict style do you tend to default to? And how do you balance empathy with assertiveness? #ConflictResolution #Negotiation #Leadership #Empathy #Assertiveness #Leadership #DecisionMaking

In the last major internal conflict I had, I stopped and thought: am I the first one to live this?! Hostility. Threats. Ah, and I was in the car on the way back from the hospital from giving birth. Nice welcome back 😂 Managers spend up to 40% of their time handling conflicts. This time drain highlights a critical business challenge. Yet when managed effectively, conflict becomes a catalyst for: ✅ Innovation ✅ Better decision-making ✅ Stronger relationships Here's the outcomes of my research. No: I wasn't the first one going through this ;) 3 Research-Backed Conflict Resolution Models: 1. The Thomas-Kilmann Conflict Model (TKI) Each style has its place in your conflict toolkit: - Competing → Crisis situations needing quick decisions - Collaborating → Complex problems requiring buy-in - Compromising → Temporary fixes under time pressure - Avoiding → Minor issues that will resolve naturally - Accommodating → When harmony matters more than the outcome 2. Harvard Negotiation Project's BATNA Best Alternative To a Negotiated Agreement - Know your walkaway position - Research all parties' alternatives - Strengthen your options - Negotiate from confidence, not fear 3. Circle of Conflict Model (Moore) Identify the root cause to choose your approach: - Value Conflicts → Find superordinate goals - Relationship Issues → Focus on communication - Data Conflicts → Agree on facts first - Structural Problems → Address system issues - Interest Conflicts → Look for mutual gains Pro Tips for Implementation: ⚡ Before the Conflict: - Map stakeholders - Document facts - Prepare your BATNA - Choose your timing ⚡ During Resolution: - Stay solution-focused - Use neutral language - Listen actively - Take reflection breaks ⚡ After Agreement: - Document decisions - Set review dates - Monitor progress - Acknowledge improvements Remember: Your conflict style should match the situation, not your comfort zone. Feels weird to send that follow up email. But do it: it's actually really crucial. And refrain yourself from putting a few bitter words here and there ;) You'll come out of it a stronger manager. As the saying goes "don't waste a good crisis"! 💡 What's your go-to conflict resolution approach? Has it evolved with experience? ♻️ Share this to empower a leader ➕ Follow Helene Guillaume Pabis for more ✉️ Newsletter: https://lnkd.in/dy3wzu9A

Navigating Team Conflicts In team dynamics, some level of conflict is inevitable—even healthy. However, understanding the nature of the conflict can help leaders manage and resolve it more effectively. Here are four common conflict patterns and strategies for handling them: 1. The Solo Dissenter This conflict arises when one individual disagrees with the rest of the team. Whether due to personal differences or a challenge to the status quo, isolating or scapegoating this person is counterproductive. Instead, leaders should engage in one-on-one conversations to better understand their perspective and address any underlying concerns. Open communication can transform a dissenter into a valuable source of alternative viewpoints and broader system awareness. 2. The Boxing Match This frequent form of conflict involves a disagreement between two team members. If the issue stems from a personal relationship, external coaching may be helpful. However, if it’s task-related, the disagreement may benefit the team by introducing diverse ideas—provided the discussion remains civil. Leaders should avoid intervening prematurely, as genuine task-based disagreements often lead to more innovative solutions. 3. Warring Factions When two subgroups within the team oppose each other, an "us versus them" mentality can develop. This type of conflict is more complex, and solutions like voting or majority rule rarely resolve the issue. Leaders should introduce new options or third-way alternatives, encouraging both sides to broaden their thinking and find a compromise that addresses the core needs of both groups. 4. The Blame Game This challenging conflict involves the entire team, often triggered by poor performance. Assigning blame worsens the situation and creates more division. A more effective approach is to refocus the team on collective goals and explore strategies for improvement. Shifting the conversation from blame to team purpose and collective problem-solving can unite the group around a shared vision. By recognizing these conflict patterns and applying the right strategies, leaders can guide their teams through disagreements, fostering a more cohesive and productive environment.

"Conversational Agents as Catalysts for Critical Thinking" Now this is good use of LLMs. A conversational AI acting as a devil’s advocate can improve group decision-making by subtly reshaping social dynamics, challenging dominant opinions and enabling more inclusive perspectives. There is great potential in AI "nudging" more useful human group collaboration, in everything from student work through board discussions. There has been some interesting work and research in the space, but it is limited and there needs be more. This research study (link in comments) showed: 🧠 AI enhances decision quality and process satisfaction. The AI-generated counterarguments led to significant improvements in how participants rated the decision-making process (5.10 to 5.55) and outcomes (5.31 to 5.89) on a 7-point scale. These gains came without significantly increasing cognitive workload, suggesting AI can enrich discussions without overburdening participants. 😊 Juniors felt more heard, seniors stayed satisfied. Junior (minority) members saw the biggest boost: process satisfaction rose by 0.76 and outcome satisfaction by 0.88. Meanwhile, senior (majority) members maintained high satisfaction across both conditions, indicating the AI helped juniors speak up without alienating others. 🙅♂️ AI reduced pressure to conform. The system’s devil’s advocate role legitimized dissent, encouraging minority opinions and mitigating groupthink. Juniors reported feeling “less isolated,” with the AI helping to shift group norms toward more inclusive deliberation. 🛠️ Success depends on timing, tone, and adaptability. The system worked best when its counterarguments were well-timed, empathetic, and contextually aware. Its greatest impact was not in changing decisions, but in enabling more open, balanced, and confident dialogue—especially from those with less power in the room.

UNPOPULAR OPINION: If your workplace has no conflict, it’s probably underperforming. 👇🏼 When you imagine a great work environment, you probably think of: ✅Good communication ✅Shared goals ✅Mutual respect ✅Motivated people One thing rarely makes the list: Conflict. Yet research shows that the highest-performing teams don’t avoid conflict — they practice the right kind of conflict. Researchers call it “constructive controversy.” The problem isn’t disagreement. The problem is what happens when disagreement stays hidden. Too often, conflict gets pushed underground. Instead of becoming a productive force that sharpens ideas and improves decisions, it quietly turns into: • Tension • Resentment • Politics • Slower progress • Weaker trust Silence doesn’t create harmony. It creates blind spots. So how do leaders actually build healthy conflict into their teams? Amy Gallo, author of Getting Along: How to Work with Anyone (Even Difficult People), offers a few powerful principles: 1. Make it safe to speak up. Disagreement isn’t disloyalty. Staying silent when you see a problem doesn’t help you — or the team. Normalize respectful dissent. 2. Pay attention to what’s really happening. Cultural shifts create discomfort. Watch body language. Listen for hesitation. Invite feedback from people who will tell you the truth. 3. State your intentions upfront. Being challenged — especially by a leader — can feel threatening. Clarify what the conversation is and what it isn’t before it begins. There’s no such thing as a conflict-free relationship. There’s only healthy conflict or unhealthy conflict. The teams that grow fastest don’t eliminate tension. They channel it. They use disagreement to sharpen thinking, surface blind spots, and build stronger solutions together. Maybe the goal isn’t more comfort at work. Maybe it’s more courage. ✅More honest conversations. ✅More productive friction. ✅More trust built through respectful challenge. Because progress rarely comes from everyone nodding in agreement.

Conversations that pull others down might feel insignificant in the moment, but they quietly shape the culture around us. Left unchecked, they create pockets of mistrust, trigger unhealthy competition, and eventually drag down the performance of even the strongest teams. Our role is to notice these early signals, address them with clarity, and reinforce an environment where people feel safe to speak up and show up as their best selves. A few practical reminders that help anchor this- What to do: » Encourage direct dialogue. Most issues resolve faster when people speak to each other, not about each other. » Be explicit about cultural expectations. Make it clear that gossip and political behavior have no place in the team. » Lead by example. Every interaction is a signal of what’s acceptable. » Reinforce positive intent. Spotlight honesty, collaboration, and constructive debate. » Build psychological safety. Ensure people can raise concerns without worrying about consequences. What to avoid: » Don’t crack jokes that ridicule people in the name of humor or wit. Trying to be funny at someone’s expense chips away at their self-esteem, strains relationships, and is rarely forgotten. Good humor doesn’t come at the cost of someone’s dignity. » Don’t dismiss small negative behaviors. That’s how they turn into norms. » Don’t indulge in conversations that attack individuals instead of solving problems. » Don’t jump to conclusions. Get the complete picture before forming a view. » Don’t let emotions dictate the response. Stay steady and fair. » Don’t let personal agendas derail collective goals. Teams do their best work when trust is high and politics is low. As leaders, shaping that environment is not a side task—it’s core to how we build sustainable performance. Gaurav Mehta Arnabi Marjit Ashutosh Kotwal Sanjay Mishra Bahar Shaikh Prasad Dixit Turlough Gorman Amy Teresa Adamos Maria C.

Last week, a mentee came to me after her annual review. Her feedback was good — specific enough to sting a little. She walked out with every intention of acting on it. I asked her one question: "What's different on your calendar this week?" She paused. Nothing was different. That's where feedback dies — not in the reading of it, but in the week after, when life resumes and the document closes. Understanding feedback and acting on it are two completely different skills. Most people only practice one. Here's what I told her to do instead: 𝟭/ 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗲 𝗲𝘃𝗲𝗿𝘆 𝗶𝗻𝘀𝗶𝗴𝗵𝘁 𝗶𝗻𝘁𝗼 𝗮 𝗯𝗲𝗵𝗮𝘃𝗶𝗼𝗿 "Be more strategic" tells you nothing. This does: take the project you're leading and present how it accelerates a priority your organization cares about — before your next leadership meeting. Specific. Timely. Actionable. For every piece of feedback, ask: what does this look like in practice? 𝟮/ 𝗔𝗱𝗷𝘂𝘀𝘁 𝘆𝗼𝘂𝗿 𝗴𝗼𝗮𝗹𝘀 If it doesn't make it into your goals, it's not going to happen. Don't create a separate "development item" that lives outside your work — embed it into the goal itself or into how you'll achieve it. If the feedback is "delegate more and develop your team," don't just note it. Update your existing goal to: 𝘥𝘦𝘭𝘪𝘷𝘦𝘳 𝘗𝘳𝘰𝘫𝘦𝘤𝘵 𝘟 𝘣𝘺 𝘘3, 𝘸𝘪𝘵𝘩 𝘵𝘸𝘰 𝘵𝘦𝘢𝘮 𝘮𝘦𝘮𝘣𝘦𝘳𝘴 𝘪𝘯𝘥𝘦𝘱𝘦𝘯𝘥𝘦𝘯𝘵𝘭𝘺 𝘭𝘦𝘢𝘥𝘪𝘯𝘨 𝘬𝘦𝘺 𝘸𝘰𝘳𝘬𝘴𝘵𝘳𝘦𝘢𝘮𝘴. Same goal. The feedback is now inside it. 𝟯/ 𝗖𝗵𝗮𝗻𝗴𝗲 𝘄𝗵𝗮𝘁'𝘀 𝗼𝗻 𝘆𝗼𝘂𝗿 𝗰𝗮𝗹𝗲𝗻𝗱𝗮𝗿 Your calendar is your priorities made visible. If the change you need to make doesn't appear there, it won't happen. If the feedback is "scale your impact by partnering across the organization," don't wait for opportunities to show up. Schedule 1:1s this week with leaders in adjacent teams to learn their priorities. What's on your calendar next Monday tells you more about your intentions than anything you wrote in your development plan. 𝟰/ 𝗧𝗲𝗹𝗹 𝘀𝗼𝗺𝗲𝗼𝗻𝗲 Share what you're working on with a peer, a mentor, or your manager. Not for accountability theater — because saying it out loud makes it real. And it invites the micro-feedback you'll need along the way. 𝟱/ 𝗦𝗲𝘁 𝗮 𝟵𝟬-𝗱𝗮𝘆 𝗰𝗵𝗲𝗰𝗸-𝗶𝗻 𝘄𝗶𝘁𝗵 𝘆𝗼𝘂𝗿𝘀𝗲𝗹𝗳 Not "am I trying harder?" — what's actually different in what you do? If the answer is nothing, the feedback is already expiring. The annual review is a gift. Most people open it, admire it, and put it back in the box. If nothing changes in what you do, the outcome is likely to be the same. What’s one change you’ve actually put on your calendar this year? PS: If you know someone in the middle of their review cycle — send this their way. --- Follow me, tap the (🔔) Omar Halabieh for weekly Leadership and Career posts

#100RulesofThumb — Rule 30 Always err on the side of providing more context than what you think is necessary. —— It's common to assume that what's obvious to you is also obvious to others. But this is rarely the case. As a rule, while communicating, always assume asymmetry in information. In other words, you should always assume that the other person knows less than you think they do about a given subject, context, or project. This isn't to belittle anyone's intelligence or experience; rather, it's a safeguard against the curse of knowledge. You see, once you get good at something, you forget what it's like to be a newbie. You're in marketing, and you think everyone knows what "CTR" or "ROAS" means. Trust me, they don't. And even if they do, you're usually better off assuming they don't while documenting stuff. Because you never know who is going to go through your documentation in the future. Don't assume; explain. Likewise, if you're running behind on a project, don't go radio silent. Tell your team what's up. A simple "Need another day, still grinding" goes a long way in keeping people's trust. When you assume symmetry — that is, when you think the other person knows what you know — you're setting the stage for misunderstandings. If you're a project manager and you assume that your team knows the project's background as well as you do, you might skip crucial details when assigning tasks. This will cause needless delays and errors. Or if a team member doesn't fully understand the problem you're trying to solve, they're less likely to come up with creative solutions. They might not even know how high the ceiling is for breaking the rules. And when things go wrong due to poor communication, it's not just the project that suffers. Team members may start to lose faith in each other and in the leadership, and we all know how that goes. Hence, always provide context when communicating. Whether it's an email, a meeting, or a one-on-one chat, make sure to include the 'why' and the 'what' along with the 'how.' Another slightly hard to implement idea: After you've communicated something, ask the other person to summarize what they've understood. This will quickly reveal any gaps in their understanding. Ambiguity charges high interest, and we all pay it in lost time and screw-ups. You want to be the person who cuts through the fog. Make things crystal clear, and you'll save everyone a lot of headaches. Also, when you provide more context, you're opening yourself up feedback. Maybe someone has a better idea or a quicker solution. Maybe they'll tell you to take a breather. Either way, you're better off than working in a vacuum. No one is going to punish you for being elaborate. So be elaborate and don't leave any space for obvious questions. In the long run, it will save you a lot of time in going back and forth on trivialities.

What's a lesser-known way of building psychological safety in your team? As a leadership consultant with SeraphCorp Institute, a leadership consulting firm, there is one skill, I realise, that many leaders struggle with. Regardless of their seniority or experience. The thing is, this one skill is probably also a lesser-known way of building psychological safety in our teams. And the leadership skill is... ✨ Giving negative feedback well. ✨ I qualify 'well' because most leaders I've met can give negative feedback-- the frown on our faces, the furrowed brows, the irritation in our voices. These little expressions signal to our teams that they didn't quite nail it. Didn't quite meet the mark. But then what often happens is that our team members are left to figure it out for themselves. Figure out why they didn't get the performance grade they thought they were going to get. Figure out why they were dropped from the team. Figure out what they did wrong and what they can do about it. I suspect that part of the reason for this is that us leaders, don't really like to be the bad guys. 😎 It's hard to tell someone that they didn't do well. It's scary to manage the emotions that will follow-- will they be angry/cry/be upset? So here's my suggestion on how to give negative feedback that will build psychological safety: 🚀 Be as specific as possible. What didn't go well? When? Why? e.g. This proposal for Client A was not well done. The client specifically asked for X, and you proposed Y. And the proposal was not proofread. 🚀 Hear from the team member. Because he/she probably has some thoughts about this piece of work too. e.g. Tell me more about your experience on this project. I'd like to hear your thoughts on how you think you did. 🚀 Be clear about the consequences and communicate it across to the team member. e.g. I will need to drop you from the team for this particular project because your being late constantly negatively impacted the team morale. This might have an impact on your performance rating this year because team work is one of our core values. 🚀 What follow up action/s are you expecting? e.g. Let's talk about what exactly you can do about this. On my part, I need you to work on being meticulous and careful. Please proofread every page of the document before it goes out to the client. 🚀 Check back in to close the loop e.g. Let's meet again to speak about this in 3 weeks. Keep me updated on your progress meanwhile. The truth is that by giving negative feedback clearly, fairly, and with the 'what to do next', we build our team members' trust in us. We take away the guesswork, the 'intrigue.' Our team members can focus on the work instead of trying to read us. It's bitter medicine but it's great for the team. My dear LinkedIn friends, what do you think? Does giving negative feedback well build psychological safety? #gracejmlam #seraphcorp #leadership #leadershipcoaching #futureskills