Range comparison
The result checks dominance, overlap, expected position, and downside protection.
Ranges show robustness, not probability
The three values are structured scenarios. They do not form a confidence interval and do not say how likely each condition is.
Use the same scenario logic
Do not give one option a severe downside and the other an ordinary bad month. Define shared external conditions before estimating performance.
Look for unacceptable downside
An option with a higher midpoint may still fail a cash, safety, or service threshold in the downside case.
Read a range in decision order
Suppose Option A has values of 20, 70, and 130 across downside, expected, and upside conditions. Option B has values of 50, 65, and 85. A has the higher midpoint and upside, but B protects 30 more units in the downside case. The ranges overlap, so neither option dominates every entered condition.
First apply the failure boundary
If any result below 40 is unacceptable, A fails in the downside condition while B remains eligible. If the decision can absorb 20 and the upside matters, compare how plausible the scenarios are and whether a reversible pilot can reveal which environment is developing.
Then test shared causes
Check whether the same demand, price, or delivery event drives both ranges. Shared causes can move both options together and make apparent diversification misleading. Record the source for each endpoint and widen weak estimates instead of making both ranges look equally certain. Revisit the range when an assumption changes rather than silently moving one endpoint.
Record the shared scenario assumptions and the downside boundary that cannot be crossed.
- Shared downside condition
- Unacceptable outcome boundary
- Evidence behind each endpoint
Continue with a full decision record
Use the two-option comparison engine to preserve constraints, evidence, and missing facts beside this calculation. Read the EITHER.SO comparison methodology before treating any calculated lead as final.