Evidence
The vendor, platform team, and business unit each describe a different owner, while no authorization record names the person who accepts responsibility for the customer outcome.
CONSTRUCTED EXAMPLE
A generic enterprise service team is reviewing an agent that recommends routing for incoming customer cases.
Published under CC BY 4.0. Free to reproduce, adapt, translate, and use commercially, including inside your own governance program, with attribution to Sougata Roy and a link to this page. Attribution is a condition of the license. Claiming authorship is not attribution. Full terms at sougataroy.com/rights
Cite this framework
Sougata Roy, "The Accountability Assumption", Version 1.0, August 2026, https://sougataroy.com/frameworks/accountability-assumption
Constructed working artifact
This scenario is constructed for explanation. It is not a real organization and is not drawn from an engagement.
Placement
Accountability assumption identified
Evidence
The vendor, platform team, and business unit each describe a different owner, while no authorization record names the person who accepts responsibility for the customer outcome.
Remaining gap
The consequential business outcome is not connected to a named individual with a review cadence.
Next action
Name the consequence owner, document the permitted use and escalation path, and retain the assignment before production use.
Output
A completed accountability assignment with an evidence path.
How to use this page
Compare this constructed example with the primary object, then replace it with organization-specific evidence before relying on the artifact for governance or examination.