Skip to content
Better Decision Making
Module 7 of 9

Accountability Is Not a Letter

9 minutes · Beginner

Learning objective

By the end of this lesson, you can assign an Accountable role only where a real acceptance or decision mechanism exists.

Why it matters

Adding A to a cell does not create budget, delegation, competence or risk authority. A false assignment can make a chart look complete while the real decision remains unresolved.

Core concept: outcome, authority, rehearsal

For every important row:

  1. write an observable deliverable or decision;
  2. assign who performs the work (R);
  3. identify who can accept the result or decide (A);
  4. verify that authority against policy or operating agreement;
  5. define necessary input before (C) and information after (I);
  6. rehearse a normal case and an exception.

If no role has authority, escalate. Do not invent A to satisfy a formatting rule.

Visual explanation

Worked example

Five teams are asked to “jointly approve” an AI service-desk launch. The group separates security acceptance, legal acceptance and the service release into distinct decision rows. Each has the role required by policy. Operations and IT prepare evidence; specialists are consulted where they do not own the decision.

The matrix exposes one gap: nobody holds service-release authority for this product. The sponsor resolves the delegation before launch.

Common mistake

Mistake: several A assignments used as a symbol of collaboration.

Collaboration can involve many R and C roles. Accountability needs a clear acceptance mechanism or an explicit joint-decision rule outside the cell.

Quick check

A row has no role authorised to accept the result. What should happen?

A. Give A to the most senior attendee.
B. Escalate and resolve the authority gap.
C. Mark everyone A.
D. Remove the row.

Answer: B. RACI reveals the problem but cannot create delegation.

Practical prompt

Take one stalled approval. Rewrite it as an observable decision, name R and the proposed A, then cite the delegation or escalation path that validates A.

Summary

  • Rows are outcomes or decisions, not topics.
  • R does work; A accepts or decides.
  • Authority must exist outside the chart.
  • Scenario rehearsal exposes hidden gaps.

Next lesson

Use Decision Matrix for auditable option comparison, then record the authorised decision and conditions in a decision log.

Next step

Premortem: Make Dissent Usable Before Launch

Continue