The incident communications brand is the version of you that shows up when things are broken — the status page, the outage update, the apology after the fact — and it is the version customers remember longest. When the product works, the brand is doing easy work; when it fails, every word you publish is read closely, sceptically, and emotionally. Most companies leave these moments to engineering or legal, which is why so many incident updates read as either robotic telemetry or evasive non-statements. The response is the brand, and designing how you communicate in failure is one of the most revealing brand decisions you can make.
Why your incident communications brand is your truest test
A brand is easy to maintain when everything is working. Anyone can sound confident and warm on a good day. The character of a brand is revealed under pressure — when the service is down, customers are angry, and there is genuine uncertainty about what happened and when it will be fixed. The incident communications brand is what the organisation actually sounds like at that moment, stripped of the marketing polish it can afford in calmer times. Customers know this intuitively, which is why they read an outage update far more carefully than a feature announcement: they are looking for evidence of who you really are when it costs you something to be honest.
This is why leaving incident communications to whoever happens to be on the bridge call is a strategic mistake. The status page and the apology are not operational exhaust; they are the brand speaking at the moment it matters most, and an organisation that has not decided how it wants to sound in failure will default to sounding defensive, vague, or coldly technical — none of which is the impression it would choose.
The status page is a brand surface
The status page is the clearest example of a brand surface that companies hand to engineering and forget. It is where customers go in their moment of highest anxiety, and what they find there — the tone, the speed, the specificity of the updates — forms a lasting judgement. A status page that updates promptly, in plain language, acknowledging the problem without minimising it, communicates competence and respect. One that stays green while customers are clearly affected, or updates hours late in impenetrable jargon, communicates that the company is either not paying attention or not being straight. Atlassian's widely cited guidance on incident communication best practices distils the discipline well: communicate early, communicate often, and keep external updates short and human rather than technical.
Designing the status page as a brand surface means deciding in advance what it sounds like, who is empowered to post to it, and how quickly. Those are brand and operational decisions made calmly before an incident, not improvised by a stressed engineer at 3am, because the quality of the communication in the moment is almost entirely determined by the preparation before it.
The grammar of a good incident update
A good incident update follows a recognisable grammar, and it is worth codifying. It acknowledges the problem plainly and early, before all the facts are in, because silence reads as either ignorance or concealment. It says what is known and what is not, without speculating or over-promising a fix time that may slip. It is specific about impact — who is affected and how — so customers can make their own decisions rather than guess. And it is written in the brand's own voice, human and direct, rather than in the passive, agentless construction that organisations reach for when they want to admit a problem without anyone appearing to own it. "We are investigating reports that logins are failing" is a brand speaking; "an issue has been identified that may be impacting some users" is a brand hiding.
The apology is the highest-stakes copy you will write
The communication after an incident — the post-incident write-up or apology — is where the incident communications brand is most exposed. A genuine post-mortem that explains what happened, takes responsibility without hedging, and describes specifically what will change earns more trust than the incident cost. A defensive non-apology — "we apologise for any inconvenience this may have caused" — squanders the goodwill the technical recovery should have earned, because customers read the formula instantly for what it is. The difference is ownership: the trusted version says "we got this wrong and here is what we are doing"; the distrusted version arranges words so that nothing was anyone's fault. The same event produces opposite brand outcomes depending entirely on which of these the organisation chooses.
This is brand-promise territory, which is why incident communication belongs in the same conversation as the operational commitments a brand makes. The credibility of an apology rests on whether the organisation actually does what it said it would, connecting directly to how brands codify reliability into operational targets and brand SLAs — promises that an incident tests in public.
Consistency across the channels of failure
An incident does not play out on the status page alone. It plays out simultaneously on the status page, in support replies, in social media responses, in the email that goes out afterward, and sometimes in a press statement. The incident communications brand only holds together if those channels say the same thing in the same voice. The common failure is divergence: the status page says one thing, support agents say another because they were not briefed, and the social account goes silent because nobody owns it during an incident. That inconsistency reads, correctly, as an organisation that does not have its story straight — which during a failure is the most damaging possible impression. Preparing the incident communications brand means deciding not just the words but who speaks where, and ensuring everyone is working from the same source of truth as the situation evolves.
Preparing the incident communications brand
The quality of incident communication is decided almost entirely before the incident. Organisations that communicate well in failure have prepared templates in the brand voice, a clear owner for incident communications who is not the same person fixing the problem, a pre-agreed view of what gets disclosed and how fast, and a tone that has been chosen deliberately rather than discovered under stress. Organisations that communicate badly are inventing all of this in the moment, which is why their updates are late, inconsistent, and defensive. Treating the incident communications brand as something to design in calm conditions — a small library of templates, a named owner, an agreed tone and disclosure posture — is what makes the difference when the calm conditions end.
What This Looks Like in Practice
In our work with BGR, the gap was not the engineering response, which was sound, but the communication around it, which was being improvised incident by incident and sounded like it — late, technical, and defensive. We treated incident communications as a brand surface and built the preparation: a set of status-page and customer-update templates written in BGR's own voice, a named owner for incident communications distinct from the people resolving the issue, and an agreed posture on how quickly to acknowledge and how plainly to admit. The next incident was communicated early, consistently across channels, and in a voice that sounded like the brand rather than a system log. The technical recovery was the same as it would have been anyway; the brand outcome was completely different.
Closing
The incident communications brand is the self you present when you have the least control and the most scrutiny, and it is the impression that outlasts the outage. Treat the status page as a brand surface, write updates in a plain human grammar, own your apologies rather than formulating them, hold one voice across every channel, and prepare all of it before you need it. The response is the brand — and in failure, that is the only brand your customers are reading.
If your incident communications are being improvised one outage at a time and you want to design them as a brand surface, we are happy to help you prepare.