You Don't Have an Accountability Problem

Every leadership team has declared accountability as a cultural priority. Almost none of them are more reliable for it. The word gets dropped in meetings, printed on value slides, and attached to dashboards — and somehow execution is supposed to improve. It doesn't. Because accountability is structurally backward-looking: it names the failure, points at the person, and asks everyone to feel appropriately serious about something that already happened.

Jackson and Scott spend this episode dismantling the accountability reflex and replacing it with something that actually moves the needle: reliability — not as a buzzword swap, but as a structural shift from blame to design. The difference between an organization that does what it says and one that perpetually chases accountability comes down to three conditions, all of which must be built before a commitment is made, not after it breaks. And if you run a high-kindness, high-trust team and feel good about your culture, this one is especially for you.

What You'll Learn

• Why accountability is backward-looking by design — and why reliability is the architecture that prevents the miss before it happens
• The three conditions that define a reliable organization: commitment clarity, an early flagging norm, and design-focused post-mortems
• Why high-kindness, high-trust teams are often the most operationally unreliable — what kindness without rigor actually produces
• What commitment clarity requires in practice: what done looks like specifically, who owns it by name, and what dependencies must be named upfront
• Why the manager's reaction to an early flag either builds or destroys the norm — and why that single behavior matters more than any policy
• How the post-mortem is a CHRO moment — and the one question that shifts the room from defensiveness to analysis
• Five concrete plays you can run this week to start moving your organization from accountability to reliability

Key Quotes

"Accountability is the word that sounds serious without requiring whoever's speaking it to do anything about the system that produced the miss."

"A risk named six weeks before a deadline is a problem with options. The same risk named the day before is a crisis."

"Kindness without rigor produces social comfort and operational drift."

"The design question produces learning. The blame question produces protection."

Sources for Statistics Cited

• Global employee engagement at 23% — Gallup State of the Global Workplace 2024 Report (Gallup's 2025 report shows this has since dropped to 21%)

Transcript

Jackson: What is actually happening when a leader says the word accountability?

Scott: Honestly, they're naming a feeling — which is usually disappointment — because they're doing it at the wrong time. Somebody said they would do something and they didn't, and accountability is the word that sounds serious without requiring whoever's speaking it to do anything about the system that produced the miss.

Jackson: Hey there, senior leader, and welcome to the Talent Sherpa Podcast, where senior leaders come to rethink how human capital really works. I'm your host, Jackson Lynch, and today I am joined by my co-host, Scott Morris. He's a former CHRO with all the scar tissue to prove it. He's the alleged founder of the world's only accountability task force that was never actually held accountable for any of its results, and the founder of Propulsion AI.

Now, Scott, here is the one that I keep tripping over. Leaders say they have an accountability problem the same way they say they have a weather problem — loudly, repeatedly, and without any plan to change the climate. Most organizations have been chasing accountability for years. And the culture is no more reliable than when they started. I've been in C-suite meetings where someone drops the accountability word, and I can literally feel myself cringe. Not because the frustration behind it isn't real — it totally is. But because the word lands as a threat every single time. It points at people. It does not point at conditions, and the room knows it even if nobody says it.

Scott: It's one of my least favorite words. I love the underlying concept. I hate this word more than a lot of them. But before we dive in, do us a favor, folks — subscribe to the podcast, or leave us a comment, or drop us a quick review on your preferred platform. It's how we grow the pod, it's how we keep it sharp for senior leaders.

Jackson: Okay, let's dive in. Every CHRO has heard this one: we need to build a culture of accountability. Shows up on engagement surveys, on value slides, and post-mortems after a bad quarter. And it's not exactly wrong. The instinct behind it is real. Leaders want people to own their work and to follow through on their commitments. But Scott, I want to start with something that you and I talked about last week, because I think you named it better than I had. What is actually happening when a leader says the word accountability?

Scott: Honestly, they're naming a feeling — which is usually disappointment — because they're doing it at the wrong time. Somebody said they would do something and they didn't, and accountability is the word that sounds serious without requiring whoever's speaking it to do anything about the system that produced the miss.

Jackson: Right. And that's the trap, because accountability is almost entirely backward-looking. It points at the person. It asks, who owns the failure? Literally after it's already occurred.

Scott: And I've seen this run hot in a lot of organizations I've worked in. The leadership team declares accountability as a cultural priority — which is my other issue, connecting it to one of those vague words we use to mean everything, like culture. A new framework goes in, a dashboard maybe, a weekly check-in, and six months later, the same misses are happening. But now the team is also exhausted from the overhead.

Jackson: And Gallup's most recent State of the Global Workforce data puts global employee engagement at 23%. We've shared that number before. And it's barely moved in a decade — it's actually gone down, despite an enormous investment in culture and accountability programs. So something's not connecting. What is it?

Scott: What I think is not connecting is that we keep treating accountability as a declaration and expecting it to produce a different behavior. We're not addressing the system underneath. And here's what I think gets missed: the organizations that do what they say they do, reliably over time — they don't talk about accountability that much. They talk about commitments. They talk about whether they did what they said. The cultural norm is different.

Jackson: I think you hit it. That's the word — reliability. And it behaves completely differently from accountability in an organization. Accountability is, generally speaking, what you reach for after something breaks. Reliability is what you build so that fewer things break in the first place.

Scott: And when you frame it that way, the CHRO's job changes. You're not running a recovery operation. You're designing the conditions for success.

Jackson: It sounds great until you ask what those conditions actually are, Scott. And that's where I think most organizations end up — they don't go all the way. They stop. They like the framing, but they don't know what to build. It's kind of like what we talked about with empowerment last time.

Scott: Which, for the record — and it's why I hate the word — is how most cultural initiatives end up. They end up like a poster. They're less interested in the architecture.

Jackson: I think we're both guilty of that. I've actually commissioned the poster. I've approved the vendor who made the poster.

Scott: Okay, you win.

Jackson: Let's call out a few faulty assumptions that get leaders stuck. Here's the first: we have an accountability problem. No one actually says we have a clarity problem — but that's almost always what's really happening. The expectation lived in the leader's head and never made it out to the rest of the team. The assumption is that the team understood exactly what they were committed to — with what resources, by when, and to what standard — and chose not to do it anyway. But in reality, in most organizational misses, the commitment was never explicit enough to honor. And you can't hold people accountable for expectations that were never made specific. When you try, you produce defensiveness, not performance. People optimize for managing blame rather than delivering outcomes. That actually works against what you were going for by saying "accountability" to begin with.

Scott: Here's another one that I think a lot of us have heard: we just need people to own it. That's said as if ownership is some kind of character trait that some people have and others lack. But ownership is an environment. And that's why I hate the phrase "I'm going to hold you accountable" — because you can't. The faulty assumption here is that telling people they own something actually transfers authority to them, and that people who don't own it are choosing not to. That's a bad assumption. The reality is that most people who look like they're not owning the work are waiting to be overridden. They've learned from experience that ownership is provisional. Once that pattern exists, asking somebody to own something is like asking them to take on risk without any authority. That's not ownership — it's exposure.

Jackson: This one's going out to all the CHROs out there — I feel a little bit like Casey Kasem, but I think we've all heard this at some stage of our career, probably multiple times. We need stronger accountability systems. Then every time that gets said, a dashboard magically appears. And then another dashboard, and then a dashboard to track the dashboards. The problem is believed to be a visibility challenge — like no one knows who owns what, and if leaders could just see the commitments more clearly, they could reinforce them more consistently. We need a PMO to make sure everything is written down. That's nonsense. Most organizations don't have an information problem. They don't have a tracking problem. They have a conversational problem. Accountability infrastructure tells you what happened. It doesn't change what people do when something is going sideways — and that's where you need to focus.

Scott: And we use this word synonymously with consequences. "I'm going to hold you accountable" means I'm going to impose consequences. "In a high-trust culture, people will hold each other accountable" — that's one I've heard. It sounds more sophisticated, and I actually think it causes more damage. The nicest organizations are often the least reliable. It's not that consequences don't belong — it's that the system that delivers clarity rules. The faulty assumption is that trust and accountability reinforce each other, and that if people genuinely care about one another and the mission, they will name broken commitments directly. But the reality is that kindness without rigor produces social comfort and operational drift. Nobody's the bad guy, and nothing gets fixed, and the miss becomes the new normal. Reliability requires somebody to say, "You said you would do this and you didn't" — and that person understood what they were supposed to deliver on. In a high-kindness culture, that sentence kind of disappears.

That last one, Jackson, is the one I keep coming back to — because I've been in rooms like you have where everyone liked each other, everyone trusted each other, and they genuinely wanted the organization to succeed. And they were completely unable to, because no one would name the thing that needed naming.

Jackson: Yeah, and we talk a lot about psychological safety. I think you just really hit on it. Psychological safety, as I define it, is the ability to put a very uncomfortable truth on the table and still feel like you belong to the team. What's one of the most important psychological truths you can put on the table? That you didn't live up to the commitment you made. Accountability as a cultural target sounds like it has rigor — and it really doesn't. It's about blame. Reliability is about something completely different. It's about whether the system is designed to keep those commitments. And designing that system requires a completely different set of questions entirely.

Scott: I think that's 100% right. And just to be painfully clear with everybody — we're not saying consequences are bad, and we're not saying we don't want people to deliver. We're just saying we're going about it wrong. So let's reframe this. How do we move from accountability as a cultural aspiration to reliability as a system? I think you landed on a framework for this that we should walk through. Three conditions — you and I refer to it as the reliability architecture. The premise: if all three aren't in place, then the word "accountable" is trying to do work it can't do.

Jackson: I want to flag something before we get too far in. This is not a feel-good reframe. These three conditions require a manager to do real work — probably work they've been avoiding. Do it up front, before the commitment is made. This is not soft. This is actually harder work.

Scott: And it's not complex either — difficult, but the concepts are straightforward. The empowerment parallel is exactly the same. The same prep work that makes empowerment feel real is the same work that makes reliability possible. You can't skip it and then be surprised when the system doesn't hold.

The first condition is commitment clarity. Before any significant commitment is made in your organization, three things need to be explicit: what done looks like — specifically and measurably — who owns it by name, not by function, and what resources and dependencies that person needs to actually deliver. Most organizations, in my experience, do one of those three, but not all three. They name the owner, but they rarely name what done looks like with specificity. And they almost never name the dependencies.

Jackson: And I think that dependency piece is where so much of the downstream failure starts. Someone commits to delivering something by a date, and no one figures out that the delivery requires three other functions to act first. Those functions have their own jobs and competing priorities, and the conversation never actually happens. The deadline arrives, the commitment misses, and the person named as the owner gets the accountability conversation. But they weren't actually the constraint.

Scott: How do you get your leadership team to actually do the work? Because I've seen it resisted in every organizational context I've worked in. It feels bureaucratic, it slows things down. How do you get them to do it?

Jackson: The only thing that works in my experience is making it a norm before something breaks — not a tool you introduce after failure. If you introduce commitment clarity after a miss, it feels punitive. If you do it up front, it feels like due diligence. The timing is everything.

So let's move on to the second condition — I think of it as the early flagging norm. In any accountability culture, flagging early feels like you've admitted to failure. You made the commitment, and then you flagged it before the deadline — which means you're no longer owning it. So people tend to keep their head down and keep trying, right up until the deadline, at which point the miss is a crisis.

Scott: And the cost of late disclosure is big. A risk named six weeks before a deadline is a problem with options. The same risk named the day before is a crisis, and you have no options.

Jackson: So the cultural shift is: flagging early is what reliable people do. It's not a sign of failure — it's a sign of reliability. The person who says, "This commitment is at risk, here's why, and here's what I need to protect it" — that person is actually being more reliable than the person who stays quiet and then misses the deadline clean.

Scott: And it requires the manager not to react to a flag the way most managers do — with visible disappointment, by jumping in to fix it, or by immediately reassigning the work. All of those reactions teach people not to bring risks to the table early.

Jackson: The manager's behavior in response to an early flag is literally as important as the norm itself. If you protect the person who flags, you're going to get more flagging. If you punish them — even subtly, because they're going to be watching for it — you're going to get silence right up until the deadline. So you have to decide: do you want to hear about it while you still have time to fix it, or at the last minute when you're stuck?

Scott: And flagging is accountability. It's them saying, "This is important to me. I own this. I want to raise this as a risk." Lest anybody thinks we're criticizing others — I certainly have been the manager who reacted badly to a flag. I didn't think I was doing it at the time, but the person read my face, and I watched them stop raising things that were problematic. I didn't connect those two things until much later.

Jackson: Yeah. I unfortunately have a rather expressive face — when I get frustrated with something, it shows. I can say all the right things, have my 68-beats-per-minute heart rate, but my expression gives it away. So we're not standing outside the pattern — that's what we're trying to say. First step is admitting you have a problem.

Scott: Let me push us to the third condition: response by design, not by blame. That third condition changes what happens after something goes wrong. In an accountability culture, when a commitment breaks down, the first question is usually, "Who owned this?" That question is useful. But in most organizations, it's the only question — which means the learning stops at the person.

Jackson: The reliability question is different. It's: what about the way this commitment was made produced a fragile outcome? Were the dependencies named? Was there a flag that didn't get heard in time? The question points at the design rather than the person. And the answer is where you find the actual lever that caused the problem.

Scott: This is where CHROs can have an enormous structural influence — because the post-mortem is a CHRO moment. Who facilitates it, what questions get asked, what the organization learns from it — that's a design choice. A CHRO who consistently introduces the design question alongside the ownership question is gradually shifting the cultural model of what went wrong.

Jackson: There is a risk it might feel like you're letting people off the hook. But here's what I've found: the people who are genuinely responsible take more ownership, not less, when the question is design-oriented — because they're not defensive. They can think clearly about what actually happened. That's what you're going for.

Scott: The design question produces learning. The blame question produces protection.

Jackson: So the real question for CHROs is: are you willing to introduce that question at your own leadership table? Because it's going to feel uncomfortable the first time, probably the second time, probably the tenth time. Because you're asking your peers to examine the system they literally built themselves. That's a different kind of conversation than most post-mortems produce.

So let's talk about how a CHRO can start this week.

Play number one: run the commitment clarity diagnostic on one active initiative. Pick something currently in flight that's at risk. Write down what done was supposed to look like, who was named as the owner, and what dependencies were required. Then ask the owner to do the same exercise independently. Compare the two documents. The gaps are where the reliability failure lives. It's a design problem, not a people problem.

Scott: What I like about that is where it moves you — from thinking about accountability as consequences, to thinking about how you set the situation up so people can be reliable. Here's another play: change one post-mortem question. In your next post-mortem after a miss, add one question that might not be on your standard agenda: what about the way this commitment was made made it fragile? You don't have to replace the ownership conversation — run it alongside. Introduce the design question and watch what happens. You'll see people stop defending and start analyzing.

Jackson: Play number three: name the next early flag publicly. The next time someone on your team flags a risk before a deadline, name it out loud in a room that matters and reinforce it. "This is exactly what we want. This is what reliability looks like. Flagging it early gave us options. Thank you." That one moment does more for the early flagging norm than any policy you could ever write.

Scott: Publicly praise the behavior you want. Play number four: find a leader on your team and have the commitment clarity conversation. Pick one person on your direct team and ask them: what are the three important commitments they're carrying right now? Then ask them to define what done looks like for each one. You will almost certainly find that the definitions are vague, the dependencies are unnamed, and the resources are assumed rather than confirmed. That conversation is the work.

And a fifth play: replace the word accountability in one important meeting. In your next leadership meeting where someone uses the word accountability as a cultural aspiration, replace it with reliability. Say, "I want to make sure we're building for reliability here." Then ask about the conditions: what needs to be true for that commitment to hold? Accountability asks who's responsible. Reliability asks what needs to be true for us to get to success. Those are really different conversations.

Jackson: They are. And the last one — fair warning — it's going to feel awkward. Because you're reframing a word that's probably been in your culture for years, maybe even decades. Some people are going to push back. Someone's going to say, "But accountability is important." And they're totally right. The word isn't the enemy. The application of the word is. The question is whether you're willing to have the conversation that moves the culture from blame to design. Candidly, I don't think you can do it while continuing to call it accountability. It has too much baggage. And a lot of people who listen to this may not feel comfortable doing it, because it requires them to implicate themselves in the system they've been running. Just like us. They probably use the word. That's uncomfortable. But it's the only thing that's actually going to change the culture. So you've got to do it anyway.

All right, senior leaders. We're at the best part of the whole show, which is when Scott talks about the things that he says. So here is your Talent Sherpa summary. Or as Scott always says, "If you want stronger accountability, just post it on a banner in the break room and wait for the transformation."

Scott: I've never said that and I never will say that. Please don't do that. Here's what I want you to take from today.

Jackson: One: accountability is backward-looking. It names what went wrong and who owns it. That's useful, but it doesn't change the conditions that produced the miss. If improvement is your goal, focus on reliability. Reliability is forward-looking — it asks what needs to be true before a commitment is made.

Two: high-kindness cultures are the most vulnerable to reliability failure. When the relationship feels too important to risk, nobody wants to name the broken commitment. That paralyzes progress. Kindness without rigor creates drift, and drift looks like an accountability problem when the root cause is the absence of an honest conversation.

Three: the three conditions that produce reliable organizations are commitment clarity, an early flagging norm, and a response culture that asks design questions after a miss rather than only blame questions.

Four — and the last one: the CHRO can drive this shift. It might be uncomfortable, but you can do it. The post-mortem is a CHRO moment. The flagging norm is a CHRO moment. The commitment clarity conversation is a CHRO moment. This is not soft culture work. This is systems design, and it directly affects execution velocity and organizational risk.

Scott: I think that's right. And to be fair, it took me years to understand this cleanly — I'm not sure I could have named it before I lived on both sides of it. I spent years watching organizations chase accountability and end up more frustrated, not less. The reason is that accountability is the name we give the symptom. Reliability is the system underneath it. If your organization keeps having accountability problems, stop adding more accountability infrastructure. You're fixing the fever, not the disease. Start asking what the design failures were, because the miss was downstream of something. Find that something.

That's all for today. Thank you so much for tuning into the Talent Sherpa Podcast, where senior leaders come to rethink how human capital really works. A quick shout-out to one of our favorite listeners — hello, Diana in Fairfax, Virginia. Thank you for being part of the Talent Sherpa community. And thanks to everyone who's been listening, whether that's in Escondido, California, or Dublin, Ireland — one of my all-time favorites. It is so great to have all of you with us.

Jackson: If you liked today's episode, do us a favor right now and subscribe to the podcast, or hit the like button, or leave us a review on your favorite platform — whether that's Apple Podcasts, Spotify, or YouTube. That's what activates the algorithm and helps us spread this content to other senior leaders. It's free to you, it'd be really helpful to us, and you might just create a benefit for somebody else.

Scott: And if you're a CHRO wondering where to start your AI journey, don't forget to check out Propulsion AI at getpropulsion.ai. They're building a team of AI teammates to help human capital leaders focus on what matters to the business.

Jackson: Scott, what are you doing? What are you helping people with?

Scott: One word, Jackson — clarity. Our AI teammates coach managers, working directly with their human colleagues to build clarity across a variety of talent management subjects. And don't forget, if you're an early-stage CHRO new to your role, Jackson has helped a lot of people just like you through personal coaching or through his best-selling Substack. You can find all of those at mytalentsherpa.com.

Jackson: And if you're a CEO trying to figure out how to create a high-altitude human capital organization, I can help you with that as well — it's not limited to working directly with CHROs. Thank you, Scott. And thanks to everyone listening. Until next time — keep raising the bar. Keep building the conditions before the commitment. And keep on climbing.