Watch a bullock-cart with one wheel try to go anywhere. It can't. It pivots around the stuck axle and digs into the ground. It will collapse before it has moved a meter. That is Pillai's image — and Kautilya's, beneath the translation — for the leader who refuses to share authority. The one-wheel cart is not lazy. It is not under-resourced. It has a wheel. It has an axle. It has someone trying to push. What it does not have is the second wheel that makes the first wheel useful. Pillai's whole chapter on Arthashastra 1.7.9 builds outward from this image, and the destination is uncomfortable: the family-business owner in the Indian context who builds his company around himself and then cannot understand why nothing scales beyond his personal bandwidth.1
Kautilya's sutra reads, in Pillai's quoted translation: "Rulership can be successfully carried out (only) with the help of associates. One wheel alone does not turn. Therefore, he should appoint ministers and listen to their opinion." (1.7.9)1 Pillai's substitution is unusually pointed here. He names the failure mode out loud. Most chapters in the book do the substitution gently — the king becomes you, the minister becomes your colleague — and the reader is invited to apply the principle. Chapter 28 ("Managers Are Important") is different. Pillai names a specific population — Indian family-business owners — and a specific pathology: the "no questions asked" leadership style. The chapter is one of the most direct moments in the book where Pillai's interpretive frame stops being polite.
Kautilya's 1.7.9 sits in the cabinet-architecture chapter of Book 1. The Arthashastra is rigorous about the ministerial apparatus. Kautilya specifies how many ministers to have, what their qualifications must be, how to test their loyalty, how to compensate them, how to organize their advisory function around different kinds of decisions. 1.7.9 is the ground sutra for the entire ministerial system: rulership cannot be done alone, the king must appoint ministers, and the king must listen to them. The instruction is not just to delegate but to actually receive their input. Pillai quotes the king-and-minister-as-sea-and-waves analogy that the Arthashastra tradition carries: "Both were dependent on each other, influenced by, and influencing, each other."1
What Pillai's reading ingests from 1.7.9 is the listening requirement. The delegation requirement alone is unremarkable — every management book in print agrees you should delegate. What distinguishes 1.7.9 is the second clause: and listen to their opinion. Pillai's chapter is built on the gap between the two requirements. Many leaders delegate authority without delegating decision-input. They give the minister a chair at the table but not a vote on what gets decided. That is the "yes-man" pattern Pillai names. The minister exists. The minister has been appointed. The minister has not been listened to.
Pillai's most striking move in this chapter is to name the failure pattern directly. The passage runs as follows:
"I have personally seen company owners who do not trust anyone at all. When it comes to their business, they restrict all control to themselves. Even if they have a manager, it is only as a formality. They do not allow the manager to think, innovate or contribute. Such business leaders like to have yes-men around them and follow the 'no questions asked' policy."1
Three things are happening in this passage. First, the population is identified — Indian company owners Pillai has personally encountered. Second, the pathology is specified — total control-retention combined with formal-only delegation. Third, the failure mechanism is named — yes-men around the leader, no-questions-asked culture downstream. Pillai is not running a generic management lesson here. He is running a culturally specific diagnostic. The phenomenon he describes is well-documented in the Indian family-business literature; family-controlled firms in India have particularly high rates of founder-bottleneck patterns where succession fails because no second-tier executive has been allowed to develop independent judgment.1
The chapter's escalation: "It makes for poor leadership skills." Pillai is calling this a leadership failure, not an executive style choice. The 1.7.9 reading is normative — the leader who does not delegate decision-input is not a strong leader who chose autocracy; he is a weak leader who could not build the cabinet 1.7.9 requires.
Pillai unpacks 1.7.9 into four operational practices for the leader who wants to actually carry the second wheel.
Move 1 — Right person for the right job. Before appointing anyone, ask the diagnostic questions: Is the person fit for the job? Do they have the required skill set and experience? Is he the right person to be delegated this work? If experience is missing, ask whether the person is trainable. "Look at the natural strengths of the person and based on that, make the person a part of your project."1 Pillai is implementing 1.8.28-29 (capacity-based selection) at this layer; the 1.7.9 cabinet only works if the cabinet members were correctly selected.
Move 2 — Pay well. This is Pillai's tactical operationalization of the listening requirement. "Pay the person well. Pay as high as you can afford. Today, human capital is the best investment you can make."1 He quotes a police-force commander: "I take care of them, and they take care of my work." The mechanism: once you take care of the financial concerns of your team members, they become mentally free to perform — they can focus on the job instead of on their own precarity. Underpaying ministers and then expecting them to give you their best decision-input is a structural contradiction.
Move 3 — Motivate them; let them fail. This is where the 1.7.9 listening-requirement becomes operationally concrete. "Empower them. Let them take decisions. Allow them to fail. All this is part of growth."1 Pillai is explicit that allowing failure is part of the empowerment. No one becomes an expert on day one. It is years of trial and error that produce the judgment 1.7.9 requires the leader to listen to. Pillai's small-gestures list — pep talks, dinner, picnic, a pat on the shoulder, a thank-you, a sorry — is the daily infrastructure that keeps the cabinet operationally engaged.
Move 4 — Give credit. This is Pillai's strongest move and the one he tags with a named exemplar. "It is said that you will be happy if you work hard and succeed, regardless of who takes the credit. Our former president, Dr A.P.J. Abdul Kalam, was known for this quality. When any of his projects succeeded, he gave the credit to his team members and project managers. When he failed, he took full responsibility for the failure."1 The Kalam pattern is the structural inverse of the yes-man pattern. The yes-man leader takes credit for successes and distributes blame for failures; the 1.7.9 leader distributes credit for successes and absorbs blame for failures. Pillai closes the chapter naming what this credit-pattern produces: humility. "Humility is what draws everyone towards you."1
The 1.7.9 substitution from king to modern-leader holds because the underlying structural constraint is real: no single decision-maker can hold the complexity of a multi-domain operation alone. Kingdoms cannot be run by one person. Companies cannot. Even families cannot — Pillai's saptanga reading at Chapter 66 makes the same point at family-scale by naming Amatya (spouse) as the executive's structural complement. The one-wheel-cart image works at every scale because the underlying physics of multi-input decision-making works at every scale. Even the most autocratic leaders who appear to operate alone are in fact relying on a cabinet — the cabinet is just unofficial, unpaid, and selected for sycophancy rather than judgment.
The yes-man pattern Pillai names is, structurally, the failure mode of pretending the cabinet is not there. The leader still has people around him giving him decision-input. He just refuses to acknowledge that he is taking input from them. The input contaminates his decisions without contributing the diversity-of-perspective that good cabinet structure produces. This is why the yes-man pattern fails so consistently: the leader thinks he is making solo decisions, but he is actually making decisions filtered through a group selected to confirm his pre-existing positions. The decisions get worse over time as the filter tightens.
The page gives back a cabinet-quality diagnostic with one operational test. When was the last time someone in your cabinet told you you were wrong, and you changed your mind because of it? If the answer is "never," you do not have a 1.7.9 cabinet. You have a yes-man arrangement that looks like a cabinet from the outside. The test is severe but operational. Pillai's chapter is implicit on this — he describes the failure mode without offering a clean test for it — but the test follows directly from the listening requirement of 1.7.9.
The page also gives back a promotion-criteria filter for next-generation leaders. If you are evaluating your team for who should ascend, ask not "who agrees with me most" but "who has, in the past year, brought me a position I initially rejected and then convinced me to revise?" That person is exhibiting the 1.7.9 minister-pattern. The person who has only ever delivered confirming feedback is, by Pillai's framework, not yet a minister candidate — they are still in yes-man category.
Pillai is the only ingested source for this specific 1.7.9 reading. But the page sits in productive tension with two other vault concepts: the Adhyaksha Bureaucratic Architecture page (the scholarly grounding for Kautilya's cabinet system) and the broader behavioral-mechanics literature on power-consolidation strategies that DO recommend something like yes-man arrangements for strategic reasons.
The convergence with the Adhyaksha tradition: both Pillai and the scholarly readings agree that Kautilya's cabinet is structurally rigorous and not optional. The Arthashastra specifies the number, type, qualifications, and consultation protocols for ministers with operational precision. 1.7.9 is the keystone sutra of that whole apparatus. Pillai and the scholarly tradition read it the same way — the king cannot operate alone, must delegate, must listen.
The tension with the behavioral-mechanics power-consolidation literature: some strategic frameworks recommend the yes-man pattern under specific conditions. The Lung tradecraft-influence reading of Kautilya, for example, emphasizes information-asymmetry and the strategic value of agents who report rather than challenge — a structural register that pulls toward the yes-man pattern rather than away from it. Pillai's dharmic-pedagogy reading and Lung's tradecraft-influence reading split sharply on 1.7.9. Pillai treats the listening-requirement as load-bearing; Lung's frame, applied honestly, would say that listening is conditional on whether the minister's information has been verified as independent and reliable, otherwise the input is noise the leader should filter out. The split tells you what neither reader names alone: 1.7.9 only works if you have already done the selection-and-loyalty-testing work that the rest of the Arthashastra describes. The cabinet you listen to has to be a cabinet you have constructed correctly first. A leader who appoints ministers without verification and then listens to them produces decisions filtered through unverified sources — which is its own failure mode, structurally distinct from yes-man arrangements but equally fatal.
The minister-not-yes-man pattern Pillai extracts from 1.7.9 surfaces across the vault in adjacent domains under different names. The rubber-duck version: any leader who needs to make decisions in a multi-domain operational environment requires a cabinet of advisors with independent judgment, and any leader who screens advisors for confirmation rather than challenge will produce decisions that are systematically worse over time. Naming the cross-domain parallels reveals what kind of cognitive-architecture claim 1.7.9 is making.
Behavioral mechanics: Laws of Human Behavior (Greene psychology-of-power tradition) — Greene's literature on power dynamics names the "court of flatterers" pattern as one of the most reliable failure modes in long-tenured power-holders. The leader becomes surrounded by people whose careers depend on his approval, the approval becomes the medium of advancement inside the court, and over time the leader cannot distinguish accurate signal from approval-seeking signal. This is the same pattern Pillai names at 1.7.9, but the behavioral-mechanics framing identifies the mechanism — the courtier-incentive structure is what produces yes-man arrangements; it is not a personality flaw of the leader. Where they diverge: Pillai's framing puts the responsibility on the leader to refuse the yes-man pattern; the behavioral-mechanics framing puts the responsibility on the courtier-incentive structure to be redesigned. The insight neither produces alone: the 1.7.9 cabinet only stays a 1.7.9 cabinet if the incentive structure rewards challenge over confirmation. Pillai's pay-well + give-credit moves are partial structural interventions, but they don't fully address the deeper issue — that long-tenured power-holders need someone in the cabinet who is positioned to lose nothing if they tell the leader he is wrong. The Indian-tradition figure of the vidushaka (court jester) was structurally positioned this way; modern corporate cabinets rarely have anyone in this slot. The 1.7.9 reading needs the courtier-incentive structure named for it to hold.
Psychology: Narcissism Spectrum — the narcissism literature describes a leader-pathology in which the leader's self-image is structurally incompatible with receiving challenge from anyone perceived as subordinate. The cabinet becomes an extension of the leader's ego rather than an independent decision-input system. Pillai's "no questions asked" pattern is a behavioral signature of narcissistic-spectrum leadership at the institutional level. The insight neither produces alone: the leadership-development literature that addresses 1.7.9 problems (delegation training, empowerment workshops, feedback culture) is operating downstream of a psychological structure it cannot reach. The leader whose self-image cannot tolerate challenge will not be trained out of yes-man arrangements; he will simply learn the surface vocabulary of empowerment while preserving the underlying control pattern. Pillai's emphasis on humility as the closing concept of the chapter is structurally important — humility is the psychological substrate that 1.7.9 requires the leader to have already built before the cabinet can be operationally functional. The chapter names the institutional pattern; the psychology literature names the individual structure that has to be in place for the institutional pattern to hold.
Creative practice: Argument as Dialectic Not Defense — the writing-craft literature describes the parallel pattern in essay-craft: writers who treat editor-feedback as something to defend against rather than something to integrate produce work that ossifies around their pre-existing positions. The yes-man pattern at company-scale is structurally the same as the defensive-writer pattern at essay-scale. In both cases, the work product gets worse over time as the feedback-loop tightens. The insight neither produces alone: the cabinet is the corporate analogue of the writing-circle, and both fail in the same way for the same reasons. A writer who selects readers who praise the work cannot improve; a CEO who selects ministers who confirm decisions cannot improve either. The 1.7.9 reading suggests that leadership-development should be structurally modeled on writing-development — the leader should be apprenticed to a "writing-circle" of independent advisors whose job is to make decisions better through challenge, the same way an editor's job is to make prose better through challenge. Almost no leadership-development programs are structured this way.
The Sharpest Implication
If you take 1.7.9 seriously as the foundational sutra of leadership, then most of the leadership styles celebrated in business-media are 1.7.9 failures dressed up as visionary autocracy. The "founder who carries the company in his head" narrative is a yes-man pattern with the leader as protagonist. The "decisive CEO who makes the call alone" narrative is the same. The 1.7.9 reading says: these leaders are operating one-wheel carts, and the carts will eventually pivot around their axle and collapse. The collapse usually happens at succession — the company cannot function once the founder leaves because no one else has been allowed to develop the judgment the company actually requires. The uncomfortable third-wire reading is that what business-media celebrates as "visionary leadership" is often the publicly-visible phase of a company that will collapse in the next decade, because the cabinet that 1.7.9 says it needed was never built. The cult-of-personality CEO is, by Pillai's framework, building a company that cannot survive him — and the celebration of his decisiveness is the eulogy of the company being written in real time.
Generative Questions