Responsibility identifies the part you own; accountability adds an agreed explanation and evidence to someone or to a record. You can own a task without a formal reporting arrangement, and you can report honestly while still needing to repair it.

Compare the operations, not a score

Question or fieldFictional completed example
Owned task?Budget update
Reporting agreement?Tuesday meeting
Evidence?Updated figures with assumptions
Unfinished part?Supplier quote
Repair?Request and flag the missing quote

A worked situation: Budget update

Fictional example. A team member owns the budget update and reports its status at a meeting. Ownership concerns completing the update; accountability concerns showing what is done and explaining the unresolved assumption.

Separate doing from reporting

Responsibility names the task you own; accountability adds an agreement about explaining progress and results. A person can own a task without a formal check-in, and a check-in does not complete the task. Record the deliverable and reporting agreement separately. When a dependency blocks delivery, the update should identify it and the requested decision.

The relevant book lens: Look at the Scoreboard

Where the comparison stops

Related reading