Decision Rights Clarification¶
Clarify who has authority to decide what, under which constraints, with which escalation paths.
The Diagnostic Story¶
Symptom: Decisions bounce between people and groups because nobody is sure who has final authority. People are held accountable for outcomes they were not empowered to determine. Meetings end with discussion but no named owner. Unofficial vetoes override formal ownership, and local teams escalate routine decisions upward because the boundary of their autonomy has never been stated.
Pivot: Create an explicit map of authority by decision category, distinguishing who inputs, who approves, who executes, who must be notified, and under what conditions a decision must escalate. Pair each category of authority with explicit constraints and a clear escalation path for boundary-exceeding cases.
Resolution: Recurring decisions get made faster because actors know who may decide. Accountability becomes traceable because authority, rationale, and follow-up obligations are on record. Routine decisions stop flooding upward, and delegation works within named limits rather than being taken back informally.
Reach for this when you hear…¶
[cross-functional team] “We spent three weeks in review because engineering thought product owned the call and product thought it needed a VP sign-off — write it down so this stops happening.”
[hospital governance] “The committee chair approved the protocol but the department head reversed it the next day — if both of them think they own that decision we have a rights conflict, not a personality problem.”
[regulatory agency] “Field inspectors keep escalating judgment calls that are clearly within their mandate because nobody told them where their authority ends.”
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
People are unsure who can decide, approve, override, veto, consult, or escalate a recurring category of decisions, causing delay, conflict, duplicated work, shadow authority, or accountability gaps.
What this problem means
The structural problem is a mismatch between responsibility, authority, participation, and accountability. A system may say that a team is responsible for an outcome while withholding decision authority. Or it may give multiple actors partial authority without clarifying who has final say. Or it may rely on informal influence paths that everyone knows but nobody records.
When this mismatch persists, the organization develops defensive behavior. People escalate routine choices, seek informal pre-approval, avoid ownership, or blame others for decisions that were structurally ambiguous. The cost appears as delay, rework, conflict, inconsistent decisions, and weak accountability.
Show the applicability expression
Applicability expression6 distinct conditions
groundedpartly groundedopen
6 conditions, all required.
6Required in every casenumbered 1–6
These hold no matter which pattern applies.
Cross-role recurring decisions · grounded · any one of 2
Work requires recurring decisions that affect multiple roles, teams, units, stakeholders, or risk domains.
People are unsure who can decide, approve, override, veto, consult, or escalate a recurring category of decisions, causing delay, conflict, duplicated work, shadow authority, or accountability gaps. The narrower requirement in this condition set is: Work requires recurring decisions that affect multiple roles, teams, units, stakeholders, or risk domains.
Permission-seeking ambiguity · open
People routinely ask for permission, seek backchannel approval, or defer decisions because formal authority is unclear.
Use this archetype when decisions stall or become political because authority is unclear. The narrower requirement in this condition set is: People routinely ask for permission, seek backchannel approval, or defer decisions because formal authority is unclear.
Unspecified category ownership · open
Formal titles, org charts, or policies do not specify who owns specific decision categories.
People are unsure who can decide, approve, override, veto, consult, or escalate a recurring category of decisions, causing delay, conflict, duplicated work, shadow authority, or accountability gaps. The narrower requirement in this condition set is: Formal titles, org charts, or policies do not specify who owns specific decision categories.
Recurring approval dysfunction · needs review
Decision delay, duplicate approvals, conflicting approvals, or after-the-fact overrides are recurring rather than exceptional.
People are unsure who can decide, approve, override, veto, consult, or escalate a recurring category of decisions, causing delay, conflict, duplicated work, shadow authority, or accountability gaps. The narrower requirement in this condition set is: Decision delay, duplicate approvals, conflicting approvals, or after-the-fact overrides are recurring rather than exceptional.
Overlapping authority boundaries · grounded
A matrix, cross-functional, regulated, or multi-agency setting creates overlapping authority boundaries.
It is especially useful in matrix organizations, cross-functional programs, public agencies, shared governance bodies, regulated operations, platform teams, crisis response, and partnerships where authority crosses role or unit boundaries. The narrower requirement in this condition set is: A matrix, cross-functional, regulated, or multi-agency setting creates overlapping authority boundaries.
Bounded localized delegation · grounded
Authority needs to be delegated or localized, but only within explicit risk, cost, policy, safety, or strategic constraints.
The design problem is to make authority clear enough for action while bounded enough for legitimacy, accountability, and risk control. The narrower requirement in this condition set is: Authority needs to be delegated or localized, but only within explicit risk, cost, policy, safety, or strategic constraints.
Other requirements and context (1)
Why these sit outside the expression
Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.
Supporting contextDecision consequences are large enough that accountability, auditability, or legitimacy matter.
The design problem is to make authority clear enough for action while bounded enough for legitimacy, accountability, and risk control. In this archetype, the relevant contextual consideration is: Decision consequences are large enough that accountability, auditability, or legitimacy matter. It helps interpret the situation or strengthens the practical case for examining the archetype.
Coverage
3 of 6 conditions grounded · 2 open · 1 needing review.
Mechanisms / Implementations¶
- Decision Rights Matrix: Maps each class of decision to who may decide, approve, be consulted, or merely be informed — fixing the agent's authority before any single choice arises.
- RACI / RAPID-Style Tool: Assigns a single, unambiguous participation label — recommend, decide, approve, consult, or inform — to each role for a given decision, prying apart the roles that ambiguity collapses together.
- Delegation Charter: A standing document that grants a bounded envelope of authority to one delegate — a role, team, project, or unit — stating what it may decide alone, the limits on that autonomy, and where cases outside the envelope must go.
- Approval Workflow: An approval workflow operationalizes decision routing through systems, forms, queues, or sign-offs.
- Governance Charter: A constitution for a collective decision body — a committee, board, council, or steering group — defining which decision categories it owns, who sits on it in what role, how it decides by vote or consent, and how it resolves authority conflicts.
- Decision Log: Captures each significant decision as a linked record — its rationale, the alternatives weighed, who approved it, and the artifacts it affects — so a choice can later be traced back to why it was made and forward to what it touched.
- Escalation Protocol: Defines the threshold at which an agent's ordinary discretion runs out and the decision must be routed up to a higher or different authority.
- Authority Boundary Review: Periodically compares actual decision delays, conflicts, overrides, exceptions, and outcome quality against the current rights map, and fires a revision where the two have drifted apart.
- Decision Registry: A searchable system of record for decision rights — look up any decision category and get its current owner, approval requirements, threshold, and escalation path on demand.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (3)
- Accountability: Responsibility for actions.
- Delegation of Authority: Assign responsibility.
- Formal vs. Informal Structures: Official vs actual systems.
Also references 9 related abstractions
- Boundary: Defines system limits.
- Checks and Balances: Distributed power.
- Hierarchy: Organizes elements into levels or ranks.
- Legitimacy: Accepted authority.
- Local Autonomy & Tiered Escalation: Escalate when needed.
- Oversight Capacity: Limits of supervision.
- Procedural Fairness (Due Process): Due process.
- Role Conflict: Conflicting roles.
- Separation of Powers: Divide authority.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Delegated Authority Envelope · governance variant · promote to full archetype candidate
Defines the scoped envelope within which a delegated actor may decide, act, spend, approve, or escalate.
Approval Boundary Clarification · governance variant · recognized
Clarifies which decisions require approval, which only require consultation or notification, and which can be made independently.
Escalation Rights Clarification · governance variant · recognized
Clarifies who may escalate a decision, what triggers escalation, where it goes, and what authority remains with the original owner.
Shadow Authority Reconciliation · governance variant · candidate
Reconciles official decision rights with the informal influence, vetoes, and approval paths that actually control decisions.
Emergency Decision Authority · risk or failure variant · recognized
Predefines who may decide under urgent, high-risk, or degraded conditions when normal consultation and approval paths are too slow.
Editorial Notes¶
Problem Classification¶
Classification: Authority, Accountability, Legitimacy & Fair-Process Failure → Authority Scope, Decision Rights & Continuity
Problem kernel: recurring decisions lack explicit rights and escalation paths
Rationale: Actors cannot tell who may decide, approve, veto, consult, or override, producing delay, shadow authority, duplication, and accountability gaps.
Independent corroboration: The earliest necessary condition in the frozen evidence is: People are unsure who can decide, approve, override, veto, consult, or escalate a recurring category of decisions, causing delay, conflict, duplicated work, shadow authority, or accountability gaps. That is a authority scope decision rights and continuity problem because Legitimate action is impaired because deciding, vetoing, overriding, delegating, or succeeding authority is unclear, nominal, externally subordinated, or functionally vacant.
Review outcome: Independent reviewer agreement; high confidence.