5 exercises — practise balancing directness and professional tact in technical and workplace communication.
0 / 5 completed
1 / 5
Which sentence uses direct, precise wording appropriate for a postmortem, avoiding vague euphemism?
"The database connection pool was exhausted...causing 502 errors" is correct: postmortems require precise, direct language that names the exact technical cause and effect so the failure can be diagnosed and prevented in the future. Option A uses the vague euphemism "a bit of an issue", which conveys no actionable technical information. Option B uses the informal, imprecise euphemism "went sideways", which similarly fails to specify what actually happened. Option C softens the failure with "some challenges", a euphemism that avoids stating the concrete technical fault.
2 / 5
Which sentence uses an appropriately softened, professional euphemism (not blunt bluntness) when informing a client about a missed deadline, while still being honest?
"We underestimated the scope of the migration, which pushed the delivery date back by one week" is correct: it is professionally softened (avoiding blunt self-criticism like "messed up") while remaining specific, honest, and informative about the cause and the concrete new timeline. Option A is unnecessarily blunt and informal ("messed up"), which is inappropriate for client communication even though it is honest. Option C uses a vague euphemism, "stuff that came up", that gives the client no real information. Option D uses a flippant, imprecise euphemism ("basically dead") that fails to state a clear status. Option E is direct but gives no cause or revised timeline, making it unhelpfully blunt without being informative.
3 / 5
Which sentence replaces the vague corporate euphemism with direct, transparent wording in an internal engineering update?
"Reducing the on-call rotation from six engineers to four this quarter" is correct: it states the specific, verifiable change directly, which is what an internal engineering update needs for planning purposes. Option A uses the vague corporate euphemism "rightsizing", which obscures whether the rotation is growing or shrinking. Option C uses "optimizing", a euphemism that could mean almost any change and gives no concrete numbers. Option D uses "streamlining", another vague euphemism that avoids stating what specifically changes.
4 / 5
In a security disclosure, which sentence avoids euphemistic minimization and states the risk directly?
"A subset of user data, including email addresses and hashed passwords, was exposed for approximately six hours" is correct: security disclosures require direct, specific language naming exactly what data was exposed and for how long, so affected users can assess their risk. Option A uses the vague hedge "may have been some exposure of certain data elements", which minimizes and obscures the actual scope. Option C downplays the incident as a "minor data situation", a euphemism that understates severity and omits detail. Option D uses the noncommittal "potentially accessible under certain conditions", which avoids confirming what actually happened.
5 / 5
Choose the sentence that replaces the euphemism "let go" with more contextually appropriate direct HR/technical-team phrasing, while remaining professional.
"Are no longer with the company due to headcount reductions in this quarter's reorganization" is correct: it is direct and specific about the cause (headcount reductions, reorganization) while remaining professionally appropriate, striking the needed balance between honesty and workplace tact. Option A uses the softer euphemism "let go", which is common but less specific about the underlying cause than the correct answer. Option B uses the flippant, unprofessional euphemism "released into the wild", inappropriate for a serious HR context. Option D uses the vague, overly cheerful euphemism "moved on to new adventures", which misleadingly implies a voluntary departure.