Gap-Closure Experiment Backlog¶
Prioritization backlog — instantiates Realized-Possible Outcome Gap Mapping
Turns closable gap portions into a prioritized queue of experiments, each ranked by the expected gap it would close against its cost, so effort flows to the highest-return tests first.
Gap-Closure Experiment Backlog is the execution-facing artifact of the archetype: an ordered queue of interventions or experiments, each aimed at a portion of the gap judged closable, each carrying an estimate of how much gap it would close and at what cost, and each positioned by an explicit priority rule. Its defining commitment is sequencing under scarcity — accepting that you cannot chase every closable portion at once and deciding, on a stated rule, what to test first. It does not judge whether a portion is closable (it inherits those verdicts) and it does not measure results after the fact; its contribution is converting a set of scored opportunities into a ranked, resourced plan of what to actually try next.
Example¶
A consumer-app growth team faces a large gap between its current activation rate and a demonstrated-possible one, already decomposed and scored: onboarding friction is highly closable, an email-nudge tweak is cheap and moderately closable, a pricing-page redesign is expensive and uncertain. The backlog turns these into candidate experiments and ranks them with an explicit rule — a RICE-style score[1] combining reach, expected impact (the gap points each test would plausibly close), confidence, and effort. Each item states its expected closable gap in the same activation-rate units the gap table uses, so a "+0.8 pts, high confidence, one sprint" onboarding test outranks a "+2 pts, low confidence, six weeks" redesign.
The output is a living queue: the top three experiments are staffed this cycle, the rest wait with their scores visible. When the onboarding test lands, its slot frees and the next-highest item rises. Nobody argues about the whole gap anymore; they argue about the ranking of the next few tests — a far more tractable fight.
How it works¶
- Turn scored portions into candidate experiments. Each closable portion becomes one or more concrete interventions to test, not an abstract "improve X."
- Estimate expected closable gap per item. Each experiment carries how much of the gap it would plausibly close, in the gap's own units, so items are comparable.
- Apply an explicit priority rule. A stated scoring formula (expected closure over cost, adjusted for confidence) orders the queue; the rule is visible and revisable.
- Staff the top, park the rest. Only the highest-ranked items draw resources now; the remainder wait with their scores, re-sorted as evidence and capacity change.
Tuning parameters¶
- Priority formula — what the rule weights (expected closure, cost, confidence, strategic fit). Simpler formulas are transparent; richer ones capture more but hide judgment inside weights.
- WIP limit — how many experiments run at once. Tight limits force focus and faster learning; loose ones spread thin.
- Closure-estimate rigor — guessed vs. modeled expected-gap-closed per item. More rigor improves ranking but slows intake.
- Re-ranking cadence — how often the queue re-sorts as results land. Frequent re-ranking stays responsive; constant churn destabilizes planning.
- Confidence discounting — how hard low-confidence items are penalized, trading bold long shots against safe incremental wins.
When it helps, and when it misleads¶
Its strength is flow control: it keeps a team from diluting itself across every shortfall and instead routes scarce effort to the tests with the best expected return, with the ranking logic out in the open where it can be challenged. Because items carry expected closure in gap units, the plan stays tethered to the actual gap rather than to enthusiasm.
Its failure mode is priority theater — a precise-looking score that encodes guessed impact and confidence numbers, producing a ranking no more grounded than the estimates feeding it, yet harder to question. A classic misuse is gaming the formula: inflating a pet project's impact or confidence to float it to the top. The guarding discipline is to treat each item's expected-closure figure as a hypothesis the experiment will test — and to reconcile predicted against actual closure once results land, so the rule earns or loses trust over time.
How it implements the components¶
gap_priority_rule— its core: the explicit, visible rule that ranks candidate experiments and decides what is tested first under limited capacity.realization_gap_measure— each backlog item carries its expected closable gap in the gap's own units, keeping the queue tethered to the measured shortfall.
It sequences closable work but does not judge closability: closability_classification belongs to its nearest twin, Closability Scoring Rubric, whose scores the backlog consumes. Nor does it measure what an experiment actually closed afterward — post_intervention_gap_update is Post-Closure Gap Remeasurement.
Related¶
- Instantiates: Realized-Possible Outcome Gap Mapping — supplies the prioritized execution plan for closing the gap.
- Consumes: Closability Scoring Rubric supplies the closability scores that decide which portions enter the queue.
- Sibling mechanisms: Realized-Possible Gap Table · Loss-Channel Decomposition · Feasible-Frontier Mapping · Best-Demonstrated-Practice Comparator · Counterfactual Ceiling Probe · Closability Scoring Rubric · Theoretical-Ceiling vs Feasible-Target Review · Post-Closure Gap Remeasurement
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Gap-Closure Experiment Backlog operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it turns closable gap portions into a prioritized queue of experiments, each ranked by the expected gap it would close against its cost, so effort flows to the highest-return tests first.
Independent corroboration: The frozen evidence defines Gap-Closure Experiment Backlog as 'Turns closable gap portions into a prioritized queue of experiments, each ranked by the expected gap it would close against its cost, so effort flows to the highest-return tests first', so its operative form is Decision, Gate & Allocation.
Nearest alternative: Protocol, Workflow & Routine — The queue ranks experiments and allocates effort to the highest expected gap closure; test execution occurs after that disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Innovation & Entrepreneurship
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Product management established prioritized experiment backlogs ranked by expected impact and effort.
Related originating lineages:
- Operations Research — Resource-allocation methods contribute explicit value-per-cost sequencing.
- Organizational & Management Science — Continuous-improvement backlogs and gap remediation materially shape ownership and closure.
Review resolution: Product-management guidance defines a backlog as prioritized work and recommends impact-versus-effort and other scoring frameworks; lean portfolio guidance frames roadmap items as hypotheses and experiments. This makes innovation_entrepreneurship the primary lineage. Organizational management supplies ownership and backlog operations, while operations research supplies explicit return/cost ranking. The gap-closure formulation is an encyclopedia synthesis.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- https://www.atlassian.com/agile/product-management/prioritization-framework — Atlassian product prioritization frameworks.
- https://www.atlassian.com/agile/scrum/backlogs/ — Atlassian product-backlog practice.
References¶
[1] McBride, S. "RICE: Simple Prioritization for Product Managers". Intercom (2018). Defines RICE as an explicit prioritization score combining reach, impact, confidence, and effort. registry ↩