Accountable vs Responsible

Alex Ewerlöf treated responsibility and accountability as synonyms until readers pushed back on his “ownership trio” framework, which asks for mandate, knowledge, and full responsibility for consequences. The two words turn out to carry a real distinction, one that matters less for day-to-day team ownership than for role definitions, legal liability, and military command structures.

He works through several framings: the RACI matrix, where Accountable can only be one person who signs off on work the Responsible party does; the legal sense, where responsibility is a factual cause/effect relationship while accountability (liability) carries punishment; and the military sense, where accountability means both positive and negative consequences tied to a chain of command.

Fichamento

#

• His core claim is that most organizations don’t need to separate accountability from responsibility; when they insist on the split, it usually signals a deeper cultural problem rather than a terminology gap.
• He lists the people who tend to push for the separation: managers who want unilateral control, upper management looking for someone to blame without understanding the details, and team members avoiding consequences for their own actions.
• Legitimate reasons to separate the two include contexts where legal consequences are real (bankruptcy, military command, parent-child liability) or where a “head” role concentrates thinking while a “body” merely executes.
• In his own ownership trio, he treats accountability as embedded inside responsibility and mandate: a team with the mandate to improve its service is also responsible for measuring it from the consumer’s perspective and for mitigating threats to that commitment.
• He credits incidents and on-call pain, not legal exposure, as the actual mechanism that pushes healthy teams to grow their knowledge and use their mandate well.
• He cites Gitte Frederiksen’s TED talk on network-based leadership as a companion argument: a hierarchy that routes decisions through one person creates a bottleneck and misses ideas distributed across the organization.