Sharing Lessons Learned from Past Crises

I recently had the pleasure of presenting on crisis comms to a group of Central Washington University students. It’s a topic I get asked about all the time, so sharing 6 key learnings I usually highlight: 1) Preparation is key – If you wait until you are in a crisis to think about your plans, you’re starting at a huge deficit. Scenario plan early and build out as much process/content as you can so you have a running start when the time comes. With careful planning and an early warning system in place, you may even be able to intercept an issue before it turns into a full-blown crisis. 2) Stakeholders (and their roles) matter – A critical part of preparedness: who needs to be involved and in what capacity. Who is the decision maker, who needs to be informed, who is part of the working group, etc. It will vary based on the situation, so see point #1 and get this sorted out in advance. Including how to reach people after hours. 3) Get the facts first ­– Resist the urge to “message” a situation or talk tactics until you understand the facts, including what is unknown. A comms strategy is only as good as the data it is based on; faulty information = faulty strategy. 4) Consider ALL audiences – Customers, partners, employees, the local community, etc. Again, it will vary by situation but things can go sideways fast if you forget about a major audience. You need to own your story across all of them. Pro tip: If you find yourself prioritizing press as your top audience (vs. say, customers or employees), you’re probably doing it wrong. 😊 5) Third parties can tip the scales – They can work in your favor or they can keep fanning the flames. For any given situation think about who can be an advocate…and who is likely to be a detractor. For those who are advocates, remember to nurture those relationships over time vs. simply tapping them when you need something. 6) Practice, practice, practice – The best way to ferret out gaps is to do a few practice drills. But don’t pick a day/time where everyone is around, has time available, etc. Mimic a real scenario which likely includes a couple key people being on vacation, on the road, tied up in all day meetings, etc. The final bit of advice I give people: keep calm. Comms leaders have a unique opportunity to set the tone. Showing up as calm and in control can go a long way to settling others’ nerves. (And yes, it’s completely fair to be stressing out internally/privately.) Joe Tradii thanks again for the opportunity to spend time with your students! #PR #CrisisComms #VoxusPR

Organizational Trauma: The Recovery Killer Your Change Plan Ignores After Capital One's 2019 data breach exposing 100 million customers' information, leadership rushed to transform: new security platforms, restructured teams, revised processes. Despite urgent implementation, adoption lagged, talent departed, and security improved more slowly than expected. What they discovered—and what I've observed repeatedly in financial services—is that organizations can experience collective trauma that fundamentally alters how they respond to change. 🪤 The Post-Crisis Change Trap When institutions experience significant disruption, standard change management often fails. McKinsey's research shows companies applying standard OCM to traumatized workforces see only 23% transformation success, compared to 64% for those using trauma-informed approaches. ❌ Why Traditional OCM Fails After Crisis Hypervigilance: Organizations that have experienced crisis develop heightened threat sensitivity. Capital One employees reported spending time scanning for threats rather than innovating. Trust Erosion: After their breach, Capital One faced profound trust challenges—not just with customers, but internally as well. Employees questioned decisions they previously took for granted. Identity Disruption: The crisis challenged Capital One's self-perception as a technology leader with superior security. 💡 The Trauma-Informed Change Approach Capital One eventually reset their approach, following a different sequence: 1. Safety First (Before planning transformation) - Created psychological safety through transparent communication - Established consistent leadership presence - Acknowledged failures without scapegoating 2. Process the Experience (Before driving adoption) - Facilitated emotional-processing forums - Documented lessons without blame - Rebuilt institutional trust through consistent follow-through 3. Rebuild Capacity (Before expecting performance) - Restored core capabilities focused on team recovery - Invested in resilience support resources - Developed narrative incorporating the crisis 4. Transform (After rebuilding capacity) - Created new organizational identity incorporating the crisis - Shifted from compliance to values-based approach - Developed narrative of strength through adversity 5. Post-Crisis Growth - Built resilience from the experience - Established deeper stakeholder relationships - Transformed crisis into competitive advantage Only after these steps did Capital One successfully implement their changes, achieving 78% adoption—significantly higher than similar post-breach transformations. 🔮 The fundamental insight: Crisis recovery isn't just about returning to normal—organizations that address trauma can transform crisis into opportunity. Have you experienced transformation after organizational crisis? What trauma-informed approaches have you found effective? #CrisisRecovery #ChangeManagement #OrganizationalResilience

In 2011, the Amazon Appstore failed on launch and Jeff Bezos was furious. It was my fault, and I handled one aspect of recovery so poorly that one of my engineers quit. I still regret it 14 years later. Please learn from my mistake. The main lesson is that when you are leading through a crisis, it can feel like it is all about you. It isn’t. It is about: 1) Solving the problem 2) Guiding your team through it The product issue was that there were some pretty simple bugs, and we solved those problem well enough that I was eventually promoted. Where I failed was in guiding my team through the crisis. My leadership miss was that I neglected to encourage and support the engineer who had written the bad code. He did a great job stepping up and supporting the effort to fix the problem, but shortly afterward, he resigned. During the crisis, I failed to make clear to him that we did not blame him for the launch failure despite the bugs. I imagine that left room for him to think we blamed him or that he didn’t belong. It is also possible that others did blame him directly and that I was too caught up in the crisis to realize it. Both instances were my responsibility as the leader of the team. His resignation taught me a valuable lesson about leading through a crisis: No matter how bad the situation is, your team must be your first priority. If you make them feel safe, they will move heaven and earth to fix the problem. If you don’t, they may still fix the problem, but the team itself will never be the same. As a leader, here is how you can give them what they need: 1) Take the blame and do not allow others to be blamed. In some bug cases after this we did not release the name of the engineer outside the team in order to protect them from judgment or blame. 2) Separate fixing the problem from figuring out why it happened. Once the problem is fixed, you can focus on root-causing. This lowers the risk of searching for answers getting confused with searching for someone to blame. 3) Realize that anyone involved in the problem already feels bad. High performers know when they have fallen short and let their team down. As a leader you have to show them the path to growth and success after the crisis. They do not need to be beaten up on- they have taken care of that themselves. 4) See crises and problems as growth opportunities, not personal flaws. Your team comes with you in a crisis whether you like it or not, so you might as well come out stronger on the other side. As a leader, the responsibility for a crisis is yours in two ways: The problem itself and the effect it has on the future of the team. Don’t get too caught up in the first to think about the second. Readers- Has your team survived a crisis? How did you handle it?