Scaling Courage Starts with Empathy

At Full Scale, we run quarterly performance reviews for every engineer on the team. We measure the usual factors: problem solving, code quality, architecture, communication skills, and more.

There's one pattern we've seen again and again. As engineers gain experience, every metric improves. Communication improves too, but it's always the last to catch up.

Not because these engineers have nothing to say. Even the quietest introverts have insights worth sharing. But they've learned not to share them. It's not just a communication problem.

It's a courage problem. And most leaders never even recognize it.

If courage isn't showing up across your team, you might think you've hired the wrong people. But often, the system is teaching them that safety matters more than truth.

Do they speak up in meetings?

Do they push back on bad ideas?

Do they admit when they don’t understand something?

If someone on your team rarely speaks up, create opportunities for them. In your next meeting, ask them specifically: "What's your take on this?" Make it normal for them to share their perspective. Courage grows through practice, not pressure.

You've seen brilliant engineers plateau. Not because they lacked skill, but because they stopped engaging with the hard parts of the job. They stay quiet in meetings. They stick to well-defined tasks. They avoid the messy problems that actually need solving.

Courage is the foundation on which everything else is built.

Without it, people stop growing. Ownership never takes root.

If you want people to grow, you need more than a career growth framework. You need empathy.

The kind that notices what isn’t being said, and cares enough to ask why. If you’re asking these questions, you’re doing the work that builds trust. Because courage doesn’t just appear, it has to be invited, coached, and reinforced.

You have to see past the silence and ask:

What system has taught them to hold back?

And what can I do to change that?

That’s what this chapter is about.

Courage is both a personal strength and an indicator of your culture. One that starts with leaders, spreads through behavior, and unlocks teams that care enough to build what matters.

Courage Starts at the Top

When engineers don’t speak up, the instinct is often to coach them.

“Don't be afraid to challenge requirements.”

“You need to be more vocal in meetings.”

“I want to see you take more initiative.”

But you can’t coach your way out of a larger cultural problem.

If courage is missing across the entire team, it’s not a people problem. It’s the system talking. And systems don’t change through encouragement alone. They change through behavior.

Teams won't challenge assumptions if you never change your mind. They need to see you admit mistakes, pivot on decisions, and actually listen when they push back.

It’s about what you do next when someone speaks up.

Do you thank them?

Do you pause the plan to re-evaluate?

Do you give them credit when their challenge leads to a better outcome?

Or do you get defensive? Talk over them? Move on?

You build courage two ways: show it yourself, and reward it in others.

You Can’t Coach Around a Broken System

The roadmap is always packed, but nobody can tell you why the work matters. Feedback loops are weak or nonexistent. Priorities shift with no warning.

Leaders preach ownership but make every decision behind closed doors. Truth gets filtered. And everyone knows it.

In that kind of environment, courage becomes silent.

Engineers stop asking hard questions. Not because they’re checked out, but because they learn it doesn’t change anything.

They become experts at quiet compliance. From the outside, they still look productive.

They’re attending meetings, but not speaking up.

They’re writing code, but not asking why.

They're shipping features, but not solving problems.

This isn't apathy. It's self-preservation. The system taught them it wasn't worth the risk.

That's why courage doesn't start with coaching. It starts with fixing what's broken.

When speaking up gets you burned, you stop.

When bad ideas ship anyway, you stop caring.

When truth gets punished, you learn to stay quiet.

No amount of encouragement erases those lessons.

Before you ask for courage, you need to rebuild the psychological safety that makes it possible. That’s not a failure. It’s leadership work that most teams never realize needs doing.

That means telling the truth about what’s not working. Inviting feedback and making sure it leads to visible change. Not punishing silence, but being curious about it.

Silence is a signal. It doesn’t mean people don’t care. It means the system stopped listening.

Vision, focus, clarity, and shared ownership only work if people are willing to speak the truth. Speaking up takes courage.

So before you coach the team to speak up, pause and ask:

What happens in this organization when someone disagrees with the plan?

When was the last time we changed course based on feedback from the team?

What stories are we telling explicitly or implicitly about what happens to people who challenge the status quo?

If the answers are hard to face, you’re not alone. Every courageous culture starts with someone willing to face them anyway. That’s where real change starts.

Empathy Is How You Earn Courage

You can’t build courage in people you don’t understand. And you can’t expect courage from people who feel invisible.

If you want engineers to speak up, you have to understand what’s holding them back. And that starts with asking: “What would it take to make someone feel safe enough to care out loud?”

It means leading with context, not pressure. It means assuming there’s a reason for the hesitation, and being curious enough to find it.

Empathy is how you meet people where they are, so you can lead them somewhere better.

Empathy has to be practiced across the team, not just expected from leaders. Engineers need empathy for each other, for their users, and even for their leaders.

It takes courage to stay curious, especially when you risk being wrong about what someone else needs. Empathy is what makes engineers ask better questions about who the work is for and how it helps.

It’s what turns “What are we building?” into “Who is this for, and how will it help?” If you want your team to challenge bad ideas, they have to care who gets hurt if they don’t.

Empathy shows you what needs to be said. Courage helps you say it.

But vision is what guides them both. Because without a clear purpose to rally around, even brave feedback has nowhere to land.

Recognize How Courage Shows Up Across Cultures

If you're working with a global team, you can't teach courage without understanding their culture.

Some engineers learned that challenging authority publicly brings consequences. Others come from environments where being outspoken damaged relationships. Many have been trained by their education, their previous jobs, or company cultures that silence is safer than speaking up.

Silence doesn’t mean they don’t care. It might reflect different cultural norms.

That’s why your job isn’t just to invite courage. It’s to localize what it looks like.

Ask yourself:

Are we making space for different communication styles?

Do our rituals reward only extroverted or direct forms of assertiveness?

Are we unintentionally biasing promotions toward the loudest voices?

Instead, look deeper:

Who’s giving quiet, thoughtful feedback one-on-one?

Who consistently brings problems forward through private channels?

Who pushes for quality or clarity even when it's uncomfortable?

Courage isn’t always loud. Sometimes it’s quiet, and just as brave.

That’s still courage. And if you want more of it, your job is to notice it.

Not Everyone’s Ready for the Big Stage

At Full Scale, we've noticed that people often go quiet when executives join the chat. A fun conversation suddenly feels like it needs to be overly professional because the boss is there.

Some people simply feel comfortable in small groups and uncomfortable on a bigger stage.

We saw this at our summer company party. When we asked for volunteers to perform solo in front of everyone, no one raised their hand. But the moment they could do it as a group, they hammed it up.

Just because someone won't sing karaoke in front of 200 people doesn't mean they won't speak up where it matters. Sometimes courage shows up in 1:1s, DMs, or in smaller meetings where they feel more comfortable.

If you want a culture of courage, you have to recognize how it shows up and create safe spaces where it can grow before expecting people to step onto the big stage.

Designing for Courage at Scale

You scale courage by designing your organization to expect it and protect it.

That means embedding it into how decisions are made, how communication happens, and how leadership responds under pressure.

At scale, what you reward becomes culture.

That might look like:

Building reflection questions into planning: “What feels risky? What assumptions are we making?”

Making retrospectives a place for surfacing what felt wrong, not just what went wrong.

Creating anonymous ways for people to challenge decisions, so safety doesn’t rely on personality.

Celebrating people who stopped a project, not just those who shipped one.

What matters most is how you respond to feedback and moments as they arise. If everyone sees that nothing happens when they do speak up, they simply learn not to.

Feedback has to lead to change that’s visible and swift.

But courage doesn't start in all-hands meetings or public forums. It starts in 1:1s. Those quiet moments where someone decides whether it's safe to tell you the truth.

Every time someone brings you something hard and you handle it well, you’re shaping their belief in whether this is a company where honesty is valued.

How Courage Scales: The Loop That Leaders Create

Courage doesn’t spread because you said it mattered. It spreads because someone tested the water, and it felt safe.

It’s not belief that makes courage scale. Its behavior is repeated in a loop.

Empathy creates safety.

Safety invites truth.

Change builds trust.

Trust fuels more courage.

Every time someone speaks up and something changes, the loop strengthens. Every time someone speaks up and nothing happens, the loop breaks.

So if you want more courage, your job isn’t just to ask for it. It’s to complete the loop again and again until people start doing it on their own.

The loop is small. It shows up in 1:1s, roadmap reviews, Slack threads, and hallway questions. Over time, these small moments become the culture. Not because it was policy. Because it was practiced.

The loop works because empathy makes people believe they matter.

Courage doesn’t start with someone raising their hand. It starts with the belief that someone will care if they do.