Humility in leadership: what it looks like, why it works and how to practice it

A humble leader sees their own strengths and gaps accurately and lets that show in daily behavior. Because your team sees that behavior far more clearly than you do, the most reliable check is their view, gathered through upward feedback or employee survey software rather than self-assessment.

Research gives the idea a usable shape. In a 2012 study for the Academy of Management Journal, Bradley Owens and David Hekman grouped humble leader behaviors into three categories: acknowledging personal limits, faults and mistakes; spotlighting followers' strengths and contributions; and modeling teachability. Their conclusion, drawn from 55 in-depth interviews with leaders, is that humility works by modeling how to grow: when the leader is visibly still learning, people feel their own development and uncertainty are legitimate at work.

That makes humility a set of behaviors you can practice, not a personality you either have or lack. It sits alongside the other traits covered in our guide to what makes a good leader, and it is one of the few that costs nothing to start.

The evidence has grown well beyond anecdotes. A 2022 meta-analysis in Frontiers in Psychology pooled 53 independent studies with 16,534 participants and found humble leadership positively related to affective trust (0.62), affective commitment (0.56), job satisfaction (0.51), engagement (0.40), employee voice (0.34) and task performance (0.33). These are correlations, not proof of cause, but they are consistent and they point to the outcomes most managers are accountable for.

The effect also travels down an organization. A 2014 study in Administrative Science Quarterly, covering 63 private companies in China, found CEO humility positively associated with empowering leadership; that in turn correlated with a better-integrated top team and, through an empowering climate, with middle managers' engagement, commitment and job performance.

Why would that be? Teams act on what they see a leader reward. When the person in charge says "I missed that" without penalty, others start reporting problems early. When the leader names who did the work, people keep doing it. Neither requires a program, only repetition.

Many people avoid humility because they confuse it with self-doubt. The two are different. Pride overrates your judgment and shuts out correction. Insecurity underrates your judgment and often hides it, which can look like pride from the outside. Humility rates your judgment accurately and stays open to being wrong.

Intellectual humility research makes the same point: Duke University psychologist Mark Leary describes intellectually humble people as able to hold strong beliefs while recognizing their fallibility and being willing to be proven wrong. Strong views and openness are not opposites.

The leaders Owens and Hekman studied said the same thing from experience: humility could be read as weakness unless the leader was also seen as confident and effective. The matrix below shows the four combinations. The goal is the top-right corner.

Signs of pride in a leader

Look for behaviors, not labels. Each of these is common and fixable:

• Explaining a mistake before anyone has finished describing it.
• Taking the "we" out of results ("my numbers", "my launch").
• Asking for input after the decision is already made.
• Treating a question as a challenge to your authority.
• Rarely saying "I don't know" in meetings, even on topics outside your field.
• Hearing about problems late, or from your own manager first.

The last sign is the most telling, because it is a result, not a habit you can see in yourself. Owens and Hekman describe humble leaders as less susceptible to the belief that their position exempts them from acknowledging weakness or admitting mistakes. The more senior you are, the more deliberately you need to resist that belief.

Signs of insecurity in a leader

• Avoiding decisions until consensus is complete.
• Over-apologizing, or apologizing for things that were not your call.
• Reworking people's tasks instead of coaching them.
• Avoiding feedback conversations, including asking for feedback on yourself.
• Keeping information close so you stay needed.

If you recognize yourself in the second list more than the first, the fix is not more humility. It is more clarity: decide, say why, and invite correction.

1. Check your motive before you speak. Ask: "Am I saying this to help the team decide, or to look right?" If the honest answer is the second, ask a question instead.
2. Speak last in decisions. Give your view after others have given theirs, so they are not anchoring on the boss.
3. Keep a "where I was wrong" log. Once a week, write one call you would make differently. Share the useful ones with the team.
4. Give credit by name, with detail. "Your test plan caught the billing bug before release" teaches the team what good looks like; "great job, everyone" does not.
5. Learn from someone junior every month. Ask a newer colleague to show you a tool, a customer view or a shortcut. Then use it where they can see.
6. Ask for help on a known weakness. Owens and Hekman describe a leader who told his direct reports he was not a good listener and asked them to help him with it. Naming the weakness and recruiting help turns a private flaw into a shared project.

"I was wrong", "I don't know" and "I need help" are the clearest daily evidence of humility, and the ones leaders most often soften until they say nothing. The trick is to keep them short and end with direction.

Notice the pattern: own it, give the fact, give the next step. One sentence of ownership is enough; three sentences of apology shift the focus back to you.

Every leader will make a visible mistake. How you handle it teaches the team more than any values statement.

1. Say it early and plainly. Bad news ages poorly. Tell the people affected before they find out elsewhere.
2. Separate the facts from the story. "We shipped with the old tax table" is a fact. "I'm careless" is a story. Share the first.
3. Fix forward. State what you are doing now and what will change in the process, not only in your intentions.
4. Close the loop. Report back when the fix is done. This is what turns an admission into trust.

Honesty extends past your own errors. Share the reasons behind decisions, including the ones the team will not like, and say when you cannot share something rather than pretending there is nothing to share. People forgive limits on what you can say far more easily than spin.

Spotlighting others' strengths is the second of the three humble behaviors, and an easy one to drop under pressure. A few habits make it routine:

• Ask before you tell. "What would you do?" signals that you expect a good answer.
• Correct in private, credit in public. A correction in front of peers lands as a verdict; the same words in private land as coaching.
• Praise the method, not just the result. "You tested it with three customers first" is repeatable. "Nice work" is not.
• Let people present their own work. Do not summarize your team's project for senior leaders when the person who built it can.
• Stay quiet when someone else has the answer. Being right second is fine.

These habits rely on reading the room and managing your own reactions, skills covered in depth in our guide to emotional intelligence in leadership.

When you miss a deadline, you know the reasons: the late input, the sick child, the changed brief. When someone else misses one, it is tempting to conclude they are disorganized. Psychologists call this the fundamental attribution error: overweighting someone's disposition and underweighting their situation. A 2014 study found that stress may make people more likely to commit it and to evaluate others less favorably. Managers spend a lot of time under stress, so this is a daily humility test.

Humility helps here too. In one of the Duke studies, intellectually arrogant participants rated the writer of an essay they disagreed with lower on morality, honesty, competence and warmth, while intellectually humble participants were less likely to judge the writer's character by his or her views.

A simple routine before you react: stop, ask, consider.

• Stop. Do not send the message while you are annoyed.
• Ask. "Walk me through what happened" gets you the situation you cannot see.
• Consider. If a capable colleague did this, what would explain it? Then decide whether it is a skill, a process or a priority problem.

Charitable is not the same as lax. You still address the missed deadline. You just start from the facts rather than a verdict about the person.

Humility has limits, and knowing them keeps it from turning into indecision. Owens and Hekman report that humility was effective only to the degree the leader was also seen as competent, especially when admitting mistakes and limitations. They also found that modeling teachability was less effective when the status quo had been seriously disrupted, time for action was short, or followers faced a significant threat.

Use this table to adjust:

• False humility. A humblebrag ("I'm so bad at saying no, I ended up leading three projects") is self-promotion in disguise, and people hear it that way. If you want credit, ask for it directly.
• Self-deprecation as a habit. Constant jokes about your own incompetence make people doubt your decisions. Accurate is the goal, not lower.
• Apologizing without changing anything. An admission with no next step reads as performance.
• Vague credit. "Thanks, team" spreads credit so thin that nobody receives it.
• Outsourcing every decision. Asking for input is humble; refusing to decide is not.
• Humility only upward. Some leaders defer to their own boss and lecture their team. Your reports are the ones who notice.

You are a poor judge of your own humility, so measure what your team sees. The stakes justify the effort: Gallup estimates that managers account for at least 70% of the variance in employee engagement scores across business units.

Upward survey items. Ask direct reports, anonymously, to agree or disagree on a five-point scale with statements tied to the three behaviors:

• "My manager admits mistakes openly."
• "My manager says so when they don't know something."
• "My manager gives specific credit for the work people do."
• "My manager changes their mind when given good evidence."
• "I can disagree with my manager without negative consequences."
• "My manager asks for my input before decisions that affect my work."

Signals to watch between surveys. How early you hear about problems; how often people other than you present in leadership meetings; how many ideas from the team you adopted this quarter; whether people raise objections in meetings or only afterward.

Cadence. Run the items twice a year with at least five respondents per manager to protect anonymity, share the results with your team, pick one item to work on and ask about it again at the next round. For a practical way to discuss results, see our guide to giving feedback.

Software cannot make anyone humble. It can make the feedback loop easier to run and harder to ignore. Survey tools collect anonymous upward feedback and track items like "my manager admits mistakes" over time. Performance management platforms add 360-degree reviews, so peers and reports can tell a leader what they do not see. Mentoring tools match leaders with mentors, including reverse mentors who are earlier in their careers, which builds the habit of learning from anyone.

Where it does not help: a dashboard does not apologize, credit a colleague or change a decision. If results are collected and nothing visible changes, expect fewer and less candid answers next time.