The Ideal Team Player: Lencioni's Humble, Hungry, Smart Model

By Tara Minh · Updated Oct 10, 2026

The Ideal Team Player model, created by Patrick Lencioni, says the best teammates share three virtues: they're humble, hungry, and smart. Humble means putting the team ahead of credit. Hungry means self-driven effort. Smart means good judgment about people. Lacking even one in a significant way creates a predictable kind of problem, which makes the model useful for hiring, review and coaching.

Most leaders already screen for skills. This model asks a different question: how will this person behave once they're on the team? It's short enough to remember, and specific enough to act on in an interview or a one-on-one.

What is the Ideal Team Player model?

Patrick Lencioni published The Ideal Team Player: How to Recognize and Cultivate The Three Essential Virtues with Jossey-Bass in 2016. Like his earlier work, it's a leadership fable: a story that delivers the model at the end.

Lencioni says the idea came out of his consulting practice. In The Table Group's model overview, he explains that clients kept asking to borrow the three values his own firm used, humble, hungry and smart. He eventually realized those values were the building blocks of real team players, and the book followed.

One line from that overview is worth keeping in mind. Lencioni believes that, given time and a good manager, almost anyone can learn to be a team player. But some people need much less coaching to add value in a team setting, and the model describes what those people have in common.

Key Facts

Key Facts

• Originator: Patrick Lencioni, founder and president of The Table Group.
• Source: The Ideal Team Player, published by Jossey-Bass in 2016.
• The three virtues are humble, hungry and smart, and the combination of all three is what defines an ideal team player.
• Lencioni describes six types of people who are missing one or two virtues: the Pawn, the Bulldozer, the Charmer, the Accidental Mess-Maker, the Lovable Slacker and the Skillful Politician (The Table Group leader's guide).
• "Smart" here means people smarts, not intelligence. Lencioni compares it to emotional intelligence.
• The Table Group warns against using the six types as labels for people. They describe behavior patterns that can change.
• It's a practitioner framework from consulting and fable, not a peer-reviewed measurement instrument.

The three virtues

Humble

Humility comes first in Lencioni's model. According to The Table Group, humble people lack excessive ego or concern about status. They're quick to point out the contributions of others, slow to seek attention for their own, and they define success collectively.

Humble doesn't mean timid or self-erasing. The same overview says humble team players can honestly acknowledge their own skills, just never in a proud or boastful way. A humble engineer will say "I'm the strongest person on this database problem" without turning it into a performance.

Hungry

Hungry people want more: more to do, more to learn, more responsibility. The overview says they almost never need a manager to push them, because they're self-motivated and diligent. They volunteer to fill gaps and look around corners for new ways to contribute.

Hungry isn't the same as ambitious for a title. The test is whether someone does the work the team needs, including the unglamorous parts, without waiting to be told.

Smart

This is the one people misread. Smart isn't about IQ or credentials. Lencioni's overview defines it as common sense about people: reading what's happening in a group, understanding the subtleties of team dynamics, and knowing how your words and actions land.

If that sounds like emotional intelligence, it should. The Table Group's leader's guide says Lencioni himself noted the similarity.

The six misfits: what happens when a virtue is missing

The real power of the model is in the combinations. The Table Group's leader's guide names six types, three missing two virtues and three missing one.

Lencioni's overview adds a warning about the last one. A person who is hungry and smart but truly lacking humility can have a devastating impact, because they know how to present themselves as a well-meaning colleague while looking out for their own needs. By the time teammates figure it out, people have often been manipulated.

And here's a caution the same leader's guide gives: these aren't labels for people. Using them casually can become a self-fulfilling prophecy, or can turn a situational pattern into a supposed character trait. Use the six types to describe behavior you've seen, then talk about it.

How it compares with other team frameworks

The model sits at the individual level. Other frameworks look at the team as a whole, at roles, or at stages of development.

The two Lencioni models fit together neatly. The Table Group's overview argues that most struggling teams aren't short on knowledge or competence, they just can't access it because of dysfunctional behaviors, and that a team full of humble, hungry, smart people overcomes those dysfunctions quickly. Our guide to the five dysfunctions covers the team side. This model covers the people you put on it. For more on Lencioni's wider body of work, see Patrick Lencioni's leadership approach.

How to apply the model, step by step

Step 1: Define the three virtues in your own words

Write one plain sentence for each virtue, using examples from your company. "Hungry here means picking up the support queue when it backs up, without being asked." Shared language is the foundation, and The Table Group's guide suggests memorizing the three and describing each in your own words.

Step 2: Hire for the virtues, not just the skills

Lencioni says hiring ideal team players is mostly about knowing what to look for and probing in non-traditional ways. A few approaches that follow from that:

• Ask about specific past situations, not hypothetical ones.
• Involve more than one interviewer, and have each probe a different virtue.
• Talk to the people who worked with the candidate, and listen for how they describe credit, effort and conflict.
• Pay attention to how the candidate treats everyone they meet, from reception to the hiring manager.

Step 3: Score what you saw

Rate each virtue separately with evidence, not a gut feel. The template below gives you a structure. Compare notes across interviewers before anyone shares an overall verdict, so one confident voice doesn't set the score.

Step 4: Run a self-assessment with the current team

The Table Group's overview says merely introducing the model to teams and letting them self-assess goes a long way toward improvement. Ask each person to rate themselves, name their weakest virtue, and ask one teammate for their view.

Step 5: Develop the weakest virtue

The leader's guide offers direction for each virtue:

• Humility: the leader models it. Sharing your own struggles with humility makes the topic safer to discuss.
• Hunger: connect the person's work to the mission and to the people it affects. Lack of hunger sometimes has causes outside work, so ask before assuming.
• People smarts: these are the most coachable. People weak in this area usually aren't that way by choice, and tend to be open to real-time, caring feedback.

Step 6: Repeat expectations, and let people opt out well

The guide says regular reminders about expectations usually lead to one of two outcomes: the person changes, or they decide it's not for them. If someone chooses to leave, helping them go on good terms is better than forcing a confrontation.

Template: interview and self-assessment scorecard

Copy this table into your hiring doc or one-on-one notes. Score each row 1 (no evidence) to 5 (strong, repeated evidence), and write the evidence in the last column. Our wording is a starting point; adapt it to your roles.

Reading the result: any virtue averaging 3 or lower is a flag to explore, not an automatic no. A very low score on humility deserves the most scrutiny, since the Skillful Politician can look excellent in short interviews. This is a conversation tool, not a validated psychometric test.

Examples by business function

These scenarios are hypothetical and generic, meant to show how each pattern appears.

Sales. A sales manager has a top closer who hits quota every quarter but hoards leads and never shares what works. Hungry, yes. Humble and smart, not much. That's a Bulldozer, and the cost shows up in a team that stops collaborating. The fix is to add a team metric to their compensation and give direct feedback on specific moments.

Operations. A warehouse supervisor has a reliable, kind team member who always agrees and rarely speaks up about problems. Humble, but not showing much hunger or judgment about escalating issues. That's closer to a Pawn. Coaching focuses on tying their role to outcomes and asking for their view in every handoff review.

HR and recruiting. A recruiter is charming in every interview and gets glowing feedback from candidates, but follow-through on commitments is thin. Smart without humility or hunger is the Charmer pattern. A structured reference check on delivery, not warmth, brings it out.

Product and engineering. A brilliant, hardworking engineer keeps rewriting teammates' code in review with blunt comments. Humble and hungry, but unaware of the impact. That's an Accidental Mess-Maker, and people smarts coaching, such as a peer reading comments before they post, is a good fit.

Customer success. An agreeable team member who is great with clients does only what's on the checklist. Humble and smart, not hungry: the Lovable Slacker. Connecting their work to client outcomes, and setting clear expectations, tends to help.

Leadership team. An executive is polished, ambitious and well-liked, but quietly steers decisions toward their own function. That's the Skillful Politician, and it's the hardest to catch. Peer feedback and watching how they handle shared credit are the best signals. Our guide to psychological safety explains why teams need to feel safe raising these concerns.

Do's and don'ts

Common mistakes

Hiring on skills and personality alone. Skills tell you what someone can do. These virtues tell you how they'll do it with others. Both matter, but teams usually only screen for the first.

Mistaking charm for people smarts. Smart in this model includes caring about teammates. Smooth social skills without humility or hunger is the Charmer.

Using it as a one-time filter. People change, and so do circumstances. Someone going through a hard stretch may look less hungry for a while. Revisit the conversation instead of locking in a verdict.

Ignoring the leader's example. Humility spreads from the top. If the manager takes the credit and hides the mistakes, the team learns that humble people lose.

Putting it into practice

Pick one thing this week. Try the self-assessment with your own team: have each person name their weakest virtue and one concrete step to work on it. Go first, and name yours.

The model won't tell you who to fire. It will give you a sharper question for your next interview, a clearer reason for your next piece of feedback, and a shared vocabulary for what good teamwork looks like. If you're wondering what the team looks like once it works, the servant leadership model is a useful companion.