The public usually sees the final crisis message. It does not see the machinery behind it: monitoring, verification, agency coordination, message approval, translation, media distribution, visual evidence, digital publishing, feedback and continuous updates. That hidden machinery is why crisis communication should be treated as an operating system rather than a press-release function.
Mona Ghanem Al Marri’s public work around the Government of Dubai Media Office provides a useful case. In 2022, a knowledge-sharing session with the UAE’s National Emergency Crisis and Disasters Management Authority documented how GDMO teams coordinated across strategy, editorial, strategic communication, social media, government relations and media relations during the Jebel Ali port fire, while linking with operational entities including the port authority, police, civil defence and ambulance services. In 2026, Dubai’s government communication network again emphasised coordinated, timely and accurate communication, while the Dubai Media Narrative Committee chaired by Al Marri was given a mandate around clear messaging, coordinated effort, rapid responsiveness, facts, credibility and transparency.
The value for CEOs and boards is not that a company should copy government structures. It is that crisis communication fails when the communication team is treated as the last stop in a chain rather than part of the operating system that turns facts into trusted public understanding.
This analysis is based on public-record material. It does not claim that Executive Authority trained, advised or influenced Mona Ghanem Al Marri. The purpose is to identify observable communication principles that leaders can test in corporate, institutional and high-stakes settings.
The crisis communication failure that begins before the statement
Many organisations discover during a crisis that no one owns the full information flow.
Operations knows one set of facts. Security knows another. Customer service sees a different problem. Legal is reviewing language. The CEO is receiving partial updates. Social media is moving faster than internal approval. Journalists are calling people who are not authorised to speak. Employees learn key facts from external channels.
The resulting communication problem is not primarily writing. It is coordination.
A beautifully written statement issued from a fragmented system will still be late, incomplete or contradicted by another part of the organisation.
1. Build one verified fact base
The first requirement is a shared source of truth.
That does not mean every fact is known. It means the organisation has a disciplined way to distinguish:
- verified fact;
- operational estimate;
- management judgment;
- third-party claim;
- unknown information;
- information that cannot yet be disclosed.
The fact base should update continuously and show timestamps. Crisis communication becomes dangerous when a sentence that was accurate at 10:00 is repeated at 12:00 after the situation has changed.
2. Connect communication to operations in real time
GDMO’s public account of the Jebel Ali port fire is useful because it describes communication teams coordinating with the entities actually handling the incident.
That relationship matters. Communication should not wait for operations to finish before asking what happened. Nor should communication interrupt the operational response unnecessarily.
The system needs agreed interfaces:
- who supplies verified updates;
- who confirms safety information;
- who approves customer instructions;
- who confirms imagery;
- who can authorise publication outside normal hours;
- who escalates disputed facts.
The operating model should exist before the crisis.
3. Design for speed and accuracy together
Organisations often talk about a trade-off between speed and accuracy. The stronger objective is to redesign the system so fewer decisions require that trade-off.
Speed improves when roles, templates, thresholds and approval paths are prepared in advance.
Accuracy improves when the fact source, verification owner and uncertainty language are clear.
The executive question is therefore not, “Should we be fast or accurate?” It is:
“What process lets us be accurate faster?”
That changes crisis preparedness from a writing exercise into an operating-design exercise.
4. Make visual proof part of the information system
The 2022 GDMO account of the Jebel Ali incident highlighted the use of photos and videos alongside updated information.
Visual evidence can reduce uncertainty when used responsibly. It can show containment, operational activity, access conditions or the scale of an event more efficiently than adjectives.
But images also need verification and context. Old footage, misleading angles or unverified user-generated material can damage credibility.
A crisis information system should therefore treat approved imagery as a governed data type, not a social-media afterthought.
5. Create a message hierarchy
Not every fact deserves equal prominence.
A crisis message hierarchy can be:
- Safety: Is anyone at immediate risk?
- Behaviour: What should people do now?
- Status: What is happening?
- Control: What is the organisation doing?
- Impact: What services or operations are affected?
- Uncertainty: What is not yet known?
- Next update: When and where will more information appear?
This sequence is more useful than starting with reputation protection.
6. Align channels without making every channel identical
The website, media statement, employee message, customer alert and social post should share the same fact base but may have different functions.
A customer may need an action. An employee may need an internal instruction. A journalist may need verified facts and spokesperson access. An investor may need material impact. A regulator may need formal notification.
Consistency does not mean copy-pasting the same paragraph everywhere.
It means the organisation never contradicts itself on the core facts.
7. Build multilingual communication into the system
Dubai’s public communication model has repeatedly referenced multilingual outreach because the population contains many language communities.
The corporate lesson is broader. Translation should not be the final step after the English statement is approved.
Important crisis messages should be designed for translation:
- simple sentence structure;
- minimal idiom;
- stable terminology;
- clear numbers and dates;
- explicit actions;
- approved translations for recurring safety terms.
A technically accurate message that half the affected audience cannot understand is not operationally complete.
8. Treat rumours and misinformation as system inputs
The organisation should monitor what people believe, not only what it has published.
If the same false claim is spreading repeatedly, that is information about a gap in the communication system.
The response should ask:
- Is the false claim material?
- Is it growing?
- Could it change behaviour?
- Do we have verified evidence to correct it?
- Would responding amplify it unnecessarily?
The decision needs a threshold, not panic.
The SENSOR → VERIFY → ALIGN → AUTHORISE → DISTRIBUTE → LISTEN → UPDATE framework
A crisis communication operating system can be organised into seven functions.
Sensor
Collect information from operations, security, customers, media, employees and digital channels.
Verify
Separate confirmed fact from estimate, assumption and rumour.
Align
Bring relevant operational and communication owners around the same fact base.
Authorise
Use pre-defined approval rights so urgent messages do not become trapped in hierarchy.
Distribute
Issue the right message to the right audience through the right channel.
Listen
Monitor questions, confusion, behaviour and false narratives.
Update
Correct, expand or replace earlier messages as facts change.
The system is cyclical. A crisis is not handled by one statement.
The 15-minute executive dashboard
During a fast-moving event, the CEO should not receive 60 pages of monitoring.
A useful executive dashboard contains:
- current verified facts;
- safety status;
- operational status;
- customer/public action;
- unresolved questions;
- misinformation requiring attention;
- statements already published;
- next decision required;
- next update time.
This allows the principal to make communication decisions without becoming the bottleneck for every sentence.
Approval design before the crisis
Many organisations lose the first hour because no one knows who can approve what.
Set thresholds in advance.
For example:
Level 1: communications director can publish routine service disruption updates.
Level 2: COO and communications lead approve material operational incidents.
Level 3: CEO/legal/regulatory team approve statements involving major harm, market-sensitive information or attribution of responsibility.
The exact model differs by organisation. The principle is that approval rights should reflect consequence, not habit.
What the CEO should own personally
The CEO does not need to approve every update.
The CEO should own:
- the major judgment;
- the values or principles that guide the response;
- the organisation’s accountability;
- major stakeholder reassurance where appropriate;
- the point at which the crisis changes strategy.
The operating system should handle routine information flow around that leadership role.
The error-correction protocol
A crisis system must assume some information will change.
When an earlier statement is wrong or incomplete:
- correct it visibly;
- state what changed;
- give the accurate information;
- explain any resulting action change;
- do not bury the correction inside a new paragraph.
Trust is damaged more by concealed correction than by an honest update to a fast-moving situation.
Build the system around decision latency
One useful crisis metric is decision latency: how long it takes verified information to become an authorised public instruction.
Break that time into stages:
- detection;
- verification;
- escalation;
- approval;
- translation;
- publication.
If a simple customer instruction takes 90 minutes because of approvals, the organisation has a systems problem.
That metric can be rehearsed in simulations.
The difference between communication readiness and media readiness
Media readiness asks whether the spokesperson can answer questions.
Communication readiness asks whether the organisation can produce accurate answers at all.
The second comes first.
A confident spokesperson with a fragmented fact base can create more risk than an imperfect speaker with disciplined information.
This is why crisis counsel should work with the operating architecture as well as the spokesperson.
A self-diagnosis for boards and CEOs
Ask:
- Do we have one crisis fact base?
- Who verifies safety information?
- Who owns the next public update?
- Can we publish outside office hours without assembling ten approvers?
- Are customer, employee, investor and media messages drawing from the same facts?
- Can critical instructions be translated rapidly?
- Do we know which rumours matter enough to correct?
- Can the CEO see the decision dashboard without being copied on every email?
- Do we record what changed between updates?
- Have we tested the system under time pressure?
If the answer to several is no, the organisation has a crisis communication design problem before it has a crisis.
What another leader can borrow from the Dubai public record
The most transferable lesson is coordination.
Public descriptions of Dubai’s communication response emphasise aligned entities, timely and accurate information, multiple communication functions and a shared narrative framework. A corporate organisation may be smaller, but the underlying principle remains useful: trusted external communication depends on internal coordination.
The reader should not copy institutional structure blindly. The useful question is which functions need to connect inside their own organisation.
What not to copy mechanically
Government communication has different legal obligations, authority structures, information access and public-service responsibilities from a private company.
A listed company must also consider market disclosure. A hospital must protect patient privacy. A bank has regulatory constraints. A technology platform may need to coordinate cybersecurity and user notification.
The operating-system concept transfers. The governance design must fit the institution.
When this becomes commercially consequential
Crisis communication becomes principal-level when delayed, contradictory or inaccurate information can affect safety, customer behaviour, regulation, investor confidence or organisational legitimacy.
At that point, the problem cannot be solved only by writing a stronger statement. The organisation needs a fact architecture, decision rights, scenario protocols, message hierarchy and a principal who understands what they personally own.
That is where crisis communication becomes operating design.
Executive Authority Answer
Crisis information should be managed as an operating system rather than a sequence of press releases. The system needs one verified fact base, direct links to operations, pre-defined approval rights, audience-specific distribution, multilingual capability, misinformation monitoring and continuous updates. Public material from the Government of Dubai Media Office under Mona Ghanem Al Marri provides useful evidence of coordinated communication across operational entities and communication functions during high-pressure events.
Questions leaders ask
Who should own the crisis fact base?
One designated coordination function should maintain it, but operational owners must verify the facts they control. Communications should not invent or independently adjudicate technical facts.
How often should the organisation update publicly?
When there is material new information, changed customer action or a meaningful correction. Do not publish on a fixed cadence if there is nothing useful to add, but tell audiences when the next update is expected where possible.
Should every channel use identical wording?
No. They should use the same core facts while adapting the action and detail to the audience.
What is the CEO’s role?
Own the major judgment, accountability and strategic message. The CEO should not become the approval bottleneck for routine factual updates.
How should the organisation handle uncertainty?
State what is known, what is not known and what is being verified. Do not fill information gaps with reassurance.
A 30-day readiness build
Week 1: map crisis information sources, decision owners and current approval paths.
Week 2: build the shared fact-base template, message hierarchy and multilingual terminology bank.
Week 3: run a simulation that forces updates every 15–30 minutes and measure decision latency.
Week 4: fix the bottlenecks, train principals and define post-incident review metrics.
The output should be a working operating system, not a binder nobody opens.
Sources and evidence
This analysis uses public-record material and does not imply any advisory, training or commercial relationship between Executive Authority and Mona Ghanem Al Marri.
- Government of Dubai Media Office — NCEMA knowledge-sharing session on strategic crisis communication and media management
- Government of Dubai Media Office — General Network of Government Communication highlights key pillars for responses to regional developments
- Government of Dubai Media Office — Dubai Media Narrative Committee established
- Government of Dubai Media Office — media management during crises workshop
For related EA analysis, see Crisis Communication, Media Training, and Executive Communication.
When a statement is not enough
Executive Authority works with CEOs and senior principals when crisis communication needs to function across operations, customers, media, employees, investors and regulators without contradiction. The work can stress-test decision rights, message architecture, executive roles and hostile scenarios before a live incident exposes the gaps. Request confidential counsel.
This article does not claim that Executive Authority trained, advised or influenced Mona Ghanem Al Marri. It analyses observable public communication and extracts methods another leader can test in a different context.
The crisis information board
For a serious incident, create one live board that every authorised communication owner can see. It should not be a general project-management board. It should answer the information questions that determine public communication.
Suggested fields:
- fact or claim;
- source;
- verification owner;
- time verified;
- confidence level;
- public/private status;
- affected audiences;
- action required;
- published wording;
- channel;
- expiry or next-review time.
This simple structure prevents a common failure: old facts continuing to circulate because nobody knows they have been superseded.
The update clock
A crisis team should know when silence itself becomes a risk. That does not mean promising a new statement every 30 minutes. It means deciding how long affected audiences can reasonably go without useful information.
Set an update clock for each audience. Customers waiting at an airport may need faster operational updates than investors. Employees on a safety-critical site may need immediate instructions. The media may need confirmation that the organisation is still verifying facts.
The clock should restart whenever a meaningful update is issued. If the team reaches the threshold with no new fact, it can still communicate what remains unchanged, what is being verified and when the next decision point occurs.
The contradiction drill
In simulations, deliberately inject conflicting information from two credible internal sources. For example, operations reports that service will resume in one hour while safety teams say the site remains restricted.
Then test:
- who has authority to resolve the contradiction;
- whether communications knows which source has primacy;
- whether an already drafted message is stopped in time;
- how the uncertainty is explained externally if resolution takes longer than expected.
This is more realistic than a simulation in which every fact arrives cleanly. Real crises are messy. The operating system must handle disagreement inside the organisation before it becomes contradiction outside it.
The post-incident learning loop
After the crisis, do not review only media coverage. Review the information system.
Measure:
- time from fact discovery to verification;
- time from verification to public release;
- number of corrections;
- number of conflicting messages prevented or published;
- repeated audience questions;
- translation delays;
- approval bottlenecks;
- rumours that grew because the organisation left an information gap.
Those metrics tell leadership what to redesign before the next incident.
The purpose is not to prove the team performed well. It is to make the system faster, clearer and more trustworthy next time.
The executive question that reveals whether the system is real
Ask the crisis team: “If the CEO became unreachable for the next 45 minutes, what verified information could still be published safely?”
If the answer is “nothing,” the organisation has designed a personality-dependent approval chain rather than a resilient communication system. The CEO should retain control over major judgment and accountability, but routine safety, customer and status updates need pre-authorised pathways.
A mature system therefore distinguishes between messages that require principal judgment and messages that require disciplined execution. That distinction protects both speed and executive attention during the period when the organisation can least afford bottlenecks.
The one-page crisis architecture the board should see
The board does not need every workflow. It should be able to see the operating architecture on one page: source of truth, verification owners, approval thresholds, spokesperson structure, audience channels, regulatory sequence, multilingual capability and escalation rules.
If that page cannot be drawn clearly, the system is probably too dependent on informal relationships and individual memory. Those systems can work in routine periods and fail exactly when pressure, absence or conflicting information increases.
Published by Executive Authority
