5 exercises — opening with impact, quantifying business cost, security escalation framing, and requesting decisions with deadlines.
0 / 5 completed
1 / 5
You need to escalate a blocked infrastructure request to your VP. Which email opening is most effective?
An escalation email opening must state what is blocked, how long it has been blocked, the business impact, and what decision is needed — immediately, before any pleasantries. Option B hits all four in two sentences. Option A opens with an apology ("sorry to bother") which undermines urgency and buries the issue. Option C is vague ("some issues", "too long"). Option D names a team in a blame-attributing way ("not responding") — frame the obstacle as a process gap, not a people failure.
2 / 5
Complete this escalation: "This ticket _____ (block) two sprint deliverables. I _____ (already/escalate) to the infrastructure team lead on May 19 with no response. At current trajectory, the release _____ (miss) its June 3 deadline."
Is blocking (present continuous) describes an ongoing, active obstruction happening right now — the correct tense for a current blocker. Have already escalated (present perfect) links a past action (the May 19 escalation) to the present situation — it shows a prior step was taken and the problem persists. Will miss (future simple) is a factual prediction about a future deadline. Option D ("is going to miss") is grammatically possible but weaker — "will miss" is more decisive and confident in an escalation context.
3 / 5
Which sentence correctly quantifies the impact in an escalation email?
Escalation emails should quantify impact in business terms that a VP or director can act on: cost per day, SLA breach amounts, milestone slippage in concrete days. Option B does exactly that — $4,200/day in SLA credits and a 1:1 day slip on Q2. This gives the escalation recipient everything they need to justify action to their own stakeholders. Options A, C, and D use vague intensifiers ("significant", "quite serious", "very high priority") — these are not actionable because they don't tell a decision-maker what the actual cost of inaction is.
4 / 5
You've been asked to escalate an unresolved security vulnerability. What must your escalation email include that other escalations don't typically require?
Security escalations require standardized severity framing that lets recipients understand risk without domain expertise. The CVSS score (e.g., CVSS 9.1 / Critical) is universally understood. Attack surface scoping ("publicly reachable API endpoint") tells leadership who is at risk. Public disclosure status (CVE published, active exploitation in the wild) drives legal and PR considerations. Together these let a VP or CISO decide whether to invoke the incident response process immediately or schedule a fix. Repeating "urgent" (Option C) doesn't add information — severity scores do.
5 / 5
Choose the best closing for an escalation email: "I _____ (request) a decision by EOD Thursday so we _____ (can/keep) the June 3 release on track. I _____ (be/happy) to join a 15-minute call today or tomorrow to discuss options."
Request (present simple) is the most direct and professional register for a formal written request — it is declarative and confident. Can keep (present simple modal) expresses a condition: given the decision, the release can stay on track. Am happy (present simple) is the standard English phrase for expressing willing availability. Option A ("am requesting") uses present continuous which sounds more tentative and informal. Option C uses "would" throughout, which makes the email sound too conditional and soft for an escalation that needs action. Option D uses present perfect ("have requested") which refers to the past — but this is a new request being made right now.