Deferred Objectives Backlog¶

Holding register — instantiates Objective Boundary Governance

A durable, visible queue where worthy-but-not-now objectives are parked with their rationale and revisit trigger, so 'no for now' doesn't mean 'lost forever.'

Version: v1 · 2026-08-24 · History
Mechanism #: 2544
Type: Holding Register
Form family: Record, Log & Register
Solution family: Planning & Staging
Problem family: Goal, Value & Purpose Misalignment
Problem subfamily: Optimization Target & Mission-Scope Drift
Origin domain: Organizational & Management Science
Instantiates: Objective Boundary Governance

The Deferred Objectives Backlog is a persistent holding queue for additions that are good ideas but do not belong in the objective now — each parked with the reason it was deferred and the condition that would bring it back. Its defining trait is that it makes "not now" a real and safe answer. The reason additions get admitted prematurely is that declining feels like killing: a sponsor who hears "no" hears "your idea is dead," and pushes to jam it in. A visible, durable backlog converts a rejection into a deferral, removing the very pressure that drives creep. It is a store, not a decision-maker — but by giving good ideas a dignified place to wait, it lets every other mechanism say no without paying the political cost.

Example¶

A city's capital-projects office faces relentless pressure to cram every worthy proposal into the current budget cycle — a footbridge here, a park expansion there — because advocates fear that a project left out this cycle is a project killed. The office stands up a public deferred-projects register. Proposals that can't fit the current envelope go into it, each tagged with the reason (no funding this cycle) and a concrete revisit trigger (reconsider at the next bond measure).

Because advocates can see their footbridge is parked, not dead — with a named condition that will bring it back — they stop fighting to force it into a plan it doesn't fit. The register also carries a sunset rule: a parked project untouched for three cycles is reviewed and formally dropped, so the backlog doesn't silently swell into a graveyard. The current capital plan stays coherent and honestly scoped, and the good ideas are preserved rather than lost.

How it works¶

Each parked item carries its rationale — why it was deferred, so the deferral is legible and doesn't read as a brush-off.
Each carries a revisit trigger — the specific condition (a funding event, a milestone) that will bring it back for reconsideration.
It is visible to proposers — the backlog's political power comes from people being able to see their idea is preserved.
Items sunset if never triggered — a parked objective that ages out is reviewed and dropped, so the queue stays real.
It is the ledger's deferred column — parked items remain part of the objective's memory, distinct from those accepted or rejected.

Tuning parameters¶

Visibility — public register vs. internal list. Public visibility maximizes the pressure-relief but exposes the queue to lobbying.
Revisit-trigger specificity — concrete conditions actually fire; vague ones ("someday") let items rot.
Sunset age — how long an item may wait before it's reviewed out. Short ages keep the queue honest; long ones risk a graveyard.
Curation — an unbounded catch-all vs. a curated shortlist. Curation keeps it credible but requires ongoing effort.
Promotion path — how a triggered item re-enters the live objective, and who decides.

When it helps, and when it misleads¶

Its strength is defusing the add-pressure: it lets the charter, the board, and the plus/minus review decline additions without the fight that declining usually provokes, because "no for now" is visibly not "no forever." It preserves genuinely good ideas without diluting the present objective — the pattern's whole balancing act. The form echoes the "Someday/Maybe" list^[n1] from personal productivity practice, which works for exactly the same reason: a trusted holding place lets you stop carrying an idea without losing it.

Its failure mode is becoming a graveyard — a place where things are parked with no intention of ever revisiting, so "deferral" is just polite killing. Once proposers learn that the backlog is where ideas go to die, it loses the trust that makes it work, and the add-pressure returns. The guarding discipline is to make revisit triggers concrete and to honor them: actually reconsider parked items when their condition fires, and sunset the rest openly rather than letting them accumulate as false hope.

How it implements the components¶

deferred_objective_parking_lot — it is the parking lot: the durable, named place deferred objectives wait.
removal_and_sunset_path — parked items carry a sunset condition, so the backlog prunes itself rather than swelling forever.
objective_boundary_ledger — it holds the "deferred" column of the ledger, keeping declined-for-now items in the trajectory's memory.

It does not implement sub_objective_admission_rule — deciding what is admitted versus parked belongs to the Objective Change-Control Board — nor objective_dilution_signal (the Objective Drift Dashboard) or opportunity_cost_register (the Opportunity-Cost Review). The backlog is the durable queue where deferred and swapped-out objectives wait; the Plus/Minus Boundary Review is the ritual that decides the swap that sends them there.

Instantiates: Objective Boundary Governance — the backlog is the real subtraction path that makes "not now" a legitimate answer instead of a killed idea.
Sibling mechanisms: Objective Charter · Sub-objective Decision Record · Objective Change-Control Board · Objective Drift Dashboard · Mission-Creep Audit · Opportunity-Cost Review · Plus/Minus Boundary Review · Re-charter Workshop

Editorial Notes¶

Form Classification¶

Form family: Record, Log & Register

Rationale: Deferred Objectives Backlog operates as a durable record, ledger, register, or trace whose value depends on preserving actual state or history because it a durable, visible queue where worthy-but-not-now objectives are parked with their rationale and revisit trigger, so 'no for now' doesn't mean 'lost forever.'.

Independent corroboration: The frozen evidence defines Deferred Objectives Backlog as 'A durable, visible queue where worthy-but-not-now objectives are parked with their rationale and revisit trigger, so 'no for now' doesn't mean 'lost forever.'', so its operative form is Record, Log & Register.

Review outcome: Independent reviewer agreement; high confidence.

Origin Attribution¶

Primary origin: Organizational & Management Science

Origin pattern: Single lineage

Present-day reach: Multi-domain

Rationale: Work and project management cohered trusted someday/maybe backlogs that preserve deferred objectives with review triggers without admitting them to current scope.