top of page

Humility in Leadership Examples That Actually Changed How My Clients Lead

Executive leader practicing humility in leadership by listening attentively to a team member in a one-on-one meeting

Humility in leadership is the disciplined practice of staying open, staying accurate about your own limitations, and giving your team genuine credit for what they know and contribute. It is not about minimizing your authority or second-guessing every decision. It is about resisting the pull toward certainty that executive culture makes almost irresistible. Leaders who practice it do not announce it. They demonstrate it in moments most people would never think to track: the meeting where they change their mind publicly, the one-on-one where they ask a real question and sit quietly long enough to actually hear the answer, the quarterly review where they name who did the work.


In 29 years of executive coaching, I have worked with hundreds of senior leaders across healthcare, finance, technology, and government. The ones who produced the strongest results for their organizations were not uniformly charismatic or technically brilliant. Almost without exception, they shared one quality: they were willing to be wrong in front of the people they led.


Blog Summary


  • Humility in leadership is a practiced behavior, not a personality trait, and it can be developed at any career stage.

  • Research consistently links humble leaders to higher team performance, stronger retention, and faster learning.

  • The most common executive mistake is confusing humility with passivity. The two are functionally opposite.

  • Leader self-disclosure and actively soliciting upward feedback are the two behaviors that make humility visible to a team.

  • Psychological safety does not come from policy. It comes from repeated, consistent acts of humble leadership over time.


Why do so many leaders misread humility as weakness?


The misreading is structural, not personal. Executive environments reward confident assertion. Boards want decisiveness. Investors want certainty. Direct reports, at least on the surface, often seem to want answers rather than questions. Everything in the system signals that showing doubt is costly, so leaders learn to perform confidence even when they are not confident. Over time, that performance becomes a habit, and the habit crowds out any real openness to being corrected or taught.


What I observe consistently in the coaching room is that the leaders who resist humility most are not arrogant in any simple sense. Many of them are capable people who have received years of social reinforcement for behaving in ways that happen to look like arrogance from the outside. The pattern usually shows up first in how they handle pushback. A high-performing SVP I coached several years ago had a sharp, fast mind and a tendency to counter-argue within seconds of hearing a dissenting view. He was quick, not dismissive, but the effect on his team was the same: people stopped raising concerns because they had learned that his first answer was also his last answer.


The research does not support the intuition that confidence and humility trade off against each other. Jim Collins's foundational work, published in the Harvard Business Review and later expanded in Good to Great, identified what he called Level 5 leaders: executives who combined fierce professional will with extreme personal humility. They gave credit outward and took responsibility inward. They were ambitious for the organization rather than for themselves. That combination produced the strongest long-term organizational results in his study of over 1,400 companies. A 2025 research roundup published by the Harvard Business Review reinforced this pattern, finding that humble leadership at the executive level correlates with measurably better collaboration among senior teams and stronger organizational performance overall.


The weakness framing persists because humility is often confused with deference. A humble leader can hold a firm position and make an unpopular decision. What makes them humble is that they arrived at that decision through a real process of listening, and they remain open to revising it if new information comes in.



What does humility in leadership actually look like?


It looks like small, specific, repeatable behaviors, and most of them happen in ordinary moments that feel unremarkable until you start watching for them.


Real coaching scenarios showing humble leadership in action


One of the clearest examples I can offer comes from a coaching engagement with a chief operating officer who had just stepped into a new role after a successful run leading a smaller division. She was technically excellent and had strong instincts about operations. In her first two months, she made several structural changes that were objectively sound, but her team's engagement scores dropped noticeably. When we dug into the 360 feedback, the theme was consistent: people felt like she had arrived with all the answers before she had any of the questions.


Her judgment was not the problem. What she changed was her sequence. She started holding what she called "assumption checks" before major decisions: fifteen-minute conversations with two or three people closest to the work, where she would share her current thinking and specifically ask what she was probably missing. The quality of her decisions did not decline. The team's sense of ownership in those decisions increased substantially. Engagement scores recovered within a quarter.


That is what humility in leadership examples from real practice tend to look like: adjustments in sequence and in who gets to speak before a conclusion is reached, rather than grand gestures.


The difference between performing humility and practicing it


There is a version of humility that is strategic and a version that is real, and most experienced teams can tell the difference within a few interactions. Performative humility tends to involve visible self-deprecation paired with unchanged behavior. A leader says "I don't have all the answers" in an all-hands meeting and then runs every subsequent conversation as if they do. Teams notice the gap between the words and the pattern, and when they do, the credibility cost is higher than if the leader had said nothing at all.


Real humble behavior shows up in changed behavior after feedback, going further than mere acknowledgment. It shows up in giving specific credit, naming the person and the contribution, rather than generic praise. It shows up in staying curious when a direct report challenges an assumption, rather than shifting immediately into defend mode. These are learnable habits. I have watched leaders who arrived in coaching with deeply entrenched defensive patterns build durable humble practices over six to twelve months of focused work. The process is not fast, and it is not comfortable, but it is consistently achievable.



How does leader self-disclosure build team trust?


Leader self-disclosure, used well, is one of the most efficient ways to build psychological safety on a team. It signals to people that showing uncertainty is acceptable, that learning out loud is permitted, and that the person at the top is subject to the same human conditions everyone else is subject to.


What self-disclosure means in a leadership context


Self-disclosure in leadership does not mean sharing everything. It means sharing relevant limitations, relevant mistakes, or current uncertainty in a way that is purposeful and proportionate to the situation. A CEO who tells their leadership team that they are uncertain about the right strategic response to a market shift, and explains the specific factors making it hard to read, is practicing useful self-disclosure. A CEO sharing personal anxieties unrelated to the work at hand is doing something else.


The line is relevance and purpose. Disclosure that gives the team useful context for how to work with you, or that normalizes candid communication, serves a function. Disclosure that shifts the emotional labor onto the team does not.


When and how executives use self-disclosure effectively


In my practice, the two situations where self-disclosure produces the most consistent results are role transitions and post-failure conversations. When a leader steps into a new role and says directly, "Here are the areas where I know I will need your expertise," they accomplish two things at once: they gather real information and they set a behavioral norm. The team sees what it looks like to name a gap without it being a crisis.


Post-failure disclosure works in a similar way. A CFO I worked with had overseen a forecasting process that produced a significant miss. In his first all-hands after the quarter closed, he walked through exactly where the model had failed and what he had been wrong about in his assumptions. He did not over-explain or over-apologize. He was specific and direct.


Over the following two quarters, his finance team surfaced concerns earlier and more frequently than they ever had before. The causal mechanism was not complicated: they had seen what happened when a problem was named plainly, and they concluded it was safe to name problems early.



What happens when leaders ask for feedback from their teams?


Regularly soliciting upward feedback is the single most underused expression of humility in executive leadership. Most organizations have formal mechanisms for it: annual surveys, 360 reviews, skip-level conversations. The informal and ongoing practice of asking "how am I doing, what am I missing, where are you running into friction because of me" is rare. The leaders who make it a consistent habit see measurably different results.


The table below draws from published research across the Academy of Management Journal, the Center for Creative Leadership, and the Harvard Business Review to summarize what the evidence shows about teams led by leaders who actively solicit upward feedback compared to those who do not.


Outcome Dimension

Leaders Who Solicit Upward Feedback Regularly

Leaders Who Do Not

Team learning rate

Significantly higher; members share information more freely

Lower; learning stays siloed at the individual level

Employee engagement

20 to 30% higher in CCL studies across industries

Average to below average; engagement tied to feeling heard

Voluntary retention

Higher retention among high performers who feel their input matters

Higher turnover risk, especially among strong contributors

Psychological safety

Consistently higher; team members report feeling safe to raise concerns

Lower; members self-censor to manage perceived risk

Sources: Center for Creative Leadership (CCL), Academy of Management Journal, Harvard Business Review


The pattern across these dimensions is consistent enough that I treat the presence or absence of upward feedback solicitation as a leading indicator in organizational assessments. If senior leaders are not asking for it, it is almost never flowing upward on its own. When it stops flowing, the organization loses its best early warning system.



How does humility create psychological safety on teams?


Psychological safety, as defined by Amy Edmondson at Harvard Business School, is a team's shared belief that it is safe to take interpersonal risks: speaking up, challenging assumptions, admitting mistakes, proposing ideas that might not work. It does not exist because a leader announces it. It exists because the leader's repeated behavior over time makes it reasonable for people to believe it. The connection between humble leadership and trust in teams is direct: one produces the other.


What psychological safety is and what breaks it


The behaviors that build it are mostly humble ones: asking real questions, responding to concerns without defensiveness, acknowledging when someone else's idea was better, accepting correction without making the corrector feel they took a risk. The behaviors that break it run in the opposite direction: dismissing input, reacting to bad news with visible frustration, publicly favoring people who agree, and failing to act on feedback that was given in good faith. That last one is the most damaging because it does not just break safety, it actively punishes the behavior the leader claimed to want.


Humility as the daily mechanism behind safe teams


Psychological safety does not accumulate in one conversation. It accumulates across dozens of small interactions that either confirm or contradict the implicit message: your candor is welcome here. When a leader receives a critical observation from a direct report and responds by asking a follow-up question rather than defending their original position, that is one data point. When they do it consistently over months, the team stops treating candor as a risk. That shift is what changes team performance in a measurable way.


Research published in the Academy of Management Journal found that humble leaders, defined by accurate self-awareness, appreciation of others' contributions, and genuine teachability, lead teams that outperform those led by self-focused managers on learning, retention, and output quality. The mechanism is permission. Humble leaders give their teams room to function at full capacity because people are not spending energy managing up.



How do you develop humility as a leader?


Humility development is behavioral, not attitudinal. Trying to become a more humble person in some abstract sense is much harder than building three specific habits that signal humility to the people around you. In my coaching work, these three show up most consistently as the behaviors that produce visible change in team dynamics.


The three behaviors that signal humility to your team


The first is leader self-disclosure used purposefully. Share the gaps that are relevant to your work together. Name a mistake after it has happened, specifically and without excessive qualification. Tell people what you are still working through when that information gives them something useful.


The second is actively soliciting upward feedback throughout the ordinary flow of work, beyond formal review cycles. After a difficult meeting, ask one person privately what they noticed. After a decision that affected the team, ask whether the process felt fair. These are small asks with disproportionate signal value.


The third is giving specific, public credit. The difference between "great work this quarter" and "Maria's analysis in the budget review was what shifted my thinking on the allocation question, and that decision turned out to be the right one" is not a matter of warmth. It is a matter of accuracy. Vague praise reads as performance. Specific praise reads as observation.


Why this is a practice, not a personality change


The leaders I work with who make the most progress are the ones who stop treating humility as a character question and start treating it as a skill question. A leader can get better at the specific behaviors that express humility in the same way they get better at running a difficult conversation or giving structured feedback. Progress is measurable because the outcomes are observable: do people share concerns earlier, do they challenge assumptions more freely, do engagement scores move?


In my coaching practice, humility is the fifth of the five tenets of heart-centered leadership. The other four, being purposeful, engaged, empathetic, and understanding, are visible in how a leader operates day to day. Humility is the condition that makes those four credible. A leader can claim to be empathetic. Whether their team believes it depends largely on whether that leader has demonstrated a real willingness to be changed by what they hear.



Where does humility fit in the five tenets of heart-centered leadership?


Of the five tenets, humility is the one that most directly determines whether the others land. Empathy without humility reads as sympathy that stops short of real engagement. Being purposeful without humility can slide into rigidity. Understanding, in the sense of real perspective-taking, requires a willingness to be affected by what you learn, and that willingness is what humility produces.


My coaching approach, grounded in the Leading with Heart framework, treats these five tenets as interdependent. Developing one tends to surface work in the others. In practice, humility is the tenet that most changes the quality of the coaching relationship itself, because it determines whether a leader can receive feedback at all. A leader who cannot receive feedback cannot grow at the pace the work demands.


If you are working on any aspect of your leadership development, whether that is managing a role transition, building a more cohesive team, or figuring out why your direct reports are not telling you what you need to know, the question of how you practice humility is almost always part of the answer.


If you want to explore what that looks like in your specific context, I am glad to have that conversation. You can reach our team here or read more about the coaching work we do with senior leaders and HR professionals through our executive coaching services.



Frequently Asked Questions


What is an example of humility in leadership?


A concrete example is a senior leader who receives critical feedback from a 360 review, names the specific behavior they intend to change in their next team meeting, and then follows through visibly over the following weeks. The example is not the feedback itself. The example is the public acknowledgment and the changed behavior. That sequence is what makes humility observable and credible to a team.


Why is humility important in leadership?


Humble leaders create the conditions for teams to function at their actual capacity rather than a managed, self-protective version of it. Research from the Center for Creative Leadership and the Academy of Management Journal shows consistent links between leader humility and higher engagement, faster learning, and stronger retention. The practical reason is that people share more openly with leaders they trust will not penalize candor, and humility is the primary signal that candor is safe.


What does a humble leader look like in practice?


A humble leader asks more than they tell in situations where listening would produce better information. They give specific credit to specific people. They change their position when the evidence supports it and say so directly. They solicit upward feedback outside of formal review cycles and respond to it in ways the giver can observe. None of these behaviors require a different personality. They require attention and repetition.


Can a leader be too humble?


Yes. Humility that produces indecision or prevents a leader from holding a clear position under pressure is a different problem. The research on this is clear: humble leaders who lack decisiveness can be perceived as weak during high-stakes moments, which erodes the team confidence they were trying to build. The goal is accurate self-awareness paired with confident action, with deference reserved for situations where it is actually warranted.


How do you develop humility as a leader?


Start with one behavioral change rather than trying to shift your overall disposition. The highest-return starting point, based on what I see produce results most consistently, is building a habit of soliciting upward feedback informally: after a difficult meeting, after a decision, after a conversation that felt off. Over time, this builds a data stream about how you are landing that most leaders simply do not have. From there, the other behaviors, self-disclosure and specific credit-giving, tend to follow more naturally.


What is the difference between humility and weakness in leadership?


Humility is accurate self-assessment paired with real openness to learning. Weakness, in a leadership context, is the inability to hold a position under pressure or to make decisions without universal agreement. A humble leader can make an unpopular decision confidently, acknowledge the concerns of those who disagree, and hold the course when the evidence supports it. What they do not do is dismiss those concerns or pretend they were not raised. The distinction matters because developing humility is not about becoming softer. It is about becoming more accurate.


 
 
 

Comments


bottom of page