By Andreas Pettersson, Founder, Leaders ADAPT
The task came back. You handed the vendor review to two capable people on Monday. It's Friday, and it's on your desk again with a note: "Wasn't sure who was making the final call." Nobody did anything wrong. Nobody was accountable either.
That gap is the whole responsibility vs accountability question, and most definitions stop one sentence short of it. Here's the missing sentence: responsibility is for doing the work, accountability is for answering for the result, and accountability belongs to exactly one name. The Accountability Protocol in The 5-Minute Leader is what I wrote down after scaling Arcules to 150+ employees and living through more than one Friday like that one.
Quick answer: Responsibility is the obligation to do the work; accountability is the obligation to answer for the result. Responsibility can be shared among several people and can be delegated. Accountability sits with one person and is assigned rather than delegated: the accountable person can hand off tasks but still answers for the outcome. In RACI, several people can be Responsible, but only one is Accountable.
What is the difference between responsibility and accountability?
Both words point at an obligation. They point at different moments.
Responsibility is the obligation to carry out a task or a piece of work, and it can be held by several people at once and handed from one person to another.
Accountability is the obligation of one named person to answer for an outcome, including the parts of the work that other people did.
Responsibility lives before and during the work. Accountability lives after it, when the result exists and someone has to explain it, defend it, or fix it.
Back to the vendor review. Two people were responsible and both did their part. When the recommendation needed a final call, each assumed the other had it. That is the difference between accountability and responsibility, seen from the desk it lands on.
Why the difference shows up the week after the handoff
Here's the problem. Most delegation transfers responsibility and quietly keeps accountability with the leader. You hand someone "send the report to the board," they send it, and the board still calls you, because you never handed over the outcome. As I put it in The 5-Minute Leader: when you delegate tasks, people remain waiters taking your order; when you delegate outcomes, they become owners building something.
The failure has a twin on the authority side. Handing down responsibility while keeping authority produces a role in name only. I see it constantly in owner-run companies somewhere between $1.5M and $3M in revenue: a "head of operations" who is responsible for delivery and can't approve a purchase without asking.
Ambiguous authority kills ownership.
So the Delegation Protocol names three things in the handoff: the outcome, the single owner, and the authority level. Level 1, decide and tell me after; Level 2, decide but tell me before you implement; Level 3, recommend options and I decide. Saying the level out loud is what turns a responsible person into an accountable one.
When handoffs boomerang, the pattern has a name and a script: reverse delegation. The full method sits in the delegation training guide.
Responsibility vs accountability vs ownership: the comparison table
Three words, three different jobs.
Ownership is accountability that the person has taken on from the inside, so they act on the outcome before anyone asks them to.
| Responsibility | Accountability | Ownership | |
|---|---|---|---|
| What it covers | The task or the work | The outcome, including others' work | The outcome, held voluntarily |
| How many people | Several at once | One person per outcome | One person, self-selected |
| Can it be delegated? | Yes | No; it is assigned, and the assigner still answers upward | No; it can only be invited by delegating outcomes and authority |
| When it is tested | During the work | When the result exists | Before anyone checks |
| What it sounds like | "I did my part." | "I answer for this." | "I already handled it." |
| RACI letter | R | A | Not a RACI role |
Ownership vs accountability is a question of direction: accountability is placed on a person from outside, ownership is the same obligation held from inside.
How does RACI separate responsible from accountable?
Responsible does the work, and can be several people. Accountable owns the outcome, and is one person only. Consulted gives input before the decision, two way. Informed is told after, one way.
The rule: one A, or none. Every project disaster I've watched up close came from multiple people believing they were the A. Co-ownership is non-ownership.
Three triggers tell you to draw the chart: any project with more than three people, anything that crosses a team boundary, and any work where you've heard "I thought they were handling that." For a whole company, the accountability chart template puts one name in every seat.
Can accountability be delegated?
No. You can delegate responsibility, and you can hand an entire outcome to a new accountable owner. What you can't do is stop being answerable for it yourself.
Think of it as a chain, not a transfer. Your head of sales is accountable to you for the quarter, and you remain accountable to the board for it. Assigning an accountable person one level down doesn't remove you from the level above.
So the handoff needs verification, not a nod. The Delegation Protocol closes with three questions: can you repeat back what I just asked, what's your understanding of why this matters, are you fully committed to making this happen. A head nod is not comprehension.
To see where your own handoffs leak, the free delegation assessment scores exactly that.
Can two people be accountable for the same outcome?
No, and the vendor review is the proof.
Shared responsibility is healthy. Shared accountability is a gap with a polite name. When two people "co-own" an outcome, each has a reasonable story for why the other had the final call, and both stories are true.
The fix isn't to pick a favorite. Split the outcome: one person is accountable for the vendor shortlist by Wednesday, the other for the recommendation by Friday. Two outcomes, two A's, zero overlap. If it truly can't be split, it has one owner and one contributor, and you say which is which in the room.
What does accountability look like in a meeting?
It sounds like one person saying "I do" in under two seconds. Here's the test I use.
The one line test. In the meeting where the work is assigned, ask: "Who answers for this on Friday?" One person says "I do" without looking around: accountable. Two people look at each other: nobody is accountable, whatever the plan says. Someone answers "we": ask again until you get a name.
The pronoun is the fastest diagnostic, and I said this to a client reviewing a director's written plan: is he using the word I? No, he's using we, and how can a one person function say we? Take your ownership.
The second tell is verb choice. "I'll try to" is not a commitment, and neither is "hopefully" or "should be done by." In the Accountability Protocol these get replaced on the spot: "I will," "I commit to," "will be done by," and "I will, or I'll tell you now that I can't." Fuzzy language creates fuzzy accountability.
The third tell shows up after the miss. "I was waiting for." "Nobody told me." "The timeline was unrealistic."
Those are reasons, and reasons aren't results. The conversation after a miss has a script, covered in how to hold employees accountable, and it belongs in the alignment close of your one-on-one meetings: what are you committing to before we meet again. They state it, they own it.
The number that taught me the difference
At Arcules I kept a technically brilliant engineering manager on the team for three months longer than I should have. He shipped. Every deliverable he was responsible for landed. His team turned over at 20 percent a year, and I avoided the conversation because he was too valuable to upset.
He had met every responsibility I'd given him. Nobody, including me, had made him accountable for the outcome that mattered: a team that stayed.
I finally put a number on it, roughly $450K a year in turnover and morale damage, and had the conversation about three specific behaviors: interrupting in meetings, dismissing ideas without considering them, and critical emails at midnight expecting a reply. The behavior changed. Turnover on his team dropped from 20 percent to 8.
The lesson wasn't about him. Responsibility without accountability is invisible from the top, because the work keeps getting done.
I built Arcules to 150+ people and cut my own week from 60 hours to 45 along the way. Being one of Canon's youngest CEOs taught me less about accountability than that one conversation did.
If you want to see the gap in numbers, the accountability statistics page puts the 2026 Gallup ratings of leaders and managers side by side. What happens once one name sits on every outcome is the subject of building a culture of accountability, and the handoff itself, from the first brief to the week after, is mapped in how to delegate so the work stays delegated.
Responsibility vs Accountability FAQ
What is the difference between responsible and accountable?
Responsible describes the person or people who carry out the work. Accountable describes the single person who answers for the result of that work, including the parts done by others. Several people can be responsible for one outcome; only one is accountable for it. Responsible vs accountable is doing versus answering: responsibility is tested while the work happens, accountability when the result exists.
Is accountability the same as ownership?
No. Accountability is assigned from outside: a leader names one person who answers for an outcome. Ownership is the same obligation held from inside: the person treats the outcome as theirs and acts before being asked. A person can be accountable without feeling ownership, which produces compliance. Leaders assign accountability and invite ownership by delegating outcomes and matching authority to them.
Who is accountable when a task is delegated?
The person who delegated it remains accountable upward, and the person who received it becomes accountable to the delegator for the outcome, if an outcome and authority were handed over. If only a task was handed over, the receiver is responsible and the delegator still answers for the result. Delegation creates a chain of accountability; it never removes the delegator from the level above.
Can accountability be shared between two people?
Not for a single outcome. When two people are accountable for the same result, each can reasonably assume the other has the final decision, and the outcome ends up with no owner. Shared responsibility for the work is normal and useful. Shared accountability is resolved by splitting the outcome into parts with one accountable person each, or by naming one owner and one contributor.
How does RACI define responsible and accountable?
A RACI chart makes the responsibility vs accountability split explicit. Responsible marks the people who do the work, and there can be several; Accountable marks the one person who owns the outcome and signs off on it, exactly one per deliverable. Consulted marks people whose input is sought before decisions, Informed marks people told afterward, and the chart fails when a row has two A's or none.
What is the difference between accountability and consequence?
Accountability is the standing obligation to answer for an outcome. A consequence is what follows when the outcome is missed or met: a correction, a changed scope, a reward, or removal from the role. Accountability exists before any result and does not depend on punishment. Consequences are one way it is enforced; a person can be fully accountable in a culture that relies on feedback and correction rather than penalties.
One name on Friday
One habit covers all of it: never let an outcome leave a meeting without one name attached, and say the name out loud.
You already know which outcome on your plate this week has two names on it, or none. If you've been putting off the accountability vs responsibility conversation because it might feel like blame, that fear has a fix too, in accountability without blame.
So ask the question at your next meeting. Who answers for this on Friday? Then count the seconds before someone says "I do."
When the answer to "who answers for this" is always you
If every outcome in your company traces back to your name, you don't have an accountability problem. You have a delegation problem that shows up as one. Responsibility vs accountability is the vocabulary; the fix is a sequence.
The 5-Minute Leader runs four protocols in order, one week each. The Delegation Protocol moves outcomes, single owners, and authority levels off your desk in a three minute conversation. The 1:1 Protocol turns your weekly meetings into the place where you learn whether the handoff landed. The Accountability Protocol gives you the warm but firm script for the three conversations you've been avoiding, and the Rhythm Protocol makes it all repeat without you chasing it.
Part 2 adds a fifteen minute Friday review that takes no status updates at all; how it manages that, I'll leave for the book.
If the vendor review is on your desk again, start with The 5-Minute Leader. One week per protocol. The first thing you'll notice is how many outcomes finally have a name.
