When the great war of the Mahabharat finally comes, one of the strongest men alive looks at it and walks away.
His name is Balarama. In the way the story is often told, he is Krishna’s elder brother, and one of the mightiest warriors of the age. He had trained fighters on both sides: Bhima among the Pandavas, and Duryodhana among the Kauravas. Both sides knew his strength, and both had reason to want him. This is a war that will kill most of the men on that field and end an entire generation. And Balarama decides it is not his to fight. He leaves on a long pilgrimage and returns only near the end, in time to witness the final confrontation between Bhima and Duryodhana.
It is easy to read that as weakness, as running from the hard thing. The way I read it, it is the opposite. Balarama looked at a fight everyone assumed he would join, and made a deliberate choice: not this one. He seems to have understood something simple. A warrior who fights every battle offered to him is not strong. He is just available.
The Pandavas, who had suffered years of exile and humiliation, make a similar choice from the other direction. They do not begin by demanding the whole kingdom back. As it is commonly told, their final offer is five villages. Five. Not because they do not want the fight, but as a last attempt to secure a settlement they could live with, and avoid a war they know will cost far more than it can ever return. It is Duryodhana, the Kaurava prince, who refuses to give up even a needle’s point of land. He is the one who cannot choose his battles. In the story, that inability destroys him and nearly everyone he loves.
The principle
There are three habits that look separate but are really the same thing. All three are what I mean by choosing your battles.
Restraint. Not fighting a battle just because it landed in front of you.
Prioritization. Spending your limited energy on the few things that truly matter.
Saying no. Declining the requests, meetings, and fights that were never yours to take.
We tend to treat these as small logistics. Calendar tips. Productivity tricks. They are not. They are one discipline, and at heart it is a discipline of self-respect. Every yes is a no to something else, even when you can’t see the something else yet. A person who almost never says no is not more generous than the rest of us. In practice, they have handed the ranking of their own time to whoever asked last and loudest.
Duryodhana’s tragedy, the way I read it, is that he could not tell a battle worth fighting from a battle that was merely available. His pride turned every slight into a war. And someone who fights every battle tends to lose the one that actually mattered, because they show up to it already exhausted.
The translation
A few years ago I made this exact mistake, and it cost real money.
We needed reporting for our product, and early on I built it the quick way: pointing our reporting tool straight at the production database. It worked, and I was proud of how little it took. When teammates suggested we invest in a proper, separate data pipeline, I pushed back every time. Too heavy. Not worth it. We were fine.
We were not fine. As we grew, those reporting queries started dragging down the actual application, the thing customers depended on. Infra costs climbed. We burned engineering weeks patching around a problem I would not name out loud.
The honest truth is that I had stopped making a technical call. I was defending my original decision because it was mine. I had turned “keep the simple setup” into a battle, and I kept fighting it long after the cost stopped making sense.
When we finally moved reporting onto its own pipeline, the application steadied and the noise went away. I lost the battle I should have conceded months earlier because I refused to fight the one that actually mattered.
The lesson was not to avoid difficult decisions. It was to stop spending energy defending a decision that no longer served the work.
For a new manager, the inability to choose battles shows up almost everywhere:
The meeting you attend because you were invited, not because you are needed. Being available is not the same as contributing.
The disagreement you win that quietly costs you a relationship you will need next quarter. Some battles are more expensive to win than to lose.
The pet project you can’t put down even after it has stopped mattering, because your ego is now attached to it.
The yes you gave because saying no felt rude, and now you resent the person you said it to.
Here is a way to picture it. Think of your attention as a small budget you get to spend once, each day. Every “sure, I’ll take that” is money leaving the account. Most new managers never see the balance drop, because saying yes feels free in the moment. The cost shows up later, on the work that actually had your name on it.
Say a peer asks you to join a working group sorting out a process problem in another team. It is interesting, you have opinions, and saying yes feels helpful. But it is not your team’s problem, and it will eat two hours a week for a quarter, time your own people needed. That is a battle that is available, not yours. Handing it back, kindly, is not laziness. It is you defending the budget for the work only you can do.
Choosing battles well comes down to one honest question, asked before you commit: is this mine to fight, and is it worth what it will cost? Many requests fail one test or the other. The steadiest managers I have watched are rarely the ones who do the most. They are the ones who have decided, clearly, what they will not do, and can say so without a long apology.
None of this is about becoming the person who says no to everything and calls it focus. Choosing your battles means you say yes on purpose too, and then actually show up for the ones you chose.
The practice
This week, run everything asked of you through one filter, and then act on it:
“Is this mine?” Is this really my battle, or am I fighting it only because it got handed to me and no one else picked it up? If it is not yours, hand it back, gently and early.
“Is it worth the cost?” Not just the hours. The relationship you spend, the focus you lose, the thing you now can’t do. Some wins are not worth their price.
Say one clean no. Decline one thing you would normally accept out of habit or guilt. You do not owe a long defense. “I can’t take this on and do it well” is a complete sentence. Notice that the sky does not fall.
Balarama walked away from the biggest war of the age. The way I read it, his decision was not weakness. It was a choice about what he was, and was not, willing to take responsibility for. Duryodhana refused to concede even a needle’s point of land, and lost everything. The difference was not strength. It was the ability to choose.
Next week: Every Team Has Its Kurukshetra. Conflict is inevitable; what you do with it isn’t.
This is part 5 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.
This article is great. I like how you include your past experiences.