Most leaders treat accountability as a character trait. Someone either has it or they do not, and the ones who do not are a hiring mistake you are stuck with until you are not.
That is a comfortable way to think about it, because it means the problem is the person and not the system. It is also wrong, and it is expensive.
Accountability is a learned skill. The language of accountability is no different than becoming an excellent writer or an excellent public speaker. Nobody is born doing it well. People get good at it the same way they get good at anything, which is by being taught what it looks like and then practicing it where somebody can see. It is part of your operating system as a company, and like everything else in your operating system, if you did not build it on purpose you got one by accident.
I gave a version of this talk at RockBox in September 2025, and it is the talk I have delivered more than any other. The reason is not that accountability is a fashionable topic. It is that every room has the same problem, and almost every room has misdiagnosed it.
The problem is almost never the person
When a leader tells me they have an accountability problem, I ask them to walk me through the last thing that got missed. Not the pattern. One specific miss, with a name and a date.
What comes back, nearly every time, is a story with a hole in it. The ask was vague, or it was clear in the leader’s head and abbreviated out loud. The owner was implied rather than named. The deadline was “end of the month” or “soon” or, my favorite, “as soon as you can”. And nobody else in the room heard the commitment get made, so there was no moment where the person said yes in front of witnesses.
Then the thing gets missed, and the leader concludes they have a people problem.
You do not have a people problem. You have a clarity problem wearing a people problem’s clothes.
Clarity is four things, and you need all four
Here is what a real ask contains. Miss any one of these and you have not delegated anything, you have expressed a hope.
What exactly is to be completed. Paint the picture, in detail. Not the topic, the finished thing. If you cannot describe what done looks like, the person doing it certainly cannot.
Who specifically is responsible. One name. Not a team, not a department, not “you guys”. Shared ownership is the most reliable way to guarantee something does not happen, because everyone can see someone else who could have picked it up.
By when, with an exact date and time. No wiggle room. “End of the week” is four different deadlines depending on who is doing the hearing.
Shared, so there is no confusion. Everyone in the room knows who has it. The commitment gets made out loud, in front of the people it affects. That is not theater. That is the part that makes it real.
Four things. Most leaders do one and a half of them and then wonder why the work does not land.
The only three outcomes of a commitment
Once the ask is clear, a commitment has exactly three legitimate outcomes. Not ten values on a wall. Three.
- Execute as expected.
- Ask for more time, in advance.
- Ask for more resources, in advance.
That is the whole contract. What is missing from that list is the thing that breaks companies, which is showing up on the due date with an explanation. An explanation after the fact is not accountability, it is narration.
Notice what options two and three do. They make it safe to be honest early. A person who tells you on Tuesday that Friday is not going to happen has given you three days to do something about it. A person who tells you on Friday has given you a problem and a feeling. If your culture punishes the Tuesday conversation, you have trained everyone to save it for Friday, and then you have to live with that.
The expectation is execution.
And this is the line that decides whether any of it works: accountability rests on the person who accepts responsibility. Not the person who assigns it. The moment of acceptance is the moment ownership transfers, which is exactly why the ask has to be clear enough to accept and public enough to be witnessed.
What has to be true around it
The contract only holds if four conditions are in place, and all four are the leader’s job to build.
Clarity, which we just covered, and which is upstream of everything else.
Tools and resources. Holding someone accountable for an outcome they were never equipped to produce is not accountability. It is setting a trap and calling it a standard.
A platform of transparency. The score has to be visible to the people playing. Accountability without a shared scoreboard is just your opinion of how things are going, delivered at a frequency you choose.
Regular meetings. Not more meetings. Regular ones, with a rhythm people can count on, where commitments get made and revisited on a predictable cadence. Accountability that only shows up when something has already gone wrong is not a system, it is a reaction.
The hard conversation you are avoiding
Everything above is a system, and a system does not survive contact with the first person who misses and does not want to talk about it. That conversation is where most accountability programs quietly die.
The way through it is Positive Constructive Conflict. It is a principle I run inside every executive team I work with, and it says this: people should have such high trust, such unique ideas, and be so committed to tackling the problems for the company, that they are willing to vigorously debate and discuss lots of different ways of doing it. From the outside it can look like people are not getting along. It is the healthiest dialogue in the building, because it is happening in the room instead of in the parking lot afterward.
Three things make it work.
Trust comes first. Inside a team that trusts each other’s intent, conflict is stress-testing. Without that trust, the same conversation is an attack. You cannot skip to the debate.
The conflict happens in the room, not after it. Visible disagreement during the meeting is health. Visible agreement during the meeting followed by disagreement in the hallway is dysfunction. Your job as the leader is to surface it while everyone is still sitting down.
Disagree and commit. Once the decision is made, everyone leaves as a unified front. Going to a third party afterward to relitigate it is the actual betrayal, and it is far more common than open disagreement.
When the tension shows up, run it in the open. Name it out loud: there is tension in the room on this, let us surface it. Let each side make its case with the claim, the evidence, and the impact. Then have each person restate the opposing view well enough that the other one says yes, that is what I mean. Then decide, either by agreement or by whoever holds the decision rights. Then move on, and do not let it live past the meeting.
That last part is the discipline. Not the debate. The ending.
Ownership is a mindset, and you are hiring for it
There is a spectrum in every company between the person who narrates why things will not work and the person who believes the thing can be done and goes at it. Eeyore and Buzz Lightyear, if you want the shorthand I use on stage.
The uncomfortable part: if you actually implement this, some of the people who are with you today will not be with you in a year. That is not a threat and it is not a purge. It is what happens when a standard becomes real. Some people have been succeeding in the ambiguity, and clarity takes that away.
Hire for the mindset. You can teach the skill. That is the whole point of calling it a skill.
What to do Monday
Take the last thing that got missed. Write down the ask as it was actually made, not as you remember making it. Check it against the four: what exactly, who specifically, by when to the hour, shared out loud.
You will find the hole. It is almost always in “by when” or in “shared”.
Then go make the same ask again, properly, and watch what happens. Do not announce a new accountability initiative. Just make one clear ask and hold the standard on it. The culture is built one ask at a time, which is slower than a program and the only thing that actually works.
—
Positive Constructive Conflict gets a full episode of the podcast: How A Positive Constructive Conflict Signals A Healthy Company. I give this as a keynote and as a half-day workshop. If your room needs it, start at Speaking.