Portfolio Exploration Backlog¶
Artifact — instantiates Option Preservation
Keeps a governed register of exploratory options — each with an owner, a carrying cost, and kill criteria — so the option space stays balanced and pruned instead of hoarded.
A Portfolio Exploration Backlog is the durable record that keeps a whole set of options honest: a governed list in which every exploratory bet carries an owner, an ongoing carrying cost, kill criteria, and a place in an explicit balance across the portfolio. Its defining move is governance-through-bookkeeping at the set level — it does not run experiments or gate any single decision; it holds the standing inventory so that the option space as a whole stays diversified, affordable, and regularly pruned. It is the artifact that turns "we have a lot of ideas floating around" into a reviewed register where nothing lives unowned, uncosted, or unkillable.
Example¶
A consumer-goods company's innovation office maintains a single backlog of exploratory bets — reformulations, new packaging, adjacent product lines. Each row has an owner, a quarterly carrying cost (lab time, panel testing), an explicit kill trigger ("drop if two consumer panels score below threshold"), and a category tag used to enforce balance: no more than half the budget in incremental line extensions, a floor reserved for genuinely novel bets, a cap on any single high-cost exploration.
At the quarterly review, the register does its work. Three bets have blown past their carrying-cost limit with no evidence and are killed by rule, not by argument. The portfolio has drifted too far toward safe extensions, so the balance rule reallocates freed budget to the novel column. And a bet everyone had forgotten is revealed, by its own record, to have been a zombie for two quarters — listed, costing money, owned by someone who left. The backlog's value is not any one decision but that the set stays deliberately shaped and pruned instead of quietly accumulating.
How it works¶
The artifact's distinguishing discipline is what every entry is forced to carry:
- Every option has an owner and a live carrying cost. An unowned or uncosted entry is not allowed to persist — that is precisely the record that prevents zombies.
- Every option has pre-written kill criteria. Abandonment is a stored rule attached to the entry, so pruning happens by policy at review, not by whoever argues loudest.
- The set is balanced by explicit rule. Category caps and floors keep the portfolio from over-concentrating on safe or fashionable bets.
- The register is the memory. Decisions, costs, and outcomes are logged against each entry, so the portfolio's history is auditable and forgotten bets surface.
Tuning parameters¶
- Balance rule — the caps and floors across categories. Tighter rules force diversification but constrain freedom to chase a hot area; looser rules risk concentration.
- Carrying-cost cap — the total and per-bet spend the backlog may hold. A tight cap forces ruthless prioritization; a loose one tolerates more parallel exploration but courts sprawl.
- Kill-criteria strictness — how aggressively entries are pruned. Strict criteria keep the list lean but may cut bets before their evidence matures; lenient ones let zombies linger.
- Review cadence — how often the register is groomed. Frequent grooming catches drift and zombies early but costs attention; infrequent grooming lets the backlog rot.
- Record depth — how much history each entry logs. Richer records aid audit and learning but add maintenance burden.
When it helps, and when it misleads¶
Its strength is that it makes the option space itself a managed object — visible, owned, costed, and balanced — which is exactly what stops option preservation from decaying into option hoarding. It fits any setting with many simultaneous exploratory bets competing for a shared budget: R&D pipelines, innovation portfolios, research agendas.
Its failure mode is the zombie project — a bet that stays on the list, consuming budget and attention, long after it has ceased to be viable, because no one owns its death.[n1] The classic misuse is a backlog that only ever grows: every idea is added, nothing is killed, and the register becomes a graveyard that launders inaction as optionality. A related trap is kill criteria that exist on paper but are never enforced at review. The guarding discipline is to treat grooming as the point of the artifact, not overhead — enforce the kill rules on cadence, require an owner and a cost for every live entry, and read the balance report as a decision, not a status update.
How it implements the components¶
Portfolio Exploration Backlog fills the archetype's set-governance slot — it maintains and prunes the standing option space rather than acting on any one option:
portfolio_balance_rule— the category caps and floors that keep the set diversified and un-concentrated.carrying_cost_budget— the per-bet and total cost the register tracks and bounds, so optionality stays affordable.abandonment_rule— each entry's stored kill criteria, applied by policy at review.documentation_memory— the register itself: the durable, auditable record of options, costs, owners, and decisions.
It does not run the experiments that generate evidence (information_gathering_plan) — that is Parallel Prototyping and Pilot-to-Scale Gate; nor does it set the exercise bar for committing to any single option (commitment_threshold) — that is Real Options Contract. This artifact governs the set; other mechanisms decide within it.
Related¶
- Instantiates: Option Preservation — it is the governed memory that keeps the whole option set balanced, owned, and pruned.
- Sibling mechanisms: Contingency Plan with Triggers · Modular Design Option · Parallel Prototyping · Pilot-to-Scale Gate · Real Options Contract · Reversible Decision Protocol · Scenario Planning Workshop · Staged Investment · Rolling Forecast Review
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Portfolio Exploration Backlog operates as a persistent ledger, log, register, or case record that preserves history and traceability because it keeps a governed register of exploratory options — each with an owner, a carrying cost, and kill criteria — so the option space stays balanced and pruned instead of hoarded.
Independent corroboration: The frozen evidence defines Portfolio Exploration Backlog as 'Keeps a governed register of exploratory options — each with an owner, a carrying cost, and kill criteria — so the option space stays balanced and pruned instead of hoarded', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Innovation & Entrepreneurship
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Maintaining and pruning exploratory options is rooted in innovation-portfolio and real-options practice.
Related originating lineages:
- Economics & Finance — Finance contributes real-options language and carrying-cost discipline.
- Organizational & Management Science — A governed backlog of exploratory initiatives is an innovation-portfolio management practice.
Review resolution: Light authoritative-source research resolves the primary-origin disagreement in favor of innovation entrepreneurship. OECD: Working with Innovation Portfolios directly documents the defining practice or theory described in the selected origin rationale. Other domains are retained only where the blind reviews identify material co-development or translation; broad application is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Attribution caveat: The boundary with organizational management is substantive because that tradition materially developed or translated part of the mechanism; the cited provenance places the defining form in innovation entrepreneurship.
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:
Notes¶
[n1] Zombie projects is the standing term in R&D and portfolio management for initiatives that are neither succeeding nor formally killed — they consume resources and roster slots indefinitely because ending them requires someone to own the decision. A backlog that logs owners, costs, and kill criteria exists largely to make zombies visible and killable. ↩