Jim Collins and Morten T. Hansen published Great by Choice: Uncertainty, Chaos, and Luck—Why Some Thrive Despite Them All in 2011. The book grew from a nine-year research project comparing companies that achieved unusually strong results in unstable environments with selected peers facing similar conditions.
Its answer is deliberately unromantic. The authors argue that exceptional performers were not distinguished mainly by greater boldness, faster reaction, or better luck. They showed disciplined consistency, tested innovation before betting heavily, prepared for severe setbacks, and extracted more value from luck when it arrived. The memorable concepts—the 20 Mile March, firing bullets before cannonballs, productive paranoia, the SMaC recipe, and return on luck—turn those findings into a management vocabulary.
That vocabulary is useful when treated as a set of hypotheses. It becomes dangerous when a historical comparison is presented as a universal law or when discipline becomes an excuse for rigidity and excessive control.
The 20 Mile March is a range, not a punishment
The 20 Mile March represents consistent progress within self-imposed bounds. A good march has both a floor and a ceiling: a minimum that protects momentum in difficult periods and an upper limit that prevents expansion from outrunning capacity in favorable periods.
Apply the idea to one recurring outcome, not to every activity. A service team might commit to resolving a sustainable range of cases each week while preserving response quality. A solo project might set a minimum number of focused sessions and a maximum that leaves room for recovery. The measure should capture meaningful output rather than visible busyness.
Write four lines before starting:
- the outcome being protected;
- the minimum acceptable pace;
- the maximum responsible pace;
- the condition that requires revising the range.
The upper bound matters. Without it, “discipline” can reward overwork in good weeks and create a capacity crash later. The site's account of leadership without slogans adds the necessary test: standards should improve trust, feedback, and responsibility, not merely increase pressure.
Test small before concentrating risk
“Fire bullets, then cannonballs” separates learning from scale. A bullet is a low-cost, low-risk, low-distraction test. A cannonball is a concentrated commitment made after evidence improves confidence. The sequence guards against large bets based only on enthusiasm.
For a proposed initiative, define the smallest experiment that can answer a real question. A landing page may test demand, a manual workflow may test value before automation, and a limited pilot may expose operational costs. Record the result that would justify expansion and the result that would stop it.
Calibration is the important part. Repeating tiny experiments forever can become avoidance. Scaling after one favorable signal can become confirmation bias. Set the decision rule in advance and include counterevidence. The site's framework for evaluating a personal-growth claim works here too: identify the mechanism, evidence, alternatives, costs, and conditions before committing.
Prepare without letting fear run the organization
Productive paranoia means preserving reserves, monitoring critical risk, and rehearsing responses before a crisis. It does not mean treating every uncertainty as a catastrophe. Preparation earns the word “productive” only when it changes a concrete decision.
Use a compact resilience review:
- Name the event that would materially threaten the mission.
- Identify the earliest observable signal.
- Set one reserve or fallback that reduces exposure.
- Assign an owner and a review date.
- Remove one precaution whose cost now exceeds its value.
This last step prevents preparedness from accumulating into bureaucracy. A risk register with no thresholds, owners, or retirement rules produces anxiety in spreadsheet form. Good preparation preserves options while ordinary work continues.
Keep a SMaC recipe open to correction
The authors use SMaC for practices that are specific, methodical, and consistent. A sound recipe states the few operating rules that should remain stable while tactics change. It might specify how evidence is reviewed, how customer harm is escalated, or which quality threshold cannot be traded for speed.
Limit the recipe to a handful of consequential rules. For each one, record why it exists, what evidence supports it, and what would warrant revision. Consistency without an update mechanism is dogma. Constant revision without a stable core is drift.
The site's discussion of systems thinking and consequences helps expose what a rule moves elsewhere. A faster release cadence may increase support load; a larger cash reserve may delay investment; a strict process may exclude unusual but valuable cases. The system, not the slogan, determines whether the rule helps.
Luck is not a character verdict
One of the book's strongest corrections is its treatment of luck as an event rather than a personal quality. The authors ask about return on luck: what an organization does with an unexpected favorable or adverse event. That focus encourages preparation and agency without pretending that outcomes are fully controlled.
Still, the comparison does not erase structural advantage, market power, timing, regulation, or unequal access to capital and talent. A team can respond intelligently and still lose. Another can make weak decisions and benefit from a favorable environment. Avoid turning success into proof of virtue or failure into proof of insufficient discipline.
The research selected rare high performers using defined historical criteria and interpreted differences retrospectively. Its matched comparisons are more informative than isolated success stories, but they cannot establish that copying the practices will cause the same results elsewhere. Current conditions, stakeholders, and measures of success may differ substantially.
A six-week uncertainty experiment
Choose one initiative exposed to changing conditions. Establish a baseline for output, quality, workload, and one stakeholder consequence. Set a bounded march, run one calibrated test, and identify one severe but plausible risk. Review weekly without changing the rules after every noisy result.
At the end of six weeks, ask:
- Did output become more consistent?
- Did the ceiling protect quality and recovery?
- Did the small test reduce uncertainty before a larger commitment?
- Did preparation preserve an option that mattered?
- Which hidden cost appeared elsewhere in the system?
Keep only the practices that improved decisions under pressure. Great by Choice is most useful when it replaces adrenaline with repeatable judgment. It is least useful when “10X” language turns an ordinary organization into a permanent endurance contest.
Sources
Authorship, the subtitle, the nine-year project, and the book's stated purpose were checked on Jim Collins's official book page and official books overview. The 2011 publication and edition details were checked on Penguin's publisher record. The 20 Mile March and the authors' account of the research setting were checked in their official excerpts, “20 Mile March” and “How to Manage Through Chaos”. These are primary accounts from the authors and publisher; they support identity and framework descriptions, not independent proof that the prescriptions cause performance.