When an incident strikes, your team’s technical response is only half the story. The other half is how you communicate what is happening, why it matters, and what you are doing about it. Executives need to understand the business impact and make decisions. Customers need to feel informed and reassured. Both audiences are judging your competence based on the quality of your updates, not just your code.

Define Your Audience and Their Needs

Executives and customers have fundamentally different concerns during an incident. Executives care about revenue, reputation, legal exposure, and resource allocation. They need a concise summary of the impact, the expected duration, and the escalation path. Customers care about whether they are affected, when service will be restored, and what they should do in the meantime. They need a clear, honest statement that acknowledges the problem and sets realistic expectations. Sending the same message to both groups almost always fails. Tailor your language, level of detail, and channel to each audience.

Timeliness: Communicate Before They Ask

Silence erodes trust faster than a bad update. If executives learn about an incident from a customer or the press, you have already lost credibility. Establish a clear trigger for the first notification. For a major incident, the first communication should go out within minutes of the initial detection. It does not need to be complete. A simple message that states what is being investigated, what systems are involved, and when the next update will come is sufficient. For customers, the threshold may be higher, but once you confirm that a significant number of users are affected, send a public status update. Waiting for full root cause analysis before communicating is a common mistake. Partial information, delivered quickly, is far better than perfect information delivered late.

Structure Your Message for Clarity

Every incident update should answer the same five questions: What happened, what is the impact, what is being done, when will it be resolved, and where can they get updates. For executives, lead with the business impact. State the number of affected customers, the revenue at risk, and the expected recovery time in plain terms. For customers, lead with the user impact. Explain what functionality is degraded or unavailable, and provide a workaround if available. Use a consistent format for all updates. This reduces confusion and helps recipients scan the information quickly. A standard template with fields for time, status, affected systems, and next steps makes it easy for both the writer and the reader.

Acknowledge Impact and Next Steps

People want to know that you understand the gravity of the situation. Do not minimize the impact. If a feature is completely down, say so. If you are not sure about the scope, say that too. Executives appreciate candor because it allows them to make informed decisions. Customers appreciate honesty because it builds long term trust. After acknowledging the impact, always state the next steps. For executives, that might mean a decision they need to make, such as whether to deploy a hotfix or roll back. For customers, the next step might be a promise to follow up with a postmortem or to notify them when the service is restored. Never leave the recipient wondering what comes next.

Align Internal and External Messages

Nothing undermines trust faster than contradictory updates. The engineering team, the customer support team, and the executive team must share the same facts. This requires a single source of truth during the incident. Use a shared incident log or a dedicated communication channel that all teams can see. Before any external communication goes out, the incident commander should review and approve it. This does not mean everything needs to be sanitized, but it does mean that the external message should not contain speculation, internal blame, or unverified data. Aligning messages ensures that a customer hears the same story from support that the executive hears from engineering.

Post Incident: The Follow Up That Builds Trust

The incident is resolved, but the communication is not over. Executives and customers both expect a follow up. For executives, this means a summary report that includes the timeline, the root cause, the impact, and the actions taken to prevent recurrence. Keep it brief and focus on business outcomes rather than technical details. For customers, the follow up should acknowledge the inconvenience, explain what happened in plain language, and describe what you are doing to improve. Share the postmortem if appropriate, but only after removing any sensitive information. A well written post incident update can strengthen trust because it shows that you take reliability seriously and that you learn from failures.

Consistent, honest, and timely communication during and after incidents is a leadership skill that directly affects your team’s reputation and your organization’s resilience. By treating each audience with respect and tailoring your messages to their needs, you turn a potentially damaging situation into an opportunity to demonstrate competence and transparency. Start by defining your notification thresholds, building a simple template, and establishing a review process. Over time, these practices become ingrained, and your stakeholders will trust you to handle the next incident with the same clarity and professionalism.