Deferred Scope Parking Lot¶
Register — instantiates Scope Creep Containment
A visible holding register where good-but-not-now requests are parked with owner and revisit date, so deferral is an honored decision rather than a lost promise or a silent yes.
A Deferred Scope Parking Lot is a named, visible list where requests that are legitimate but out of scope for now are set down deliberately — each with the person who raised it, why it was deferred, and when it will be looked at again. Its defining move is to make deferral a real, honored outcome rather than the two failure states it usually collapses into: a silent yes (the item drifts into the work because refusing felt rude) or a silent no (the item vanishes and the requester feels ignored). The parking lot is a shelf, not a decision-maker: it does not judge whether an item is worth doing and does not admit anything into scope. It holds the deferred and the explicitly-not-now in one place so the boundary between core work and later work stays legible and so nobody has to keep a good idea alive by quietly building it.
Example¶
A small team shipping a consumer budgeting app has a public roadmap and a two-month release window for a redesigned onboarding flow. During those two months, requests pour in from support tickets, the sales channel, and the founders' own Slack: dark mode, a spending-forecast widget, CSV export, a joint-account view, a referral program. Every one is reasonable. Historically the team would have quietly slipped two or three into the onboarding sprint "since we're in there anyway," and the release would slip.
Instead they keep a Parking Lot — a single shared board column titled Deferred: revisit after onboarding ships. Each request lands there as a card with its requester, a one-line rationale, and a revisit date tied to the next planning cycle. Dark mode and CSV export get parked; the joint-account view is parked with a note that it may imply a rebaseline because it touches the data model; the spending-forecast widget is parked with a link to the support tickets that motivated it. Nothing is refused and nothing is smuggled in. When onboarding ships, the team pulls the lot open at planning, and the parked cards compete on equal footing with new work — several turn out to no longer matter, which is exactly the point.
How it works¶
What distinguishes the parking lot from a graveyard or a silent backlog is that deferral is recorded as a decision with a future:
- Everything parked keeps an owner and a rationale. A card with no requester and no reason is how a parking lot rots into a junk drawer; the metadata is what makes a revisit meaningful.
- Every parked item carries a revisit trigger — a date, a milestone, or a condition — so the lot is a queue with a scheduled reopening, not a place things go to be forgotten.
- The lot is the visible alternative to the quiet yes. Its whole reason to exist is to give the team a socially acceptable "not now" that neither refuses the requester nor expands the perimeter.
- Parked is not admitted. Pulling an item out of the lot into committed work is a separate act, made by whoever owns admission — the lot itself only holds.
Tuning parameters¶
- Revisit cadence — how often the lot is reopened. Rare reviews let it silt up into an unusable pile; constant reviews re-litigate deferrals and drain the discipline of saying "not now."
- Parking bar — how easily something can be parked. A low bar keeps the working perimeter clean but grows a lot nobody can triage; a high bar keeps the lot small but tempts people back into silent yeses.
- Expiry policy — whether stale cards auto-archive after N cycles. Aggressive expiry keeps signal high but can drop genuinely-good slow-burn ideas.
- Visibility — who can see and add to the lot. A shared, public lot builds requester trust; a private one risks becoming a manager's convenient dumping ground.
When it helps, and when it misleads¶
Its strength is social and cognitive: it converts the hardest moment in scope containment — telling a stakeholder "not this, not now" — into a constructive act that visibly preserves their idea, which is why the "parking lot" is a staple of facilitated planning.[n1] It keeps the working set small without making anyone feel unheard.
Its failure mode is the infinite parking lot — a bin that only ever accumulates, never revisited, so parking becomes a polite synonym for burial and requesters learn that "we'll park it" means "no." A second, subtler failure is scope leaking out of the lot: items pulled back into work without passing the admission gate, using the lot as a side entrance. The guarding discipline is to treat every parked card as owing a revisit and every pull-out as owing an explicit admission decision — a parking lot with no scheduled reopenings is just a backlog wearing a nicer name.
How it implements the components¶
out_of_scope_register— the lot is the register of what is deliberately not in the current perimeter, keeping deferred and not-now items distinct from committed work.stakeholder_request_queue— each parked card is a queued request with its raiser attached, awaiting a scheduled window rather than an immediate answer.subtraction_or_tradeoff_path— deferral is the gentlest subtraction route; parking an item is how a request is kept off the perimeter without being refused outright.
The lot only holds; it does not judge or admit. It does not apply the scope_addition_admission_rule (that verdict is the Change Control Board's) and it does not compute the capacity_and_dependency_impact_model a serious pull-out would need (the Impact Assessment Checkpoint).
Related¶
- Instantiates: Scope Creep Containment — the parking lot is where deferral becomes a visible, honored outcome.
- Sibling mechanisms: Plus/Minus Scope Review · Change Control Board · Impact Assessment Checkpoint · Scope Change Request Template · Scope Drift Dashboard
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Deferred Scope Parking Lot operates as a durable record, ledger, register, or trace whose value depends on preserving actual state or history because it a visible holding register where good-but-not-now requests are parked with owner and revisit date, so deferral is an honored decision rather than a lost promise or a silent yes.
Independent corroboration: The frozen evidence defines Deferred Scope Parking Lot as 'A visible holding register where good-but-not-now requests are parked with owner and revisit date, so deferral is an honored decision rather than a lost promise or a silent yes', 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: Facilitation and agile project practice cohered the visible parking lot for preserving off-topic or out-of-scope items while keeping current work bounded.
Related originating lineages:
- Education & Pedagogy — Workshop and classroom facilitation independently used parking lists to defer discussion without dismissing contributions.
Review resolution: Facilitation and agile project practice cohered the visible parking lot for preserving off-topic or out-of-scope items while keeping current work bounded. The retained alternate lineages materially shaped the mechanism's form.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The parking lot shares the subtraction-or-tradeoff idea with the Plus/Minus Scope Review, but they sit on opposite sides of the decision: the review is the room where the tradeoff is decided (this in, that out), while the parking lot is the shelf where the not-now outcome is stored. Confusing the two turns the lot into a decision body it was never meant to be.
[n1] Parking lot (facilitation technique) — a standard practice in workshops and agile planning of writing down off-topic or out-of-scope items on a visible list to be addressed later, so the current session stays focused without dismissing the raised point. The mechanism here is that technique made durable: a standing register rather than a flip-chart erased after the meeting. ↩