Uncertainty does not make a recommendation weak. Hidden uncertainty does. A decision-maker needs to know what the evidence supports, where it may not apply and which conditions would justify a different action.
The task is to separate uncertainty about facts, interpretation, future conditions and values. Each requires a different response.
Name the type of uncertainty
| Type | Example | Useful response |
|---|---|---|
| Measurement | A metric may not capture the intended behavior | Validate the measure or add a second indicator |
| Sampling | Evidence may not represent an important segment | Bound the claim or recruit that segment |
| Interpretation | Several mechanisms could explain the pattern | Compare explanations and seek discriminating evidence |
| Forecast | Market conditions may change | Use scenarios and trigger points |
| Value judgment | Stakeholders weigh outcomes differently | Make the trade-off explicit |
Saying “more research is needed” does not tell a leader which uncertainty matters or whether waiting is justified.
Use bounded claims
Replace universal language with a claim tied to population, context, time and evidence.
Weak: “Customers find the process confusing.”
Stronger: “Among first-time small-business administrators in the observed onboarding sessions, uncertainty about account permissions delayed completion at the invitation step.”
The stronger sentence is narrower, but more actionable and defensible.
Distinguish confidence from importance
A high-impact issue can have low-confidence evidence. A well-established pattern can have modest business impact. Report both dimensions.
For each recommendation, show:
- the decision it supports;
- the evidence and counter-evidence;
- confidence in the interpretation;
- expected consequence;
- assumptions;
- reversible and irreversible elements;
- the signal that would trigger review.
Recommend an action class
Uncertainty should influence the form of action:
- Act: evidence and reversibility support implementation.
- Pilot: expected value is meaningful but important uncertainty remains.
- Prepare: monitor a trigger while removing future constraints.
- Investigate: a specific evidence gap prevents responsible choice.
- Do not proceed: the case is weak or the downside cannot be controlled.
This prevents false certainty while still moving the organization forward.
Write the recommendation in two sentences
First state the action and rationale. Then state the boundary.
Pilot the revised onboarding flow with new small-business administrators because observed permission uncertainty blocks task completion and the change is reversible. Do not generalize the result to enterprise administrators until their delegated-access workflow has been studied.
This is clearer than a long list of caveats separated from the recommendation.
End with a review condition
A recommendation is more robust when it states when it should be revisited. Use a date, threshold, event or new evidence source.
Examples include a material change in conversion, entry into a new jurisdiction, a new user segment, a policy change or contradictory support data.
Related MTF resources
See the Research and Business Analysis Practice and MTF’s Business Writing program.