Conflict Is Information Turning Friction Into Better Ways of Working. Conflict within a team does not inherently indicate dysfunction; rather, it often serves as a crucial piece of information. It can act as a visible signpost indicating that certain aspects such as expectations, priorities, roles, communication methods, or handover processes are not operating as effectively as they should. When teams view friction as informative data rather than a personal shortcoming or failure, they can shift from assigning blame to identifying practical improvements that strengthen workflow and collaboration.
Conflict as a Signal
Most workplace conflicts are layered, with root causes that extend beyond the immediate disagreements. For instance, a dispute over a missed deadline might signal deeper issues such as unclear task ownership, contradictory instructions from leadership, an unmanageable workload, or poorly defined handover procedures. Similarly, tension between two departments may reveal differing expectations about quality standards, deadlines, decision-making authority, or what counts as a project being “complete.”
This understanding underscores the importance of reframing how teams approach conflict. Instead of asking, “Who is right?” which can create a divisive atmosphere, it is more productive to ask, “What is this conflict revealing about our processes and communication?” Low role clarity—characterised by ambiguous responsibilities, shifting performance standards, conflicting priorities among team members, or overlapping duties—is a significant source of workplace stress and conflict.
When friction arises repeatedly, it is exceptionally valuable, as it often points to consistent patterns of process gaps rather than mere isolated incidents of error. By recognising and addressing these recurring issues, teams can implement more effective practices that not only resolve current conflict but also prevent future misunderstandings and improve collaboration. This proactive approach fosters a healthier team environment where constructive discussions lead to meaningful change and clearer pathways to success.
Address Issues Early
Addressing small disagreements early can significantly improve team dynamics and project outcomes. When conflicts fester, they can lead to deeper resentment, increased avoidance, and siloed work, where team members work in isolation rather than collaboratively. This avoidance of direct conversation can lead individuals to withhold important information or unnecessarily route decisions through management, further complicating the situation. As an issue grows more complex, it typically becomes harder to resolve and more costly for the team and organisation.
Early conversations about potential conflicts don’t require a formal setting or a confrontational approach. A practical way to initiate this dialogue is by using prompts such as, “I noticed some friction in our handover process last week, and I believe it’s essential for us to address it before it hurts the next release. Could we spend about 20 minutes discussing what transpired?” This approach names the concern, keeps the focus on work-related issues, and conveys an intent to improve rather than assign blame.
Separate People from Problems
In any constructive conflict discussion, it is crucial to distinguish the issue at stake from the individuals involved. A statement like “You are difficult to work with” tends to provoke defensiveness and can further escalate tensions. In contrast, when you articulate specific observable issues, such as “The review comments were submitted after the deadline, which meant the team was unable to act on them promptly,” it frames the conversation around a concrete problem that both parties can collaboratively work to resolve. This distinction is vital for maintaining professionalism and keeping the conversation focused on finding solutions.
Moreover, it is essential to centre the discussion on behaviours, impacts, and processes rather than jumping to conclusions about malicious intent. For instance, a colleague might have acted in a way that seems problematic because of various pressures or limited information at the time. Thus, instead of assigning blame, it is more productive to ask, “What circumstances led to this outcome, and what changes can we implement to facilitate a better result next time?” This approach encourages collaboration and continuous improvement while strengthening understanding among team members.
Anchor in Shared Goals
Conflict in a team environment often fosters a divisive mentality, framing issues as a struggle between “me versus you.” Common scenarios include tensions between sales and delivery teams, or clashes between engineering and design departments, where the focus shifts to individual agendas rather than collaborative success. To mitigate this, reframe discussions around a shared goal. This could be anything from delivering a reliable product and ensuring exceptional customer service to meeting a critical launch date.
Establishing a common objective creates a unified standard that all team members can use to evaluate their options and decisions. When everyone is aligned towards a specific outcome, it transforms competitive mindsets into cooperative efforts.
A practical and effective phrase to initiate this reframing is, “We both want this project to succeed. What needs to change so we can work together more effectively?” This question acknowledges differing perspectives while promoting collaboration. Rather than dismissing divergent views, it encourages open dialogue to address and negotiate those differences constructively. As a result, the team is better equipped to choose strategies that prioritise collective achievement, increasing the likelihood of reaching their shared goal. This approach not only strengthens relationships within the team but also fosters a culture of collaboration and mutual respect.
Understanding Each Perspective Fully
Before attempting to propose any solutions, each party involved must be granted the opportunity to articulate their viewpoints comprehensively. This means taking the time to explain not only what they observed during the situation but also their expectations, the constraints they experienced, and the repercussions the situation had on them personally and professionally. This listening process must happen without interruptions or premature judgments, as the initial narrative is often incomplete and may not reflect the full range of experiences or insights.
To facilitate a deeper understanding, consider posing the following questions during discussions:
“What were you expecting to happen?” This question clarifies the goals or outcomes each expected before the incident. Understanding these expectations can reveal potential misalignments and set the stage for constructive dialogue.
“What information did you have at the time?” Asking what information each party had at the time can highlight gaps in communication or understanding that may have contributed to the situation. This can also highlight whether everyone had equal access to critical data that could have informed their actions.
“What made that difficult?” This question encourages individuals to discuss any obstacles or challenges they faced while attempting to achieve their goals. Identifying these difficulties allows the team to recognise external pressures or constraints that may not have been previously considered.
“What impact did this have on your work?” Understanding how the situation affected each individual’s work highlights the issue’s broader ramifications. Understanding the emotional and operational impacts can foster empathy among team members and guide future improvements.
“What would have helped you succeed?” This question shifts the focus to problem-solving and encourages individuals to share thoughts on resources or supports that could have led to better outcomes. It opens the door for collaborative brainstorming about potential solutions moving forward.
The goal of this process is not to assign blame or identify who is at fault, but rather to construct an accurate, shared understanding of the workflow failure. By creating a safe and open environment for expressing disagreements or concerns, teams are better equipped to identify root causes and renegotiate roles and responsibilities as circumstances evolve. This collaborative approach fosters a culture of transparency and continuous improvement, ultimately enhancing team dynamics and effectiveness.
Identifyit’s Process Issue
Once all relevant perspectives on the incident have been gathered, it’s crucial to delve deeper into the underlying systemic causes that contributed to the problem. Commonly observed process issues can manifest in various forms, such as unclear ownership of tasks and responsibilities, competing deadlines that create tension between teams, poor handover practices that lead to loss of information, ambiguous decision-making rights that cause confusion, inconsistent definitions of quality standards that leave teams uncertain, or dependent communication chains where crucial information relies on someone’s recollection to be transmitted effectively.
To address these challenges, shift the focus from asking “Who is to blame for the mistake?” to a more constructive inquiry: “At what point in the workflow did we lack clarity regarding ownership?” For instance, if projects frequently delay during the transition between design and engineering, the problem may not lie solely with either team; it may stem from a broader issue where no one clearly owns that transitional phase. This could be exacerbated by vague acceptance criteria, which leave both teams uncertain about expectations, or by handovers that occur too late in the process, preventing timely feedback and necessary adjustments. By critically examining these elements, organisations can identify and address the root causes of process-related issues, fostering a more efficient and accountable workflow.
Agree, Test, and Review
To foster effective collaboration within a team, conversations should conclude with clear, actionable outcomes rather than mere expressions of goodwill. Each agreement should be anchored in specific, measurable changes that are established with a clear understanding of ownership, timelines, and success metrics. Vague commitments often lead to disappointment and failure; therefore, define detailed actions, assign responsible parties, and set deadlines to foster accountability and ensure follow-through.
For example, imagine a team identifies issues with the handover process. They could agree that each handover will now include a concise written summary that outlines key points, an assigned person to oversee the handover, a deadline by which the handover must be completed, and a dedicated 15-minute check-in meeting to discuss the handover’s effectiveness. The team can implement this new process over two weeks, then reconvene to assess the results. During this review, they should critically examine whether handovers have become clearer, whether fewer items stall due to unclear information, and whether team members still find themselves chasing details. If issues persist or new ones arise, the team should adapt the process accordingly instead of reverting to a blame culture.
Build it into Team Norms.
To make this approach a regular practice rather than a one-time effort, teams should build friction reviews into routine meetings, such as project kickoffs, retrospectives, post-mortems, and planning sessions. During these discussions, teams should reflect on critical questions like, “Where were roles ambiguous?” or “What agreements can we establish to prevent similar misunderstandings in the future?” By reframing individual conflicts as opportunities for organisational learning and growth, teams can cultivate a culture of continuous improvement.
Managing conflict this way creates a constructive feedback loop: issues highlight where processes need clarification, the team makes targeted adjustments, and outcomes are measured. The goal isn’t to eliminate all disagreement—healthy teams recognise that differing opinions are natural and drive growth—but to ensure these disagreements strengthen collaboration. Through this process, trust, efficiency, and teamwork strengthen rather than weaken.
Tomorrow’s post will be: Building Trust in Hybrid Teams: Small Habits That Prevent Distance and Drift.
