Activity: Identify the Root Cause of Conflict

Introduction

There is a particular gap between knowing about the causes of conflict and being able to recognize which cause is actually operating in a specific situation in front of you. You can read every article in this chapter. You can understand personality clashes, communication failures, performance issues, interest differences, resource scarcity, and value differences in detail. You can hold the framework that conflicts often have multiple causes operating together, that triggers are different from causes, that what looks like one kind of conflict is often actually another. And then a real conflict appears in your team, and despite all of that understanding, you find yourself unsure what is actually driving the situation. The visible incident is clear. The parties are identifiable. But the underlying cause is not obvious. It might be communication. It might be interest difference. It might be a personality clash masking a performance issue. It might be resource scarcity amplifying a value difference. And without clear diagnosis, you cannot intervene effectively, because different causes require different responses.

This is the gap that the activity in this article is designed to help you close. Diagnosing conflict is a skill, like every other leadership skill. It is not just about knowing the categories. It is about being able to look at a real situation and recognize, often with limited information and under time pressure, what is actually producing the friction. That recognition cannot be developed through reading alone. It develops through practice, through repeated exposure to scenarios in which you have to make diagnostic judgments, examine your reasoning, learn from where your initial reads turned out to be wrong, and refine the pattern recognition that allows faster and more accurate diagnosis in real situations. That practice is what role play, in conflict diagnosis, is designed to support. Not by giving you the right answers, but by giving you the chance to practice the skill of looking at situations and identifying what is actually going on.

There is another reason this activity matters. Most leaders, when they face conflict in their teams, react quickly. They see the visible incident. They form a hypothesis about what is going on. They intervene based on that hypothesis. And often, the hypothesis is wrong, or at least incomplete, because they did not take the time to diagnose carefully before acting. The pattern of acting on incomplete diagnosis is one of the most common failure modes in conflict management. It produces interventions that miss the actual issue, that address symptoms while leaving causes intact, that sometimes make situations worse because the wrong intervention activates other dynamics that were not previously prominent. Practicing diagnosis explicitly, in conditions where the answer is not immediately obvious, builds the discipline of slowing down to look carefully before acting. That discipline is what distinguishes leaders who handle conflicts well from leaders who handle them quickly but not well.

This article is structured differently from the other articles in this chapter. It is not just about explaining a concept. It is about giving you the structure to actually practice conflict diagnosis, either individually or with a partner or learning group. It walks through how to read a conflict situation, what diagnostic questions to ask, how to consider multiple possible causes, how to test your hypothesis, and how to refine your diagnosis as you learn more. It includes detailed scenarios that you can use directly, with the dimensions and complications that real conflicts typically include. It offers guidance on how to debrief your diagnostic process so the learning sticks. And it provides ways to integrate this practice into your ongoing development as a leader, because conflict diagnosis is a skill that benefits from sustained development over years rather than a one-time activity. By the end of this article, you should be able to look at any conflict in your team and engage with it diagnostically before intervening, and you should have a practice you can return to whenever you want to develop this capacity further.

Simple Meaning: What Is This Activity?

This activity is a structured practice exercise in which you work through scenarios of team conflict to identify the underlying causes operating in each situation, drawing on the diagnostic frameworks from this chapter and developing the pattern recognition that allows faster and more accurate diagnosis in real conflicts. It is not a test with right answers. It is a practice ground for developing the diagnostic skill that distinguishes effective conflict engagement from reactive intervention. The activity works whether you do it individually, with a partner, or as part of a learning group, and it benefits from sustained practice over time rather than a single session.

Identifying the root cause of conflict is one of the most important and most underdeveloped skills in conflict-related leadership work. Most leaders develop conflict engagement skills through experience, which means they learn through trial and error in real situations with real consequences. The errors produce damage, the trials produce learning, and over years a leader develops better diagnostic instincts. But the cost of this learning is borne by the team members whose conflicts are the practice ground. Structured practice in conflict diagnosis offers an alternative path. Working through scenarios in which the underlying causes are complex, in which initial reads can be wrong, in which multiple causes operate together, in which surface incidents mask deeper dynamics, develops the diagnostic capacity faster and with less cost to real teams. What makes diagnostic practice powerful is not the scenarios themselves, but what they make visible. The way you read a situation reveals your default assumptions about what causes conflict. The hypotheses you reach for first reveal what categories of causation are most available to you. The questions you would ask reveal how you gather information when you do not yet know what is happening. The way you refine your diagnosis as you learn more reveals how willing you are to update your initial reads in light of new information. Practicing these moves explicitly, with structured feedback or self-reflection, accelerates the development of skills that would otherwise take years to develop through chance and experience. The activity in this article is designed to support that development. The scenarios it provides are not the only scenarios you can practice with. The frameworks it offers are not the only frameworks you can use. But together, they give you a starting point for the kind of sustained practice that builds the diagnostic capacity to engage with real conflicts in your team with confidence, accuracy, and the discipline to look carefully before acting. That capacity is one of the most valuable things a leader can develop in the work of leading teams through the inevitable conflicts that real work involves.

This activity can be understood through four essential dimensions:

How to Read a Conflict Situation

Before working through scenarios, it helps to have a clear approach to reading conflict situations. This approach is what you will practice applying.

Step 1: Observe the Visible

Start with what you can actually see. Who is in conflict? What is the visible incident or pattern? What are the parties saying or doing? What has been the visible sequence of events? Observation is not interpretation. It is the raw material of diagnosis. Many leaders move too quickly from observation to interpretation, which means they are interpreting incomplete observation.

Step 2: Distinguish Triggers From Causes

The visible incident is often the trigger, not the cause. What was happening between the parties before the trigger? What conditions were present that made this trigger lead to conflict when similar triggers might not have? What patterns exist that the trigger is the latest expression of? This distinction, which was explored in the article on why conflicts happen in teams, is one of the most important diagnostic moves.

Step 3: Consider Multiple Possible Causes

Rather than locking in on a single cause, consider multiple possibilities. Could this be a communication problem? An interest difference? A personality clash? A performance issue? Resource pressure? A value difference? Several of these together? The discipline of considering multiple causes prevents the trap of acting on the first hypothesis that comes to mind.

Step 4: Look for Distinguishing Markers

Each cause of conflict has markers that distinguish it from others. Communication problems are about specific information failures. Interest differences persist across attempts at clarification. Personality clashes show up across multiple substantive contexts. Performance issues are connected to specific outputs or patterns. Resource scarcity is amplifying other tensions. Value differences touch identity and resist persuasion. Looking for these markers helps distinguish among possible causes.

Step 5: Identify What You Would Need to Know

Often, the available information is not enough to make a confident diagnosis. Identify what additional information would help. What would you ask the parties? What would you observe in their interactions? What patterns would you look for across their history? What context would you want to understand? Naming what you need to know prevents premature commitment to incomplete diagnoses.

Step 6: Form a Working Hypothesis

Based on what you have observed and what markers you have noticed, form a working hypothesis about the primary causes. The hypothesis is not a final answer. It is a starting point that you will refine as you learn more. A good working hypothesis includes the primary cause you suspect, any secondary causes that may be operating, and the level of confidence you have in your read.

Step 7: Be Honest About Uncertainty

Diagnosis is not always certain. Sometimes the available information genuinely allows multiple interpretations. Being honest about uncertainty, both with yourself and with anyone you are working with, is more useful than projecting false confidence. Knowing what you do not know is part of skilled diagnosis.

Step 8: Plan the Investigation

Based on your hypothesis and the uncertainties, plan how you would investigate further. Who would you talk with? What would you ask? What would you observe? What evidence would shift your read in different directions? The investigation plan is what allows your initial hypothesis to be tested and refined, rather than locked in despite contradicting evidence.

Step 9: Refine Based on What You Learn

As you gather more information, refine your diagnosis. New evidence may confirm your hypothesis, modify it, or suggest a different one altogether. Be willing to update. The discipline of refining diagnosis in light of new information distinguishes effective diagnostic work from confirmation-bias-driven analysis.

Scenario 1: The Strained Senior Engineers

The Situation

Two senior engineers on your team, Karthik and Meera, have been increasingly difficult with each other for the past two months. In meetings, they often disagree on technical decisions in ways that feel personal rather than substantive. When other team members propose work that touches both of their areas, they push back at each other rather than collaborating. Other team members have started routing communication around the two of them rather than asking them to work together. You have noticed that their disagreements have become less specific and more frequent. Karthik recently told you in a one-on-one that he finds Meera difficult to work with. Meera, in a separate one-on-one, mentioned that she feels Karthik does not respect her judgment. Both have been on the team for over two years. They worked together effectively in their first year on the team. The pattern of friction began around four months ago.

What Additional Context Might Help

Before diagnosing, what would you want to know? Consider:

• What happened around four months ago when the friction started?
• What is the specific work each of them is responsible for, and how do their areas intersect?
• What is the broader pressure on the team right now? Deadlines? Resource constraints?
• What has happened in past similar tensions on this team?
• What are each of them being measured on or recognized for?
• Have there been any organizational changes that affected either of them?
• What do their other colleagues observe about the friction?

Possible Hypotheses to Consider

• Personality clash. Their styles may have become harder to navigate together as the team has evolved.
• Interest difference. They may have different stakes in technical decisions that have become more contested.
• Resource pressure amplifying other tensions. Increased pressure on the team may be amplifying tensions that were previously manageable.
• Performance issue masked as friction. One of them may be performing below expectation and the friction may be a consequence.
• Unaddressed past incident. Something specific may have happened four months ago that has not been resolved.
• Structural overlap. Unclear ownership in their areas may be producing recurring friction.
• Value difference. They may have come to disagree fundamentally about how the work should be done.

Distinguishing Markers to Look For

• If personality clash: The friction would be across substantive topics, not tied to specific issues. It would feel about style rather than substance.
• If interest difference: Each would have stakes in different outcomes from specific decisions. The friction would be specific to those decisions.
• If resource pressure: The pattern would track with pressure increases. Other team relationships would be strained too.
• If performance issue: One of them would have specific output problems. The other's frustration would track with those problems.
• If unaddressed incident: They would carry specific memory of an event around four months ago that they have not discussed.
• If structural overlap: Their disagreements would cluster around specific areas of overlap. Clearer roles would dampen the friction.
• If value difference: They would express different beliefs about what good work looks like that go beyond specific decisions.

Diagnostic Reflection

Work through the scenario and ask yourself:

• Which hypothesis did you reach for first? Why?
• What in the scenario information supports your initial hypothesis?
• What in the scenario information does not fit your initial hypothesis?
• What additional information would shift your diagnosis?
• If you had to engage with this situation tomorrow, what would you do first?
• What is the risk if your diagnosis is wrong?

Scenario 2: The Withdrawn Team Member

The Situation

One of your team members, Aman, has become noticeably less engaged over the past six weeks. He used to contribute actively in meetings and volunteer for stretch work. Now he speaks less, takes on only what is asked, and has reduced his interaction with colleagues. His work output is still meeting expectations, but it is no longer exceeding them as it used to. When you have asked him in one-on-ones if everything is okay, he has said yes. Two of his colleagues have separately mentioned to you that they think something is wrong with Aman. One of them suggested that Aman may have a conflict with another team member, Priya, although the colleague was not specific. Aman has not raised any conflict with you directly.

What Additional Context Might Help

• What changed around six weeks ago for Aman, the team, or the organization?
• What is Aman's relationship with Priya specifically, and what specifically did the colleague observe?
• What does Aman's career trajectory look like? Has anything happened recently with promotion, recognition, or opportunity?
• What is Aman's broader life context, to the extent you have any insight?
• What is the team's current pressure level?
• Has Aman received any feedback recently that may have affected him?
• What do other people who interact with Aman observe?

Possible Hypotheses to Consider

• Unaddressed conflict with Priya. The colleague's observation may point to a real interpersonal conflict that Aman is handling through withdrawal rather than direct engagement.
• Personal circumstances. Something outside work may be affecting Aman's engagement.
• Career frustration. Aman may be frustrated about lack of recognition, opportunity, or advancement.
• Burnout. Sustained pressure may have depleted his capacity for the extra engagement he previously brought.
• Disengagement from the work itself. Aman may have lost interest in or commitment to the team's mission or his role within it.
• Hidden performance concern. Aman may be aware of some performance issue and may be reducing his exposure to limit damage.
• Value-based concern. Something the team is being asked to do may conflict with Aman's values.
• Considering leaving. Aman may be quietly preparing to move to a different role and reducing investment accordingly.

Distinguishing Markers to Look For

• If conflict with Priya: The withdrawal would specifically affect his interaction with Priya. He would be more avoidant of her than of other colleagues.
• If personal circumstances: The withdrawal would affect his life broadly, not just work. Energy levels would be down in general.
• If career frustration: He would have specific moments where opportunity or recognition was missed. He may have raised these previously and felt unheard.
• If burnout: There would be sustained periods of overwork preceding the withdrawal. Other signs of depletion would be present.
• If disengagement from work: His withdrawal would be specifically from the work itself, not from individual relationships.
• If hidden performance concern: There would be specific work issues that he may be aware of and you may not yet have noticed.
• If value-based concern: There would be specific decisions or directions that troubled him, possibly tied to when the withdrawal started.
• If considering leaving: He may be reducing investment, taking fewer risks, and limiting visibility in ways that suggest preparation for departure.

Diagnostic Reflection

• This scenario has many possible causes. What does that tell you about diagnostic work?
• The colleague's mention of Priya pulls toward one hypothesis. How much should you weight that observation versus your own observation?
• Aman has said everything is fine. How do you balance his stated position against the visible pattern of withdrawal?
• What is your initial diagnosis, and what is your confidence level?
• What would you do first to learn more without making the situation worse?

Scenario 3: The Cross-Team Friction

The Situation

Your team has been increasingly in conflict with another team in the organization, the platform team led by a peer manager named Rahul. The friction has been building for three months. Your team members complain that the platform team is slow to support their requests and dismissive of their concerns. Rahul has told you, in a peer conversation, that his team finds yours demanding and inconsiderate of their constraints. Specific incidents have included missed deadlines, escalated emails, and a recent meeting in which two of your team members and two of Rahul's were openly hostile to each other. You and Rahul have a generally good relationship. Both teams are critical to the organization, and the leadership above you both has begun to express concern about the cross-team dynamics.

What Additional Context Might Help

• What is the structural relationship between your team's work and the platform team's work?
• What changed three months ago that may have started the friction?
• What are the formal expectations and informal patterns of how the teams should work together?
• Are there resource pressures on the platform team that affect their capacity?
• Are there resource pressures on your team that affect what you are asking of them?
• What are the leadership-level expectations for both teams, and are they aligned?
• What incentives are operating for each team that may pull them in different directions?
• What is the history of the cross-team relationship before the current friction?

Possible Hypotheses to Consider

• Misaligned organizational expectations. The two teams may be operating under different definitions of success that produce structural friction.
• Resource scarcity in the platform team. Their slowness may reflect real capacity constraints that your team is interpreting as dismissiveness.
• Resource pressure on your team. Increased demands on your team may be producing requests that look unreasonable to the platform team.
• Interpersonal escalation. Specific friction between specific people may be spreading to broader team-level dynamics.
• Communication breakdown. The teams may be communicating in ways that are producing repeated misunderstandings.
• Power dynamics. One team may have more organizational power, and the other may be expressing frustration about being de-prioritized.
• Value difference about service. The teams may hold different beliefs about what service to other teams should look like.
• Triangulation through escalation. Each team may be escalating to leadership rather than addressing concerns directly, which is creating its own friction.

Distinguishing Markers to Look For

• If misaligned expectations: There would be specific decisions where the teams have legitimately different priorities based on what they are being measured on.
• If resource scarcity: Platform team capacity would be visibly stretched. Their slowness would track with capacity, not with attitude.
• If pressure on your team: The requests your team is making would have changed in volume or urgency three months ago.
• If interpersonal escalation: The friction would be concentrated among specific individuals on each team, with others less affected.
• If communication breakdown: There would be specific instances of misinterpretation or missing context that produced friction.
• If power dynamics: One team's concerns would consistently be addressed and the other's would not, producing predictable frustration.
• If value difference: The teams would express different beliefs about the right way to handle cross-team work.
• If triangulation: Concerns would be raised through escalation channels before being raised directly between the teams.

Diagnostic Reflection

• Cross-team conflicts often have multiple causes operating together. What combination feels most likely here?
• How does your position as one team's leader bias your diagnosis?
• What is Rahul's likely diagnosis, and how does it differ from yours?
• What conversation between you and Rahul would help clarify what is actually going on?
• What is the risk of diagnosing this primarily at the interpersonal level when the cause may be structural?

Scenario 4: The Sudden Eruption

The Situation

In a team meeting yesterday, one of your usually calm team members, Lakshmi, became visibly upset during a discussion about a project decision. She raised her voice, accused two other team members of consistently overruling her input, and left the meeting before it ended. The other team members were surprised and uncomfortable. One of them sent you a message immediately after asking what to do. You have not yet spoken with Lakshmi. She is normally one of the most measured people on the team and almost never expresses strong emotion in work contexts. You are aware that she has been working on a project that has been particularly demanding, but you have not noticed any significant signs of strain before this meeting.

What Additional Context Might Help

• What specifically was being discussed when she became upset?
• What was the pattern of input being given and considered before her eruption?
• What is her broader experience of feeling heard or unheard on this team?
• What is happening in the demanding project she is working on?
• What is her relationship with the two team members she accused of overruling her?
• What has been her recent capacity and well-being, to the extent you can see it?
• Has anything happened recently between her and others on the team that you might not have been aware of?
• What was the context of similar past meetings where input was being discussed?

Possible Hypotheses to Consider

• Accumulated suppressed conflict. The eruption may be the surfacing of friction that has been building for some time, perhaps months.
• Crisis trigger. Something specific in the meeting may have been the tipping point for cumulative pressure.
• Value-based reaction. The specific decision may have touched a value she holds strongly.
• Capacity exhaustion. Her overall capacity may have been depleted to the point where normal friction broke through her usual composure.
• Pattern of being unheard. There may be a real pattern of her input not being incorporated, and this meeting was where it finally surfaced.
• Personal context. Something in her broader life may be affecting her capacity to handle normal work friction.
• Specific interpersonal issue. She may have specific unresolved issues with the two team members named, going beyond the meeting incident.
• Disengagement signaling. The eruption may be a way of signaling that something more fundamental is wrong that she has not been able to articulate directly.

Distinguishing Markers to Look For

• If accumulated suppressed conflict: She would have specific past incidents she carries memory of. The pattern of being overruled would be one she can articulate.
• If crisis trigger: The specific moment in the meeting would have a clear quality that made it different from other moments.
• If value-based reaction: The decision would touch a specific value she holds. She could articulate the value clearly.
• If capacity exhaustion: There would be other signs of depletion preceding the eruption that may have been visible only on close attention.
• If pattern of being unheard: Other team members would be able to confirm the pattern. Specific examples would exist.
• If personal context: The work pattern would be largely fine but life pressures would be high.
• If specific interpersonal issue: She would have specific concerns about specific people that go beyond the meeting.
• If disengagement signaling: There would be broader patterns of reduced investment that the eruption is making visible.

Diagnostic Reflection

• Sudden eruptions almost always have causes that preceded them. What does this tell you about how to engage?
• What is your responsibility to Lakshmi, the other team members, and the team as a whole, given the public nature of the incident?
• What is the risk of diagnosing this too quickly versus the cost of letting too much time pass before engaging?
• What is the first conversation you would have, and with whom?
• How do you balance Lakshmi's privacy with the team's need for some understanding of what happened?

How to Use These Scenarios for Practice

The scenarios above can be used in several ways depending on whether you are practicing alone, with a partner, or with a group.

Solo Practice

• Choose one scenario at a time.
• Read it through once, then put it aside for a few minutes.
• Write down what you remember about the situation. The act of recalling reveals what you found salient.
• Go back to the scenario and work through the diagnostic process step by step.
• Form a working hypothesis with the confidence level you actually feel.
• Write down what you would do next, including investigation and initial engagement.
• Reflect on what your diagnosis and intervention plan reveal about your default assumptions.
• Return to the scenario a week later and see how your read changes.

Partner Practice

• Both partners work through the same scenario independently.
• Each writes down their diagnosis, confidence level, and investigation plan.
• Share your diagnoses without judging each other's reads as right or wrong.
• Discuss where you agreed and disagreed. Differences are particularly valuable, because they often reveal different default assumptions.
• Explore what evidence would shift each of you toward the other's hypothesis.
• Discuss what each of you would do next and what risks each plan carries.

Group Practice

• The group works through one scenario together, with one person facilitating.
• Each participant offers their initial read individually before discussion.
• The facilitator surfaces the range of hypotheses and confidence levels in the room.
• The group discusses what evidence would distinguish among the hypotheses.
• The group develops an investigation plan that everyone can endorse.
• Participants reflect on what their initial reads revealed about their assumptions.

Practice Variations

• Use the same scenario at different times to see how your diagnosis evolves with practice.
• Modify the scenarios with additional information to see how it changes your read.
• Create your own scenarios based on actual conflicts you have observed, with details changed for privacy.
• Practice diagnosing conflicts in stories from your professional history, applying the framework retrospectively.

How to Debrief Your Diagnostic Process

The diagnostic process is more important than the specific diagnosis you reach. Debriefing the process is where the learning happens.

Questions to Ask Yourself

• What hypothesis did I reach for first? Why that one?
• What categories of causation are most available to me, and which are least available?
• What did I notice in the scenario, and what did I miss on first read?
• What evidence supports my initial hypothesis? What evidence does not fit?
• How confident did I feel in my diagnosis? Was that confidence warranted by the evidence?
• What would I want to investigate? How did my investigation plan emerge from my hypothesis?
• What is the risk if my diagnosis is wrong? What is the cost of being wrong in each direction?
• How did I balance the visible incident against the underlying conditions?
• Did I consider multiple hypotheses, or did I lock in on one quickly?
• What does my process reveal about my default assumptions about why conflicts happen?

Patterns to Watch For

• Reaching for the same category every time. If you consistently diagnose conflicts as one type, you may be missing the other types.
• Locking in on the first hypothesis. If you do not seriously consider alternatives, you will miss situations where the alternative is correct.
• Overconfidence in early diagnosis. Real conflicts often turn out to be different from initial reads. Strong confidence early may signal incomplete analysis.
• Underconfidence that prevents action. Too much uncertainty can produce paralysis. Diagnostic work supports action, not endless analysis.
• Locating cause primarily in individuals. If your diagnoses consistently locate cause in personality or character, you may be missing structural or systemic causes.
• Avoiding diagnoses that implicate the leader. If you never diagnose situations where the leader contributed to the conflict, you may be protecting yourself from honest examination.
• Difficulty with diagnoses that have no clear villain. If your diagnoses always have someone to blame, you may be missing causes where the friction emerges from conditions rather than people.

Integrating This Practice Into Ongoing Development

Diagnostic skill develops through sustained practice over time, not through a single session.

Building It Into Your Routine

• Practice diagnosis with one scenario each week, either from this article or from situations you have observed.
• When real conflicts arise in your team, take five minutes to practice diagnosis explicitly before intervening.
• After real conflicts resolve, reflect on what the actual underlying cause turned out to be and compare to your initial diagnosis.
• Discuss diagnostic process with peer leaders periodically. Different perspectives reveal what you may be missing.
• Use this article and the chapter as ongoing reference, not as one-time reading.

Tracking Your Development

• Notice when your initial reads turn out to be wrong. Patterns in your errors reveal what to work on.
• Notice when your initial reads turn out to be right. Patterns in your accuracy reveal what you do well.
• Notice when you act on incomplete diagnosis versus when you slow down to gather more information.
• Notice when you become aware of causes you would not have seen a year ago. That awareness is growth.

Connecting to Larger Conflict Work

• Diagnosis is the first step in conflict engagement. The subsequent steps depend on what is being diagnosed.
• Practicing diagnosis develops the pattern recognition that supports the rest of the conflict engagement work explored in this chapter.
• The capacity to diagnose accurately enables interventions that match the actual cause, which produces better outcomes than reactive intervention.
• Over years, diagnostic skill becomes one of the foundations on which the rest of your conflict-related leadership rests.

Practical Workplace Reflection

Scenario

A team lead named Hari had been managing his team for three years. He had read all the articles in this chapter and felt he understood the categories of conflict causation well. Then a conflict arose in his team that did not fit easily into any category. Two team members, Vikram and Anjali, had been increasingly difficult with each other. Hari's first read was that it was a personality clash. He talked to each of them, facilitated a conversation between them, and felt he had handled it. Two months later, the same friction reappeared, with new incidents and the same underlying tone. Hari realized he had misdiagnosed.

What He Did

Rather than rushing to another intervention, Hari decided to practice diagnostic work more carefully. He used the scenarios in this article as the foundation for sustained practice. He worked through them alone, then with a peer, then in a small learning group. He noticed that he consistently reached for personality clash as his first hypothesis when team members were struggling to work together. He noticed that he rarely considered structural, performance, or value-based causes for interpersonal friction. And he noticed that his interventions tended to be at the interpersonal level even when the actual cause was elsewhere.

He returned to the Vikram-Anjali situation with fresh diagnostic discipline. He observed more carefully. He considered multiple hypotheses. He talked with each of them with more open questions. And he discovered that the friction was actually about an interest difference: they had been competing for the same growth opportunity that had been left undefined, and the competition was producing the friction. The personality clash diagnosis had missed the underlying cause entirely. With the right diagnosis, the intervention was different: he clarified the growth opportunity decision, made the process transparent, and had honest conversations with both about their career aspirations. The friction dissolved within weeks.

Result

The Vikram-Anjali conflict resolved. More importantly, Hari's diagnostic practice continued. He noticed his own patterns more clearly. He developed the discipline of slowing down before intervening. He became more accurate in his reads of subsequent conflicts. And his interventions, because they were matched to actual causes, became more effective. A year later, he reflected: "The chapter on conflict gave me the categories. But the activity of practicing diagnosis is what made the categories useful in real situations. Without the practice, I would have continued to default to my familiar patterns and miss what was actually happening. With it, I have become a better diagnostician, which has made me a better leader of teams through conflict."

Learning

The chapter teaches the categories. The activity builds the capacity to use them. That capacity is one of the most valuable things a leader can develop in conflict-related work, because it is what allows interventions to be matched to actual causes rather than to assumed ones. And it develops only through sustained practice, including practice with scenarios where the answer is not obvious and where your initial reads may be wrong. That practice is what this activity is designed to support. Not in a single session, but as an ongoing development practice that builds capacity over years.

Activity Checklist

Self-Reflection Questions

Use these questions to think about your own diagnostic practice.

1. When I face a conflict in my team, do I take time to diagnose carefully before intervening, or do I tend to act on the first hypothesis that comes to mind?
2. What categories of conflict causation are most available to me? Which do I tend to default to?
3. What categories do I least consider? What does this tell me about my assumptions?
4. When my initial diagnoses have turned out to be wrong in the past, what was the pattern of my errors?
5. How honestly do I engage with uncertainty in my diagnostic work? Do I project confidence I do not have?
6. Do I locate cause primarily in individuals, or do I consider structural and systemic causes too?
7. Do I consider my own contribution as a leader to the conflicts in my team?
8. What scenarios in this activity stretched my thinking? Which felt easy?
9. What is one specific change I want to make in how I approach conflict diagnosis going forward?
10. If I imagined a year of sustained diagnostic practice, how do I think my conflict-related leadership would change?

Key Takeaways

• Identifying the root cause of conflict is one of the most important and most underdeveloped skills in conflict-related leadership work. It is a skill that develops through practice, not just through reading about categories of causation.
• This activity is structured practice in conflict diagnosis, designed to build the diagnostic capacity that distinguishes effective conflict engagement from reactive intervention.
• The activity has four essential dimensions: scenarios with real complexity, a structured diagnostic process, honest engagement with uncertainty, and reflection that develops skill.
• Reading a conflict situation well involves observing the visible, distinguishing triggers from causes, considering multiple possible causes, looking for distinguishing markers, identifying what additional information would help, forming a working hypothesis, being honest about uncertainty, planning the investigation, and refining diagnosis based on what you learn.
• The scenarios in this article cover common situations: the strained senior engineers (likely multiple causes operating together), the withdrawn team member (many possible causes, requiring careful investigation), the cross-team friction (structural and interpersonal layers), and the sudden eruption (visible incident with hidden causes preceding it).
• The scenarios can be used solo, with a partner, or in a group, with each approach producing different kinds of learning. The diagnostic process itself is more important than the specific diagnoses reached.
• Debriefing the diagnostic process reveals patterns: which categories you reach for first, what you tend to notice or miss, how confident you are versus how confident the evidence warrants, what your defaults reveal about your assumptions.
• Common patterns to watch for include reaching for the same category every time, locking in on the first hypothesis, overconfidence in early diagnosis, underconfidence that prevents action, locating cause primarily in individuals, avoiding diagnoses that implicate the leader, and difficulty with diagnoses that have no clear villain.
• Diagnostic skill develops through sustained practice over time. Building it into your routine, tracking your development, and connecting it to your larger conflict work over years is what produces the capacity that distinguishes skilled diagnostic work from reactive intervention.
• The chapter teaches the categories of conflict causation. The activity in this article builds the capacity to use them in real situations. That capacity is what allows interventions to be matched to actual causes rather than to assumed ones, which is what makes the difference between conflicts that resolve and conflicts that recur in different forms.
• This activity is not a one-time exercise. It is an ongoing development practice that you can return to whenever you want to strengthen your diagnostic capacity. The leaders who treat it this way build a foundation that supports the rest of their conflict-related work for the rest of their careers.

Conclusion

The gap between knowing about conflict and being able to diagnose it accurately in real situations is one of the most important gaps in conflict-related leadership work. This article has tried to support you in closing that gap through structured practice with scenarios that include the kind of complexity real conflicts have. The scenarios are not the only practice you can do. The frameworks are not the only frameworks you can use. But together, they give you a starting point for the sustained practice that builds the diagnostic capacity to engage with real conflicts in your team with confidence, accuracy, and the discipline to look carefully before acting.

A leader who develops strong diagnostic capacity engages with conflict differently. They do not rush to intervene based on first impressions. They consider multiple possible causes before committing to a diagnosis. They look for distinguishing markers that help them choose among hypotheses. They engage honestly with uncertainty rather than projecting confidence they do not have. They plan investigations that help them refine their reads. They update their diagnoses as they learn more. And they match their interventions to actual causes rather than to assumed ones. That kind of engagement produces better outcomes, fewer recurring conflicts, and a team that experiences its leader as someone who actually understands what is happening rather than someone who responds quickly but inaccurately.

The most important lesson of this article is this: Conflict diagnosis is a skill, not just a body of knowledge. Knowing the categories of conflict causation is necessary but not sufficient. The capacity to look at a specific situation and recognize what is actually operating, with all the complexity, ambiguity, and overlap that real conflicts include, develops through practice, not through reading alone. This activity is the practice. Engage with it seriously. Work through the scenarios honestly. Notice your patterns. Practice with partners and groups when possible. Apply diagnostic discipline to real conflicts in your team. Track your development over time. And treat the activity as ongoing rather than as a one-time exercise. The leaders who develop strong diagnostic capacity make their interventions more accurate, more effective, and more aligned with the actual causes of the conflicts they engage with. The team members they lead benefit from interventions that address what is actually happening rather than what was assumed to be happening. And the leader develops, over years, the foundation that supports the rest of their conflict-related leadership work. That foundation is what this activity is designed to help you build. Build it. Practice it. Refine it. Return to it. And let your diagnostic capacity become one of the consistent ways you engage with the inevitable conflicts that arise in the teams you lead, conflict by conflict, year by year, throughout the long arc of your leadership career. The chapter has given you the understanding. The activity gives you the practice ground. What comes next is the application, in real conflicts with real teams, where the diagnostic capacity you have been developing meets the situations that actually need it. Apply what you have practiced. Trust the process. Update your reads when evidence requires it. And let your diagnostic discipline become one of the quiet strengths you bring to the work of leading teams through the friction that real work always produces.