Structural Courage

We keep asking people to be brave. Maybe the system should stop requiring it.

Over the past few weeks, I’ve been obsessively thinking and writing about why change stalls in organizations. Training that doesn’t transfer because the environment doesn’t support it. Empowerment that reverts the moment the leader who built it leaves. Enabling constraints as a way to encode the right defaults. And the unofficial rules that reveal what happens when all of that is left to chance.

Each of these explored a different piece of the puzzle, but I kept landing on the same pattern: we keep asking individuals to be braver inside systems that reward complacency.

Individual Bravery vs. Structural Courage

We talk a lot about psychological safety, the idea that people should feel safe enough to speak up, take risks, and admit mistakes. It matters, and I believe in it. But I’ve been thinking about what it asks of people.

Think about what “feel safe to speak up” means in practice. Someone still has to go first. They have to raise their hand, say “I think we’re solving the wrong problem,” and override every instinct telling them to stay quiet. We promise we’ll support them when they do, but the system still requires them to be brave. And then sometimes we ignore that and ask them to build that feature anyway. Their individual courage now feels like wasted effort.

The way I see it, psychological safety addresses the fear, but it doesn’t address the structure that created the fear. So what would it look like to address the structure itself?

I’ve been calling the missing piece structural courage, the idea that the system removes the need for individual courage. That people don’t need to be shock absorbers because the system absorbs it.

Psychological safety puts the burden on people to be brave. Structural courage puts the burden on the system so that bravery is no longer needed to act on what you know matters. Once we can name that distinction, we can start designing for it.

Why Caution Is Rational

Before we can design for structural courage, it helps to understand why caution is so deeply embedded. Two forces are working against us, and they reinforce each other.

Inside us: uncertainty feels like weakness

I remember the last time I said “I don’t know” in front of senior leaders. I can tell you who was in the room and what was on the screen. I hung up and replayed the conversation in my head for an hour. What I should have said. How I should have framed it. Whether I came across as if I didn’t have a handle on things.

We are conditioned to know. People look to us for answers, and when we admit uncertainty, it doesn’t feel like intellectual honesty. It feels like a gap in our competence. The system rewards having the answer and having the plan ready. Saying “I’m not sure” in a room full of people who seem sure takes more energy than most of us realize.

Around us: the system makes risk-taking a bad bet

A few years ago, my team wasn’t meeting the say/do targets. Say/do ratios measure whether you did what you said you would do, but “what you said” is defined as features committed and delivered on time, not whether the feature delivered value.

My team was working differently from most teams around us. We were breaking work into smaller increments so we could test, learn, and move forward, and we were measuring ourselves on outcomes rather than the number of features completed.

I got my hand slapped by a senior leader. I was confused at first. I expected leaders at that level to understand that we were measuring outcomes and that breaking work into learning increments was deliberate. But the metric only measured one kind of work for all teams, and leaders, far from the day-to-day, assumed the process applied to everyone.

When you’re running smaller experiments and learning as you go, the ratio looks bad even when the work is good.

My team knew that working towards the outcomes got their leader reprimanded. The system sent a message that day, and it wasn’t “keep measuring outcomes.”

The incentives are asymmetric. You bear the risk, and the organization gets the reward, so we minimize risk. We hedge. “Let’s get more data.” “Let’s start small.” These aren’t failures of courage. They’re rational responses to a system that punishes being wrong more than it rewards being right.

The loop

We play it safe because the system rewards playing it safe. And the more we do it, the more the system reinforces it.

We keep telling people it’s safe to speak up, but the system still rewards staying quiet. Structural courage closes that gap.

Why Environment Wins

Here’s how I think about why structural courage matters so much. We assume that when we train people, they change their behavior. That behavior becomes identity. And identity eventually shifts the environment. That’s the path we invest in.

Training → Behavior → Identity → Environment: this path is slow, and it usually loses to the system.

The stronger loop runs the other direction.

Environment → Identity → Behavior

When the environment changes, people change with it. I’ve seen it. Same people, different environment, different questions get asked, work gets done differently. And when the environment reverts, so do they.

You do not rise to the level of your product mindset. You fall to the level of your environment.

Structural courage is what makes the environment hold. Without it, our investments in people, training, and frameworks wash out over time.

Building Structural Courage

If you’ve been reading along, you might recognize yourself in some of this. Maybe you’ve been the one shielding your team from a metric that didn’t fit how they worked. Or, pushing for smaller experiments when the system wanted big commitments. Or running a different process and absorbing the political cost so your team could focus on what mattered.

That kind of individual heroism is real, and it works for a while. But it’s exhausting, and it doesn’t survive you leaving. I’ve been that hero. When I left, the system won.

The way I see it, the fix is redesigning the system itself. I’ve been writing about what that looks like in my last few posts: changing the defaults so the right behavior is the easy one, encoding rules that shape outcomes rather than compliance, and closing the gap between the system we document and the system people follow in practice. Those are pieces of structural courage, and they’re designed to outlast any single leader.

What would you change if your team didn’t need a hero to focus on outcomes?

The Question Worth Asking

We keep investing in better training, frameworks, and more coaching to change behavior. These investments matter. But they’re working against a system that makes the safe choice obvious and the right choice risky.

The question I keep coming back to: are we changing the system, or is the system changing us?

Structural courage doesn’t mean we stop investing in people. It means we redesign the system so it supports what we’re asking of them, instead of working against it.

Where in your organization does doing what matters still require an act of courage, that the system should make unnecessary?