Authority Boundary Review¶
Procedure — instantiates Decision Rights Clarification
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.
Every other mechanism in this archetype writes authority — assigns an owner, bounds a scope, labels a role. Authority Boundary Review is the one that checks it. It is a recurring, evidence-driven procedure that looks backward at how decisions actually behaved over the last period — what stalled, what got overridden, what escalated that shouldn't have, who really made the call — and asks a single question: does the rights map still match reality? It produces no new authority. Its whole output is a diagnosis of drift and, where the gap is large enough, a trigger to revise the map. That backward, comparative stance is what makes it this mechanism and not a design artifact: the others answer "who may decide?"; this one answers "is that still true, and is it still working?"
Example¶
A contract-manufacturing plant runs a quarterly authority boundary review on its shop-floor decision rights. The map on file says line supervisors may authorize scrap disposition up to $2,000, approve overtime within their shift, and stop the line for any safety concern; anything larger escalates to the plant manager. The review pulls a quarter of evidence against that map: how long scrap decisions actually took, how many overtime approvals were reversed, every line-stop and who called it, and the near-misses where an operator hesitated because it wasn't clear they were allowed to halt the line.
Two mismatches surface. First, a veteran night-shift technician — not a supervisor, not on the map anywhere — is the person everyone actually defers to on scrap calls, and the formal supervisor rubber-stamps him. Second, the $2,000 scrap ceiling, set three years ago, now trips on routine decisions because material costs rose, so half of scrap dispositions escalate needlessly and sit for a day. The review's output is not a reprimand; it is a revision packet: fold the night-shift technician's real authority into the formal map, and raise the scrap ceiling to $3,500 to pull routine calls back down to the floor. The rights map goes back to matching how the plant actually runs.
How it works¶
The procedure runs in four moves. Gather the behavioral signal — the metrics that reveal how authority actually flowed: decision latency, escalation frequency, override and reversal counts, exception invocations, and outcome quality (which decisions went wrong and whether the decider had the authority and information to get them right). Lay the signal against the map — for each decision category, compare what the rights map predicts against what happened. Classify the drift — sort each gap into a type: a boundary set at the wrong height (chronic needless escalation, or decisions above someone's competence sitting with them), shadow authority (someone deciding who isn't on the map, or an owner who is only nominal), or a category the map never anticipated. Fire the trigger where warranted — for gaps past a set severity, open a revision rather than logging a note that dies in a folder. The distinctive discipline is that the review is diagnostic, not corrective in itself: it does not re-assign authority on the spot, it produces the evidence and the revision request that the rights owners then act on.
Tuning parameters¶
- Review cadence — how often the sweep runs. Frequent reviews catch drift early but cost attention and can churn a map that was fine; rare reviews are cheap but let shadow authority calcify. Match cadence to how fast the operating context moves.
- Signal set — which behaviors count as evidence. A narrow set (just latency and escalations) is easy to collect but blind to quiet shadow authority; a broad set (adding outcome quality and near-misses) sees more but is heavier and noisier.
- Drift severity threshold — how large a mismatch must be before it fires a revision versus a watch-item. Set it low and the map thrashes on noise; set it high and real decay accumulates unaddressed.
- Review scope — all decision categories every cycle, or a rotating high-risk subset. Full sweeps are thorough but expensive; rotation is affordable but can miss a category between passes.
- Depth — a metrics-only scan versus interviews with deciders. Metrics are objective and cheap but miss why people route around the map; interviews surface the informal reality but invite spin.
When it helps, and when it misleads¶
Its strength is that it is the only thing keeping a rights design from silently rotting — it converts the vague sense that "authority feels murky again" into named, evidenced gaps and a concrete revision. It is uniquely good at catching the failure the design mechanisms cannot see from the inside: the formally-correct map that no longer describes who actually decides.
It misleads in two directions. Run as theater, it becomes a quarterly box-tick that re-affirms the existing map because nobody wants to reopen settled turf — the review that never triggers a change is almost always broken, not vindicated. Run too aggressively, it over-fits to noise and churns the map every cycle, destroying the stability that made the rights useful. The classic misuse is turning the review into a blame audit — hunting for who violated the rights rather than where the rights stopped fitting — which teaches everyone to hide the very shadow behavior the review needs to see. The guard is to frame every finding as map-fit evidence, not a personnel charge, in the spirit of control self-assessment, where the people doing the work surface control gaps because it is safe to.[n1]
How it implements the components¶
rights_review_trigger— its core output: the evidence-based condition (drift past threshold, repeated escalations, contested overrides) that fires a revision of the rights map.informal_authority_reconciliation— comparing recorded owners against who actually decided is exactly how it surfaces shadow authority and feeds the reconciliation back into the formal design.authority_boundary— it re-examines whether each boundary still sits at the right height and flags the ones to redraw (raise a stale ceiling, tighten a risky one).
It does not hold the standing catalog of categories, owners, and thresholds it audits against (decision_category, decision_owner, decision_threshold — that's Decision Registry); nor does it assign the recommend/decide/consult labels for a decision (decision_participation_roles — that's the RACI / RAPID-Style Tool).
Related¶
- Instantiates: Decision Rights Clarification — this is the maintenance procedure that keeps the rest of the design current as the operating context changes.
- Consumes: Decision Registry — the review compares actual decision behavior against the current rights map the registry holds.
- Sibling mechanisms: Decision Registry · Delegation Charter · Governance Charter · RACI / RAPID-Style Tool · Decision-Rights Matrix · Escalation Protocol · Decision Log · Approval Workflow
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: 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, making its operative form a bounded evaluation of existing evidence or work that produces a finding or disposition.
Independent corroboration: The frozen evidence defines Authority Boundary Review as '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', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Organization design periodically revises decision rights when actual delays, overrides, and conflicts diverge from the intended map.
Related originating lineages:
- Law & Governance — Jurisdictional review supplies formal authority-boundary reasoning.
- Public Administration & Policy — Administrative practice evaluates whether powers sit at the effective level.
Review resolution: Organizational management is the agreed primary lineage. Legal authority and administrative jurisdiction materially constrain the rights map; the evidence-driven drift review and revision trigger are a cross-disciplinary Encyclopedia synthesis.
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¶
[n1] Control self-assessment — an internal-audit practice in which the people who do the work, rather than an external inspector, evaluate whether their own controls are working. Its premise is that gaps surface honestly only when the exercise is framed as improving the system, not catching individuals — the same framing that keeps an authority boundary review from curdling into a blame audit. ↩