Decision Stall Register¶
Register — instantiates Functional Vacancy Backfill
A running ledger of decisions left unresolved under a nominally-present authority, turning scattered 'still waiting on them' complaints into dated, per-function evidence of a failing role.
Before anyone can declare a role functionally vacant, the nonperformance has to be visible — and the trouble with an absent authority is that each stalled decision looks like a one-off. Decision Stall Register fixes this: every decision the role should have closed but didn't gets a dated entry, tagged to the specific function it belonged to (arbitrate, approve, prioritize, resource), with its age and its cost of delay. Individually each line is a shrug; accumulated and sorted by function, they become an argument. The register neither judges nor triggers anything — it is pure instrumentation, the evidence base the declaration and the deadline both draw on. What makes it this mechanism is that it inventories stalls by decision function, so the pattern it surfaces is not "the sponsor is busy" but "the arbitration function of this role has produced nothing in nine weeks."
Example¶
A city planning department has a division director who signs off on zoning variances. Over a quarter, variance requests keep dying in the director's inbox, and each planner assumes theirs is the unlucky exception. The department keeps a Decision Stall Register: a shared log where any planner opens a row when a decision the director owes sits idle past its normal turnaround. Each row records the date opened, the specific director function it needed (variance approval, inter-agency sign-off, appeal arbitration), the decision's age, and what is blocked downstream — a stalled housing permit, a contractor on hold. By quarter's end the register shows eleven open rows, nine of them under "variance approval," average age ≈40 days against a ~10-day norm. That table is the thing no single planner could produce, and it is exactly the cited evidence a functional-vacancy declaration will later need. The register decided nothing; it made an invisible pattern countable.
How it works¶
- One row per stalled decision, opened by whoever is blocked — not by a monitor — so it captures felt friction rather than only tracked SLAs.
- Tag each row to the specific role function it required, so stalls aggregate by function rather than by person; a role can be healthy at three functions and dead at a fourth.
- Record age and downstream cost, not just status, so severity is legible and the worst stalls sort to the top.
- Leave the judgment out. The register stops at the evidence; whether the pattern crosses a line belongs to the deadline rule and the declaration.
Its discipline is completeness and neutrality: it logs stalls whether or not anyone intends to act on them, which is what keeps it credible when it is finally cited.
Tuning parameters¶
- Entry threshold — how overdue a decision must be before it earns a row. Low threshold catches early drift but fills with noise; high threshold stays clean but lags the problem.
- Who may open a row — anyone blocked, or only designated leads. Open entry surfaces more but invites griping; gated entry is cleaner but can be captured by the very absence it should record.
- Function granularity — how finely decisions are tagged to role functions. Finer tags localize the failure precisely but burden every logger with a taxonomy.
- Visibility — private to a governance body versus visible to the incumbent and stakeholders. Openness pressures the incumbent to re-engage but can feel like a public scorecard.
- Aging cadence — how often rows are re-aged and re-costed, which sets how fresh the "case" is when someone reaches for it.
When it helps, and when it misleads¶
Its strength is turning anecdote into evidence: it is the difference between "the director's been slow lately" and a dated, per-function table a declaration or a deadline can stand on. It is a close cousin of the risk register long standard in project management — the same move of forcing diffuse, deniable worries into a single owned, reviewed list.[n1]
It misleads when the log is mistaken for the verdict. A long register proves decisions stalled, not why — a sponsor may be blocked by a genuine dependency rather than disengagement, and the register cannot tell the two apart. It is also gameable in both directions: under-logged, it hides a failing role; weaponized, it becomes a padded dossier assembled to justify a removal already decided on. The discipline that keeps it honest is neutral, complete logging with the cause left open — the register counts stalls and hands interpretation to the health check and the declaration, which weigh whether absence, not circumstance, is the driver.
How it implements the components¶
Decision Stall Register fills only the evidence-and-inventory slice:
role_function_health_signal— each row is a raw health signal (age, completion, downstream cost); the register is where those signals are captured and trended over time.decision_function_inventory— by tagging every stall to the specific function it needed, the register maintains a live, empirical inventory of which of the role's functions are and are not being supplied.
It does not judge whether the seat is still nominally occupied or issue any status change (nominal_occupancy_assessment, legitimacy_notice_and_record, the Functional Vacancy Declaration), and it does not set the deadline at which a stall becomes actionable (decision_stall_threshold, the Decision Timeout Rule).
Related¶
- Instantiates: Functional Vacancy Backfill — the register is the archetype's instrument, the evidence base backfill decisions cite.
- Sibling mechanisms: Functional Vacancy Declaration · Decision Timeout Rule · Auto-Escalation Workflow · Acting Sponsor Rotation · Deputy Sponsor Charter · Sponsor Health Check · Sponsor Re-Engagement Notice · Interim Authority Letter · Governance RACI With Backups · Two-Key Escalation Panel · Post-Backfill Authority Review
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Decision Stall Register operates as a durable record, ledger, register, or trace whose value depends on preserving actual state or history because it a running ledger of decisions left unresolved under a nominally-present authority, turning scattered 'still waiting on them' complaints into dated, per-function evidence of a failing role.
Independent corroboration: The frozen evidence defines Decision Stall Register as 'A running ledger of decisions left unresolved under a nominally-present authority, turning scattered 'still waiting on them' complaints into dated, per-function evidence of a failing role', so its operative form is Record, Log & Register.
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: Project governance cohered maintained issue and risk registers with dated items, owners, aging, impact, and review cadence.
Related originating lineages:
- Public Administration & Policy — Administrative performance oversight supplied tracking of unresolved approvals and nonperformance by required function.
Review resolution: Project governance cohered maintained issue and risk registers with dated items, owners, aging, impact, and review cadence.
Attribution caveat: The register form is standard project management; inventorying stalls specifically by absent decision function is a 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¶
A register is only trusted if it predates the fight it is used in. One opened the week someone wants a declaration reads as a prosecutor's file; one that has quietly logged stalls for a year reads as fact. The value is in the boring, continuous keeping — which is exactly the part an organization under a functioning sponsor feels no urgency to do.
[n1] A risk register is a standard project-management artifact: a single maintained list of identified risks with owner, likelihood, and impact, reviewed on a cadence. The decision-stall register borrows its core move — making diffuse, easily-ignored concerns into discrete, owned, reviewable rows. ↩