
Is Your Team 'Good' or 'Great'? Here's How to Make the Leap.
The difference between a good team and a great one is rarely talent: Collins's five concepts, applied at team scale.
Ever feel like your team is doing all the right things, but still not achieving breakthrough results? That's the difference between “good” and “great.” Jim Collins's Good to Great offers a roadmap for managers ready to stop chasing quick wins and start building something that lasts. It's not about a magical innovation or a charismatic leader; it's about cultivating a culture of discipline.
Collins studied companies. But you don't run a company: you run a team. So let's take his five core concepts and translate each one to the scale where you actually work: a group of eight to fifteen people, a weekly rhythm, a shared backlog.
Level 5 leadership: humility plus will, at team scale
Level 5 leaders combine extreme personal humility with intense professional will. They channel ambition into the team's success rather than personal glory: plow horses, not show horses. Collins's most useful image here is the window and the mirror: when things go well, a Level 5 leader looks out the window to credit others; when things go wrong, they look in the mirror.
What that looks like in a team: in the quarterly review, you name the people behind each win, specifically, not “great team effort.” And when the release slips, you open the retro with the decision you got wrong before anyone else has to say it. Do this twice and watch what happens to honesty in the room. Humility and will are two ends of a spectrum you travel deliberately: much like the postures we describe in the leadership range.
First who, then what: casting before roadmap
Collins's most quoted idea: get the right people on the bus, in the right seats, before deciding where to drive. At team scale, this inverts how most managers plan. We write the roadmap first, then wonder why the staffing doesn't fit.
Try the team version of the question at your next planning cycle: for each seat on this team, if the person offered to leave tomorrow, would I fight to keep them? And its mirror: is anyone excellent but in the wrong seat? One of the most common moves we see in coaching sessions is also the most avoided: moving a strong performer from a seat where they're adequate to one where they'd be exceptional, because the disruption feels risky.
One caution Collins underplays: “rigorous, not ruthless” only works when people can speak honestly about fit without fearing for their heads. Rigor without psychological safety (Edmondson's research on how teams learn) just teaches everyone to hide weaknesses: the exact opposite of what “first who” needs.
What is a Hedgehog Concept for a team?
Great companies simplify their world into one elegant concept at the intersection of three circles: what they're deeply passionate about, what they can be the best at, and what drives their economic engine.
For a team, translate the circles: What does this team genuinely care about? What can we be the best at in our organization, not the world? And what single metric best captures the value we produce? A platform team we'd consider a textbook case stopped accepting bespoke one-off requests, defined itself as “the best at paved roads that other teams actually adopt,” and made adoption its one number. Half their backlog disappeared; their influence doubled.
The discipline is in what you decline. A hedgehog concept is useless if you keep saying yes to everything adjacent to it, that's the dilution trap. And finding your “economic engine” at team level usually means finding the one constraint that governs your throughput, which is exactly the skill of finding the bottleneck.
A culture of discipline: freedom within a framework
Discipline here isn't bureaucracy: it's the opposite. When you have disciplined people, you don't need hierarchy. When you have disciplined thought, you don't need bureaucracy. When you have disciplined action, you don't need excessive controls.
Team rituals that build it: a quarterly stop-doing list reviewed with the same seriousness as the to-do list; a definition of done nobody negotiates under deadline pressure; decision rules agreed in calm that hold in storms. Discipline is what lets you loosen your grip as a manager: the more self-disciplined the team, the further toward coaching you can shift.
The flywheel: momentum from consistent pushes
Success isn't a single “aha” moment. It's the cumulative effect of pushing a heavy flywheel, turn upon turn, until momentum compounds. For a team, the flywheel is usually a cadence: the weekly demo that slowly builds stakeholder trust, the monthly quality review that slowly drops the defect rate. No single push matters; the unbroken sequence is everything: the same logic as consistency over perfection. The corollary Collins insists on: there is also a doom loop, where teams lurch from one silver-bullet reorganization to the next, resetting the flywheel each time.
Should we trust Collins's method? An honest caveat
We owe you the critique as well as the concepts. Good to Great's methodology has been seriously challenged: most sharply by Phil Rosenzweig in The Halo Effect. Two problems stand out.
First, survivorship bias: Collins selected companies because they had already succeeded, then looked backward for shared traits. Picking winners and studying what they have in common can't tell you whether those traits caused the winning: plenty of failed companies may have had Level 5 leaders and hedgehog concepts too. Second, the halo effect: once a company is successful, observers retroactively describe its culture as disciplined and its leaders as humble; the data was largely retrospective impressions. And reality tested the sample harshly: several of the eleven “great” companies later stumbled, some catastrophically.
So why still read it? Because the concepts survive as vocabulary and hypotheses, even if they fail as laws. “Are we first-who or first-what right now?” is a genuinely useful team question regardless of how the original research holds up. Treat Collins as a source of sharp questions, not guaranteed answers: holding our own explanations lightly is, ironically, the most Level 5 move available.
From good to great, one ritual at a time
Don't launch a transformation program. Pick one: run the window-and-mirror discipline for a month, draft your team's three circles, or start the stop-doing list. If you want to think it through first, practice it with Lumia, your AI coach: describe your team honestly and stress-test which of the five concepts would move it most.
Frequently asked questions
What is Level 5 leadership?
Collins's term for leaders who combine extreme personal humility with intense professional will. They are ambitious for the collective's success rather than their own, credit others when things go well (the window) and take responsibility when they don't (the mirror). At team scale, it shows up as naming individuals behind wins and opening retrospectives with your own mistakes.
What is the Hedgehog Concept for a team?
The intersection of three circles, translated to team scale: what your team genuinely cares about, what it can be the best at within your organization, and the single metric that best captures the value it produces. Its power lies in what you stop doing: a hedgehog concept only works if the team declines the adjacent work that dilutes it.
What are the main criticisms of Good to Great?
The strongest critique, articulated by Phil Rosenzweig in The Halo Effect, is methodological: Collins selected already-successful companies and looked backward for shared traits, survivorship bias, so the study can't establish causation. Retrospective accounts were also colored by the halo effect. Several of the eleven companies later declined badly. The concepts remain useful as questions and vocabulary, not as proven laws.
How do I apply Good to Great to a small team?
Pick one concept and turn it into a ritual. Practice window-and-mirror in reviews and retros for Level 5 habits. Ask the two casting questions, who would I fight to keep, and who is in the wrong seat, before writing the roadmap. Draft the team's three circles in a workshop. Or start a quarterly stop-doing list. One ritual, sustained, beats a transformation program.
References
- Collins, J. (2001). Good to Great. HarperBusiness.
- Rosenzweig, P. (2007). The Halo Effect… and the Eight Other Business Delusions That Deceive Managers. Free Press.
- Edmondson, A. C. (1999). Psychological Safety and Learning Behavior in Work Teams. Administrative Science Quarterly, 44(2), 350–383. DOI: 10.2307/2666999