Which Assumption Could Change Our Decision?
An estimate can look convincing because its uncertain inputs were hidden. Vary the assumptions and find where the preferred design changes.
13 sections · 4 questions · 1 coding challenge
The arrow keys move between sections too.
Measurements Need an Account of Their Uncertainty
BOTIE
We will borrow the question about sensitivity, using a simple design comparison. Our scenarios are chosen alternatives for an uncertain cost. They are not a confidence interval, and we will not assign probabilities to them without evidence.
Sources for this history
The New Model Wins, Unless Our Cost Estimate Is Wrong
Botie’s candidate catches more faults than the old rule, but it requires more inspections. Our first calculation says it is worthwhile. That conclusion depends on how costly a missed fault is, and the team only has a rough estimate.
We can inspect that dependence directly. Keep the observed policy differences fixed, vary the uncertain cost, and find where the decision changes. Then we know which missing evidence deserves attention.
Costs and policy differences are invented. The scenario list is not a probability distribution.
Step 1 of 2
Hold the observed difference fixed
Compared with the baseline, the candidate misses two fewer faults but requires five extra inspections. Each inspection costs 4 units.
| Miss cost | Avoided miss loss | Extra inspection cost | Net savings |
|---|---|---|---|
| 5 | 10 | 20 | −10 |
| 10 | 20 | 20 | 0 |
| 20 | 40 | 20 | 20 |
5
- Avoided miss loss
- 10
- Extra inspection cost
- 20
- Net savings
- −10
10
- Avoided miss loss
- 20
- Extra inspection cost
- 20
- Net savings
- 0
20
- Avoided miss loss
- 40
- Extra inspection cost
- 20
- Net savings
- 20
Step 2 of 2
Ask what we need to learn
Some inputs come from the evaluation; others still need investigation.
| Input | Status | Useful next evidence |
|---|---|---|
| Misses avoided | Sample estimate | More representative labelled cases |
| Extra inspections | Sample estimate | Replay the policy on later shifts |
| Cost per miss | Uncertain consequence | Review downtime and repair records |
Misses avoided
- Status
- Sample estimate
- Useful next evidence
- More representative labelled cases
Extra inspections
- Status
- Sample estimate
- Useful next evidence
- Replay the policy on later shifts
Cost per miss
- Status
- Uncertain consequence
- Useful next evidence
- Review downtime and repair records
Show what the conclusion depends on
One input remains a list of scenarios, so the calculation returns one conclusion per assumption instead of hiding the range.
Where does the candidate stop paying for itself?
Change the cost per miss or the extra inspections. Positive savings favour the candidate under this cost model.
BOTIE
Net savings for each miss-cost scenario
- 0-10
- 10
- 220
Follow the operations
1. Estimated misses avoided
2
2. Miss cost scenarios
- 05
- 110
- 220
3. Multiply
- 010
- 120
- 240
4. Additional inspections
5
5. Cost per inspection
4
6. Multiply
20
7. Subtract
- 0-10
- 10
- 220
8. Result
- 0-10
- 10
- 220
These are conditional estimates, not confidence bounds. Policy effects, upkeep, and relationships between uncertain inputs need separate evidence.
1. Write the difference between designs
We already know how to calculate a policy’s loss. Subtract candidate loss from baseline loss to obtain savings. We can simplify that difference into avoided miss loss minus added inspection cost.
This arrangement shows exactly which assumption drives the recommendation. Keep the sign convention beside it: positive savings favour the candidate, negative savings favour the baseline.
Savings = avoided_misses × cost_per_miss
− extra_inspections × cost_per_inspection
At miss cost 20: 2 × 20 − 5 × 4 = 20 unitsThe comparison covers these consequences only. Added upkeep would reduce savings further.
2. Try values that could plausibly change the answer
Use a low, central, and high estimate only if those labels mean something in the problem. You might have several documented operating scenarios instead. There is no requirement to use three.
Here we try miss costs of 5, 10, and 20 units because they show a change of sign. The list is an exploratory choice. It has no implied probability or confidence level.
A result that stays positive across a justified range is more robust to that input than one that changes sign after a small revision.
3. Find the break-even value
At break-even, savings are zero. If avoided misses is positive, divide the extra inspection cost by the avoided miss count to find the miss cost at that boundary.
If avoided misses is zero, that division is undefined. A candidate that adds inspection work while avoiding no misses cannot justify itself through this particular benefit. A different benefit would need to be stated.
0 = 2 × cost_per_miss − 5 × 4
Break-even cost_per_miss = (5 × 4) / 2 = 10 unitsAt exactly the boundary, these terms tie. A tie does not establish that the designs are equivalent in every other respect.
A vector makes the sweep visible
Each input cost produces its own savings estimate. We round only for display if needed.
import numpy as np
miss_cost = np.array([4., 8., 12., 16.])
savings = 3*miss_cost - 6*5
print(savings.tolist())[-18.0, -6.0, 6.0, 18.0]The sign changes within this range. The later challenge uses a different policy difference.
Check yourself
Questions on Parts 1 to 3
Question 1 of 2
What does the break-even miss cost represent?
Use the information below.
A candidate avoids 2 misses and adds 5 inspections costing 4 units each. Miss cost is uncertain.4. Sensitivity describes change, not plausibility
For this linear comparison, one extra unit of miss cost changes savings by the number of avoided misses. That slope is a sensitivity. It tells us how strongly the output responds, but not how likely a large cost change is.
An input with a small sensitivity can still matter if its uncertainty range is large. Conversely, a sensitive input that is measured precisely may contribute little uncertainty. Examine both properties.
Do not call an arbitrary parameter sweep a statistical confidence interval. A probability statement needs an uncertainty model and supporting assumptions.
5. Change related inputs together when needed
The number of faults, inspection duration, and server load may all increase during the same difficult operating conditions. Varying one input at a time can miss that combination. Describe scenarios that preserve plausible relationships.
For example, a busy shift might contain more pumps and longer inspections because access is harder. A design that passes isolated changes could fail their combination. On the other hand, combining every worst value may describe an impossible scenario.
Keep a reason for each scenario and identify which conditions the design promises to handle.
6. Choose the next measurement deliberately
If the recommendation changes within a plausible miss-cost range, review the evidence for that cost before polishing a model score. If capacity fails under the busy-shift scenario, measure inspection duration there.
There may also be a reason to choose a design that is slightly worse under the central estimate but acceptable across more plausible conditions. Explain the trade to the person responsible for the decision.
Botie’s workshop leaves the uncertain inputs connected to the calculation. The conclusion can move when the assumptions move.
Check yourself
Questions on Parts 1 to 6
Question 1 of 2
What should we call the results?
Use the information below.
Costs [5,10,20] were chosen to explore outcomes. No distribution was fitted.Try it with Botie
Build with Botie
Write and run Python