Cross-functional Crisis Communication Coordination

Two years ago, I'm invited to observe a large healthcare organization's disaster recovery tabletop. Walk in expecting the usual PowerPoint parade. What I witnessed changed how I think about business continuity forever. COO kicks off the meeting. CISO runs the show. Every functional group in the hospital is there. Not just IT. Nursing. Surgery. Pharmacy. Billing. Everyone. Then they start the simulation. "Ransomware hits at 2 AM. Systems are down. What do you do?" Here's the brutal truth: Most disaster recovery plans are IT fantasy documents. They assume perfect communication. They assume backup systems work. They assume people remember their training under pressure. This hospital? They tested every assumption. And reality hit hard. First Reality Check: Communication Breaks Down Fast IT ops team identifies the threat. Starts recovery procedures. They're about to bring systems back online when someone asks, "Did security confirm the attackers are actually out?" Silence. IT was moving at recovery speed. Security was moving at investigation speed. Nobody was talking. In a real attack, they would have restored infected systems and made everything worse. Second Reality Check: Your Backup Communication Plan Is Broken Physical phones down. No problem, everyone has cell phones, right? Wrong. They actually tested cell coverage throughout the hospital. Dead zones everywhere. Including the incident command center. Imagine coordinating disaster response via text messages that won't send. That's what they were planning for. Third Reality Check: Testing Reveals What Planning Misses A tabletop exercise on paper would have checked all the boxes. "Communications plan? Check. Recovery procedures? Check. Command structure? Check." But when humans actually walked through it, the gaps became canyons. Here's what this taught me about real business continuity: First: Cross-Functional Drills Beat IT-Only Exercises Your entire operation needs to practice together. IT might restore systems perfectly while operations makes decisions that amplify the damage. Everyone needs to know their role and how it connects. Second: Test Your Assumptions Physically Don't just say "we'll use cell phones." Walk the building. Make the calls. Test the coverage. Don't just say "we'll restore from backup." Time it. Watch it fail. Fix it before it matters. Third: Communication Protocols Save Companies Who talks to whom? Who has decision authority? Who can pull the "stop everything" cord? Write it down. Practice it. Make it instinct. Fourth: Speed Without Coordination Is Dangerous Fast recovery means nothing if you're restoring compromised systems. Quick decisions mean nothing if departments aren't aligned. Build in checkpoints. Force communication. Slow is smooth, smooth is fast. Your disaster recovery plan looks great on paper. But when's the last time you actually walked through it with everyone who'd be involved in a real crisis? What would break if you tested it tomorrow?

🎯 I just published an exploration of how military crisis communication frameworks are revolutionizing how organizations manage their most critical moments. 💡 **Here’s what military strategic communicators understand that many organizations miss:** ✅ Crisis management isn’t linear—it requires continuous OODA Loop thinking (Observe, Orient, Decide, Act) ✅ Every crisis is an opportunity to build organizational resilience, not just restore status quo ✅ Multi-domain awareness matters—modern crises don’t stay in single channels 🔥 **The convergence of military operational planning + academic crisis theory = game-changing frameworks** I’ve implemented these integrated approaches globally—from coalition environments to high-stakes government communications. The results? Faster response times, clearer stakeholder messaging, and organizations that emerge stronger from adversity. 📊 **Key frameworks we’re deploying:** - SCCT (Situational Crisis Communication Theory) with military threat assessment - Crisis Communication Management Plans (CCMPs) that actually work under pressure - Signal detection systems adapted from intelligence gathering 🌍 **This isn’t theoretical.** These are battle-tested approaches now transforming how organizations prepare for and respond to crisis. ➡️ **Want this level of crisis preparedness for your organization?** Whether you’re facing reputational threats, operational challenges, or navigating complex stakeholder environments, these frameworks can be customized for your context. **Let’s talk about building your crisis-ready organization. DM me or comment below to discuss bringing this training to your team. Read the full article: https://lnkd.in/gs4c3Gth #CrisisCommunication #StrategicCommunications #Leadership #RiskManagement #OrganizationalResilience #MilitaryLeadership #PublicAffairs #CrisisManagement #ConsultingServices Steve "Bleeder" Blevins

Ever heard of the CERC model? Pronounced “sirck”, it stands for Crisis and Emergency Risk Communication, a framework developed by the CDC to guide leaders in communicating during a crisis. The core idea is simple: information is as critical as the response itself. CERC’s 6 principles keep your messaging clear, credible, and human: 1) Be First – Own the narrative by speaking early. 2) Be Right – Accuracy over speed (but don’t delay). 3) Be Credible – Honesty builds trust. 4) Express Empathy – People need to know you get it. 5) Promote Action – Tell them what the team is doing and what they can do now. 6) Show Respect – Always honor dignity and diversity. Though born in public health, CERC’s value extends to cybersecurity, corporate incidents and brand crisis management. In high-stakes moments whether it’s a breach, outage, or public emergency; the right words at the right time can make the difference between chaos and control.

“Another Boeing plane has crashed…” That headline didn’t just inform the world. It shook it. Airlines grounded fleets. Passengers canceled bookings. Families waited in grief. And in those painful moments, everyone turned to Boeing — waiting for reassurance, compassion, and clarity. But what they received instead was silence, technical statements, and corporate coldness. ⸻ 💬 The Dialogue That Never Happened Imagine if Boeing’s CEO had stood before the world and said: 👉 “We are devastated by this tragedy. Our deepest condolences go to the families who lost their loved ones. We take full responsibility to uncover the truth, fix it, and make sure this never happens again. Every passenger’s life matters. We will not rest until trust is restored.” Instead, the company issued vague technical explanations about “software updates” and “pilot procedures.” The difference? One statement speaks to the heart. The other hides behind jargon. 📉 The Fallout of Silence Boeing didn’t just lose billions in market value. They lost something far more precious: trust. • Passengers felt unsafe. • Governments demanded groundings. • Airlines questioned contracts. • Employees lost pride. A global brand that once symbolized safety became a symbol of fear. And the leadership lesson? 👉 In crisis, your communication is your reputation. ⸻ When tragedy strikes, the human brain looks for three things immediately: 1. Reassurance (Pathos): “Do you see my pain? Do you care?” 2. Clarity (Logos): “What exactly happened? Am I safe?” 3. Responsibility (Ethos): “Can I trust you to fix this?” ⸻ Here’s a 3-step Crisis Communication Framework every CEO must remember: 1. Acknowledge Emotion (Pathos): • Show empathy immediately. • Example: “We are heartbroken by this tragedy. Lives were lost. Families are grieving.” 2. Share Facts Clearly (Logos): • State what you know, what you don’t know, and what you’re investigating. • Example: “The incident involves [details]. Investigations are ongoing. Safety checks are underway globally.” 3. Commit to Responsibility (Ethos): • Show accountability and promise change. • Example: “We take full responsibility. Here’s how we are fixing it: [specific steps].” ⸻ ✅ Do’s & ❌ Don’ts of Crisis Communication ✅ Do’s • Respond quickly. Speed signals responsibility. • Lead with humanity. Speak to emotions first, facts second. • Be transparent. Say what you know and admit what you don’t. • Take responsibility. Even partial acknowledgment builds trust. • Be consistent. Updates must be regular, not one-time. ❌ Don’ts • Stay silent. Silence is filled with rumors. • Use jargon. “Software anomaly” means nothing to grieving families. • Deflect blame. Saying “pilot error” erodes credibility. • Downplay loss. Even one life lost must be honored. • Overpromise. “It will never happen again” sounds hollow if unproven. ⸻ 💡 The Bigger Leadership Lesson Crisis doesn’t just test your company. It tests your character.

Most organizations don’t struggle in a crisis because they lack smart people. They struggle because they lack command-and-control discipline when pressure spikes. In policing, high-consequence events assume a few basics: clear command, shared situational awareness, common language, coordinated movement, disciplined communications, and accountability. In many corporate environments, a critical incident gets handled like a meeting, too many “decision-makers,” unclear authority, fragmented communications, and parallel teams acting on different assumptions. That isn’t a culture issue. It’s a risk issue. THE REALITY: The crisis “lead” is appropriately an executive owner (CEO/COO, business unit leader, designated incident executive) because the decisions are enterprise-level. THE SECURITY ROLE: Security often owns the crisis-management process, playbooks, coordination, communications rhythm, deconfliction, and the structure that keeps the response coherent. WHERE SECURITY SHINES: -      Build the system before it’s needed. -      Teach leaders how to use it. -      Keep it nimble when the tempo spikes. -      Serve as the trusted advisor who keeps the organization aligned, informed, and defensible. THE BASELINE: -      Clear incident lead. -      Clear decision rights. -      Common operating picture. -      Tight deconfliction and communications. -      Capture lessons and improve the playbook. THE GOAL: Speed and alignment that protects people and preserves the enterprise: stabilize operations fast, minimize downtime, reduce preventable mistakes, document decisions, manage liability, and ensure communications reinforce trust in the brand. Where does your organization still default to “committee” when it needs “command”?

We almost crunched a €200,000 asset in a French lock last week. The cause wasn't mechanical. It was linguistic. We have 8 people on this boat. Our "working languages" are a mix of French, English, and Russian. In the quiet moments, it’s a cultural win. In a high-pressure 30-second maneuver inside a narrow stone lock, it is a massive operational liability. The "Translation Tax" in Business Last week, I gave a technical command. In that split second, the chain broke: Technical Jargon: I used a boating term that wasn't universal. Language Latency: The "receiver" had to translate the English term into Russian, then map that to a physical action. The Gap: By the time the brain processed the instruction, the wind had already moved 14 tons of fiberglass toward a concrete wall. Why your "Global Office" is at risk: Most leaders assume that because everyone "speaks English," the communication is solved. It isn't. When the "engine noise" of a crisis hits, people revert to their primary thought patterns. My takeaways for the Q3 strategy: Kill the Nuance: In a "lock" (a deadline or a crisis), don't use adjectives. Use verbs. "Pull," "Stop," "Hold." If your SOPs require a dictionary, they will fail when the pressure rises. Visual Overrides: When we realized the 3-language mix was too slow, we switched to standardized hand signals. Hands don't have an accent. Does your team have a "non-verbal" way to signal a red-flag? The 8-Person Limit: Coordination complexity doesn't grow linearly with team size; it grows exponentially. 8 people on one deck is a crowd; without a clear "Protocol Lead," it’s just a catastrophe waiting to happen. Bottom line: If your strategy depends on everyone being a linguistic genius in a crisis, your strategy is broken. Simplify the language or prepare to hit the wall.