A team fails. Everyone gathers to figure out why. The story usually settles fast: the leader overreached, or a lieutenant was incompetent, or a rival simply outplayed them, or bad luck intervened. Someone gets fired. Lessons get written down. Everyone moves on feeling like something was learned.
A few years later, nearly the same failure happens again, with different names attached to the same roles.
Robert Greene's diagnosis of this repeating pattern is blunt: the actors were never really the problem. What's actually broken is the group's underlying dynamic — and unless that gets fixed, it will keep manufacturing the same kind of incompetent lieutenant and the same kind of grandiose leader, indefinitely, no matter who currently holds either job.1
The failure mode has a specific shape. A confused group loses clarity about roles and direction. In that fog, people start protecting their own interests instead of the group's, and factions form. Status anxiety spikes; egos get touchy; people obsess over who's getting more. Into that opening step the group's worst actors — the Stirrers, the low-character operators — who thrive precisely on this kind of contentious atmosphere. Meanwhile the people who are actually good at schmoozing and playing politics, rather than doing real work, rise fastest. Mediocrity gets rewarded.2
Leaders caught inside this dynamic feel the internal dissension dragging them down, and — feeling vulnerable — surround themselves with courtiers who tell them what they want to hear. Inside that insulated bubble, they hatch grandiose, poorly grounded plans, cheered on by exactly the people whose job should have been to push back.2
The way out, Greene argues, isn't replacing the individuals. It's shifting the whole group's orientation toward what he calls the reality group — one built around a tight, ongoing relationship to actual conditions: what needs doing, what resources exist, what the environment genuinely requires, adjusted continually rather than defended stubbornly.3 His named historical instances: Napoleon's battalions, early IBM under Thomas Watson, FDR's first cabinet, John Ford's long-running film crew, Phil Jackson's Chicago Bulls.4
Five strategies build it.
The social force that makes people want to belong and fit in — the same force covered elsewhere in this law — is something a leader can deliberately channel rather than merely survive. The method: establish a genuinely stated purpose, not vague or implied, that the group can organize itself around — creating something excellent, solving a real problem, improving conditions that need improving. Making money should be the result of pursuing that purpose, not the purpose itself.5
The catch is unforgiving: any visible gap between the stated ideal and the group's actual practice destroys the whole effort. You need an actual track record backing the mission, and you need to keep restating the purpose as the group grows and risks drifting from it.5 Done right, this does real psychological work — it gives people access to a nobler, more purposeful side of themselves that the ordinary transactional workplace rarely calls on, and once they've felt that, they help police the culture themselves, isolating the merely political and self-interested rather than requiring a manager to do it for them.6
A leader has finite mental bandwidth, and the single biggest threat to spending it wisely is the fear of delegating. Micromanage, and your own mind clogs with details and courtier squabbles, and that confusion cascades straight down through the group.7
The fix: build a team of lieutenants who share the mission and can be trusted to actually run execution. Select for competence, not charm, and never hire friends. Weigh character as heavily as skill — a brilliant person with a poisonous ego is a net drain, not an asset.7 Choose people whose strengths differ from yours and from each other's, willing to speak up, take initiative, and even challenge outdated rules within the frame of the shared mission.8
Treat the team evenly — no special privileges, rewards and punishments applied consistently, and you sharing in whatever sacrifices the group has to make. Do this and you starve the specific conditions (unfairness, hidden privilege) that grow envy and factions.8
As a group grows, its greatest hidden danger is a bubble forming around the leader — well-meaning lieutenants filtering what reaches the top, telling the leader what will please rather than what's actually happening, until the leader's grip on reality quietly warps without anyone intending it.9
Greene's model is Napoleon reviewing concise field reports from marshals down to individual soldiers — deliberately keeping the report count small enough to actually read, while making sure the sources were diverse enough to triangulate a clear picture of what was really happening.10 The practice: encourage frank, unfiltered discussion up and down the chain; run meetings where people aren't afraid to bruise egos in service of getting it right; stay careful not to signal your own preferred answer too early, since that alone will silently steer the room toward agreeing with you; and bring in outside perspective when the internal view has gone stale.10
Extend the same openness to failure review — turn post-mortems into a genuinely useful practice focused on what the group can learn, not on finding someone to blame.11
People in a group setting are unusually permeable to the emotional state of whoever's leading it — which means a leader's mood isn't a private matter, it's an input the whole group runs on. Greene's counterexample to the standard playbook is instructive: while many coaches try to rev a team up before a big game, Phil Jackson found calmness far more effective — it let players actually execute the plan instead of overreacting to every swing in momentum.12
Grounding the group in concrete, completable tasks naturally produces that calm. So does a visible sense of resolution — not being knocked off course by setbacks, staying persistent, letting the group notice that hysteria over minor shifts in fortune has become mildly embarrassing rather than normal. Confidence helps too, carefully — Greene's caution is that unmanaged confidence slides easily into grandiosity, so it needs to stay tethered to an actual track record rather than untethered belief.13 Periodically breaking routine with something new keeps the group from settling into the complacency success tends to breed.13
The truest read of a team's strength almost never shows up in ordinary conditions. Day to day, most groups look motivated and connected; add real stress, and a different picture surfaces — some people disconnect and think only of themselves, others become anxious in ways that spread.14
Greene's advice is to test this deliberately, before a real crisis forces the question: give people tighter deadlines or harder tasks than usual and watch who rises. Treat anyone who performs better under real pressure as a genuine asset worth protecting. Push the group itself into slightly riskier, more novel action on purpose, and watch how it handles the resulting uncertainty. And after any real crisis or failure, use the aftermath deliberately to assess who actually held up.14
The payoff of doing this repeatedly: a group that's been through real difficulty and come out functional stops flinching at new obstacles — it starts welcoming them, and you can keep expanding what you ask of it as its confidence compounds on real, tested experience rather than untested belief.15
You're leading a team, or trying to fix one that's already drifted into dysfunction — factions forming, mediocrity getting quietly rewarded, the good people going quiet.
Start with the purpose, out loud, specific. Not "we're going to be great" — the actual thing you're building or solving, stated plainly enough that a new hire could repeat it back accurately after one meeting. Then check your own recent decisions against it. If you can find three where the stated purpose and your actual choice diverged, fix those before adding anything else.
Look at your current lieutenants and ask, honestly, whether any of them are there because you like them rather than because they're the strongest person available for the role. That's a harder conversation than it sounds, and it's the one Greene insists you have first.
Audit your own information diet for a week. Count how many of the people telling you what's happening are doing so because it's true, versus because they've learned it's what you want to hear. If you can't tell the difference, that's the bubble Greene is warning about, already partly formed.
Notice your own emotional weather during the next minor setback. Did you stay calm and let the team execute, or did the room pick up your anxiety and amplify it? You are the group's emotional thermostat whether you intended to be or not.
And find one low-stakes way to stress-test your team this month — a tighter deadline, a slightly harder ask than usual. Watch who steps up. That information is worth more than another quarter of steady, untested performance.
Greene's named examples — Napoleon's battalions, early IBM, FDR's cabinet, John Ford's crew, Phil Jackson's Bulls — are all independently well-documented historical cases, though Greene doesn't cite specific sources for any of them within this passage, treating them as background knowledge. [POPULAR SOURCE] throughout.
Open tension: Greene explicitly acknowledges that a true reality group is "a rare occurrence in history," which sits oddly against a chapter otherwise written as a practical five-step playbook. If the named exemplars really are rare exceptions rather than typical outcomes of following the five strategies correctly, the chapter may be understating how much of each case's success depended on unrepeatable circumstance (Napoleon's specific military genius, Jackson's specific roster) rather than the transferable method Greene is presenting them as evidence for.
Open question: all five named examples are led by one exceptionally capable individual at the top. Does the reality group model actually require that kind of singular leadership talent to work, or can the same five strategies produce a reality group under more distributed, less individually brilliant leadership?
This chapter's Strategy Two — never hire friends, select purely on competence and character — sits in real tension with Strategy Four's claim that a leader's genuine, felt calm (not performed calm) is what actually spreads through a group. Greene doesn't reconcile the two, but a working reading connects them: the discipline of Strategy Two (a competent team you can actually trust) is very plausibly the precondition for the genuine calm Strategy Four requires — a leader surrounded by unreliable people hired for comfort rather than skill has legitimate reasons to feel anxious, and that anxiety will read through no matter how well it's performed. The five strategies aren't independent levers; Two appears to be load-bearing for Four in a way the chapter's flat, parallel structure obscures.
→ Shackleton and the Endurance
That business-domain page documents Ernest Shackleton monitoring his crew's morale as closely as he monitored the weather during the Endurance's Antarctic ordeal — including engineering small, seemingly minor improvisations (like hot milk) specifically to protect one struggling crew member's psychological state. This page's Strategy Four cannot be fully understood without that case, because Shackleton supplies the extreme-conditions proof that Phil Jackson's calm-over-hype approach isn't a basketball-specific luxury — it holds under genuinely life-or-death stakes, where the temptation to manufacture urgency and fear would seem far more justified than in a playoff game.
The insight neither page produces alone: Greene frames productive-emotion management as something a leader does to a group; Shackleton's case shows it functioning as continuous, individualized diagnostic work — he wasn't broadcasting one emotional tone at the whole crew, he was reading who specifically was closest to breaking and adjusting a small, targeted intervention for that one person. The Reality Group strategy, read alongside Shackleton, sharpens from "keep the group calm" into "know which individual member's state is currently the group's actual bottleneck, and intervene there specifically."
→ Ministers Not Yes-Men: Pillai's Reading of Arthashastra 1.7.9
That page reads Kautilya's Arthashastra through the image of a one-wheeled cart — a leader who refuses to share real authority and information access cannot actually move, no matter how much individual effort they apply, because a cart needs a second wheel to be a vehicle at all. This page's Strategy Three cannot be fully understood without that framing, because it supplies the deeper mechanism Greene's Napoleon example only gestures at: the problem with an information bubble isn't just inaccurate data, it's that a leader operating alone, however brilliant, is structurally incapable of the thing an organization actually needs — which is why Kautilya's ancient prescription and Greene's modern one converge on the identical fix independently, twenty-three centuries apart.
The insight the two pages produce together: "let information flow freely" sounds like a communications policy, but both traditions treat it as something closer to a structural necessity of leadership itself — not an optional virtue for the unusually humble leader, but the specific thing that converts a single person's effort into an organization's capacity. A leader who insists on being the only wheel isn't being admirably self-reliant; by both accounts, they've built a vehicle that is mechanically incapable of moving, regardless of how hard that one wheel works.
Sharpest implication: the five strategies read as parallel and independent, but Strategy Two — the quality of the lieutenants — is the load-bearing one the other four quietly depend on. A leader can state a purpose beautifully, want open information flow, intend to model calm, and plan to battle-test the team — and every one of those efforts will be sabotaged by a single poorly chosen, poisonous-egoed lieutenant sitting between the leader and the group. Fix the team's composition first; the other four strategies become dramatically easier to execute once that's right, and dramatically harder to execute if it isn't.
Generative questions: