Chapter 1 · Shloka 11— The Yoga of Arjuna's Dejection

ayaneṣhu cha sarveṣhu yathā-bhāgamavasthitāḥ bhīṣhmamevābhirakṣhantu bhavantaḥ sarva eva hi

ayaneṣhu

— at the strategic points

cha

— also

sarveṣhu

— all

yathā-bhāgam

— in respective position

avasthitāḥ

— situated

bhīṣhmam

— to Grandsire Bheeshma

eva

— only

abhirakṣhantu

— defend

bhavantaḥ

— you

sarve

— all

eva hi

— even as

Duryodhana issues his battle order: 'Therefore, all of you, stationed in your respective positions in the divisions of the army, protect Bhishma above all.' Having named his champions and betrayed his anxiety, he settles on a single strategic priority — guard the grandsire Bhishma, his commander-in-chief and greatest warrior. The instruction is militarily sound: protect your strongest, most central player and the whole formation holds. But commentators again catch the undertone. The man who began by boasting of an 'unlimited' army now reveals that everything hinges on protecting one person; his confidence has narrowed to a single point of dependence. There is also dramatic irony, since it is Bhishma's eventual fall that breaks the Kaurava spirit. The verse captures a real principle of strategy — identify and protect what is load-bearing — while quietly continuing the portrait of a leader whose security rests on something fragile and external.

Duryodhana's order is actually smart strategy: identify your most load-bearing player and protect them, because if that pillar falls, everything wobbles. Every team, project and system has such a keystone — the one person, server, relationship or skill that everything quietly depends on. Knowing what yours is, and protecting it, is real wisdom. But the verse also flags the risk of single points of failure. Duryodhana's whole confidence now rests on one man — and in the story, the day Bhishma falls, the Kaurava morale collapses. Over-dependence on one pillar is fragile, however strong that pillar is. The mature version of this lesson is twofold: yes, protect what's critical — but also, don't let everything hinge on a single point. Build some redundancy, develop more than one strength, so your stability doesn't live or die with one person, one client, or one lucky advantage.

Duryodhana's actual order is legit strategy: figure out your most important player and protect them, because if the keystone drops, the whole thing wobbles. Every group/project has one — the one person, the one skill, the one relationship everything quietly leans on. Knowing yours and guarding it = smart. BUT the verse also exposes the trap of a single point of failure: his entire confidence now rides on ONE guy, and in the story, the day Bhishma falls, his whole side's morale crashes. Leaning everything on one pillar is fragile, no matter how strong it is. Pro move: protect what's critical AND don't let your whole stability depend on one person/client/lucky break. Build a backup. Have more than one strength.

Duryodhana tells all his soldiers, 'No matter where you are, protect grandfather Bhishma the most!' Bhishma was his strongest and most important warrior. It was a smart plan — protect your most important player. But it also meant everything depended on just one person, which can be risky if something happens to them.