Author: gothamCulture

The word “vulnerability” makes some leaders uncomfortable.

I understand that. In a lot of organizational cultures, showing uncertainty or admitting you don’t know something is read as weakness. Leaders are supposed to have the answers. They’re supposed to project confidence.

But that instinct — to always appear certain, always appear in control — is exactly what erodes psychological safety on teams.

What Interpersonal Risk-Taking Actually Means

Interpersonal risk-taking is the willingness to do things at work that could result in negative social consequences: disagreeing with someone more senior, admitting a mistake, sharing an unpopular opinion, asking a “stupid” question, or trying something new that might not work.

These behaviors require a belief that the social cost will be tolerable — that you won’t be humiliated, dismissed, or punished for being honest.

In teams with low psychological safety, people systematically avoid these behaviors. They agree when they disagree. They hide uncertainty. They don’t ask for help. They don’t challenge bad ideas. And over time, those individual choices add up to a team that can’t really learn or improve.

Vulnerability as a Leadership Practice

Here’s what I’ve seen in organizations that build high levels of psychological safety: it almost always starts with a leader who models interpersonal risk-taking publicly.

They say “I don’t know” when they don’t know. They change their mind in front of their team and explain why. They share a recent failure and what they learned from it. They ask for feedback from their direct reports and actually use it.

These aren’t soft behaviors. They’re organizational acts that reshape what people believe is safe to do.

When a senior leader says “I got this wrong” and doesn’t collapse, people notice. When a manager says “I disagree with the direction we’re heading, and here’s why” in front of their team, and nothing bad happens to them, others start to believe they can do the same.

The Courage It Requires

Modeling interpersonal risk-taking isn’t always comfortable, even for leaders who understand its value. It requires a real tolerance for not being seen as the most informed person in the room.

But the payoff is significant. Teams that see their leaders take interpersonal risks become more willing to do the same. Over time, the team becomes the kind of place where honest, productive disagreement is the norm — where the best ideas surface because people aren’t holding them back. That’s a competitive advantage. Most organizations never build it.

Practical Starting Points

Share a recent mistake with your team. Be specific about what you learned. Invite challenge. Next time you’re in a meeting and someone disagrees with you, get curious before you get defensive. Ask a question you don’t know the answer to — in front of people.

None of this is complicated. All of it is harder than it sounds. But this is where psychological safety actually gets built — in small, visible, consistent acts of courage from the people with the most power in the room.

The word “vulnerability” makes some leaders uncomfortable.

I understand that. In a lot of organizational cultures, showing uncertainty or admitting you don’t know something is read as weakness. Leaders are supposed to have the answers. They’re supposed to project confidence.

But that instinct — to always appear certain, always appear in control — is exactly what erodes psychological safety on teams.

What Interpersonal Risk-Taking Actually Means

Interpersonal risk-taking is the willingness to do things at work that could result in negative social consequences: disagreeing with someone more senior, admitting a mistake, sharing an unpopular opinion, asking a “stupid” question, or trying something new that might not work.

These behaviors require a belief that the social cost will be tolerable — that you won’t be humiliated, dismissed, or punished for being honest.

In teams with low psychological safety, people systematically avoid these behaviors. They agree when they disagree. They hide uncertainty. They don’t ask for help. They don’t challenge bad ideas. And over time, those individual choices add up to a team that can’t really learn or improve.

Vulnerability as a Leadership Practice

Here’s what I’ve seen in organizations that build high levels of psychological safety: it almost always starts with a leader who models interpersonal risk-taking publicly.

They say “I don’t know” when they don’t know. They change their mind in front of their team and explain why. They share a recent failure and what they learned from it. They ask for feedback from their direct reports and actually use it.

These aren’t soft behaviors. They’re organizational acts that reshape what people believe is safe to do.

When a senior leader says “I got this wrong” and doesn’t collapse, people notice. When a manager says “I disagree with the direction we’re heading, and here’s why” in front of their team, and nothing bad happens to them, others start to believe they can do the same.

The Courage It Requires

Modeling interpersonal risk-taking isn’t always comfortable, even for leaders who understand its value. It requires a real tolerance for not being seen as the most informed person in the room.

But the payoff is significant. Teams that see their leaders take interpersonal risks become more willing to do the same. Over time, the team becomes the kind of place where honest, productive disagreement is the norm — where the best ideas surface because people aren’t holding them back. That’s a competitive advantage. Most organizations never build it.

Practical Starting Points

Share a recent mistake with your team. Be specific about what you learned. Invite challenge. Next time you’re in a meeting and someone disagrees with you, get curious before you get defensive. Ask a question you don’t know the answer to — in front of people.

None of this is complicated. All of it is harder than it sounds. But this is where psychological safety actually gets built — in small, visible, consistent acts of courage from the people with the most power in the room.

Article 11 of 16 · Pillar 4

Every organization says it learns from failure.

Very few actually do.

Not because people don’t want to learn — but because the culture around failure makes honest reflection almost impossible. When mistakes get punished, people hide them. When post-mortems become autopsy sessions, people minimize what went wrong. The learning doesn’t happen because the environment doesn’t allow it.

The Difference Between Blame Culture and Learning Culture

In a blame culture, the question after something goes wrong is: “Whose fault is this?”

In a learning culture, the question is: “What happened, and what can we do differently?”

These aren’t just different phrasings of the same thing. They create fundamentally different outcomes. Blame cultures get better at hiding failure. Learning cultures get better at preventing it.

Amy Edmondson’s research found something striking: teams with higher psychological safety reported more errors. The high-safety teams weren’t making more errors — they were catching and reporting errors that other teams were concealing.

What Failure Looks Like in High-Psychological-Safety Teams

Mistakes get reported early. When people aren’t afraid of the response, they surface problems while they’re still small.

Analysis is honest. People can describe what actually happened — including their own role — without excessive self-protection.

Lessons get institutionalized. The insights from what went wrong don’t stay in someone’s head. They become updated processes, training, or shared knowledge.

People try again. Because failure wasn’t catastrophic, people are willing to take risks again. That’s how innovation actually works.

How Leaders Shape the Response

When something goes wrong, the leader’s first response sets the tone for everything that follows.

Separate the performance conversation from the learning conversation. If someone made a significant mistake, there may be a performance issue to address. But that conversation shouldn’t happen in the same moment as the learning conversation. One is about consequences; one is about improvement. They need different rooms.

Ask “what” not “who.” What processes broke down? What assumptions turned out to be wrong? What information was missing? These questions surface learning. “Who dropped the ball?” surfaces defensiveness.

Make lessons visible. When your team learns something from a failure, say so — publicly, if appropriate. “We tried X, it didn’t work for these reasons, and here’s what we’re doing differently” is a cultural act as much as a practical one.

The Bottom Line

The organizations that iterate fastest and innovate most consistently aren’t the ones that avoid failure. They’re the ones that fail well — quickly, openly, and with enough honesty to actually improve.

That only happens when the environment is safe enough to be honest about what went wrong.

Every organization says it learns from failure.

Very few actually do.

Not because people don’t want to learn — but because the culture around failure makes honest reflection almost impossible. When mistakes get punished, people hide them. When post-mortems become autopsy sessions, people minimize what went wrong. The learning doesn’t happen because the environment doesn’t allow it.

The Difference Between Blame Culture and Learning Culture

In a blame culture, the question after something goes wrong is: “Whose fault is this?”

In a learning culture, the question is: “What happened, and what can we do differently?”

These aren’t just different phrasings of the same thing. They create fundamentally different outcomes. Blame cultures get better at hiding failure. Learning cultures get better at preventing it.

Amy Edmondson’s research found something striking: teams with higher psychological safety reported more errors. The high-safety teams weren’t making more errors — they were catching and reporting errors that other teams were concealing.

What Failure Looks Like in High-Psychological-Safety Teams

Mistakes get reported early. When people aren’t afraid of the response, they surface problems while they’re still small.

Analysis is honest. People can describe what actually happened — including their own role — without excessive self-protection.

Lessons get institutionalized. The insights from what went wrong don’t stay in someone’s head. They become updated processes, training, or shared knowledge.

People try again. Because failure wasn’t catastrophic, people are willing to take risks again. That’s how innovation actually works.

How Leaders Shape the Response

When something goes wrong, the leader’s first response sets the tone for everything that follows.

Separate the performance conversation from the learning conversation. If someone made a significant mistake, there may be a performance issue to address. But that conversation shouldn’t happen in the same moment as the learning conversation. One is about consequences; one is about improvement. They need different rooms.

Ask “what” not “who.” What processes broke down? What assumptions turned out to be wrong? What information was missing? These questions surface learning. “Who dropped the ball?” surfaces defensiveness.

Make lessons visible. When your team learns something from a failure, say so — publicly, if appropriate. “We tried X, it didn’t work for these reasons, and here’s what we’re doing differently” is a cultural act as much as a practical one.

The Bottom Line

The organizations that iterate fastest and innovate most consistently aren’t the ones that avoid failure. They’re the ones that fail well — quickly, openly, and with enough honesty to actually improve.

That only happens when the environment is safe enough to be honest about what went wrong.

Article 10 of 16 · Pillar 3

The first question people ask themselves before speaking up isn’t “Is this a good idea?”

It’s “Is it safe to say this here?”

If the answer is uncertain — or worse, if they’ve learned from experience that it isn’t — they stay quiet. And in that silence, organizations lose the information they most need.

A speak-up culture is the visible, experienced belief that voicing concerns, asking hard questions, and sharing difficult perspectives is welcomed — not just permitted.

Why Silence Is Expensive

We tend to think of disengagement as passive. But the cost of organizational silence is anything but passive.

The nurse who notices a potential medication error but doesn’t say anything because the attending physician seems annoyed. The engineer who has a nagging concern about a design but doesn’t raise it because no one else seems worried. The account manager who knows a client is unhappy but doesn’t escalate because the last person who raised bad news got shut down.

Every one of those silences has a downstream cost. Mostly, they’re invisible until they aren’t.

What Prevents People from Speaking Up

The barriers are usually social, not structural. People don’t stay quiet because there’s no suggestion box. They stay quiet because they’ve seen others get dismissed or punished for speaking up. Because they don’t think their input will be taken seriously. Because they’re worried about being labeled a complainer or a troublemaker.

These aren’t character flaws. They’re learned adaptations. If the environment has historically been unsafe, people adapt by going silent. Reversing that pattern takes deliberate, consistent effort from leadership.

What Leaders Can Do

Model it themselves. The most powerful signal a leader can send is being openly fallible — sharing uncertainty, inviting challenge, admitting mistakes. When leaders do this, they give everyone else permission to be human too.

Reward the messenger. Explicitly. When someone raises a difficult issue, acknowledge the courage it took. “I’m glad you brought this up” should be followed by something real: taking the concern seriously, acting on it, or explaining clearly why you can’t.

Never shoot the messenger. Even subtle signals — the slight defensiveness, the visible frustration, the changed dynamic after someone raised a concern — teach people not to speak up next time.

Ask better questions. “Is everything on track?” invites a yes or no. “What’s the one thing that keeps you up at night about this project?” invites honesty. The questions leaders ask in meetings shape what kind of information gets surfaced.

The Foundation Isn’t Policy. It’s Trust.

You can post a “speak-up culture” statement on the intranet. It won’t change anything.

What changes the culture is consistent leadership behavior over time — leaders who demonstrably listen, take concerns seriously, act on what they hear, and protect the people who were willing to say the hard thing. Build that, and speaking up starts to feel less like a risk and more like an expectation.

The first question people ask themselves before speaking up isn’t “Is this a good idea?”

It’s “Is it safe to say this here?”

If the answer is uncertain — or worse, if they’ve learned from experience that it isn’t — they stay quiet. And in that silence, organizations lose the information they most need.

A speak-up culture is the visible, experienced belief that voicing concerns, asking hard questions, and sharing difficult perspectives is welcomed — not just permitted.

Why Silence Is Expensive

We tend to think of disengagement as passive. But the cost of organizational silence is anything but passive.

The nurse who notices a potential medication error but doesn’t say anything because the attending physician seems annoyed. The engineer who has a nagging concern about a design but doesn’t raise it because no one else seems worried. The account manager who knows a client is unhappy but doesn’t escalate because the last person who raised bad news got shut down.

Every one of those silences has a downstream cost. Mostly, they’re invisible until they aren’t.

What Prevents People from Speaking Up

The barriers are usually social, not structural. People don’t stay quiet because there’s no suggestion box. They stay quiet because they’ve seen others get dismissed or punished for speaking up. Because they don’t think their input will be taken seriously. Because they’re worried about being labeled a complainer or a troublemaker.

These aren’t character flaws. They’re learned adaptations. If the environment has historically been unsafe, people adapt by going silent. Reversing that pattern takes deliberate, consistent effort from leadership.

What Leaders Can Do

Model it themselves. The most powerful signal a leader can send is being openly fallible — sharing uncertainty, inviting challenge, admitting mistakes. When leaders do this, they give everyone else permission to be human too.

Reward the messenger. Explicitly. When someone raises a difficult issue, acknowledge the courage it took. “I’m glad you brought this up” should be followed by something real: taking the concern seriously, acting on it, or explaining clearly why you can’t.

Never shoot the messenger. Even subtle signals — the slight defensiveness, the visible frustration, the changed dynamic after someone raised a concern — teach people not to speak up next time.

Ask better questions. “Is everything on track?” invites a yes or no. “What’s the one thing that keeps you up at night about this project?” invites honesty. The questions leaders ask in meetings shape what kind of information gets surfaced.

The Foundation Isn’t Policy. It’s Trust.

You can post a “speak-up culture” statement on the intranet. It won’t change anything.

What changes the culture is consistent leadership behavior over time — leaders who demonstrably listen, take concerns seriously, act on what they hear, and protect the people who were willing to say the hard thing. Build that, and speaking up starts to feel less like a risk and more like an expectation.

Article 9 of 16 · Pillar 2

Teams don’t fail because people lack talent.

They fail because people hold back.

They don’t share the concern because they’re not sure how it will land. They don’t challenge the assumption because no one else seems to be questioning it. They don’t admit the mistake early because they’re afraid of how it will be received.

That’s what psychological safety addresses. And until your team has it, their capacity to perform — really perform — is capped.

What Psychological Safety Actually Is

The concept was developed by Amy Edmondson, a researcher at Harvard Business School, who defined psychological safety as “a belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes.”

It’s not about being comfortable or being nice to each other. It’s not about eliminating friction or conflict. Psychological safety is the specific belief that interpersonal risk-taking — saying the difficult thing, questioning the plan, admitting you don’t know — won’t result in rejection or retribution.

Edmondson’s original research, conducted on hospital teams, showed that teams with higher psychological safety actually reported more errors. Those teams caught mistakes early because people weren’t afraid to flag them.

Why It’s the Foundation of High-Performing Teams

Google’s Project Aristotle — a major internal study on what makes teams effective — analyzed 180 teams and found that psychological safety was by far the most important factor in team performance. More important than individual talent, seniority, or work structure.

The logic is straightforward: innovation requires risk-taking. Learning requires the ability to admit failure. Honest problem-solving requires the ability to disagree. All of these things require psychological safety.

Without it, teams default to conflict avoidance, groupthink, and the kind of performance where everyone looks capable but nothing really improves.

The 5 Pillars of Psychological Safety

Over the next few weeks, we’ll break down five conditions that build — or erode — psychological safety:

Speak-Up Culture. The first building block: an environment where raising concerns and asking questions is genuinely welcomed, not just tolerated.

Learning from Failure. How a team or organization responds to mistakes sends a stronger signal than any policy ever could.

Interpersonal Risk-Taking. The willingness to be vulnerable, admit uncertainty, and challenge the status quo — especially in front of people who have power over your career.

Inclusion and Belonging. Psychological safety can’t coexist with exclusion. When some people’s voices are systematically undervalued, the whole team suffers.

Trust and Vulnerability. The interpersonal substrate that makes all of this possible.

This Isn’t About Being Soft

Psychological safety gets mislabeled as a “culture initiative” or a sensitivity exercise. It isn’t.

It’s a performance imperative. Teams that don’t have it leave capability on the table — because the people who might catch the problem, spot the opportunity, or flag the risk are keeping their mouths shut. That’s expensive. Often, it’s catastrophic.

Teams don’t fail because people lack talent.

They fail because people hold back.

They don’t share the concern because they’re not sure how it will land. They don’t challenge the assumption because no one else seems to be questioning it. They don’t admit the mistake early because they’re afraid of how it will be received.

That’s what psychological safety addresses. And until your team has it, their capacity to perform — really perform — is capped.

What Psychological Safety Actually Is

The concept was developed by Amy Edmondson, a researcher at Harvard Business School, who defined psychological safety as “a belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes.”

It’s not about being comfortable or being nice to each other. It’s not about eliminating friction or conflict. Psychological safety is the specific belief that interpersonal risk-taking — saying the difficult thing, questioning the plan, admitting you don’t know — won’t result in rejection or retribution.

Edmondson’s original research, conducted on hospital teams, showed that teams with higher psychological safety actually reported more errors. Those teams caught mistakes early because people weren’t afraid to flag them.

Why It’s the Foundation of High-Performing Teams

Google’s Project Aristotle — a major internal study on what makes teams effective — analyzed 180 teams and found that psychological safety was by far the most important factor in team performance. More important than individual talent, seniority, or work structure.

The logic is straightforward: innovation requires risk-taking. Learning requires the ability to admit failure. Honest problem-solving requires the ability to disagree. All of these things require psychological safety.

Without it, teams default to conflict avoidance, groupthink, and the kind of performance where everyone looks capable but nothing really improves.

The 5 Pillars of Psychological Safety

Over the next few weeks, we’ll break down five conditions that build — or erode — psychological safety:

Speak-Up Culture. The first building block: an environment where raising concerns and asking questions is genuinely welcomed, not just tolerated.

Learning from Failure. How a team or organization responds to mistakes sends a stronger signal than any policy ever could.

Interpersonal Risk-Taking. The willingness to be vulnerable, admit uncertainty, and challenge the status quo — especially in front of people who have power over your career.

Inclusion and Belonging. Psychological safety can’t coexist with exclusion. When some people’s voices are systematically undervalued, the whole team suffers.

Trust and Vulnerability. The interpersonal substrate that makes all of this possible.

This Isn’t About Being Soft

Psychological safety gets mislabeled as a “culture initiative” or a sensitivity exercise. It isn’t.

It’s a performance imperative. Teams that don’t have it leave capability on the table — because the people who might catch the problem, spot the opportunity, or flag the risk are keeping their mouths shut. That’s expensive. Often, it’s catastrophic.

Article 8 of 16 · Pillar 1

People need to believe that their voice matters.

Not that it’s tolerated. Not that it’s collected in a survey and filed away. That it actually influences decisions, shapes direction, and makes a difference.

When employees feel heard — genuinely heard — engagement goes up. When they feel like they’re speaking into a void, they stop trying.

What Employee Voice Actually Means

Employee voice is the ability and confidence to raise concerns, offer ideas, push back on decisions, and share perspectives — without fear of being dismissed or penalized.

It’s distinct from having an anonymous suggestion box. It’s distinct from the CEO doing a quarterly “ask me anything.” Those things can be part of the picture, but voice as a driver of engagement requires something more: ongoing, trust-based channels through which employees actually influence outcomes.

The Engagement Connection

Research by Gallup and others consistently shows that employees who feel their opinions count are more engaged. The inverse is equally reliable: when people believe their input will be ignored, they stop offering it — and they start disengaging.

There’s also a trust element here. When leaders act on employee input — or explain clearly why they aren’t — they demonstrate that the feedback loop is real. That builds trust. Trust drives engagement.

Why Most Organizations Fail at This

The most common failure mode is the feedback loop that goes nowhere. The company surveys its employees, shares the results, and then nothing changes. Maybe there’s a presentation about the scores. Maybe there’s a working group. But 12 months later, nothing is visibly different.

That’s worse than not asking. It confirms what people already suspected: the survey is theater.

Building Real Employee Voice

Take visible action on feedback. Even small, fast actions signal that input leads somewhere. Close the loop explicitly: “We heard this from the survey; here’s what we’re doing about it.” When you can’t act on something, explain why.

Create team-level listening channels. The most powerful voice isn’t the enterprise survey — it’s the team meeting where people can raise concerns without a 30-day feedback cycle. Manager-led conversation is the fastest, most responsive listening channel you have.

Train leaders to receive feedback well. If employees have seen leaders get defensive, dismiss concerns, or subtly penalize people for raising issues, they’ve learned not to speak up. That behavior has to stop before voice can exist.

Don’t wait for formal channels. The most engaged cultures have informal voice woven into how the organization operates — leaders who proactively ask, listen, and respond. Not as an event. As a daily habit.

The Bottom Line

Employee voice isn’t about giving everyone a vote on every decision. It’s about building an organization where people believe their perspective is valued and their input can change things.

Do that, and engagement follows.

People need to believe that their voice matters.

Not that it’s tolerated. Not that it’s collected in a survey and filed away. That it actually influences decisions, shapes direction, and makes a difference.

When employees feel heard — genuinely heard — engagement goes up. When they feel like they’re speaking into a void, they stop trying.

What Employee Voice Actually Means

Employee voice is the ability and confidence to raise concerns, offer ideas, push back on decisions, and share perspectives — without fear of being dismissed or penalized.

It’s distinct from having an anonymous suggestion box. It’s distinct from the CEO doing a quarterly “ask me anything.” Those things can be part of the picture, but voice as a driver of engagement requires something more: ongoing, trust-based channels through which employees actually influence outcomes.

The Engagement Connection

Research by Gallup and others consistently shows that employees who feel their opinions count are more engaged. The inverse is equally reliable: when people believe their input will be ignored, they stop offering it — and they start disengaging.

There’s also a trust element here. When leaders act on employee input — or explain clearly why they aren’t — they demonstrate that the feedback loop is real. That builds trust. Trust drives engagement.

Why Most Organizations Fail at This

The most common failure mode is the feedback loop that goes nowhere. The company surveys its employees, shares the results, and then nothing changes. Maybe there’s a presentation about the scores. Maybe there’s a working group. But 12 months later, nothing is visibly different.

That’s worse than not asking. It confirms what people already suspected: the survey is theater.

Building Real Employee Voice

Take visible action on feedback. Even small, fast actions signal that input leads somewhere. Close the loop explicitly: “We heard this from the survey; here’s what we’re doing about it.” When you can’t act on something, explain why.

Create team-level listening channels. The most powerful voice isn’t the enterprise survey — it’s the team meeting where people can raise concerns without a 30-day feedback cycle. Manager-led conversation is the fastest, most responsive listening channel you have.

Train leaders to receive feedback well. If employees have seen leaders get defensive, dismiss concerns, or subtly penalize people for raising issues, they’ve learned not to speak up. That behavior has to stop before voice can exist.

Don’t wait for formal channels. The most engaged cultures have informal voice woven into how the organization operates — leaders who proactively ask, listen, and respond. Not as an event. As a daily habit.

The Bottom Line

Employee voice isn’t about giving everyone a vote on every decision. It’s about building an organization where people believe their perspective is valued and their input can change things.

Do that, and engagement follows.

Cluster 5: Psychological Safety

Article 7 of 16 · Hub