Choose the best phrasing for 5 real scenarios: introducing a chart, explaining a trend, making a prediction, answering "why?" questions, and handling unprepared questions professionally.
Data presentation formula
Lead with insight: "This chart shows X. The key takeaway is Y." — not "This is a chart."
Anchor percentages: "40% improvement — from 850ms to 510ms" — always give the baseline
Hedge projections: "Based on these trends, we expect..." — not "This proves..."
Structure explanations: data → reason → implication
0 / 5 completed
1 / 5
You are presenting a bar chart showing monthly active users over the last 6 months. Which opening line best introduces the chart to your audience?
Why B is the model chart introduction
A strong chart introduction does three things immediately:
Names the visual: "this graph" — orients the audience
States what it shows: "monthly active users" — the metric
Gives the headline insight: "grown steadily... from 12,000 to 18,000" — the so what
Why A fails: "This is a bar chart" describes the format, not the content — your audience can see it's a bar chart.
Why C and D fail: They add no value. The audience can see the data is on the slide. Your job as a presenter is to guide interpretation.
Chart introduction phrases:
"Looking at this graph, we can see that..."
"This chart shows [metric] over [time period]. The key takeaway is..."
"Let me draw your attention to [specific element] — notice that..."
"What this data is telling us is..."
Rule: Always lead with the insight, not the chart type.
2 / 5
Your app's response time improved by 40% after a refactor. A stakeholder asks you to explain this result. Which phrasing is most professional and precise?
Why B is the professional standard: anchor, delta, cause
Presenting a percentage improvement requires three elements to be credible:
Anchor: "from 850ms" — the baseline. Without this, "40%" is meaningless
Delta: "to 510ms, a 40% improvement" — the change, in both absolute and relative terms
Cause: "following the database query optimisation in sprint 14" — attributes the result
Why "a lot" and "much faster" fail: Vague qualifiers sound unscientific and make stakeholders less confident in your analysis. Numbers command attention.
Why D fails despite being longer: "Various improvements... over a number of weeks" is a hedge that actually undermines credibility — it sounds like you don't know what caused the improvement.
Metric presentation phrases:
"Response time dropped from [X] to [Y], a [Z]% improvement."
"This represents a [Z]% reduction compared to our baseline of [X]."
"The improvement is attributable to [specific change]."
3 / 5
You are presenting a trend and want to make a prediction. Which phrasing is most appropriate for professional data communication?
Why B is the gold standard: confident but hedged
Data-based predictions require two things in tension:
Confidence: you are not guessing — you are extrapolating from real data
Honesty: projections are projections, not certainties
B achieves both:
"Based on these trends": grounds the prediction in evidence
"we expect": professional-level confidence without overclaiming
"assuming growth rates remain consistent": states the assumption explicitly — this is rigorous
Why A and D fail: "Proves" and "will definitely" are too strong. Data shows correlations and trends — it rarely "proves" a future outcome. Overclaiming damages your credibility when the prediction misses.
Why C fails: "I think maybe... if things go well" is so hedged it provides no value. Excessive hedging reads as lack of confidence in your own analysis.
Prediction hedging phrases:
"Based on current trends, we project..."
"If this trajectory continues, we expect..."
"Our model suggests... though this assumes [condition]."
"The data indicates... with the caveat that..."
4 / 5
During your presentation, a stakeholder asks "Why did conversion drop 15% in March?" — a metric you have data on. What is the best response structure?
Why C is the professional answer structure: data → reason → implication
When asked to explain a metric movement, the best structure is:
Acknowledge and anchor to data: "The data shows [what happened]" — start with facts, not opinion
Give the most likely cause: "The most likely cause is [X]" — be specific; use "most likely" to signal inference, not certainty
Support with evidence: "supported by [Y]" — corroborating data point makes the explanation defensible
State the implication: "The implication is [Z]" — what should be done or monitored
This structure works even when you are uncertain — you can replace step 2 with "We have two hypotheses" and still sound rigorous.
Why A fails: "Let me get back to you" is acceptable only when you genuinely don't have the data. If you do have data, use it.
Why D fails: "Many factors... this kind of pattern" is evasive and vague — it reads as not having done the analysis.
Useful phrases for metric explanation:
"Looking at the supporting data, the most likely driver is..."
"We see a correlation with [event/change] — our hypothesis is..."
"The data points to [X]. To confirm, we would need to [Y]."
5 / 5
A stakeholder asks about a specific metric you did not prepare for today's presentation. What is the most professional response?
Why C is the professional "I don't know" for data presentations
In data presentations, you will always be asked about something you didn't prepare. The professional response has four parts:
Validate the question: "That's a fair question" — signals the question is reasonable, not a problem
Be honest about the gap: "I don't have that number in front of me" — transparent without being apologetic
Commit to action: "Let me pull the data" — shows you can and will find it
Set a deadline: "by end of day" — makes the commitment concrete
Why A (making up numbers) is always wrong: Stakeholders often know the real numbers. Even if they don't, a fabricated metric will eventually be checked. This destroys trust permanently.
Why B fails: "I don't track that metric" may be true but sounds defensive. If the question is reasonable, the implied follow-up is "maybe you should track it."
Why D fails: Dismissing a stakeholder's question is a career-limiting move in most organisations.
Professional "I don't know" phrases for data contexts:
"I don't have that number to hand — I'll check and follow up."
"Great question — that's outside today's scope but worth digging into. Can I get back to you?"
"I want to give you the accurate figure rather than guess — let me verify and send it over."