Accountability Without Fear: The Conditions Leaders Have to Create

There is a version of accountability that makes people better.

And there is a version that makes people better at hiding things.

Both can look like accountability from the leader's chair.

The difference is what happens when something goes wrong.

Can someone say, I don't understand?

Can they say, I think we're making the wrong decision?

Can they admit, I screwed this up?

Can they tell their manager, I need help?

Or have they learned that the safest thing to do is keep their head down, protect themselves, and make sure they aren't the person holding the bag when something fails?

That was the question underneath a recent Connection Lab conversation:

How do you build accountability without creating fear?

The more we talked, the clearer something became.

We've made accountability far too transactional.

Manager sets expectation. Employee delivers. Manager evaluates.

But organizations don't actually work that way.

We are accountable to each other to accomplish shared work and goals so that we can win together.

That changes what accountability requires from leaders.

Accountability isn't something you do to people

Accountability often enters the conversation when something has already gone wrong.

A deadline was missed. A customer is unhappy. Someone didn't deliver. The numbers aren't where they're supposed to be.

Then we go looking for accountability.

Who owned this?

Why didn't they get it done?

What are they going to do differently next time?

Those can be legitimate questions.

But they're incomplete.

Because if I am going to hold someone accountable for an outcome, I also have to ask what I was accountable for creating around them.

Did they understand what was expected?

Did they understand why it mattered?

Did they have enough information to make good decisions?

Did they have the skills necessary to do the work?

Did they have the authority to act?

Could they raise a concern without being dismissed?

Could they ask for help without it being interpreted as incompetence?

Could they tell me something I didn't want to hear?

Accountability isn't merely an employee obligation.

It is a mutual obligation.

And leaders have disproportionate influence over the conditions in which that accountability occurs.

Clarity comes before accountability

One of the examples that came up in our conversation was painfully familiar.

A manager asks someone to do something.

The employee does it.

Then the manager looks at the result and says:

That's not what I wanted.

Sometimes that's a performance problem.

But sometimes the manager never adequately explained what they wanted in the first place.

You cannot hold someone accountable to an expectation that existed primarily in your head.

People need to know what they're trying to accomplish, why it matters, where the boundaries are, what decisions they can make, and what success looks like.

That doesn't mean giving someone a 47-step instruction manual.

In fact, overprescribing the how can create a different problem: people become dependent on the leader rather than developing the judgment to navigate the work themselves.

The leader's job is to create enough clarity that people can move.

Direction without micromanagement.

That distinction matters.

Psychological safety doesn't mean lowering the bar

This is where conversations about psychological safety sometimes go sideways.

Psychological safety isn't permission to miss commitments indefinitely.

It isn't avoiding difficult conversations.

It isn't being endlessly nice.

And it certainly isn't removing consequences from poor performance.

It means people can tell the truth about the work.

They can say:

I'm stuck.

I don't know.

I made a mistake.

I don't agree.

I think we're solving the wrong problem.

Those statements are not the enemy of accountability.

They're often what makes accountability possible.

If people are afraid to surface problems, the problems don't disappear.

The information disappears.

And now the organization has a much more dangerous problem: leaders are making decisions based on a distorted version of reality.

High-performing organizations need both.

High standards and high candor.

People should be expected to deliver.

And they should be safe enough to tell you when something is getting in the way of delivering.

People have to be allowed to be bad at something before they become good at it

There's another tension leaders have to manage.

We say we want people to grow.

We want them to take more ownership.

We want them to make decisions without constantly coming back to us.

Then we give them something new to do and become frustrated when they aren't immediately good at it.

That's not development.

That's delegation followed by disappointment.

New capability is messy.

People ask awkward questions. They make imperfect decisions. They misunderstand things. They try approaches that don't work.

There has to be enough room for people to learn without every mistake becoming evidence that the leader should take the work back.

Otherwise we create exactly the dependency we complain about.

The employee learns:

It's safer to ask the boss.

It's safer not to decide.

It's safer to wait.

And eventually the founder or leader concludes:

See? Everything still depends on me.

Sometimes it does.

But sometimes we've inadvertently trained people to depend on us.

Leaders have to model the behavior they want

You cannot build a candid organization while being defensive when someone challenges you.

You cannot tell people to ask questions and then make them regret asking.

You cannot demand accountability while refusing to acknowledge your own mistakes.

And an open-door policy doesn't mean much if everything about your behavior says:

Please don't walk through it.

Psychological safety is created in tiny interactions.

Someone raises a concern.

What does the leader do next?

Someone disagrees.

What happens to them?

Someone admits a mistake.

Is the first response curiosity or blame?

Someone asks for clarification.

Does the manager explain—or make them feel stupid for not already knowing?

People learn very quickly what is actually safe inside an organization.

Not from the values painted on the wall.

From what happens when somebody tests them.

Two phrases that can change a conversation

One practical part of our Connection Lab discussion was how language can lower the temperature of a difficult conversation without lowering the standard.

Two phrases I use often are remarkably simple:

“Help me understand…”

and

“When you say X, do you mean Y?”

Neither avoids disagreement.

They create enough room to understand before reacting.

Instead of:

That's wrong.

Try:

Help me understand how you got there.

Instead of assuming intent:

When you say we should delay this, do you mean you don't think the work is ready, or are you concerned about something else?

That little bit of curiosity can keep a disagreement from becoming a threat.

And that's a leadership capability worth practicing.

The leader holds the flashlight

During the conversation, Alex Bartholomaus offered a metaphor I keep thinking about.

Imagine the leader is carrying a flashlight.

Where do they point it?

Some leaders walk out front, holding the flashlight where only they can see the path.

Everyone else has to follow them.

Others shine it backward, constantly checking what everyone is doing.

But there's another possibility.

The leader illuminates the path so everyone can see where they're going.

That's a very different picture of leadership.

The leader still has responsibility.

The leader still helps establish direction.

The leader still holds standards.

But everyone can see enough of the path to move.

That's what good accountability should ultimately create.

Not dependence.

Not obedience.

Not fear.

Capability.

People understand where they're going, what they're responsible for, how their work connects to everyone else's, and what is expected of them.

They can make decisions.

They can ask for help.

They can challenge assumptions.

They can acknowledge when something isn't working.

And they can be held accountable for what they do next.

Accountability and psychological safety aren't opposites

We sometimes talk about these ideas as though leaders have to choose.

Do you want a high-accountability culture?

Or do you want a psychologically safe culture?

That's the wrong tradeoff.

Organizations need people who can tell the truth and take responsibility.

People who can acknowledge mistakes and correct them.

People who can challenge decisions and commit once a direction has been chosen.

People who can ask for help and own the outcome.

That requires more from leaders than telling people to "take ownership."

It requires creating the conditions where ownership is actually possible.

Because the goal of accountability shouldn't be to make people afraid of getting something wrong.

The goal is to build people and teams capable of making more things go right—without everything depending on the person at the top.   

---

Connection Lab with Stephanie Kord Miller is held every Wednesday at noon ET. Each week, thoughtful leaders, entrepreneurs, and builders come together to explore one important question shaping the future of leadership, AI, trust, and organizational change.

If you'd like to think through these ideas with us—not just read about them—I hope you'll join the next conversation.