Realized-Possible Gap Table¶
Comparison ledger — instantiates Realized-Possible Outcome Gap Mapping
Lays each realized outcome beside its credible possible value in one row-per-outcome ledger, turning the gap between them into an explicit, comparable quantity.
The Realized-Possible Gap Table is the archetype's central bookkeeping artifact: one row per outcome of interest, with columns for what the process actually produced, what it credibly could have produced, and the difference between them expressed in matched units. Its defining move is co-location — forcing the realized result and the possible result onto the same line, in the same units, over the same boundary, so the gap stops being a rhetorical claim ("we're leaving money on the table") and becomes a number someone can point at and dispute on the merits. The table does not construct the possibility figure and it does not explain the gap; it imports the one and sizes the other. That deliberate narrowness is what keeps it trustworthy as the shared ledger every other mechanism reads from and writes back to.
Example¶
A SaaS company's support organization argues every quarter about whether its first-contact resolution (FCR) rate is good. One VP calls 62% "industry-leading"; another calls it "a disaster." The Realized-Possible Gap Table ends the argument by making the terms explicit. The first column pins the boundary: FCR counts only Tier-1 tickets, measured over a full quarter, resolved within the first agent interaction, excluding auto-closed spam. The realized column records 62% with the query and sample that produced it. The possible column imports 78% from a best-demonstrated comparator (a peer with a near-identical product mix). The gap column then reads a flat 16 points, tagged "±3 pts, comparator-conditional."
Nothing in the table says why the 16 points exist or whether they are recoverable — but now the debate is about a specific, sourced number rather than two people's adjectives. The table is what makes every downstream step (decompose it, score its closability, queue experiments against it) possible, because they all need a single agreed figure to work on.
How it works¶
- Fix the boundary first. Each row's outcome is defined precisely — unit, time window, inclusion rules, measurement method — before any number is entered. An unstated boundary is the fastest way to a meaningless gap.
- Record the realized value with provenance. The actual result carries its source query, sample size, and window, so it can be re-derived rather than trusted on faith.
- Import, don't invent, the possible value. The possibility figure comes from a sibling envelope mechanism and is labeled with its source, so the table never smuggles in an aspiration as if it were evidence.
- Compute the gap in matched units. Realized minus possible, in one consistent unit per row (points, dollars, defects), with an uncertainty tag carried alongside.
Tuning parameters¶
- Row granularity — one headline outcome or a decomposed set of sub-outcomes. Finer rows localize where the gap lives but multiply boundary-definition work.
- Unit convention — absolute quantity, rate, or ratio-to-possible. Ratios make rows comparable across outcomes; absolutes preserve magnitude.
- Envelope-source column — whether each row names which possibility mechanism its possible value came from. Naming it prevents silent apples-to-oranges comparisons.
- Refresh cadence — a one-time snapshot or a living ledger re-run each period. Living tables catch drift; snapshots are cheaper and more auditable.
- Boundary strictness — how tightly inclusion rules are drawn. Tighter boundaries reduce noise but can define away real but messy outcomes.
When it helps, and when it misleads¶
Its strength is that it converts a vague sense of underperformance into an explicit, sourced, comparable quantity — the one object every other gap-mapping mechanism depends on. It also disciplines arguments: once realized and possible sit in the same units on the same row, "is this good?" becomes answerable.
Its failure mode is that a tidy table lends authority to a badly-drawn boundary. If the realized and possible values are measured over different populations, windows, or definitions, the gap column is arithmetic laid over an apples-to-oranges comparison, and the false precision is more dangerous than an honest shrug. The classic misuse is entering a possible value whose measurement conditions were never checked against the realized one's. The discipline that guards against this is rigorous operationalization[1] — freezing each row's boundary and unit before any figure is entered, and re-deriving both sides under the same definition.
How it implements the components¶
outcome_of_interest_boundary— each row's boundary column names the exact outcome, unit, window, and inclusion rules, separating it from proxies and intermediate outputs.realized_outcome_record— the realized column records the actual result with its measurement method and provenance, so it is auditable rather than asserted.realization_gap_measure— the gap column computes realized-versus-possible in matched units with an uncertainty tag, the quantity the whole archetype turns on.
The table imports its possibility figures rather than building them: it does not implement possible_outcome_envelope — that is Best-Demonstrated-Practice Comparator and Feasible-Frontier Mapping. Nor does it explain the gap by splitting it into gap_decomposition_scheme — that is its nearest twin, Loss-Channel Decomposition, which takes the single number this table produces and breaks it apart.
Related¶
- Instantiates: Realized-Possible Outcome Gap Mapping — the table is the ledger the whole archetype reads from.
- Consumes: Best-Demonstrated-Practice Comparator or Feasible-Frontier Mapping supplies each row's possible value.
- Sibling mechanisms: Loss-Channel Decomposition · Feasible-Frontier Mapping · Best-Demonstrated-Practice Comparator · Counterfactual Ceiling Probe · Closability Scoring Rubric · Gap-Closure Experiment Backlog · Theoretical-Ceiling vs Feasible-Target Review · Post-Closure Gap Remeasurement
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Realized-Possible Gap Table operates as a persistent ledger, log, register, or case record that preserves history and traceability because it lays each realized outcome beside its credible possible value in one row-per-outcome ledger, turning the gap between them into an explicit, comparable quantity.
Independent corroboration: The frozen evidence defines Realized-Possible Gap Table as 'Lays each realized outcome beside its credible possible value in one row-per-outcome ledger, turning the gap between them into an explicit, comparable quantity', so its operative form is Record, Log & Register.
Nearest alternative: Representation, Specification & Plan — Realized-Possible Gap Table includes features of a static representation, map, specification, schema, or prospective plan that externalizes information, but its defining operation is a persistent ledger, log, register, or case record that preserves history and traceability.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Operations Research
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: The row-wise comparison of realized value with a feasible alternative is an opportunity-loss or regret calculation used in decision analysis; economics supplies opportunity cost and valuation.
Related originating lineages:
- Economics & Finance — Counterfactual value and opportunity cost supply the economic interpretation of the gap.
Review resolution: The blind reviewers disagreed on primary lineage. Light authoritative research resolves the defining form in favor of operations_research: The row-wise comparison of realized value with a feasible alternative is an opportunity-loss or regret calculation used in decision analysis; economics supplies opportunity cost and valuation. The rejected primary is retained only when it materially shaped the mechanism, and present-day breadth is recorded separately as domain_reach=multi_domain.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
References¶
[1] Adcock, R., & Collier, D. "Measurement Validity: A Shared Standard for Qualitative and Quantitative Research". American Political Science Review 95(3), 529–546 (2001). Defines operationalization as moving from an explicitly systematized concept to indicators. registry ↩