How to Learn from Crisis Management Experiences

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?

The recent news on AWS center in the Middle East going down because of the war made me relive my experience decades ago! I once helped build what we proudly called a best-in-class disaster recovery architecture. We did everything right—on paper. ✔️ Business Impact Analysis done ✔️ RTO & RPO agreed with stakeholders ✔️ Sophisticated tools deployed ✔️ DR site fully provisioned We were confident. Almost too confident and then came the day that tested everything ! A dual power supply failure hit our primary data center. Within minutes, 300+ servers went down abruptly. What followed was worse than downtime: Critical application databases got corrupted AND THEN The DR site also got corrupted ! Real-time transactions came to a complete standstill. With every passing hour, we lost millions of dollars in revenue. In that moment, all our architecture diagrams, tools, and planning meant one thing: NOTHING —because the system didn’t recover !!! What this experience taught me: 1) Testing isn’t real until it’s brutal Table-top simulations give comfort. Full-scale failover drills expose truth. Test like it’s already failing: -Simulate real load -Introduce chaos scenarios -Assume components will fail unexpectedly 2) DR is not a technology problem—it’s a systems problem We focused heavily on tools. We underestimated dependencies. Ensure: -End-to-end recovery (infra + app + data integrity) -Isolation between primary and DR (to avoid cascade failures) -Backup validation, not just backup completion 3) Communication is your real recovery engine In crisis, confusion spreads faster than outages. Build: -Clear SOPs for business continuity -Pre-defined escalation paths -Regular cross-team drills (not just IT—include business teams) 4) Leadership presence changes outcomes War rooms are intense. Fatigue, panic, and noise creep in. As a tech leader: -Your presence brings calm -Your clarity drives prioritization -Your energy keeps teams going Sometimes, leadership is less about answers… and more about Stability 5) Assume your DR will fail—and design for that This was the hardest lesson. Build layers: - Immutable backups - Offline recovery options -“Last resort” recovery playbooks Because resilience is not about one backup plan. It’s about what happens when that backup plan fails... Have you ever seen a #DR plan fail in real life? How often do you run full-scale disaster recovery drills? What’s the one thing most organizations still get wrong about resilience? Curious to hear real experiences—those are always more valuable than frameworks. #DR #disasterrecovery #drill #test #BCP #leadership #technology #resilience

The best crisis strategy is written in hindsight and used for foresight. I keep a crisis journal. Not to relive the chaos. To learn from it. Every major crisis I've worked on—every headline, every misstep, every win—gets an entry. Not a diary. A debrief. Because the patterns matter more than the individual fires. Here's what I track: ⇢ What happened (the facts, stripped of emotion) ⇢ What we did (our strategy, our messaging, our timeline) ⇢ What worked (the decisions that moved the needle) ⇢ What didn't (the mistakes, the delays, the blind spots) ⇢ What I'd do differently (the hindsight clarity) It's not about shame. It's about evolution. Some of the best crisis strategies I use today came from entries written years ago—when I was scrambling, improvising, and learning in real time. Here's what the journal has taught me: 1.) Patterns repeat across industries. Different companies. Different crises. Same mistakes. Delayed responses. Defensive messaging. Legal-first thinking. When you see the pattern, you can prevent it. 2.) Speed beats perfection. The entries where we moved fast—even imperfectly—almost always ended better than the ones where we waited for perfect clarity. Action creates options. Hesitation creates headlines. 3.) Emotion drives poor decisions. In every crisis, someone wanted to fight back, defend the brand, or go silent out of fear. The entries where we led with strategy instead of emotion? Those are the wins. 4.) The first 48 hours define everything. What you say, when you say it, and who says it—those decisions set the trajectory. Get those right, and you can recover. Get them wrong, and you're playing defense for months. 5.) Most crises are preventable. Looking back, the majority of the crises in my journal didn't have to happen. A policy audit. A difficult conversation. A proactive statement. Small decisions that could have stopped the fire before it started. The crisis journal isn't just a record. It's a playbook. And every entry makes me sharper for the next call at 2 AM. Follow for weekly insights on crisis psychology and leadership under pressure.

Most leaders waste their biggest growth opportunities. Here's what I learned after studying 200+ crisis responses across $50B+ in market cap... Everyone talks about "crisis management." But elite leaders? They focus on crisis EXTRACTION. The difference is everything. After tracking Fortune 500 CEOs, military commanders, and unicorn founders, here's the pattern: They treat every crisis like a million-dollar MBA program. 1️⃣ The Crisis Value Extraction Framework Within 72 Hours: → Structured debrief sessions (not blame meetings) → Data collection while memories are fresh → Cross-functional perspective gathering The 4-Layer Analysis: → What happened? (Facts without interpretation) → Why did it happen? (Root causes, not symptoms) → What worked? (Strengths to amplify) → What's the opportunity? (Strategic advantages gained) Most leaders skip layer 4. That's where the real value lives. 2️⃣ The Johnson & Johnson Playbook 1982 Tylenol crisis 7 deaths, brand nearly destroyed. CEO James Burke's response? Immediate debriefs across every level. Not to assign blame. To extract systematic improvements. Result: → Tamper-proof packaging industry standard → Crisis communication benchmark → Sales rebounded within 12 months → Trust metrics higher than pre-crisis The crisis became their competitive moat. 3️⃣ Why 90% of Crisis Debriefs Fail Fatal Error #1: Waiting too long Memory fades. Lessons evaporate. Fatal Error #2: Focusing on blame Elite teams ask: "What systems failed?" Fatal Error #3: Surface-level analysis Winners drill down: "Which communication channels failed under stress?" Fatal Error #4: No implementation tracking Insights without execution = expensive therapy sessions. 4️⃣ The $5 Billion Zoom Lesson COVID hits. Zoom usage explodes 30x overnight. Servers crash. Security issues emerge. CEO Eric Yuan's response? Daily crisis debriefs with every department. Not damage control meetings. EXTRACTION sessions. Questions they asked: → Which assumptions broke first? → What capabilities did we discover? → How did customer behavior shift? → What market gaps opened? Result: Zoom captured 70% market share and built the hybrid work infrastructure powering today's economy. The crisis became their category-defining moment. Because here's what most miss: Your competitors face the same crises. The question isn't whether you'll face disruption. It's whether you'll extract more value from it than they will. Elite leaders don't avoid crises. They architect systems to profit from them. In a world where change is the only constant... The fastest learners win. === 👉 What's the biggest crisis your organization faced recently - and what systematic advantage did you extract from it? ♻️ Kindly repost to share with your network 💌 Join our our newsletter for premium VIP insights. Link in the comments.

In late 2016, while at Microsoft, I wrote a piece of code that caused severe crashes across 8+ regions, reducing our Service Level Agreements (SLAs) significantly. Within 30 hours, our team had jumped into action and resolved the crisis. This is the story of one of my biggest career mistakes and what it taught me. It all started with a subtle error: a null pointer exception in a rarely used code path. I thought it wasn't urgent and even considered going on vacation. But as life would have it, another team made changes that increased the frequency of this problematic code path, leading to massive crashes in multiple regions and affecting our SLAs badly. I was in shock when I realized the magnitude of what had happened. My heart pounded, but I knew I couldn't freeze. I took ownership and immediately informed leadership. Initially, they thought I was joking, but soon realized the severity of the issue. I involved the Product Management team to communicate with impacted customers while I focused on finding a fix. Within 30-40 minutes, I had a solution. I tested it thoroughly, validated it in a test region, and gathered approvals for a hotfix. Within 30 hours, we rolled out the fix to all regions. This experience taught me: 1. High-Quality Code Is Non-Negotiable: Quality code and thorough testing are critical, especially at scale. 2. Ownership Earns Respect: Taking responsibility rather than deflecting blame is crucial in resolving issues. 3. Communication Is Key: Proactive communication with leadership and customers maintains trust. 4. Learn and Reflect: Reflecting on mistakes and learning from them is what makes us better. I survived one of my worst mistakes by owning, fixing, and growing. Mistakes happen, but it’s how we respond that defines us. What's your biggest mistake, and what did it teach you?

Your stomach drops. Slack is on fire. This isn’t just a crisis—it’s the moment that makes you. Handling high-stakes moments isn’t a bonus skill. It’s 𝘵𝘩𝘦 leadership skill. Here’s what separates those who bounce back stronger from those who don’t: 1. Own the outcome → Use active language: “We deployed a change that caused the outage,” not “The system failed.” → Show up. Be visible. → Skip the explanations initially — lead with acknowledgment → Own the full impact, not just your part → Roll up your sleeves alongside the team → Ask “How can I help?” — not just “When will it be fixed?” 2. You’re communicating even when you’re not → Send regular updates, even if there’s little new info → Set clear expectations for the next update (and meet them) → Differentiate clearly between what you know and don’t → Be transparent about severity and impact 3. Don't let a good crisis go to waste → Document lessons while the experience is fresh → Share learnings beyond your immediate team → Turn insights into system improvements → Use the crisis to upgrade your playbooks These actions build something more valuable than a crisis-free record: Unshakable trust. Teams trust the leaders who show up. Stakeholders remember the ones who stay steady under pressure. Your toughest moments are your biggest opportunities for leadership growth. What’s one crisis that changed how you lead?

I learned one of my most important leadership lessons during a crisis I didn’t see coming. Six months into a recession, the division I was leading missed a major revenue target. The kind of miss that makes the room go quiet. The easy reaction would’ve been to freeze, cut back, and wait it out. Instead, my team and I reframed it as a chance to rebuild our resilience. Here’s what we did, fast: 1. Found untapped opportunities inside our existing client base 2. Accelerated product enhancements that had been sitting on the backlog 3. Repositioned our offering to deliver even more value in a recessionary market Six months later, we were back on plan. But the real lesson wasn’t the recovery. It was this: Every crisis tests your character more than your strategy. During tough moments, your team isn’t just watching what you decide. They’re watching how you show up. Over the years, from Fortune 200 environments to private-equity transformations to my work now at K1x, I’ve learned a few things about resilience: Builders beat managers. Managers maintain. Builders create from zero, under pressure, with limited resources. When the stakes are real, you want builders next to you. Consistency builds trust. Clear, early communication matters: “Here’s what we know.” “Here’s what we don’t.” “Here’s what we’re doing next.” It sounds simple, but most leaders skip these steps when stress hits. Reliable systems create calm. Urgent fixes are temporary. Well-built processes keep the team steady long-term. Personal resilience is a discipline. When your chips are down, people take their cues from your steadiness. That responsibility is real and it never goes away. At K1X, Inc., we bring that philosophy into how we build: people-first, clarity over complexity, and systems that scale. That’s how we now support 40,000+ organizations with AI-powered automation of K-1s, 1099s, W-2s, and 990s. Crisis doesn’t create leaders. It reveals them and refines them. Curious: What’s one leadership lesson you learned the hard way?

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

18 years ago last week, I left the Royal Marines and moved to Dubai to focus full-time on building Sicuro Group.... Two decades later - operating in some of the world’s hardest places - I’ve been tested, nearly broken, and constantly reminded why this work matters. Here are 20 lessons worth passing forward to anyone building a career or a team in this field: 1. Don’t try to predict every threat. Build systems that can respond to anything. 2. Geography matters. Where you base yourself shapes what you can reach. 3. Experience and judgment are your real moat. Tools only amplify them. 4. Build relationships before you need them. In crisis they become lifelines. 5. Speed saves lives. Preparation enables speed. 6. Conventional models break in unconventional situations. Have alternatives. 7. Trust is earned slowly and lost quickly. In this business it’s currency. 8. Layer your capabilities like body armor. Redundancy protects people. 9. Technology helps, but it doesn’t decide. Judgment does. 10. You only learn crisis management by being where crises happen. 11. Worst-case planning should feel uncomfortable. That’s the point. 12. Duty of care isn’t compliance. It’s a competitive advantage. 13. Integration beats “best of breed.” Unified response saves time when it matters. 14. When lives are at stake, cost arguments disappear. Focus on outcomes. 15. Remote capability multiplies reach. Build systems that work anywhere. 16. Expertise compounds. Each crisis prepares you for the next. 17. Partnerships extend your capability beyond what you can build alone. 18. Document everything. The next crisis will need that record. 19. Cultural competence is operational competence. Ignore it and you fail. 20. Build for the worst case. If it works there, it will work anywhere. But... the lessons aren’t only operational. I’ve been hurt by people close to me, yet shown belief and support by strangers when I needed it most... the world works in odd ways. I came close to bankruptcy - twice - early in my career - valuable lessons about business, and people that could fill a book alone! And... I’ve learned that the better you become, the more you love the job for what it is: solving problems, protecting people, and helping others protect what they care about. There are easier ways to make money, with less risk and more predictability. But this life gives you the best relationships, the hardest challenges, and the opportunities that matter most... and the odd anxiety at airport security! Don’t be afraid to fail. That doesn’t mean be reckless. Take your risks early if you can. Learn fast. Stay curious. Never stop. If even one of these helps someone prepare better....or avoid a mistake I had to make, then it’s worth sharing. SW.

When I was a Corporate Affairs Director at Centrica, I drilled my comms team on crisis response every two weeks. Here’s why: Real-time pressure doesn’t warn you. And most comms teams aren’t ready - not because they’re not good, but because they’ve never actually practiced how to respond when things go badly wrong. So, when I led the team at Centrica, we built a crisis habit. Every two weeks, we ran a table top exercise: “What would you do right now if this happened?” No slides. No notes. Just talk it through. Once a month, we simulated a real-time crisis across an hour, with new updates and stakeholder pressure added in. Once a quarter, we ran it with another business unit - because most failures happen at the interface between teams. And once a year, we brought in legal, HR, operations - because these are the functions that can really send things sideways if they don't know what to do and when. The goal wasn’t perfection. It was to make crisis response feel routine. That habit helped us sleep at night. And, when something did go wrong, we weren’t scrambling.