A manager admits in a town hall that she got a hiring call badly wrong. The room exhales, people lean in, trust ticks up. Two weeks later, a different manager spends a town hall narrating his anxiety about the quarter in unsparing detail, and the room quietly decides he can't carry the weight. Same raw material, exposure, honesty, the dropped mask, and opposite results. The difference is not how much each leader revealed. It's whether the revelation was in service of the work or in service of the leader.

The quick version

  • Vulnerability is putting yourself at emotional risk on purpose, saying "I don't know," "I was wrong," "I need help", when there's no guarantee it lands well.
  • Humility is the steady disposition underneath it: owning your limits, crediting others, staying teachable. It's a trait you build, not a moment you perform.
  • Courage is the decision to act through fear, the engine that makes the other two happen when it would be easier to bluff.
  • The test for all three is simple: does this serve the team, or does it serve me? Get that backwards and vulnerability becomes oversharing, humility becomes fishing for reassurance, and courage becomes recklessness.

The idea in depth

The three words get blurred because they overlap in practice. But they sit in different places. Humility is the trait you carry. Courage is the act of will. Vulnerability is what that will produces in the moment.

flowchart LR
    H(["HUMILITY
the standing trait:
owns limits, credits
others, stays teachable"]) --> C(["COURAGE
the act of will:
chooses to act
through fear"])
    C --> V(["VULNERABILITY
the visible moment:
I don't know /
I was wrong / I need help"])
    V -.->|"feeds back:
each rep makes
the trait stronger"| H
How the three relate: a trait, an act, and the moment it produces. Leaders Loop

Vulnerability is a choice, not a leak

The popular version of vulnerability, "being seen", comes from the work of researcher Brené Brown, who defines it as uncertainty, risk, and emotional exposure. Her central, much-repeated argument, drawn from more than a decade of qualitative research and laid out in Daring Greatly (2012), is that vulnerability is not weakness, it's the most accurate measure of courage we have. You can hear the through-line in her 2010 TEDxHouston talk, one of the most-watched talks ever recorded.

Brown's work is built from interviews, not controlled experiments, so treat it as a powerful frame rather than a measured effect size. But the frame matters because it draws a line most leaders blur: chosen exposure versus involuntary leakage. Telling your team "I genuinely don't know if this bet pays off, and here's how we'll find out" is vulnerability, it's deliberate, bounded, and aimed at the work. Visibly unravelling under pressure is not vulnerability; it's a leak, and it transfers your anxiety to people who can't do anything with it.

So the move is: before you share something uncomfortable, ask who it's for. If the answer is "so the team can decide or act better," say it. If the answer is "so I feel lighter," that's what a peer, a coach or a journal is for, not a standup.

Humility is the trait that makes uncertainty safe

Humility is the steadier, slower-built cousin. In a foundational study, organizational researchers Bradley Owens and David Hekman built a grounded model of expressed humility from 55 in-depth interviews and identified three observable behaviours: admitting mistakes and limitations, spotlighting followers' strengths and deflecting credit, and being teachable, modelling, in their phrase, "how to grow" (Academy of Management Journal, 2012). The mechanism is contagion: when the boss treats their own uncertainty as legitimate and improvable, followers conclude their own uncertainty is legitimate too, and stop hiding it.

That connects directly to Amy Edmondson's research on psychological safety. Her early hospital studies found, counter-intuitively, that the better-led teams reported more errors, not because they made more, but because they felt safe enough to surface them. In The Fearless Organization (2019) she names the leader's job plainly: model fallibility, frame the work as a learning problem, and replace blame with curiosity. Humility is the trait that does that framing.

This is also where Jim Collins's "Level 5 leadership" (Harvard Business Review, 2001) earns its keep: the executives who took companies from good to great paired personal humility with fierce professional will. The pairing is the point. Humility without resolve is just niceness; resolve without humility is just ego. (See self-awareness & reflective practice, humility runs on an accurate read of your own limits.)

Humility is not thinking less of yourself. It's keeping the question "what am I missing?" permanently open.

So the move is: pick one of Owens and Hekman's three behaviours and do it visibly this week, name a specific mistake of your own in a team setting, hand real credit to the person who actually did the work, or ask a direct report to teach you something they understand better than you do.

Courage is the switch that turns intention into action

Vulnerability and humility are inert without the third element. Courage, acting through fear rather than the absence of it, is the switch. It's what carries you from "I should probably admit I was wrong about this" to actually saying it, out loud, to the people it costs you most to say it to. Courage is also what stops humility from sliding into passivity: the same leader who can say "I don't know" must also be able to say "and here's the call we're making anyway."

The honest limitation: none of this is universally safe. The research that praises humility also marks its boundaries. Owens and Hekman, and the studies that followed, found that humble behaviours backfire when followers read them as inauthentic, flattery, or impression management, which breeds distrust rather than trust. And in an acute crisis, where people are scanning for someone to be resolute, visible self-doubt can register as a lack of competence. So vulnerability and humility are not modes you leave switched on at full volume. They're calibrated: high in the messy, exploratory work where surfacing problems is the win; deliberately dialled toward steadiness when the building is on fire and the team needs a hand on the wheel.

flowchart TD
    A(["Something uncomfortable
is true (a mistake,
a gap, a fear)"]) --> B{"Who does sharing
this serve?"}
    B -->|"The team's
decision or learning"| C(["Share it, deliberately,
bounded, aimed at the work"])
    B -->|"Mostly my own
relief"| D(["Take it to a peer,
coach or journal instead"])
    C --> E{"Is the moment
exploratory or
acute crisis?"}
    E -->|"Exploratory"| F(["Lean in: admit, ask,
invite challenge"])
    E -->|"Acute crisis"| G(["Name reality once,
then be resolute"])
A working filter for when to be open and how far. Leaders Loop

A worked example

Priya runs a 12-person product team that has just missed a launch date for the second time. (Illustrative scenario; the figures are made up to show the moves.) The reflex is to project control, reassure upward, tighten the screws downward, and never let the team see her rattled.

Instead she does three deliberate things. In the team retro she admits her own contribution to the miss: "I added the analytics scope late and pretended it was free. It wasn't. That's on me." That's vulnerability, chosen, specific, aimed at the work, not a confession of generalised panic. Then she asks the room what she's not seeing: "What did I make hard for you that I don't know about?" That's humility, treating her own blind spots as the problem to solve, which (per Edmondson) is exactly what makes the next person comfortable enough to flag the real bottleneck. An engineer admits the estimates have been fiction for months because nobody wanted to deliver bad news; now it's on the table.

Finally, courage stops the meeting from dissolving into shared helplessness. Priya names the next call clearly, "we cut the analytics scope, we ship the core flow on the 30th, and I'll handle the conversation upstairs", and owns it. The room gets both halves: a leader honest enough to surface the truth, and resolute enough to act on it. That pairing is the whole toolkit in one meeting.

Frequently asked questions

Isn't this just an excuse for managers to overshare?

It's the opposite. The filter, does this serve the team or me?, exists precisely to rule out oversharing. Dumping your anxiety on the people you lead isn't vulnerability; it's outsourcing your emotional regulation to subordinates. Chosen, bounded disclosure aimed at the work is the version that builds trust.

Won't admitting mistakes make me look weak or lose authority?

The evidence points the other way for ordinary, exploratory work: Edmondson's teams surfaced more problems and learned faster when leaders modelled fallibility, and Collins's highest-performing executives paired humility with fierce resolve. The caveat is real, though, in an acute crisis people want resolve first, and visible self-doubt can read as incompetence. Calibrate to the moment.

What's the difference between humility and low self-esteem?

Self-esteem is how you feel about yourself; humility is how accurately you see yourself. A humble leader can hold "I'm genuinely good at this" and "I am missing something here" at the same time. Low self-esteem can't, it collapses into either self-criticism or defensiveness, neither of which keeps the question "what am I missing?" usefully open.

How do I show humility without looking like I'm performing it?

This is the trap the research flags directly: humble behaviours backfire when they read as impression management. The fix is specificity and cost. Vague self-deprecation ("oh, I'm hopeless at spreadsheets!") reads as a performance. Naming a concrete, consequential mistake and what you learned reads as real, because it actually costs you something to say.

Can you teach courage, or do you just have it?

Courage is situational and trainable. It grows by doing slightly harder true things and surviving them: one honest piece of feedback, one admitted error, one unpopular-but-right call. Each rep lowers the cost of the next. It's a muscle, not a birthright.

Related in the Toolkit

Where to go next