Skip to content

Reserve Option Board

Reserve register — instantiates Divergence-Convergence Cycle Orchestration

Keeps rejected-but-viable alternatives on an explicit, maintained roster — recording what was chosen and holding the runners-up in a state of readiness — so a later reversal reactivates an option instead of rebuilding it.

Most selection processes treat "not chosen" as "gone," and so a setback six months later means starting the search over. Reserve Option Board is the artifact that refuses that erasure. When the cycle converges, the board records not just the winner but the fate of every serious contender — selected, combined, sequenced, held, or reserved — and it keeps the reserved options in a declared state of readiness: what is known about each, what has gone stale, and what it would cost to bring it back. Its defining property is that it makes the line between selection and deletion explicit and maintained, so the organisation gets recoverability without indecision. It is a register, not a judgment: it stores which alternatives remain live and how live they are, so that if the chosen path fails, the fallback is a warm option on a shelf rather than a cold restart.

Example

A drug-discovery program advances one lead compound series into development. Three runner-up series that had cleared early potency and selectivity screens don't get discarded — they go onto the reserve board. For each, the board records the commitment context (which series won, and at what depth of investment) and the reserve's readiness: which assays it passed, which toxicity questions are still open, and a rough cost to reactivate. A year later the lead throws an unexpected cardiotoxicity signal in vivo. Because series #2 sat on the board fully characterised rather than buried in a closed folder, the team reactivates it in weeks instead of re-running discovery from scratch. The board didn't make that call — a separate trigger did — but it is the reason a viable answer existed to switch to.

How it works

  • Record the whole disposition, not just the winner. Every contender gets a logged fate — selected, combined, sequenced, held, reserved, or rejected — with its rationale, so "we chose X" also says what happened to everything else.
  • Hold reserves in a declared readiness state. Each reserved option carries what is known, what has decayed, and its reactivation cost, so its liveness is a fact on the board rather than a hopeful assumption.
  • Keep provenance and rationale attached. A reserve travels with why it lost, which is exactly what a future reversal needs to judge whether the loss still holds.
  • Prune on a cadence. Reserves that have gone stale are revalidated or retired, so the board's promise of recoverability stays honest.

Tuning parameters

The dials that adapt this register to a specific commitment:

  • Reserve capacity — how many options are kept warm. More reserves buy recoverability but cost maintenance and can dilute commitment to the chosen path.
  • Readiness depth — fully maintained (cheap to reactivate, expensive to hold) versus archived-with-notes (cheap to hold, slow and costly to revive).
  • Retention criteria — how good a losing option must be to earn a board slot rather than an outright rejection.
  • Refresh-and-prune cadence — how often reserves are revalidated before staleness turns them into decoration.
  • Commitment-strength annotation — how explicitly the board marks the chosen path as provisional versus durable, which sets expectations about how readily a reserve can be recalled.

When it helps, and when it misleads

Its strength is recoverability: it defeats the "option cemetery" in which rejected work is lost so completely that every change of context forces a restart, and it keeps the selection-versus-erasure boundary inspectable so a reversal is cheap and legitimate. It is most valuable when the chosen path is genuinely uncertain and the runners-up were genuinely good.

Its failure modes come from reserves being either too costly or only nominal. Maintaining warm alternatives consumes real effort, and a board full of options can quietly weaken commitment — teams hedge and never fully execute the choice they made. The mirror failure is a board of stale reserves that look live but aren't, offering false security exactly when it is relied upon.[1] The classic misuse is keeping everything "just in case," so the board becomes a way to avoid ever really deciding. The discipline that keeps it honest is to bound reserve capacity, mark readiness (and staleness) truthfully, and treat the board as a record of a decision made, not a licence to defer it.

How it implements the components

Reserve Option Board fills the preserve-what-was-not-chosen components, and only those:

  • reserve_option_pool — the board is the pool: the maintained set of held-back alternatives with their readiness and reactivation cost.
  • convergence_commitment_record — it logs what was selected versus reserved versus rejected, making the selection/erasure distinction an explicit, durable record.

It does not decide when a reserve should be reactivated — that judgment is Reopening Trigger Review — and it does not generate the options it holds; those arrive as the candidate inventory from Parallel Concept Sprints. Gating investment depth is Stage-Gate Concept Review.

Notes

The board and Reopening Trigger Review are complementary halves of adaptive capacity: the board holds what to switch to, the review decides when to switch. A board without maintenance is just an option cemetery with better branding — a reserve is only real to the extent its readiness is kept current.

References

[1] The worth of preserving the ability to switch to an alternative later — rather than collapsing to a single choice now — is the intuition behind real options: optionality itself carries value under uncertainty. A reserve is only worth its carrying cost while it stays genuinely exercisable, which is why readiness, not mere listing, is the board's real product. ↩