IT incidents—such as outages, software bugs, or security alerts—are a routine part of managing business technology. The effectiveness of incident management depends not only on technical resolution but also on how clearly the situation is communicated across the organization.
It’s important that communication during an IT incident separates technical details from business impact.
Technical communications focus on the nature of the incident, technical root cause, and steps to resolution.
Business communications address what the incident means for users, customers, and ongoing operations.
Tactical vs. Strategic Impact
A key aspect of effective communication is differentiating between tactical and strategic impact:
This refers to the immediate, short-term effects of the incident. For example, a payment processing outage might delay customer transactions or require manual workarounds. Tactical impact is about “what’s happening right now,” how it disrupts daily operations, and what steps are being taken to restore service.
This concerns whether the incident has any meaningful effect on the organization’s long-term goals, strategic initiatives, or overall direction. In most cases, IT incidents do not affect strategic objectives. Communication should make it clear to leadership and stakeholders if an incident is limited to tactical impact, helping to avoid unnecessary escalation or concern.
1. Technical Teams
“The payment gateway service is returning intermittent 503 errors due to a backend database lock. We are currently restarting the affected services and monitoring log files for additional errors. No data loss has been detected, and all failed transactions are being queued for reprocessing.”
2. Business Operations
“We are experiencing a temporary issue with our payment processing system. Some transactions may be delayed. Our IT team is actively working on a resolution, and we expect normal operations to resume within the hour. In the meantime, please inform customers of the delay and assure them that no payments have been lost.”
3. Executive Leadership
“There is a temporary disruption in our payment processing system that is affecting transaction completion for some customers. The issue is strictly tactical and does not have any impact on our strategic initiatives or financial targets. The technical team is addressing the problem, and we anticipate full resolution shortly. No long-term risk or reputational impact is expected.”
Segment communications by audience and need.
Be explicit about whether an incident has any strategic impact—most do not.
Use plain language for non-technical stakeholders, focusing on what matters to them.
Provide timely updates and clarify as the situation evolves.
Clear communication during IT incidents means more than just relaying facts—it means ensuring that all audiences understand the scope of the impact, especially the difference between tactical disruptions and strategic threats. Consistently making this distinction helps manage expectations, reduces unnecessary concern, and supports more effective incident management.
This site and all contents is © 2025 Tymans Group BV