Accountability – Who Puts Their Hand Up?

There’s a moment that happens in every team or business, usually when something has gone wrong or a difficult decision needs to be made.

Someone has to step forward. Someone has to say, “I’ll own this,” or “That was on me,” or “Let me take the lead here.”

And in that moment, you learn a lot about a team’s culture. Not from what people say they value, but from what actually happens. Who steps forward? Who steps back? And which behaviour does the environment reward?

This isn’t about blame. It’s about ownership. And in my experience, the difference between high-performing teams and struggling ones often comes down to this: accountability.

The Two Types

I’ve worked with a lot of people over the years, across different organisations, industries, and team structures. And while everyone is different, I’ve noticed a pattern.

Some people step forward. When there’s ambiguity, they clarify. When there’s a gap, they fill it. When something goes wrong, they acknowledge their part and focus on fixing it. They don’t wait to be told. They don’t look around for someone else to take responsibility. They just act.

Other people step back. When there’s ambiguity, they wait. When there’s a gap, they assume it’s someone else’s problem. When something goes wrong, they distance themselves, point fingers, or stay quiet. They’re most likely a good person. But they’ve learned, somewhere along the way, that stepping forward is risky and stepping back is safe.

The difference isn’t always about character. Often, it’s about culture. People behave the way their environment has taught them to behave.

Why Hiding Happens

No one wakes up wanting to avoid responsibility. Hiding is usually a learned behaviour, and it’s worth understanding why it happens.

Fear of blame. In some environments, mistakes are punished. Not just the serious ones, but any mistake. People learn that admitting fault leads to consequences, so they stop admitting. They hedge, deflect, or go quiet. The safer move is to say nothing and hope no one notices.

Unclear ownership. When responsibilities are vague, it’s easy to assume someone else is handling it. “I thought that was their job.” “No one told me I was responsible for that.” Ambiguity creates gaps, and gaps create hiding spots.

Learned helplessness. In some teams, people have tried to step forward before and been shut down. Their ideas were ignored, their initiative was criticised, or their accountability was used against them. After enough of that, they stop trying. Why put your hand up if it only makes things worse?

Self-preservation. Sometimes the culture actively rewards hiding. The people who stay quiet don’t get blamed. The people who speak up get scrutinised. If you want to survive, you learn to keep your head down.

None of this is an excuse. But it is an explanation. And if you want to fix accountability problems, you have to understand what’s driving them.

The Cost of Hiding

When people hide, teams suffer. Not always immediately, but eventually.

Slow decisions. No one wants to commit, so decisions stall. Meetings end without resolution. Issues get kicked down the road. Everyone waits for someone else to take the lead.

Repeated mistakes. If no one owns the problem, no one fixes the root cause. The same issues keep surfacing because no one is accountable for making sure they don’t.

Frustration and resentment. The people who do step forward end up carrying more than their share. They get tired. They get resentful. They start wondering why they bother when others contribute less and face no consequences.

Eroded trust. Stakeholders lose confidence when things fall through the cracks. “Who’s responsible for this?” becomes a question no one can answer clearly. That’s not a good look for any team.

Missed opportunities. Innovation requires risk. If people are afraid to own outcomes, they won’t propose new ideas, challenge assumptions, or push for change. The team stagnates.

The irony is that hiding feels safe in the short term, but it creates long-term damage. The problems don’t go away. They just get bigger.

What Accountability Actually Looks Like

LHere’s something that gets misunderstood: accountability isn’t about blame.

Blame is backward-looking. It’s about finding fault, assigning punishment, making someone pay for what went wrong. Blame creates fear, and fear creates hiding.

Accountability is forward-looking. It’s about owning outcomes, good or bad. It’s about saying, “This is mine, and I’ll make sure it gets done.” And when things don’t go well, it’s about saying, “Here’s what happened, here’s what I learned, and here’s what I’ll do differently.”

Accountability sounds like:

• “I’ll take that.”
• “That was my responsibility, and I missed it.”
• “I don’t have the answer yet, but I’ll find out.”
• “Let me own the follow-up on this.”

It doesn’t sound like:

• “That wasn’t my fault.”
• “I was waiting for someone to tell me.”
• “That’s not my area.”
• Crickets.

The best teams I’ve worked with treat accountability as a shared value, not a weapon. When someone owns a mistake, they’re supported, not punished. When someone steps forward, they’re recognised, not taken advantage of.

That’s the difference between a blame culture and an ownership culture.

QA and the Hand that Goes Up

Here’s an observation from my own experience: QA professionals tend to put their hand up when no one else will.

Maybe it’s because we’re used to being the last line of defence. Maybe it’s because we spend our careers looking for problems others have missed. Maybe it’s because we’re often the ones in the room asking the uncomfortable questions that no one else wants to ask.

Whatever the reason, I’ve seen it again and again. A gap appears. Ownership is unclear. Everyone looks around. And it’s often the tester who says, “I’ll take it.”

That’s not always a good thing. Sometimes QA ends up carrying responsibilities that should belong elsewhere, simply because no one else stepped forward. That can lead to burnout and resentment.

But it does speak to something about the QA mindset. We’re trained to notice what’s missing. We’re trained to think about risk. And when something needs to be owned, that training kicks in.

If you’re in QA and you recognise this pattern in yourself, know that it’s a strength. Just make sure you’re not the only one exercising it.

How Leaders Can Encourage Ownership

If you’re in a leadership position, the culture around accountability starts with you. Here’s what I’ve seen work.

Model it yourself. If you want your team to own outcomes, you have to own yours. Admit when you’re wrong. Take responsibility for team failures, not just successes. Show that accountability is valued, not punished.

Make ownership clear. Ambiguity breeds hiding. Be explicit about who owns what. When assigning work, make sure there’s a name attached, not just a team. “Someone should look at this” is an invitation to no one.

Respond to mistakes with curiosity, not blame. When something goes wrong, ask “what happened, was it a timing issue, a miscommunication, a gap in the process?” before “who’s responsible?” Focus on understanding and fixing, not punishing. People are more likely to own mistakes when they know they won’t be attacked for them.

Recognise those who step forward. When someone takes ownership, acknowledge it. Not with empty praise, but with genuine recognition. Let the team see that stepping forward is valued.

Don’t let hiding succeed. If someone avoids responsibility and faces no consequences, others notice. You don’t have to punish, but you do have to address it. Otherwise, you’re teaching the team that hiding works.

Create psychological safety. People need to feel safe to speak up, admit uncertainty, and own mistakes. That safety comes from consistent behaviour over time, not from a single speech about values.

None of this is easy. Culture change is slow. But it starts with small, consistent actions from the people at the top.

A Question to Leave With

Here’s something worth reflecting on, whether you’re a leader or an individual contributor.

Think about the last time something went wrong in your team. Or the last time there was ambiguity about who should handle something.

What happened? Who stepped forward? Who stepped back? And what did the outcome teach people about how to behave next time?

Does your culture reward hiding or owning?

If hiding is the safer option, don’t be surprised when people hide. If owning is valued and supported, you’ll see more hands go up.

Accountability isn’t about finding someone to blame. It’s about building a team where people are willing to own outcomes, because they know that ownership is respected, not weaponised.

That’s the kind of team that delivers. That’s the kind of team people want to be part of.

And if you’re the person who always puts their hand up, keep doing it. Just make sure you’re surrounded by others who do the same.

A Note on Context

Every business and every project is different. What works in one place won’t work in another, and that’s the point.

Nothing here is meant to be a step-by-step prescription. It’s guidance, drawn from my own experiences, and deliberately kept general to avoid pointing fingers anywhere.

Take what’s useful, ignore what isn’t, and adapt it to your own context. Or as Joe Colantonio always says: “Test everything and keep the good.”