The words you use when something goes wrong matter more than the words you use in any other professional context. Crisis communication in English is demanding because it requires precision, speed, and emotional calibration simultaneously — and because the instinct in difficult moments is to say less, not more, and to hedge rather than own.
For non-native English speakers, the challenge is sharpened: the language of accountability, empathy, and decisive action has specific patterns in English that don't map cleanly to all other languages. Getting it slightly wrong — sounding dismissive, evasive, or falsely confident — has visible consequences when people are already on edge.
This post covers the core principles and language patterns for communicating when things are bad: with your team, with clients or customers, with the press, and with your own leadership.
The First Response: What to Say Before You Know Everything
The biggest mistake in crisis communication is waiting until you have complete information before communicating. By the time you have complete information, the story has already been told without you — by others, by absence, by silence.
The principle: communicate early, acknowledge what you know, name what you don't, and commit to when you'll have more.
Template for a first response when facts are incomplete:
"We're aware of [issue]. We're taking it seriously. Here's what we know so far: [specific known facts]. We don't yet know [specific unknowns]. We're working on this now, and we'll update you by [specific time]."
This response does four things:
- Signals awareness and seriousness (prevents the "they didn't even know" response)
- Names only what is confirmed (prevents later corrections)
- Is honest about what's unknown (prevents the appearance of hiding information)
- Commits to a specific update time (gives the audience something to hold you to)
What to avoid in a first response:
| Avoid | Why |
|---|---|
| "Everything is under control." | You don't know this yet; if it turns out not to be true, trust is destroyed |
| "This is not a significant issue." | You don't know this yet; minimising early almost always backfires |
| "We are unable to comment at this time." | Reads as evasion; invites speculation |
| "This has nothing to do with us." | Even if true, sounds defensive; prove it later |
| Silence | In most crises, silence is interpreted as either guilt or incompetence |
Acknowledging and Apologising
The language of apology in English professional contexts has specific calibration. The two most common mistakes pull in opposite directions.
Under-owning: "We regret that some customers may have experienced inconvenience..." — this is not an apology. It is a passive, hedged formulation that signals awareness without accountability. It reads as corporate defensiveness and typically makes things worse.
Over-apologising: Repeated, effusive apology without any substance can also undermine confidence. Apologising once, clearly, and then moving immediately to what's being done about it is the right structure.
The effective apology pattern:
- Acknowledge the specific impact: "This caused [specific consequence] for [specific group]."
- Take ownership: "That's our responsibility."
- Express genuine regret: "We're sorry."
- Say what you're doing: "Here's what we're doing now."
- Say what will change: "Here's what will be different."
Language examples:
"This outage meant customers couldn't access their accounts for eleven hours. That's not acceptable, and it's our fault. We're genuinely sorry for the disruption this caused. Here's what we've done to restore service, and here's what we're changing to prevent this happening again."
The specificity matters. "Some customers experienced some disruption" is not the same as "customers couldn't access their accounts for eleven hours." The second is harder to write. It also sounds much more like a company that understands what happened and is accountable for it.
Communicating With Your Team During a Crisis
How you communicate with your team in a crisis shapes their ability to function and their trust in you as a leader. The specific demands:
Be more direct, not less. The instinct under pressure is to be vague — to avoid committing to things that might change. But vagueness creates anxiety. Teams under uncertainty fill the gap with speculation, and speculation is almost always worse than the truth.
Say what you know, name what you don't, explain what comes next: "Here's the situation as I understand it right now. [Facts.] What I don't know yet is [specific unknowns]. Here's what I need from this team in the next [time period]. Questions?"
Specific language for the team communication that doesn't happen enough:
"I want to give you my honest read of how serious this is." "I don't have all the answers yet, and I'm not going to pretend I do." "Here's what I need from you, and here's what I'll do on my side." "I'll update you by [time] even if I don't have complete information by then."
The last line is particularly important. Committing to an update time and keeping it — even to say "I still don't know" — builds more trust than providing updates only when you have complete information.
Communicating Bad News to Clients or Customers
The structure is the same as above, but the relationship context is different. Clients or customers have a transactional relationship with you — they are affected by what happened but they didn't sign up to be. Their response to a crisis is shaped by two questions: "How bad is this?" and "Do I trust that they're fixing it?"
What clients need from crisis communication:
- Timely notification — before they find out from elsewhere
- Clear explanation of impact — what specifically happened to them
- Ownership — not "there was an issue" but "we made an error"
- Specific remedy — what you're doing for them, not just what you're doing generally
- Prevention — what changes so this doesn't recur
Language example for a client communication:
"I'm writing to let you know directly about something that affected your account. [Specific description of what happened and when.] This was our error, and I want to be straightforward about that. The immediate impact to you was [specific]. Here's what we've done to correct it: [specific actions]. Here's what we're changing to make sure it doesn't happen again: [specific change]. If you have questions or if there's anything I can do, I'm available at [contact]."
The personal ownership ("I'm writing to you directly") and the specificity of impact are what distinguishes this from a generic apology email.
What Not to Say: Language Patterns That Erode Trust
Certain phrases appear frequently in crisis communications and reliably make things worse:
"Lessons have been learned." This phrase has become so associated with empty corporate apology that it has essentially no value. Name the specific lesson and what changes as a result.
"We take this very seriously." Tell them what you're doing, not how seriously you take it. Seriousness without action is worthless.
"This was an isolated incident." Unless you can prove this, don't say it. If it turns out to be false, the original crisis is now combined with a credibility crisis.
"Our customers are our priority." This is a claim that should be demonstrated, not stated.
"We cannot comment on this matter." In most contexts, this reads as evasion. If there's a reason you genuinely cannot comment (legal proceedings, active investigation), name the reason: "We can't comment in detail while the investigation is active, but here's what I can tell you..."
When It's Your Personal Error
Communicating about a personal professional error — a bad decision, a missed commitment, a mistake that affected others — requires a specific kind of language that many non-native speakers find culturally uncomfortable.
In English professional contexts, especially UK and US business culture, the expected pattern is: own the error directly, don't over-explain or over-justify, say what you're doing about it, and move forward.
"I made the wrong call on this. Here's what I was thinking, but I can see now that [specific reason that reasoning was wrong]. I'm fixing it by [specific action]. I'll keep you updated."
This pattern — own, briefly explain, act, update — is the one that recovers trust most efficiently. Lengthy justification of why the error was understandable tends to suggest that you don't fully accept responsibility. Brief explanation followed by decisive action suggests that you do.
Frequently Asked Questions
How quickly should I communicate when something goes wrong?
As quickly as you have something accurate to say. In most business crises, the first communication should happen within one to two hours of the situation becoming clear — even if all that communication contains is "we're aware and we're on it, more shortly." Waiting for complete information before communicating is almost always the wrong call.
What if I don't know how bad the situation is yet?
Say exactly that: "We're still assessing the full extent of this." Uncertainty, named honestly, is preferable to either overstatement or understatement. The only commitment you need to make is to the next update: "We'll have a clearer picture by [time]."
How do I handle it when the crisis is partly someone else's fault?
Don't reference blame in your first communication. Your audience doesn't need to know whose fault it is — they need to know what's happening and what you're doing about it. If assigning responsibility matters later (e.g., for insurance, legal reasons, or transparency), do it in a separate, considered communication after the immediate situation is under control.
What are the signs that a crisis communication has made things worse?
The most reliable signals: media coverage that focuses on your response rather than the original incident, a follow-up story about "what they said vs. what really happened," customer communications that reference feeling patronised or misled, and team members who feel they weren't told the truth. The good news is that most of these signals appear quickly enough to course-correct if you're paying attention.
If any of this resonates, I run weekly sessions with founders and senior professionals on exactly this kind of thing. Free 10 minute fit call to see if it's a fit. Book here.