Realized Possible Outcome Gap Mapping¶
Compare what a process actually produced with what it could credibly have produced, then treat the gap as the main diagnostic object.
Summary¶
Compare what a process actually produced with what it could credibly have produced, then treat the gap as the main diagnostic object.
Disposition¶
This is a full gap-fill draft for realized_vs_possible_outcomes. The pre-draft check found adjacent accepted material, especially counterfactual_comparison, comparative_benchmark_validation, completeness_audit, and the generic gap_analysis component, but no accepted archetype centered on making the realized-versus-possible outcome gap the primary diagnostic object.
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
A process, program, model, production system, learning path, policy, or strategy produces an observed result, but participants do not know whether that result is excellent, adequate, wasteful, disappointing, or impossible to improve. The missing object is the realized-versus-possible gap: the structured difference between actual outcome and credible outcome possibility. Without that object, teams confuse low performance with hard limits, mistake theoretical maxima for feasible targets, over-credit lucky realization, under-invest in closable losses, or pursue fantasy gains outside the true constraint envelope.
Applicability expression6 distinct conditions
groundedpartly groundedopen
6 conditions, all required.
6Required in every casenumbered 1–6
These hold no matter which pattern applies.
Implicit possibility set · grounded
An observed result exists while the relevant feasible or possible outcome set is not explicit.
The source archetype describes the situation as follows: A result is available, but the relevant possible, feasible, theoretical, or attainable outcome set is not explicit. The normalized requirement above isolates the load-bearing portion used in this condition set.
primeRealized vs Possible Outcomes— The comparison between what a process actually produces and what it could in principle produce, with the gap as the primary object of analysis.
Suspected capacity gap · grounded
A gap is suspected between current output and latent capacity, attainable practice, or reachable alternatives.
The source archetype describes the situation as follows: There is a suspected gap between current output and latent capacity, theoretical maximum, best attainable practice, or reachable alternatives. The normalized requirement above isolates the load-bearing portion used in this condition set.
primeRealized vs Possible Outcomes— The comparison between what a process actually produces and what it could in principle produce, with the gap as the primary object of analysis.
Undefended possibility standard · open
The outcome standard comes from aspiration, comparison, memory, or politics rather than a defensible possibility envelope.
The source archetype describes the situation as follows: The outcome standard is being set by aspiration, comparison, memory, or politics rather than by a defensible possibility envelope. The normalized requirement above isolates the load-bearing portion used in this condition set.
Conflated deficit sources · open
Losses, bottlenecks, exclusions, missed options, and unrealized capacities are lumped into one deficit.
The source archetype describes the situation as follows: Losses, bottlenecks, missed options, exclusions, or unrealized capacities need to be separated instead of lumped into one deficit. The normalized requirement above isolates the load-bearing portion used in this condition set.
Multistage output loss · grounded
A multistage process can lose realized output at several points.
The source archetype describes the situation as follows: A process spans stages, channels, or transformations where realized output can disappear at multiple points. The normalized requirement above isolates the load-bearing portion used in this condition set.
domainOutbreak Underascertainment— The surveillance failure in which recorded case counts fall systematically below the true count because a multi-stage detection pipeline — symptom expression, care-seeking, testing, confirmation, reporting — filters cases with biased attenuation at each layer.
How this was matched — 3 shared + 3 branches
realized output can be lost at multiple process points
All of
- roleA process carries or produces realized output through multiple points.
- modalityRealized output can be lost or disappear within the process.
- quantifierAt least two distinct process points can contribute to realized-output loss.
…and any one of
- branchThe multiple loss points are process stages.
- branchThe multiple loss points are channels.
- branchThe multiple loss points are transformations.
Baseline-sensitive interpretation · grounded
The same realized outcome changes interpretation under different feasible baselines or constraint assumptions.
The source archetype describes the situation as follows: The same realized outcome can be interpreted differently under different feasible baselines or constraint assumptions. The normalized requirement above isolates the load-bearing portion used in this condition set.
primeRealized vs Possible Outcomes— The comparison between what a process actually produces and what it could in principle produce, with the gap as the primary object of analysis.
Other requirements and context (2)
Why these sit outside the expression
Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.
Application gate — it governs whether applying the archetype is appropriate or material, rather than defining the structural problem itself.
Supporting contextStakeholders debate whether a process is underperforming, overperforming, adequate, wasteful, or constrained.
A process, program, model, production system, learning path, policy, or strategy produces an observed result, but participants do not know whether that result is excellent, adequate, wasteful, disappointing, or impossible to improve. In this archetype, the relevant contextual consideration is: Stakeholders debate whether a process is underperforming, overperforming, adequate, wasteful, or constrained. It helps interpret the situation or strengthens the practical case for examining the archetype.
Application gateImprovement work needs to distinguish closable gap from irreducible limit, measurement error, intentional tradeoff, and unchosen opportunity.
Without that object, teams confuse low performance with hard limits, mistake theoretical maxima for feasible targets, over-credit lucky realization, under-invest in closable losses, or pursue fantasy gains outside the true constraint envelope. In this archetype, the relevant application gate is: Improvement work needs to distinguish closable gap from irreducible limit, measurement error, intentional tradeoff, and unchosen opportunity. It narrows when choosing or applying the archetype is warranted or decision-relevant.
Coverage
4 of 6 conditions grounded · 2 open.
Merge boundary¶
Keep this draft distinct when the work requires a credible possible-outcome envelope, a measured realized outcome, a decomposed realization gap, and a decision about which portions are closable. Collapse to counterfactual_comparison when the work is simply actual path versus one plausible alternative for causal inference. Collapse to generic gap-analysis components when the work is about missing records, requirements, or cases rather than possible outcomes.
Common Mechanisms¶
9 documented mechanisms across 4 implementation forms.
The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.
Analysis, Modeling & Optimization · 4 mechanisms
- Best-Demonstrated-Practice Comparator — Anchors the possible-outcome envelope on the best result actually demonstrated by a comparable unit somewhere, so the ceiling is an existence proof rather than a model.
- Counterfactual Ceiling Probe — Estimates the theoretical ceiling by asking what the outcome would have been if identified losses were counterfactually removed, and carries the answer with an uncertainty band.
- Feasible-Frontier Mapping — Derives the possible-outcome envelope from an explicit constraint model — what the system could reach given its real limits — rather than from any single achieved result.
- Loss-Channel Decomposition — Breaks a single measured realized-possible gap into named loss channels that sum back to the whole, so a lump deficit becomes an itemized account of where the outcome leaked.
Assessment, Review & Assurance · 2 mechanisms
- Closability Scoring Rubric — Scores each portion of a decomposed gap on how closable it is — recoverable latent capacity versus irreducible limit — using a shared, explicit rubric instead of intuition.
- Post-Closure Gap Remeasurement — Re-runs the gap measurement after an intervention lands, updating both the realized outcome and its uncertainty band to confirm how much gap actually closed versus what was predicted.
Decision, Gate & Allocation · 2 mechanisms
- Gap-Closure Experiment Backlog — 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.
- Theoretical-Ceiling vs Feasible-Target Review — Adjudicates between the theoretical ceiling and a feasible target, deciding which portion of the gap to pursue and formally recording the ceiling-to-target band as intentionally left open.
Record, Log & Register · 1 mechanism
- Realized-Possible Gap Table — 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.
Compression statement¶
When realized outcomes are judged without a disciplined account of what was possible, underperformance, hidden slack, lost yield, false failure, and impossible expectations blur together. Realized-Possible Outcome Gap Mapping establishes the outcome boundary, constructs a feasible possibility envelope or principled ceiling, records the realized outcome, measures the gap with uncertainty, decomposes it into constraints, losses, missed options, avoidable frictions, and intentional tradeoffs, then prioritizes closure only where evidence shows the unrealized portion is feasible, valuable, and worth pursuing.
Canonical formula: RealizationGap = CrediblePossibleOutcomeEnvelope − RealizedOutcome, decomposed by constraint × loss_channel × uncertainty × closability × value
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (7)
- Comparison: Place items in a shared frame along chosen dimensions to read off a relation between them.
- Constraint: Limits possibilities to guide outcomes.
- Feedback: Outputs influence inputs.
- Frictionless Benchmark Reasoning: A precisely stated idealised case yields a sharp invariance, irrelevance, or efficiency result that is then used not as an empirical claim but as a coordinate system against which the real world is decomposed into separately named and measured deviations.
- Latent Realizable Capacity: A power, disposition, or function that exists in a bearer continuously but manifests only when its triggering conditions are met.
- Observability: Infer internal state externally.
- Realized vs Possible Outcomes: The comparison between what a process actually produces and what it could in principle produce, with the gap as the primary object of analysis.
Also references 25 related abstractions
- Accidental Vs Essential Complexity: A system's complexity splits into the irreducible difficulty of the problem and the removable difficulty introduced by the chosen approach.
- Boundedness: Values remain within limits.
- Calibration: Aligning a system's output to a trusted reference by measuring deviation, adjusting to reduce it, and monitoring for drift.
- Counterfactual Reasoning: Hypothetical alternatives.
- Counterfactuals: Alternate hypothetical scenarios.
- Decomposition: Breaking a whole into parts that can be analyzed independently and recombined to reconstitute the whole, making complexity tractable through divide-and-conquer.
- Effect Size: Magnitude of effect.
- Eventual Realisation of Possibility: In a system subject to many independent trials, every outcome with non-zero per-trial probability eventually occurs, so design posture shifts from per-trial prevention to containment.
- Formalization: Rendering informal practice into explicit, codified, rule-governed form.
- Measurement Uncertainty and Observational Noise: Measurement noise arises from instrument and observation limits.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Feasible Frontier Gap Mapping · subtype · recognized
A subtype that compares realized outcomes with a constraint-aware feasible frontier rather than a theoretical maximum.
- Distinct from parent: The parent permits several possible-envelope types; this variant specializes in feasible-frontier construction.
- Use when: Multiple constraints shape the attainable outcome envelope; A theoretical maximum would mislead action; The goal is to identify closable distance to a feasible frontier.
- Typical domains: operations research, portfolio design, public policy, manufacturing
- Common mechanisms: feasible frontier mapping, closability scoring rubric
Unrealized Capacity Gap Review · domain variant · recognized
A capacity-focused variant that compares realized performance with latent capacity that could manifest under trigger or constraint-release conditions.
- Distinct from parent: It narrows the parent to capacity activation and manifestation gaps.
- Use when: A system appears to have dormant capability; Triggers, access, coordination, or resources limit manifestation; The goal is to separate absent capacity from blocked capacity.
- Typical domains: organizational capability, education, workforce development, platform operations
- Common mechanisms: best demonstrated practice comparator, gap closure experiment backlog
Yield-Gap Diagnostic Subtype · domain variant · likely subtype
A transformation-output subtype that compares realized yield with a theoretical or feasible maximum and decomposes the deficit into loss channels.
- Distinct from parent: It is narrower and more balance-accounting oriented than the parent.
- Use when: A process converts inputs into outputs; Mass, counts, quality units, or value units can be balanced; The deficit can be decomposed into named losses.
- Typical domains: manufacturing, data pipelines, agriculture, service operations
- Common mechanisms: loss channel decomposition, realized possible gap table
Near names: Realization Gap Analysis, Actual vs Possible Outcome Analysis, Unrealized Potential Mapping, Outcome Possibility Frontier Mapping, Outcome Gap Analysis.
Editorial Notes¶
Problem Classification¶
Classification: Uncertainty, Evidence & Inference Failure → Comparator, Value, Demand & Outcome Calibration
Problem kernel: actual outcomes lack a credible attainable comparator
Rationale: Earliest causal condition: A process, program, model, production system, learning path, policy, or strategy produces an observed result, but participants do not know whether that result is excellent, adequate, wasteful, disappointing, or impossible to improve. The missing object is the realized-versus-possible gap: the structured difference between actual outcome and credible outcome possibility. Without that object, teams confuse low performa
Independent corroboration: The earliest necessary condition in the frozen evidence is: A process, program, model, production system, learning path, policy, or strategy produces an observed result, but participants do not know whether that result is excellent, adequate, wasteful, disappointing, or impossible to improve. That is a comparator value demand and outcome calibration problem because Performance, demand, preference, regret, and realized outcomes lack a legitimate feasible benchmark that accounts for risk, constraints, and selection.
Review outcome: Independent reviewer agreement; high confidence.