Who Owns the Decision? A Founder Responsibility Map
Map recurring business decisions to accountable owners, reviewers, evidence and escalation triggers before automating the work.
For: Founders designing recurring business workflows
Create an operational responsibility map for decisions that cross business, legal, finance and technology roles.
Which recurring business decisions need an authority owner?
Every recurring decision that can change a commitment, disclose information, affect people or accept risk benefits from an identified owner. Start with the consequence, then assign preparation, review, decision and execution. Do not assume the person who administers the software can approve the business outcome.
Map consequences before job titles
Use decision families that appear in the company's real operations: purchasing, hiring, customer terms, incident response, public statements and dispute handling. For each, identify what changes when the decision is made. A role called operations may prepare several of these decisions without owning all of them.
- Purchasing: price, duration, renewal and termination commitments.
- People: hiring criteria, access changes and communications affecting workers.
- Customer terms: pricing exceptions, warranties and negotiated obligations.
- Data: new recipients, purposes, retention or access.
- Disputes: positions, offers, releases and response strategy.
Synthetic responsibility map
Fictional business: Harbor Notebook Co. The company wants an agent to prepare software renewals and customer exceptions. The following assignments are design assumptions for the example, not statements of law.
- Renewal under an existing approved budget: operations prepares; finance checks cost; designated purchasing officer decides; agent executes only the approved transaction.
- New use of customer data: product describes purpose; privacy and security review; designated risk owner decides whether to proceed.
- Customer liability exception: sales explains business need; counsel reviews legal implications; the delegated executive decides commercial acceptance.
- Public outage notice: engineering verifies facts; communications prepares language; incident lead approves the identified notice.
Keep the map useful as the business changes
Add a review trigger when a person leaves, a spending limit changes, a vendor adds a new data use or a workflow gains a new external action. A responsibility map that is never reconciled to current delegations can become misleading.
NIST's AI RMF organizes risk-management activity into Govern, Map, Measure and Manage. These functions offer a vocabulary for maintaining the process; they do not appoint corporate decision makers. [S2]
- Monthly sample: select a few completed decisions and locate their authority evidence.
- Exception record: name the missing owner or conflicting delegation.
- Completion criterion: the final artifact and observed action match the approval.
- Unresolved ownership: hold the consequential step and route the specific question.
Scope and limitations
A proposed governance method for businesses. The Delaware corporate-law example is limited to corporations governed by that statute.
The company and delegations are fictional. Actual authority depends on entity type, jurisdiction, governing documents and the facts; this is not a corporate legal opinion.
Sources
- Delaware Code, Title 8, Chapter 1, Subchapter IV: Directors and Officers — Section 141(a) board-management baseline and section 142 officer roles, subject to statutory and governing-document qualifications. Checked 2026-11-05
- NIST AI Resource Center: AI RMF — Framework organization around Govern, Map, Measure and Manage; voluntary use and ongoing revision. Checked 2026-11-05
Explore further
This decision map provides context for exploring Agentic Attorney at https://agenticattorney.com/ and evaluating how agent-assisted work could fit a business's existing human responsibilities. Explore Agentic Attorney.