Responsibility Accounting Matrix¶
Mapping template — instantiates Conservation Accounting
Maps every duty, risk, and obligation from its old owner to a named new owner across a reorganization, so responsibility relocates rather than evaporating in the gap between roles.
A Responsibility Accounting Matrix conserves a quantity that has no meter: obligation. When a team is dissolved, a function is outsourced, or a workflow is automated, the duties it carried do not automatically move — they can simply fall into the gap between the old owner and the new one, and become nobody's job until something breaks. The matrix treats every duty, risk, and maintenance obligation as a conserved unit that must have an owner before and after the change, and lays them side by side in a before/after table so that each old-state responsibility either points to a named new owner or is explicitly, deliberately retired. Its whole discipline is that an obligation with no destination is not a loose end to sort out later but an orphan — a duty with no owner — surfaced at the moment of transition rather than discovered in the incident report months on.
Example¶
A mid-size company outsources its internal IT helpdesk to a managed-service vendor and plans to dissolve the in-house team. The matrix is the template that keeps duties from vanishing in the handover. Down the rows go every responsibility the in-house team actually held — not just "answer tickets," but the quiet ones: renewing the SSL certificates, holding the master password vault, being the escalation contact when the badge system fails at 2 a.m., maintaining the runbook for the legacy payroll integration. Each row's "before" owner is the departing team; each "after" owner must be filled in. Most map cleanly to the vendor. But three do not: the vendor's contract explicitly excludes the legacy payroll integration, nobody has agreed to own the certificate renewals, and the after-hours badge escalation has no named contact once the team is gone. Those three are the orphaned obligations — and the matrix has surfaced them before the team's last day, while there is still someone to ask, rather than after, when a lapsed certificate takes down a customer login and the post-mortem discovers the duty was silently dropped in the reorg. Where a duty is genuinely being retired, the matrix says so on the record, with the assumption that justified it.
How it works¶
- Enumerate obligations, not roles. The rows are concrete duties, risks, and standing commitments — including the tacit ones — rather than job titles, because titles move while duties hide.
- Pair before-owner with after-owner. Each obligation carries its old owner and must be assigned a named new owner; the two columns are the transfer record for that duty.
- Treat a blank after-column as an orphan. An obligation with no new owner is an orphaned obligation, raised for resolution before the change completes.
- Log the scope assumptions. Duties assumed to be handled elsewhere, out of scope, or deliberately retired are recorded with the assumption that justifies excluding them — so the exclusions can be challenged.
Tuning parameters¶
- Obligation granularity — coarse ("run the helpdesk") or fine ("renew certificate X by date Y"). Fine granularity catches the buried duties but produces a large, high-maintenance matrix.
- Coverage horizon — only active duties, or also dormant and contingent ones (disaster response, rare escalations). Wider horizon catches the 2 a.m. duties that surface rarely but hurt most.
- Owner specificity — a named individual, a role, or a team. Naming an individual removes ambiguity but ages fast as people move; naming a role is durable but can diffuse.
- Sign-off requirement — whether each new owner must explicitly accept the duty. Required acceptance prevents assignment-without-consent but slows the reorg.
- Assumption strictness — how much justification an "out of scope" exclusion needs. Strict logging catches convenient omissions; loose logging is faster but reopens the evaporation risk.
When it helps, and when it misleads¶
Its strength is that it makes responsibility conserved on paper at the exact moment it is most likely to leak — the handoff — by forcing every duty to name a destination or be explicitly retired.[n1] It is most valuable for the tacit, low-frequency obligations that no process diagram captures and that surface only in a crisis.
Its failure mode is that a filled-in cell is a claim, not a fact: writing a vendor's name next to a duty does not mean the vendor has agreed to it, is capable of it, or even knows about it. Its classic misuse is the reorg-theater matrix, completed to satisfy a governance checkbox, where every after-column has a name and none of the named owners has accepted — responsibility looks conserved while actually being assigned by fiat to people who will disown it the first time it bites. The discipline is to require explicit acceptance from each new owner and to log every "handled elsewhere" assumption so the convenient exclusions stay visible and challengeable rather than becoming silent orphans.
How it implements the components¶
transfer_path— each obligation's before-owner-to-after-owner pairing is the transfer record showing where the duty went.initial_and_terminal_state— the before-org and after-org columns anchor the comparison, so a duty present before must be located after.accountability_owner— the matrix's core output: every conserved obligation resolves to a named owner, or is explicitly retired.boundary_assumption_log— duties excluded as out-of-scope or handled elsewhere are recorded with their justifying assumption, keeping the exclusions open to challenge.
It does not count a measurable stock against a record or flag a numeric discrepancy (reconciliation_rule, variance_or_leakage_signal) — those fit metered quantities and belong to Inventory Reconciliation and Variance Report; a duty is not measured but either owned or orphaned, so the matrix conserves it by assignment rather than by tally.
Related¶
- Instantiates: Conservation Accounting — the organizational instantiation that conserves obligations across a reorganization.
- Sibling mechanisms: Energy Accounting · Financial Ledger · Inventory Reconciliation · Quota or Credit Ledger · Variance Report · Mass Balance · Chain-of-Custody Record · Data Lineage Map
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Responsibility Accounting Matrix operates as a static representation, map, specification, schema, or prospective plan that externalizes information because it maps every duty, risk, and obligation from its old owner to a named new owner across a reorganization, so responsibility relocates rather than evaporating in the gap between roles.
Independent corroboration: The frozen evidence defines Responsibility Accounting Matrix as 'Maps every duty, risk, and obligation from its old owner to a named new owner across a reorganization, so responsibility relocates rather than evaporating in the gap between roles', so its operative form is Representation, Specification & Plan.
Nearest alternative: Organization, Role & Governance — Responsibility Accounting Matrix includes features of an enduring role, team, authority, channel, or governance body that allocates responsibility, but its defining operation is a static representation, map, specification, schema, or prospective plan that externalizes information.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Mapping responsibilities to named owners during reorganization is a management and organizational-design practice.
Related originating lineages:
- Accounting & Auditing — Responsibility accounting materially shaped explicit transfer of obligations and controls.
- Law & Governance — Successor liability and duty transfer independently constrain responsibility relocation.
Review resolution: Both blind reviewers agree that organizational_management is the primary historical origin. Explicit reconciliation of alternate origin disagreement, origin mode disagreement, domain reach disagreement adopts reviewer_a's evidence: Mapping responsibilities to named owners during reorganization is a management and organizational-design practice. The selected record uses alternates=accounting_auditing, law_governance, origin_mode=cross_disciplinary_synthesis, and domain_reach=multi_domain; the other review proposed alternates=accounting_auditing, law_governance, systems_cybernetics, origin_mode=convergent, and domain_reach=universal. The selected combination better preserves the mechanism-specific formative lineages and calibrated scope; broader present-day use is not treated as proof of additional historical origin.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The conserved quantity here — obligation — is the only one in the family that a spreadsheet cell can claim to have moved while nothing has actually moved. That is why acceptance sign-off, not just a filled cell, is the load-bearing part: an unaccepted assignment is an orphan wearing a name tag.
[n1] A RACI matrix (Responsible, Accountable, Consulted, Informed) is the common template for assigning responsibility across roles for a set of tasks. The responsibility accounting matrix applies the same table to a transition — mapping duties from their old owners to new ones — with the specific aim of catching obligations that would otherwise be dropped in the handoff. ↩