How do I communicate during an incident without causing panic?

Use factual, specific language: state what's happening, who's affected, what you're doing, and when you'll update next. Avoid vague phrases like 'something is wrong' and emotional language. Example: 'We're investigating elevated latency affecting checkout. 15% of users impacted. Next update in 30 minutes.'

What's the difference between 'issue' and 'incident' in tech?

An 'issue' is a general problem or bug. An 'incident' is a significant event that impacts users or services and requires immediate response. Incidents are typically classified by severity (Sev-1 being most critical). Use 'incident' for outages and major problems; use 'issue' for smaller bugs or concerns.

How formal should my Slack updates be?

Match your audience. In team channels, informal is fine: 'Heads up—API might be slow today.' For cross-functional updates or executive visibility, be more formal: 'Please be advised that API response times may be elevated due to scheduled maintenance.' When in doubt, slightly more formal is safer.

Is 'media' singular or plural in English?

Grammatically, 'media' is plural (singular: 'medium'), so 'The media are...' is technically correct. However, many native speakers use it as singular, especially in American English. 'News' is always singular: 'The news is good.' 'Information' is uncountable—never say 'informations.'

What vocabulary should I use for a weekly engineering digest?

Use action-oriented headlines: 'shipped,' 'launched,' 'resolved,' 'opened for review.' Structure with clear sections: Wins, Updates, Action Items. Keep items brief (2-3 sentences), link to details, and end with what's coming next week.

How do I say a project is delayed without sounding negative?

Use 'at risk' for potential delays: 'The timeline is at risk due to dependency on the design team.' For confirmed delays, be direct but solution-focused: 'We've revised the target date to March 15 to ensure quality. Here's the updated plan...' Avoid blame language.

How to Deliver Updates and Announcements in English at Work

Pronunciation Guide: Terms That Trip Up ESL Speakers

These terms appear frequently in updates and announcements. Getting the stress and pronunciation right helps you sound confident and professional.

monitoring /ˈmɒnɪtərɪŋ/

MON-i-ter-ing

Saying 'mon-i-TOR-ing' with stress on third syllable

stakeholder /ˈsteɪkˌhəʊldər/

STAKE-hohl-der

Pronouncing 'stake' as 'stack'

occurrence /əˈkʌrəns/

uh-KUR-ence

Adding extra syllable: 'oc-cur-rence'

archive /ˈɑːkaɪv/

AR-kive

Saying 'ar-CHEEV' like French

postmortem /pəʊstˈmɔːtəm/

post-MOR-tem

Saying 'post-mor-TEM' with final stress

Gathering Information: How Tech Professionals Collect News

Before you can deliver updates, you need to gather information from multiple sources. In tech workplaces, this happens through monitoring dashboards, tapping Slack channels, and attending standups or syncs.

Just as journalists tap sources for stories, engineers monitor alerts and check status pages. Product managers gather updates from multiple teams before issuing a statement to stakeholders. The key vocabulary here connects traditional news-gathering to modern tech communication.

News Term	Tech Workplace Equivalent	Example Usage
tap sources	check with teams / ping stakeholders	I need to tap my sources in Platform before the all-hands.
monitor	track dashboards / watch alerts	We're monitoring latency metrics after the deploy.
press conference	all-hands meeting / incident bridge	The CTO will address this at the all-hands tomorrow.
issue a statement	post an update / send a communication	We need to issue a statement to affected customers within the hour.
coverage	visibility / attention	This outage is getting coverage from the exec team.
deadline	SLA / target / due date	We have a hard deadline of 5pm for the incident postmortem.

Culture Tip: The 'Single Source of Truth'

In tech, we often designate one channel or document as the 'single source of truth' for updates. During incidents, this might be a dedicated Slack channel. For projects, it's usually a status doc or JIRA board. Always clarify where people should look for the latest news.

Scenario 1: Writing Incident Updates and Post-Incident Communication

When an incident breaks (becomes known), you need to communicate quickly and clearly. Incident communication follows a predictable structure: what's happening, who's affected, what we're doing, and when we'll update next.

The vocabulary of urgency matters here. Compare 'we have an issue' (vague) with 'we're experiencing elevated error rates affecting 15% of users' (specific). Stakeholders need facts, not drama.

❌ Vague / Weak	✅ Clear / Professional
Something is wrong with the database.	We're investigating elevated latency on the primary database cluster.
Users are complaining.	We've received reports of checkout failures from approximately 200 users.
We're working on it.	The on-call engineer is actively investigating. Next update in 30 minutes.
It's fixed now.	The issue has been resolved. We'll share a postmortem by EOD tomorrow.
This was a bad incident.	This was a Sev-1 incident with significant customer impact.

Use 'investigating' not 'looking into' for formal updates
Specify impact: 'affecting X% of users' or 'impacting the checkout flow'
Give a timeline: 'Next update in 30 minutes' builds trust
Avoid blame language: 'The deploy caused issues' not 'John's deploy broke everything'

Grammar Note: Active vs Passive in Incidents

Use passive voice to focus on the issue, not the person: 'A configuration change was deployed' (neutral) vs 'Someone deployed a bad config' (blame). However, use active voice for actions: 'We are investigating' shows ownership.

Scenario 2: Delivering Project Status Updates in Team Meetings

Status updates in standups and team meetings require different vocabulary than incident communication. Here, you're reporting progress, flagging blockers, and keeping stakeholders informed.

The key is to be concise but complete. A good status update hits the headlines (main points) without burying people in details they don't need.

Phrase	When to Use	Example
on track	Progress is as expected	The API migration is on track for the Q2 milestone.
at risk	There's potential delay	The frontend work is at risk due to a dependency on the design team.
blocked on	Can't proceed without something	I'm blocked on code review from the security team.
flagging	Raising awareness of an issue	I'm flagging a potential scope creep in the requirements.
parking	Postponing discussion	Let's park this discussion for the retro.
circling back	Returning to a topic	Circling back on the database decision from last week...

Informal (Slack / Standup)	Formal (Email / Status Doc)
Quick update: we shipped the fix 🎉	Update: The hotfix for JIRA-1234 was deployed to production at 14:00 UTC.
Heads up—might slip to next week	Please note that the delivery date may be extended to the following week.
Need eyes on this PR	This pull request requires review before we can proceed.
Hit a snag with the auth service	We encountered an unexpected issue with the authentication service integration.

Scenario 3: Writing a Slack Digest or Engineering Newsletter

Weekly digests and engineering newsletters summarise the week's news for your team or org. Like an editor compiling a newspaper, you're curating what matters most and presenting it clearly.

Good newsletters have clear sections, scannable headlines, and enough context for readers who missed the original announcements. Think of each item as a headline that hits the key points.

Lead with the most important news (the 'exclusive' or biggest story)
Use consistent formatting: emoji headers, bold for names/dates, bullet points for details
Link to sources: 'Full RFC here' or 'See the postmortem doc'
End with a call to action or preview of next week
Keep each item to 2-3 sentences maximum

Example newsletter opening: '📰 This Week in Platform Engineering — The big news: we shipped the new caching layer (see #platform-wins for celebration). Also: RFC-047 on API versioning is open for comments until Friday. And a reminder that the Q3 planning kickoff is Monday at 10am.'

Notice how this hits the headlines quickly, provides context, and tells readers where to find more information.

Vocabulary Note: 'News' in Tech

In tech, 'news' can mean announcements (company news), incidents (breaking news), or updates (project news). Match your tone to the type: celebratory for wins, neutral for incidents, informative for updates.

Common Mistakes: What We Hear at Work vs Better English

❌ Heard at Work	✅ Better English
The media is reporting the outage.	The media are reporting the outage. (Media is plural)
We need to give an update about the situation.	We need to issue an update on the situation.
The news are not good.	The news is not good. (News is uncountable singular)
I will air my concerns in the meeting.	I will raise my concerns in the meeting. (Air views is more formal)
Let me give you some informations.	Let me give you some information. (Information is uncountable)

Grammar Trap: Media (Plural) vs News (Singular)

Media is technically plural ('The media are covering this'), though many native speakers treat it as singular in informal speech. News is always singular ('The news is good'). Information is uncountable—never 'informations'.

English for Developers Bundle