Hydro: prepare the facts before you prepare the statement

Hydro’s March 2019 cyberattack illustrates how differentiated operational updates can inform customers; build the ownership and verification process before an incident exposes its absence.

A communications team may have a polished crisis template and still be unable to answer the question customers care about: will my order arrive?

During a serious incident, that answer belongs partly to operations, partly to customer service and partly to whichever team can verify the underlying systems. The CMO cannot manufacture certainty through better wording.

The useful preparation is therefore a route from changing operational facts to clear public information. Norsk Hydro’s March 2019 cyberattack provides a concrete example of why that route matters.

Specificity without pretending recovery is complete

In its 26 March 2019 update, Hydro distinguished conditions across business areas rather than describing the entire company as simply operating or closed. It also identified preliminary financial estimates as preliminary and scheduled an analyst and media update.

Reuters reporting carried by Claims Journal described production disruption, manual workarounds and uncertainty about full recovery. These were substantial operational difficulties, not merely a reputational event.

The communications lesson is the shape of the information: separate what is functioning, what is impaired, what remains unknown and when further information will be available. That structure is useful even when the facts are uncomfortable.

It does not prove that transparency removed every commercial consequence. Nor does the case make communications a replacement for technical incident response. It shows a way to prevent a single reassuring headline from concealing materially different customer situations.

Build a facts table with owners

Before an incident, identify the facts customers would need for the most plausible disruptions. For a service firm, these might include access, scheduled work, data availability, response times and temporary alternatives.

Assign a person or role that can verify each fact. Add a backup owner and a contact method that does not depend entirely on the system likely to fail.

A useful record contains the statement, evidence, confirming owner, confirmation time and next review time. That is more helpful than a shared document filled with confident sentences whose origins nobody can trace.

Some information will remain unknown. Give uncertainty an owner too: who is investigating, what would resolve it and when will the team reassess? Otherwise an unanswered question can disappear between departments.

Separate facts from forecasts

“The booking system is unavailable” is an observation. “It will return in two hours” is a forecast. Both may be publishable, but they need different supporting evidence and different wording.

Ask the incident lead what would make a forecast fail. If recovery depends on a test that has not yet succeeded, the communication should not present the estimate as a promise.

Similarly, distinguish the absence of confirmed harm from confirmation that no harm occurred. A technical investigation may simply be incomplete. Marketing should not turn a preliminary finding into a broader assurance for the sake of a cleaner headline.

These distinctions help preserve credibility when information changes. The audience can understand a revised estimate more readily when the original message honestly described its limits.

Design approvals around the next update

A crisis approval chain should be short enough to function and clear enough to prevent contradictory claims. Decide which roles verify operations, assess legal obligations and approve the public wording.

Create approved structures for routine updates, while keeping factual content subject to confirmation. A template can speed up the order of information; it cannot pre-approve facts that have not occurred.

Name an alternate approver. The absence of one executive should not leave customers without an update for an entire day. The fallback must be agreed before the incident rather than improvised during it.

Rehearse a messy scenario

Use a hypothetical exercise in which the normal communication channel also fails. Give the team conflicting initial reports and an important customer demanding a guarantee.

The exercise should test whether staff can identify what is known, find the right verifier, produce an accurate holding update and route individual customer needs. A beautifully written statement is only one small part of success.

Introduce a changing fact halfway through. Perhaps one location recovers while another remains unavailable. See whether the team updates its customer segmentation or keeps issuing a single company-wide message that has become misleading.

Measure time to verified information, unresolved ownership gaps and contradictions between customer-facing teams. Use those findings to improve the process before another rehearsal.

Keep the customer instruction close

Every update should consider the action an affected person can take. That may be using an alternative route, postponing a non-essential action or contacting a dedicated support channel. Avoid an instruction that merely moves the queue to another overwhelmed team.

Publish the time and scope of the update so that old information is recognisable. Preserve a clear correction trail when material facts change; silently rewriting an earlier statement can leave customers unsure which version they relied on.

For the CMO, readiness means knowing how verified information will reach the people who need it. Hydro’s example is valuable because it makes that operational discipline visible. The best time to establish it is when the organisation can still practise without customers bearing the cost.