Decision
Ask what action or choice the analysis should inform.
Analysis creates value only when people understand what you found, trust the evidence, and know what decision or next step follows.
Stakeholder management is not saying yes faster. It is aligning the question, evidence, decision and confidence level.
“Can you just build the dashboard first? We can figure out the details later.”
The fastest way to waste analytical time is to accept an output request before understanding the decision behind it.
A good analyst can clarify scope quickly, propose a minimum useful version, and explain what cannot be responsibly answered yet.
Ask what action or choice the analysis should inform.
Resolve ambiguous metrics and populations.
Agree the minimum useful output and deadline.
Communicate evidence, uncertainty, recommendation and next step.
Push back on ambiguity, not on the stakeholder. Offer a sharper path forward.
Rewrite my analytical update for a VP.
Structure:
1. What changed
2. Evidence
3. What we know / do not know
4. Recommended next action
Constraints:
- no jargon unless necessary,
- no causal language without evidence,
- preserve uncertainty,
- put the decision-relevant point first,
- keep it under 150 words.
Do not add facts that are not in my notes.Is the decision explicit?
Are metric definitions agreed?
Did I distinguish requested output from actual need?
Does the update lead with the business point?
Is uncertainty specific rather than vague?
Is the recommendation supported by evidence?
Ask what decision and audience define success.
Offer a minimum useful first version.
Lead with the finding, then evidence and caveats.
State the next action and why it follows.
Before sending analysis, ask: if the stakeholder reads only the first two sentences, will they understand the decision-relevant point?