The war of the Mahabharat is a family fight. This is the detail that is easy to forget. The way the story is commonly told, Kurukshetra is not two nations at war. It is one family turning its weapons on itself: cousins raised in the same palace, taught by the same teacher, blessed by the same grandfather. Bhishma, the grandfather who loves both sides, fights for the Kauravas because his vows and his loyalty to the throne bind him. Drona, the teacher, aims arrows at the students he trained. Karna and Arjuna, who (as the story goes) are brothers without both of them knowing it, hunt each other across the field.
And here is what is at stake, so the scene lands even if you have never opened the epic: this is not a war anyone truly wanted. It is a war that, despite repeated attempts to prevent it, eventually became impossible to contain. By the end, almost everyone on that field is dead, on both sides. A whole family destroys itself over a conflict that kept escalating.
Because the way I read it, the tragedy of the Mahabharat is not that a conflict happened. Conflicts happen. The tragedy is how it was fought. It was allowed to grow, over years, from the dice game into a total war, until the conflict had reached a point where the cost would be almost unimaginable. At many points along the way, the fight could have been cooled. Krishna even went as a final emissary of peace, but that effort failed. And so the field is remembered for the slaughter, not for the family it used to be.
The principle
On any team worth being on, conflict is not a sign of failure. It is usually a sign that people care about different things and are willing to say so. A team that never disagrees openly is not necessarily a healthy team. Sometimes it is a team where people no longer feel safe telling the truth. So the goal is not to get rid of conflict. It is to fight it in a way that leaves the team more whole afterward, not less.
There are, roughly, two kinds of conflict, and from a distance they can look the same. One kind is about the work: which approach, whose data, what tradeoff. That kind, argued in the open, tends to make decisions better. The other kind is about ego and position: who is right, who won, who feels threatened. That kind, left alone, slowly turns colleagues into opponents. And once a fight becomes personal, almost no outcome feels good enough, because the fight is no longer about the thing you were actually deciding.
The way I read Kurukshetra, the whole disaster is the story of the first kind of conflict (who should rule, an honest and real question) being allowed to curdle into the second (who must be destroyed). The escalation is the villain here, not the disagreement.
Think of a house fire. A small flame in a pan is a normal part of cooking. The problem is when no one deals with it, and it reaches the curtain, then the wall, then the whole kitchen. The flame was never the danger. Leaving it to spread was. Team conflict works the same way.
The translation
Early in my career, I was leading a small team building an IVR SDK, and two of my most senior engineers could not agree on the architecture. One wanted a single, traditional build. The other wanted to break it into smaller services. At first this was exactly the good kind of fight: two capable people, two real philosophies, argued in the open. I let it run, because it was making the design better.
Then it shifted. The comments in code reviews got sharper. The disagreement stopped being about the design and started being about who was the better engineer. The room went tense. Standups got quiet in the wrong way. That was the moment that mattered, and I almost missed it, because I was still watching the technical argument and not the two people having it.
What fixed it was not picking a winner. I met each of them alone to hear the real concern, then put the two designs into a structured debate with clear criteria, and brought in a respected architect from another team as a neutral outside voice. We landed on a hybrid neither had proposed alone. The feature shipped. But the lesson stayed with me: the disagreement was never the problem. The moment it became personal was.
Watch how a team handles conflict and you can often see whether it will heal or fracture.
Healing teams fight about the work, out loud, and then decide. The disagreement is on the table, everyone gets heard, a call gets made, and people commit to it, including the ones who lost the argument. The conflict is closed.
Fracturing teams take it underground. The disagreement goes quiet in the room and loud in the side channels: the DMs, the hallway, the after-meeting meeting. Nothing gets decided, so it just piles up. Like the years between the dice game and the war, resentment compounds until it is no longer about the original issue at all.
The escalation tell. When people start needing to be right more than they need the team to win, you may be watching a Kurukshetra begin. That is often the moment to step in, before positions harden into vows no one can climb down from.
Say you are a new manager and two engineers on your team disagree about how to build something. At first it sounds healthy: one wants the fast approach, the other wants the safe one, and they argue it in standup. Good. But a week later you notice the arguing has gone quiet, and instead they are each quietly building their own version, cc-ing you on messages that are really about the other person. That is the flame reaching the curtain. The disagreement did not go away. It went underground and turned personal. Your job is not to pick the winner. It is to pull the fight back above ground and back onto the work.
Because a leader’s job in team conflict is usually not to prevent it. It is to keep it about the work, keep it in the open, and close it, so it does not ferment into the kind of conflict that ends teams.
The practice
Next time conflict flares on your team, and at some point it will, try three things:
Name which kind it is, out loud. Something like: “I think we’re disagreeing about the approach here, not about each other. Let’s keep it there.” Naming it early helps keep a work conflict from sliding into an ego conflict.
Bring the underground conversation up. If the real disagreement is happening in DMs and hallways, say so, gently: “It feels like there’s a concern we’re not talking about openly. Let’s put it on the table.” Silence is where resentment compounds.
Close the loop. After the argument, make the decision explicit and ask for commitment, including from the people who did not get their way. An unclosed conflict rarely disappears. It waits.
Every team has its Kurukshetra: a moment when what people care about collides. The field is only remembered for the slaughter because no one cooled the fight in time. You can.
Next week: The Battle Within, the opponent you can’t out-argue.
This is part 6 of a 10-part series on the inner game of organizational life, drawn from the Mahabharat. Subscribe to get one episode every Thursday, one battle at a time.