Crisis Decision-Making Skills

Land the plane. If you’re in it right now, dealing with a missed goal, a major bug, a failed launch, or an angry keystone customer, this is for you. In a crisis, panic and confusion spread fast. Everyone wants answers. The team needs clarity and direction. Without it, morale drops and execution stalls. This is when great operators step up. They cut through noise, anchor to facts, find leverage, and get to work. Your job is to reduce ambiguity, direct energy, and focus the team. Create tangible progress while others spin. Goal #1: Bring the plane down safely. Here’s how to lead through it. Right now: 1. Identify the root cause. Fast. Don’t start without knowing what broke. Fixing symptoms won’t fix the problem. You don’t have time to be wrong twice. 2. Define success. Then get clear on what’s sufficient. What gets us out of the crisis? What’s the minimum viable outcome that counts as a win? This isn’t the time for nice-to-haves. Don’t confuse triage with polish. 3. Align the team. Confusion kills speed. Be explicit about how we’ll operate: Who decides what. What pace we’ll move at. How we’ll know when we’re done Set the system to direct energy. 4. Get moving. Pull the people closest to the problem. Clarify the root cause. Identify priority one. Then go. Get a quick win on the board. Build momentum. Goal one is to complete priority one. That’s it. 5. Communicate like a quarterback Lead the offense. Make the calls. Own the outcome. Give the team confidence to execute without hesitation. Reduce latency. Get everyone in one thread or room. Set fast check-ins. Cover off-hours. Keep signal ahead of chaos. 6. Shrink the loop. Move to 1-day execution cycles. What did we try? What happened? What’s next? Short loops create momentum. Fast learning is fast winning. 7. Unblock the team (and prep the company to help). You are not a status collector. You are a momentum engine. Clear paths. Push decisions. Put partner teams on alert for support. Crises expose systems. And leaders. Your job is to land the plane. Once it’s down, figure out what failed, what needs to change, and how we move forward. Land the plane. Learn fast. Move forward. That’s how successful operators lead through it.

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?

If a major tech incident hit your organization tomorrow, would your executive team know how to respond? I’ve been in rooms where systems were down, information was incomplete, and every decision carried real consequences. In those moments, preparedness isn’t a binder sitting on a shelf. It shows up in the quality of leadership decision-making under pressure. There are three stages of crisis response during a cyber incident: before, during, and after. Each one requires different executive discipline. Before an incident - Clarify who has decision authority. - Align on risk tolerance at the board and executive level. - Rehearse executive communication plans. - Agree in advance on what transparency looks like during a crisis. During an incident - Avoid reactive decisions driven by fear. - Prioritize action over consensus-building. - Delegate execution to the technical experts. - Avoid speculation. Make decisions based on verified facts. After an incident - Run a rigorous, blameless review. - Fix structural weaknesses, not just surface symptoms. - Reinforce accountability without triggering defensiveness. - Institutionalize what was learned. Technology will fail at some point. That’s the nature of complex systems. What matters is whether your leadership team has already been tested before that moment arrives. #BusinessLeaders #Cybersecurity #RiskManagement #LeadershipDecisionMaking #TechnologyRisk

At Boeing, Deloitte, and Baker Hughes, I was one of the guys who decided if a cybersecurity threat required calling the FBI. Today, I use that decision-making framework to build a $243M real estate empire. As a cybersecurity incident commander at Baker Hughes, when a threat hit, I had seconds to make critical decisions. A security alert comes in: something's wrong, potentially very wrong. My job wasn't just to respond - it was to assess, prioritize, and decide who needed to be involved. Is this urgent or can it wait? Minor issue or major breach? Handle internally or need external help? And the biggest question: Is this serious enough to call the FBI? That wasn't taken lightly. Calling the FBI meant the threat was severe - potential data breach, nation-state actors, serious financial implications. The decision-making process: 1. Identify: What's happening: Real threat or false alarm? 2. Assess severity: How bad is it and what's at risk? 3. Contain: Stop it from spreading. Like a fire - don't let it burn through the whole house. 4. Determine stakeholders: Who needs to know: Leadership? Legal? FBI? 5. Recover: Once contained, how do we restore systems? 6. Root cause analysis: What caused this and how do we prevent recurrence? I made these decisions under pressure, fast, with incomplete information, millions of dollars and company reputation on the line. Here's what that taught me: 1. Speed matters, but precision matters more. You can't freeze, but you can't panic. Assess quickly and act decisively. 2. Know when to escalate. Some problems you handle internally. Some require bigger resources. 3. Containment first, then recovery. Stop the bleeding before treating the wound. 4. Always do root cause analysis. If you don't understand what went wrong, it'll happen again. Today, I apply this framework to real estate investing at XSITE Capital Investment: Identify: What's the opportunity? What are the risks? Assess: Is this a good deal or are there red flags? Contain risk: What due diligence do we need? Determine stakeholders: Who needs to be involved? Execute and monitor: How do we ensure performance? Learn and improve: What worked? What didn't? The pressure of deciding whether to call the FBI taught me how to make high-stakes decisions quickly and accurately. That skill translates directly to real estate: assessing deals, protecting investor capital, knowing when to move forward or walk away. Different industry. Same decision-making framework. What high-pressure experience taught you skills you use in your current career?

9 out of 10 engineering leaders reverse their emotional intelligence at the worst possible moment. They micromanage when teams need space. They vanish when teams need technical leadership. The pattern shows up everywhere: The VP who rewrites code during sprint planning but goes silent when production burns. The engineering director who can't let teams architect solutions but disappears during crisis calls. This costs you everything: Your best engineers leave because they can't grow, then watch you vanish when things break. Your team's trust erodes. Your credibility becomes situational incompetence. Here's what changed my understanding completely: 3 AM. Huge retail client's entire payment system crashes during their biggest sales day. $50K bleeding per hour. Team paralyzed. Junior developer hyperventilating. Senior architect stuck in analysis paralysis for 2 hours. As Solutions Architect, I had a choice: Stay in my "leadership lane" and coach from the sidelines. Or violate every management book and dive into the code myself. I grabbed my laptop. Found the database deadlock in 20 minutes that they'd missed for hours. System restored. Revenue bleeding stopped. Client saved their biggest sales day. But the real impact wasn't the fix. The team watched a leader step in without blame during the moment that mattered most. That night taught me the framework that separates adaptive leaders from rigid ones: Your emotional intelligence requirements flip based on the situation. Same leader. Completely different EQ skills. CRISIS MODE - Lead from the front: ↳ Self-awareness: Recognize when your technical skills matter more than your title ↳ Humility: Code-level problem-solving regardless of organizational chart ↳ Ego management: Solution over status, every single time ↳ Calm under pressure: Your stress becomes their panic - manage it ↳ Technical empathy: Feel the weight of what your engineers are carrying NORMAL OPERATIONS - Lead from the back: ↳ Trust: Your team solves it better when you're not hovering ↳ Patience: Growth happens slower than your impatience wants ↳ Restraint: Keep your hands off the keyboard when fingers itch ↳ Active listening: Hear the problems they're not saying out loud ↳ Psychological safety: Failure becomes learning when you're not judging ↳ Empowerment: Autonomy with availability, not abandonment Get this right: teams innovate fearlessly and execute flawlessly under pressure. Get this wrong: teams stagnate during calm and collapse during crisis. Your comfort zone isn't what your situation requires. Crisis demands technical courage. Innovation demands emotional maturity. Before you step in today, ask yourself: Does this situation need my technical skills or my restraint? ♻️ Share this to your network. 🔔 Follow Dan Tudorache for leadership insights that match what your technical team actually needs right now.

When I was in flight school, we were taught a protocol for emergencies that every leader facing a crisis should know, and I’ve (thankfully) used it more in business than I ever did in the cockpit. It’s deceptively simple: 1. Aviate: This comes before anything else. Don't troubleshoot, don’t panic, don't immediately grab the radio. Keep the wings level and maintain airspeed—fly the plane–because if you crash, nothing else matters. 2. Communicate: Once you’ve stabilized the airplane, THEN get on the radio, explain what’s happening, ask for help, and coordinate. 3. Navigate: The final step is figuring out where to land, adjusting course, and planning your approach. But this strategic thinking can only happen after you’ve stabilized the airplane and are communicating. The sequence matters, and most leaders get it wrong. In a crisis, their first instinct is to problem solve and plan. They jump straight to emergency meetings before first ensuring the business can operate properly and that all the right people–employees, clients, partners, vendors, etc.–are aware of the issue. Fly the airplane first. Then communicate. Then and only then, use all available resources to navigate and adjust course to land safely.

One of my students lost $150,000 in a single day. When he told me this on our coaching call, I asked him: "Wouldn't you quit trading after that?" He didn't. Instead, he went on to tell me how your ability to handle pressure determines your ceiling in business. And he's right. I see this same principle play out every day managing operations across our companies. When you're down six figures in a single morning, emotion wants to take over. Panic tells you to close everything. Fear tells you to never trade again. Anger tells you to double down and make it back. All three will destroy you. Same thing happens when you're running a company with 220 employees - A client threatens to leave - A key hire quits - Revenue drops 30% in a month You need the nerve to stand in the loss and make the right decision anyway. That's ultimately what separates entrepreneurs who scale from those who stay stuck. But reaching the point where you can operate under massive pressure takes time. It helps to first put yourself in low-stakes pressure situations deliberately - Take the meeting that makes you nervous - Make the hire before you feel ready - Launch the campaign without perfect copy. Each time you do this, you're training your nervous system to stay calm when things get real. Create a decision protocol before the pressure hits. When revenue drops, what three questions will you ask before reacting? When a client threatens to leave, what's your step-by-step process? Write these down now (not during the crisis) Then build a support system of people who've been through it. Find three entrepreneurs who've lost clients, missed payroll, or had their business nearly collapse, and talk to them monthly. Their perspective will anchor you when your world feels like it's falling apart. Track your emotional patterns under stress. Do you freeze? Do you overreact? Do you make rash decisions? Know your default so you can catch yourself before it takes over. The next time pressure hits, pause for 60 seconds before you do anything. Breathe. Ask yourself what decision you'd make if this wasn't urgent. Then make that decision. Your capacity to handle pressure is built through repeated exposure and intentional practice. So start building it today.

The Silence of Hesitation is Louder Than a Crash, The Cost of "Wait and See" In leadership, we often fear the "Wrong Decision." But we rarely account for the silent, compounding cost of The Delayed Decision. Look at this video: The signs were there. The cracks were visible. There was a window of time -perhaps only seconds- where an intervention could have changed the outcome. But when the ground starts to shift, "Wait and See" is the most expensive strategy you can own. The Leadership Lesson: In a crisis, Analysis Paralysis is just failure in slow motion. Here is how high-stakes leaders navigate these moments: Trust the "Early Warning" System: Your intuition and your team’s "gut feeling" are data points. If the front line says the wall is cracking, don't wait for a 50-page PDF report to confirm it. Speed is a Feature, not a Bug: In stable times, we optimize for perfection. In a crisis, we optimize for momentum. A 60% correct decision made now is often safer than a 100% "perfect" decision made after the collapse. The Risk of Inertia: We spend hours calculating the "Risk of Action." How much time do we spend calculating the "Risk of Doing Nothing"? Inertia isn't safety; it’s a gamble that the environment will stop changing. Believe me, it won't. The Bottom Line: As leaders, we aren't just here to manage the "Green" days. We are here to have the courage to make the hard call when the dashboard turns "Red." When you see the cracks, don't just watch. Lead by Act. #ADVANCEINSIGHT #Leadership #DecisionMaking #CrisisManagement #PRINCE2Ambassador #StrategicLeadership #GrowthMindset #ExecutiveExcellence #RiskMitigation

When your AI system fails, every minute counts. Most companies panic and make the crisis worse. The playbook that prevents disasters: Step 1: Immediate Assessment (0-15 minutes) Identify scope and severity of AI failure. Determine if customer data or safety is at risk.  Assess legal and regulatory implications. Document timeline of events for investigation. Step 2: Containment (15-30 minutes) Shut down affected AI systems immediately. Switch to manual backup processes. Prevent further automated decisions or actions.  Isolate compromised data or systems. Step 3: Communication (30-60 minutes) Notify internal crisis response team.  Alert legal counsel and compliance officers. Prepare holding statements for customers and media.  Contact insurance providers if applicable. Step 4: Customer Impact Mitigation (1-4 hours) Identify all affected customers and transactions.  Reverse incorrect AI decisions where possible.  Provide direct communication to impacted users.  Offer remediation or compensation as needed. Step 5: Root Cause Investigation (4-24 hours)  Preserve all system logs and data trails. Engage technical teams to analyze failure points.  Review AI training data and model performance.  Document findings for regulatory reporting. Step 6: Regulatory Response (24-72 hours) File required incident reports with regulators.  Coordinate with legal teams on disclosure requirements.  Prepare detailed timeline and remediation plans.  Engage external experts if needed for credibility. Step 7: System Recovery (3-7 days) Implement fixes to prevent recurrence. Test all systems thoroughly before redeployment. Gradually restore AI functionality with monitoring. Update governance and monitoring procedures. Step 8: Post-Crisis Review (1-2 weeks) Conduct comprehensive post-mortem analysis.  Update crisis response procedures based on learnings.  Provide transparency report to stakeholders.  Strengthen AI risk management frameworks. When AI crises hit, two things happen: Some companies have playbooks ready and execute flawlessly. Others panic, make emotional decisions, and turn failures into disasters. The difference isn't luck or resources. It's preparation. The companies that survive AI failures practice crisis scenarios. They choose transparency over cover-ups. They treat failures as learning opportunities, not scandals. The ones that don't survive wait until disaster strikes to figure out their response. They hide problems until they explode publicly. They make reactive decisions that amplify the damage. Your AI crisis response determines whether failures become learning opportunities or business disasters. Are you prepared for when your AI fails? Found this helpful? Follow Arturo Ferreira and repost.