Before the great war in the Mahabharat, Krishna travels to the enemy court on one last mission: to stop the war.
The deal is simple. If the Kauravas give the Pandavas just five villages, everyone goes home and no one dies. Krishna walks into the most powerful court in the land and argues for peace with everything he has.
And Krishna knows how unlikely peace is with Duryodhana.
He knows Duryodhana, the Kaurava prince. He knows how the man thinks. So why make the trip at all?
Not simply to change Duryodhana’s mind. Krishna goes so that when the war comes, no one can say the Pandavas started it. He wants every elder and king in that hall to watch peace get offered honestly, and refused. The meeting he appears to be losing is doing exactly what he needs. He walks out having “failed,” and that failure is the win.
Krishna didn’t go to win the argument in the room. He went because he had already decided what the room was for.
Here is the move, and it is simpler than it sounds. He treated the meeting as a place to confirm an outcome, not to create one. He argued for peace with everything he had. But he wasn’t counting on that argument to move Duryodhana. He was making the case for the record, so the whole hall would watch it play out exactly as he needed.
The principle
Meetings rarely decide things. The deciding mostly happens before, in the quiet. The meeting is where it gets confirmed out loud.
Put another way: an important meeting should almost never be the first place a key person encounters the idea, the problem, or the decision. This is easy to forget. As a new manager, you walk into the big meeting hoping to win it live: on your feet, in front of everyone, in the one room where changing a mind is hardest. That feels like leadership. It is actually the hardest way to get a yes.
Think about why a meeting is a bad place to persuade anyone:
People are being watched. Changing your mind in front of everyone feels like losing face, so people dig in instead.
People feel rushed. A real concern needs time to sit with. In the room, they either blurt a half-formed version of it or stay quiet and kill your idea later.
People are surprised. When someone hears your idea for the first time in the room, their first instinct is to defend, not to consider. Surprise triggers defense.
So the real work happens before the meeting, in the quiet. The pre-read someone actually opened. The 1:1 where the key person got to react without an audience. The hallway sentence that let them object where saving face costs nothing. By the time everyone sits down, the big surprises are gone. Whatever disagreement is left is disagreement you already knew about, and the meeting is where you resolve it in the open, not where you discover it for the first time.
Here is a picture that helps: a wedding. The couple decided to marry weeks ago. The ceremony doesn’t create the marriage. It makes it official and lets everyone witness it. No one walks into their own wedding hoping to win an argument about whether to get married. Treat your important meetings the same way. Do the real work first. Let the room make it official.
So the question is never “how do I perform in the room?” It is “what do I need the room to confirm, and have I secured that yet?”
The translation
Early in my career, I was handed my first big project: build an IVR system for an important client. I thought I knew exactly what we were building. I gathered the team, assigned people, and walked into the kickoff ready to go.
Twenty minutes in, it fell apart. What I thought was a simple system, my boss thought was something three times the size. We had understood the project completely differently, and now that gap was sitting on the table in front of everyone, with people already assigned to the wrong work.
The mistake wasn’t the misunderstanding. It was that I’d let the meeting be the first place we checked whether we agreed. I had assumed alignment instead of confirming it.
So I fixed it the slow way. Before the next project, I sat with each stakeholder privately and got explicit agreement on scope, one conversation at a time, long before anyone gathered in a room. After that, kickoffs stopped being where we discovered disagreements. They became where we confirmed we didn’t have any.
“Winning before the meeting” is not a trick, and it is not politics in a bad sense. It is three ordinary things, done ahead of time.
No one is surprised. If a key person is hearing your proposal for the first time in the room, you are already behind. The people who matter should have seen it privately, with room to object where saving face costs nothing. You are not hiding the ball. You are giving them the chance to say no somewhere it is cheap to say.
Say you want to propose a new on-call rotation. Before the meeting, you send it to the two engineers most likely to hate it and ask, “What am I missing?” One of them points out it breaks during holidays. You fix it. Now, in the room, that objection never even comes up, because you already handled it in private.
The hard questions are already answered. You should know the three toughest objections before you walk in, because you asked the people likely to raise them and either fixed the concern or decided where you’ll hold your ground. The important objections should not be new to you.
You know what the room is for. Is it a decision? Just alignment? Cover from your boss so you can move? A place to talk through a disagreement you already know is there? Krishna’s meeting looked like a negotiation, but it was really about proof: proof that peace was offered. If you can’t say in one sentence what you need the room to confirm, you’ll drift, and the loudest person there will name it for you.
Put simply: you are not going in to create the outcome. You are going in to confirm one you already built. Which means most of your prep is not about the meeting at all. It is the conversations that happen before it. The deck is the smallest part.
The practice
Before your next important meeting, do the work that actually decides it:
List everyone whose “no” would sink this, and everyone the decision actually affects. These are often the same people: the ones living with the outcome are the ones whose quiet no shows up later. This is not about hunting for powerful people and getting them onside in secret. Talk to each one before the meeting, even a two-line message, and let them react in private, where they can change their mind without an audience.
Write the three hardest questions you could be asked. If you don’t have a real answer to one of them, that is not a meeting problem, it is a homework problem. Fix it before, not during.
Finish this sentence: “I need this meeting to confirm ___.” If it’s a decision, know who makes it and what they need to hear to say yes. If it’s alignment, know exactly which known disagreement you’re there to settle.
Do this and the meeting itself becomes almost boring, a formality confirming what you already built. That flat, boring feeling is what winning looks like. Krishna’s face never changed in that court, because nothing in that room was still being decided.
Next week: Choosing Your Battles, why the most strategic word in the language is “no.”
This is part 4 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.