5 exercises — precise quantification in performance reports, incident metrics, and capacity planning.
Key patterns:
A threefold / twofold reduction/increase — multiplicative noun phrase
P99/P95 latency of [X ms] — standard percentile metric format
In the order of / approximately / roughly — hedged estimates
From X to Y, a reduction of Z% — before/after plus derived change
0 / 5 completed
1 / 5
A performance report needs to describe a dramatic improvement in build time. Which sentence quantifies the improvement most precisely and professionally?
"A threefold reduction" is precise quantification using a multiplicative noun phrase. It is more formal than "3x faster" and appropriate for written performance reports. Adding the before-and-after figures (from 18 minutes to just over 6 minutes) makes the metric independently verifiable. "Just over" is an honest hedging quantifier when the exact figure is 6.1 minutes. Option C is informal (or so). Option D is nonsensical (by about a lot). Related patterns: "a 40% reduction in", "a twofold increase", "reduced by a factor of three".
2 / 5
An incident metric report describes the tail latency. Which sentence is most precise for a p99 latency figure?
P99 latency (99th percentile) is the standard metric for describing tail latency in incident reports. A precise report names the metric (P99 latency), the peak value (1,240 ms), the time frame (during the incident window), and the baseline for comparison (180 ms). Option D uses north of — an informal approximation idiom that has a place in verbal communication but is too vague for a written report. Options A and C are uselessly vague. Related patterns: "P50/P95/P99 latency of", "error rate of approximately", "in the order of".
3 / 5
A capacity planning report estimates future traffic. Which sentence uses quantification language most appropriately for an estimate?
"In the order of [figure]" is a quantification hedge for estimates — it signals that the figure is an approximation of the correct magnitude rather than a precise measurement. Pairing it with an explicit basis (3× growth assumption over twelve months) makes the estimate auditable: if the assumption changes, the estimate changes proportionally. Option A is vague; option C is grammatically incoherent; option D is not a sentence. Related patterns: "approximately", "roughly", "up to", "at least".
4 / 5
A sprint review report needs to describe a partial improvement in error rate. Which sentence quantifies it most accurately?
Precision in sprint reviews requires before/after figures plus the derived percentage change. Reporting both the absolute values (2.3% to 0.4%) and the derived reduction (approximately 83%) allows stakeholders to verify the arithmetic and understand both the relative and absolute scale. Approximately hedges the derived percentage because 83.% is not a round number. Option C uses informal approximation (or something). Option D is too qualitative for a metrics report. Related patterns: "a 40% reduction in", "down from X to Y, a decrease of Z%".
5 / 5
A capacity planning document warns about approaching a system limit. Which sentence quantifies the risk most effectively?
"North of [threshold]" is an informal but widely used idiom in engineering communication meaning "above" — it is appropriate in sprint reviews and verbal updates but less so in formal reports. However, in this sentence it is balanced by precise figures: 87% (current), 80% (threshold), and approximately 2 GB per day (growth rate). The combination gives operations teams the three data points they need to plan a response. Option A and C lack the specific numbers required for action. Related patterns: "exceeding the target by", "within N% of the limit", "growing at a rate of".