Tribal Leadership: The 5 Stages of Organizational Tribes

By Tara Minh · Updated Oct 11, 2026

Tribal Leadership is a culture model from Dave Logan, John King, and Halee Fischer-Wright. It says every organization is a set of tribes of roughly 20 to 150 people, and each tribe sits at one of five stages, from "life sucks" (Stage 1) to "life is great" (Stage 5). You can tell the stage by what people say, and leaders lift a tribe by moving it one stage at a time.

Most culture talk is abstract. Values posters, engagement scores, offsite workshops. Tribal Leadership is refreshingly physical by comparison: listen to how people talk in a hallway or a stand-up, and you can place the group on a map. That's the appeal. It turns "our culture feels off" into something a manager can actually name.

What Is Tribal Leadership?

Key Facts

• Tribal Leadership is published by Harper Business, and the publisher describes it as based on a ten-year study of twenty-four thousand people.
• In a 2008 Gallup Business Journal interview, the authors said tribes typically have 20 to 150 members, and that the research covered more than 24,000 people in two dozen companies.
• The authors' own site reports that 49% of workplace tribes sit in Stage 3, 25% in Stage 2, and fewer than 2% in Stage 5. These are the authors' reported research, not an independent finding.
• Logan also introduced the five tribe types in a TEDxUSC talk in March 2009.

The core idea is simple. A company isn't one culture. It's many overlapping tribes: a sales team, a finance group, a product squad, a night shift. Each has its own way of talking, and each can be at a different stage. A company can be "mostly Stage 3" and still contain a Stage 4 team that everyone else envies.

The model also gives you a rule for change: you don't jump stages. According to the authors, the way to move a group is to speak the language of the stage just above where it is now.

One caution before we go further. This is a practitioner framework. The study behind it is reported by the authors themselves, in the book and on their own site, so treat the percentages as their research, and treat the model as a useful lens rather than a measured law.

The 5 Stages at a Glance

The stage descriptions above follow the authors' own account in the Gallup interview and on their site. The rest of this article unpacks each stage and what a leader can do about it.

Stage 1: "Life Sucks"

Stage 1 is hostile and despairing. The authors describe the people in it as despairingly hostile, the kind of group that might create scandals or steal from the company. The authors place it at the far end of the scale, and it is the least common of the early stages in everyday teams.

What it sounds like: "Nothing works here." "They're all against us." Talk about the world as a place that's out to get you.

What a leader does: The model offers little method for this stage. A sensible reading is to stabilize the person or group first, then work on the jump to Stage 2.

Stage 2: "My Life Sucks"

Stage 2 is apathy. In the Gallup interview the authors say members of these tribes don't try, care, innovate, or hold each other accountable. The authors' site calls it the dominant culture for 25% of workplace tribes, with members who are passively antagonistic and resistant to new management initiatives.

The difference from Stage 1 is that the tone changes from "life sucks" to "my life sucks." People believe the problem is personal, and that someone else (management, the market, the system) is responsible for fixing it.

What it sounds like: "I tried that before. It didn't work." "Why bother?" Plenty of jokes at the expense of any new initiative.

What a leader does: Find the few people who still want something to change. Talk to them one at a time, in Stage 3 language: "I think you have real potential to lead." The authors describe asking each person to do the same for someone else, so belief spreads person to person rather than through a speech.

Stage 3: "I'm Great (and You're Not)"

Stage 3 is the stage most professionals recognize, because it's where achievement lives. People are in it for themselves, and the authors say they're averse to collaboration. The authors' site says 49% of workplace tribes are in this stage, and describes each employee as a "lone warrior."

Walk through any high-performing but exhausting team and you'll see it. Strong individual contributors, hoarded knowledge, a quiet competition over who's the smartest person in the room.

What it sounds like: Lots of "I," "me," and "my." In the authors' words from the Gallup piece, speakers at this stage use those words most often.

The trap: Stage 3 leaders keep relationships in twos. The leader talks to each member separately, and members rarely compare notes. That keeps the leader at the center, and it caps how far the team can grow. It also leaves information stuck in individual heads, which is one reason high-trust, high-safety teams do better at sharing it.

What a leader does: Learn what each person values with open-ended questions, not assumptions. Then design work nobody can finish alone, and anchor the new partnerships on shared values.

Stage 4: "We're Great (and They're Not)"

Stage 4 is where the "we" arrives. Members share knowledge and collaborate, while competing with other tribes or other companies. The tribe has an identity and often a rival that sharpens it.

The structural shift is from pairs to triads. The authors say Stage 4 relationships are three-person relationships anchored on shared values. If you introduce two people because both care about the same customer problem, and a third because she can fix it, you've built a triad. No one has to go through the leader to make things work.

What it sounds like: "We" and "our." Pride in the team's work. Some trash talk about the competition or the department next door.

The trap: The "they're not" half can turn into silo thinking. Sales versus marketing, engineering versus support. A Stage 4 tribe that treats other tribes as the enemy will win battles and lose the company. If this sounds familiar, the patterns in Lencioni's five dysfunctions of a team are a good diagnostic for what keeps a team from collaborating.

What a leader does: Keep the shared values alive, then point the tribe's energy at a larger goal than beating the rival.

Stage 5: "Life Is Great"

Stage 5 is rare. The authors say it "only happens about two percent of the time", and their site puts it at less than 2% of workplace tribal culture. Members here care about a purpose that goes beyond their own tribe. They describe it as "innocent wonderment," and as groups that create things nobody had imagined.

In the interview, the authors give examples from their own research: Genentech, parts of IBM and General Electric, Pixar, and Apple. Those are their characterizations, not independent ratings, and they describe the stage as unstable, because it tends to appear in bursts.

What it sounds like: Talk about what's possible, not about who's winning. "Life is great" is as much a statement about the future as the present.

What a leader does: The authors don't offer a step-by-step method for the move from Stage 4 to Stage 5. They describe it as shifting from a focus on competition to a shared sense of what everyone is searching for.

How to Move a Tribe Up One Stage

The authors' central instruction in the Gallup interview is to speak a language one stage above the group's current stage. Preach collective values to a Stage 3 group, for example, and you'll get eye-rolls. Talk to them about personal potential and results, and you'll get a hearing.

Here's a working version as a routine you can run over a quarter.

1. Pick one tribe. Not the whole company. A team of 20 to 150 people at most, and ideally one you lead.
2. Listen for a week. Note the pronouns, the jokes, and the complaints. Count how often you hear "I" versus "we."
3. Map who talks to whom. The authors suggest simply walking around and watching conversations. Look for who is a hub, who is isolated, and whether everything runs through you.
4. Name the dominant stage. Don't average. Pick the stage you hear most.
5. Choose the one-stage-up move.
   • Stage 2 to 3: individual conversations about potential and ownership.
   • Stage 3 to 4: open-ended questions about what people value, then joint work that needs two or three people.
   • Stage 4 to 5: a purpose bigger than beating a rival.
6. Build triads on purpose. Introduce people to each other around shared values and shared work, and step out of the middle.
7. Make it safe to be wrong. People won't share what they know if mistakes get punished. See psychological safety for how that works, and the SCARF model for the status and fairness threats that make people hold back.
8. Listen again after 60 to 90 days. Is the language changing? Are people talking to each other without you?

Tribal Leadership Stage Tracker (Template)

Copy this table into a doc and fill it in for one tribe.

A good tracker ends with one or two moves, not a culture overhaul.

Tribal Leadership vs Other Team and Culture Models

Tribal Leadership overlaps with several frameworks but asks a different question. It places a group on a culture stage using language, rather than prescribing a leadership style.

The practical difference: Tuckman describes a path groups tend to follow in sequence. Tribal Leadership says a mature team can still sit at a low stage, and that moving up is a leadership choice. They can work together. A team that is "performing" in Tuckman's sense may still be Stage 3 in Logan's sense, high output but little real collaboration.

Examples by Business Function

These are illustrative scenarios, not case studies.

Sales. A team ranked by individual quota, with reps guarding their accounts, sounds like Stage 3. A leader builds triads by pairing a rep, a sales engineer, and a customer success manager on one account plan, and rewards the account outcome, not just the rep's number.

Operations. Shift teams that blame each other at handover are often Stage 3 with Stage 4 pride in their own shift. Joint handover checklists and shared metrics give two shifts one thing to be proud of.

HR. HR teams that process requests and complain about leadership are often closer to Stage 2. Start with the one or two people who still want to change something, and give them a visible project.

Product and engineering. Teams with hero developers are Stage 3. Shared ownership of a service, pairing, and open reviews move them toward Stage 4, where the team takes pride in the system, not just their own code.

Customer support. A team that sounds tired and sarcastic about new tooling may be at Stage 2. Ask what the agents would fix first, and let them own it.

Do's and Don'ts

Limitations to Keep in Mind

• It's a practitioner model. The stage percentages come from the authors' own reported research, so use it as a diagnostic lens, not a measurement instrument.
• Language is a clue, not proof. A team can say "we" in meetings and act like Stage 3 in practice.
• Stages aren't a ranking of people. They describe a tribe's culture. A person can be Stage 4 in one team and Stage 2 in another.
• Stage 5 is thinly described. The authors themselves say it's rare, and they give less method for reaching it than for the earlier moves.
• The "they're not" edge can do damage. Rivalry fuels Stage 4 identity, and it can also harden into silos.

If you lead people and want to work on the "we" side of this, servant leadership is a natural companion, since it puts the team's growth ahead of the leader's own spotlight.

Tribal Leadership gives you a simple habit: listen to how your team talks, name the stage, and make one move up. You won't turn a Stage 2 group into a Stage 5 one in a quarter. But if the "I" language starts giving way to "we," and people begin working with each other without going through you, you're moving the right way.