Delegation During Crisis

C2 Miniseries - Part 9: Delegation as the Real Kill Chain For years, we have treated delegation as a “leadership style” question. It isn’t. In modern conflict, delegation is a structural requirement. It is the difference between initiative and paralysis. Between shaping the fight and reacting too late. Between decision advantage and operational drift. Ukraine has made this brutally clear. Tempo is measured in days, sometimes hours. Information is degraded. Communications are contested. Deception is constant. Political and legal constraints lag reality. And yet, decisions still have to be made immediately, responsibly, and under pressure. In this environment, no commander can centralise control and still remain effective. This article looks at delegation not as a soft skill, but as the real kill chain of modern C2: how authority is designed, how it flows, how it is protected by doctrine and process, how it is reinforced by culture, and how it determines whether technology becomes an advantage or a crutch. Because when delegation is unclear, everything slows down. And when everything slows down, the adversary wins. If we want credible deterrence, resilient command, and real multi-domain integration, we have to stop treating delegation as optional and start treating it as operational infrastructure. This is about how command actually works when the fog is thick, the feeds are lying, and there is no time for comfort. #CommandAndControl #C2 #MilitaryLeadership #Delegation #Deterrence #NATO #Defence #Security #MultiDomainOperations #HybridWarfare #UkraineLessons #DecisionAdvantage #Interoperability #LeadershipInCrisis #Resilience #EuropeanSecurity

How to Rescue a Dying Project , Without Burning Out Your Team Let’s be real for a moment: No project is invulnerable to crisis. If you’ve been in the game long enough, you’ve seen deadlines slip, scope creep get out of control, and your team’s morale dive like it’s trying to break records. But here's the truth: You can turn things around without losing your team’s well-being. It’s not about pulling off a miracle,it’s about managing the chaos with purpose and keeping your focus on what really matters. Here’s what I’ve learned: 1️⃣  Step Back and Assess the Situation When everything is on fire, your first instinct might be to act fast. Nevertheless, sometimes the best thing you can do is to stop and think. I’ve inherited projects on the brink of collapse, and when I paused to ask, “What’s the root cause of this problem?” instead of rushing in to fix symptoms, it made all the difference. 2️⃣ Prioritize Ruthlessly No project is too far gone if you simplify. The number of tasks and deliverables often grows exponentially in a crisis. The key to recovery is deciding what truly matters and leaving the rest behind. In one project, we reduced the list of “urgent” tasks from 50 to just 5 critical items and suddenly, the team had clarity and focus again. 3️⃣ Delegate with Confidence If you’re trying to do everything, you’re setting yourself up for failure. Trust your team to own their roles. Yes, this means giving up control (and I get that it’s hard), but the truth is, your team has expertise you might not have. I found that giving people autonomy created ownership, and that’s where the magic happened. 4️⃣ Over-Communicate, Especially When It’s Hard Bad news doesn’t get easier with time, and silence is the enemy of progress. Whether it’s with your team or stakeholders, keep communication clear and consistent. When things went sideways on a project I led, I over-communicated, weekly check-ins, constant updates, and candid conversations. The trust we built made all the difference when we had to course-correct. 5️⃣ Don’t Forget the Team’s Health A healthy team is a productive team. If you’re burning the candle at both ends, so are they. Stress is contagious. Show up with empathy and model balance. Celebrate progress, no matter how small. And don’t just talk about self-care, encourage it. I’ve found that teams are resilient, but only when they feel supported. 🔥 Remember, projects don’t need a superhero to save them. They need a leader who knows how to navigate chaos, prioritize, delegate, communicate, and protect the team’s well-being. If you can do that, you’ll pull through and your team will thank you for it. Feel free to add and share any lessons learned in comments ! #Leadership #ProjectManagement Innovera Conseil

What’s your job? One of the biggest mistakes I see leaders make during a crisis is becoming too involved. As pressure rises, they start solving every problem, making every decision, and jumping into every conversation. It feels productive because they're busy, but the moment you start doing everyone else's job, you stop doing your own. I learned this lesson in the special forces. As junior leaders, we naturally wanted to be in the fight. We wanted to be pulling the trigger, making things happen, and solving the immediate problem in front of us. But as I became more senior, my role changed. It was no longer my job to be the first person through the door. My job was to maintain situational awareness, coordinate the team, and identify the problems that everyone else was too busy to see. I used to tell my team that if they ever saw me getting dragged into the fight, they were to pull me back or simply swap places with me. Because the team didn't need another operator. They needed a leader. The same principle applies in business. When leaders become consumed by the spot fires, their perspective narrows. They can become reactive, miss emerging risks and opportunities, and lose sight of the strategic picture. We need to step back and gain perspective. When you feel yourself getting pulled into the weeds, pause and ask yourself one simple question: "What's my job right now?" Is it to solve this problem, or is it to ensure the team solves it? That question changed the way I lead. It reminds us to: - Pause before stepping in. - Delegate work that doesn't require our involvement. - Protect our situational awareness instead of getting caught up in spot fires. - Stay calm, because our teams will take their cue from us. - Give ownership of tasks to the team. Leadership under pressure isn't about doing more. It's about making sure you're doing the things that only the leader can do. #leadership #highperformance #leadershipdevelopment #ProfessionalLeadership

Delegation isn't about letting go or hovering (both approaches fail) The "let go" myth: Leaders think good delegation means handing something off completely. No. Good delegation means installing verification systems before you release control. You're not letting go. You're building visibility infrastructure. Abdication has no feedback loops. Systematic delegation catches problems when there is still time to course-correct and succeed. The "checking in is micromanaging" myth: Pre-scheduled checkpoints with clear criteria aren't micromanagement. That's quality assurance. Micromanagement is unplanned, anxiety-driven interruption. There's a difference. The "delegation saves time" myth: First delegation? Costs you 3x the time. Tenth delegation of similar work? 0.3x. Delegation isn't a time-saving tactic. It's a capability investment. Treat it like one. The "they should just know" myth: Your standards live in your head. Delegation without explicit specification transfers responsibility but not capability. Write down the outcome. Document decision boundaries. Give example scenarios. That's how standards transfer. The "can't delegate accountability" myth: You can and must delegate accountability with structured reporting. Your team owns the execution path and reports on results. What you can't delegate is final outcome ownership to stakeholders. That stays with you. Here's what systematic delegation actually looks like: Define the measurable outcome. Document where they can make calls and where they can't. Identify likely edge cases. Establish what success looks like. Then set milestone checkpoints. Not random status updates. Predetermined progress checks with pre-defined escalation triggers. After completion, analyze together. Train pattern recognition. Expand complexity based on what they demonstrated. Update your templates for next time. What happens: Within 90 days, you recover 60% of your time. Your team handles 3x the work volume. Crisis interventions drop 75%. Decisions stop routing back to you. The real choice: You're not choosing between involvement and distance. You're choosing between reactive chaos and engineered leverage. Delegation without systems creates more work for you. Systematic delegation creates self-reinforcing capacity. Most leaders abdicate or micromanage because they never built the infrastructure in between. Build it once. Benefit forever.

"It's Just Easier to Do It Myself" My client, Sarah, a successful Head of Operations, was completely overwhelmed. She was working 60-hour weeks and consistently hitting a ceiling on her team’s productivity. When we first discussed delegation, her immediate response was the same one I hear from many busy leaders: "I don't have time to show someone else. It's easier just to do it myself." Sarah wasn't wrong. In the short term, doing the task herself saved 30 minutes. But the long-term impact of this choice was devastating: Sarah was stuck in the day-to-day work, neglecting critical strategic planning. Her team felt untrusted and couldn't develop their skills, leading to high turnover. She was burning out fast. Delegation felt like losing control. She feared the mistakes her team would inevitably make, and she struggled with the initial investment of time required for training. We focused on reframing delegation not as a loss of control, but as an investment in leverage. Our process involved three key steps: The 2x Rule: We identified tasks that took her less than twice the time to delegate than they took to execute. These were immediate delegation opportunities. The "Good Enough" Mindset: We worked to redefine perfection. We established clear, measurable standards for success, allowing the team to deliver a "good enough" outcome (80% perfect), which freed Sarah to focus on the high-level 20%. Sarah committed to spending just one dedicated hour each Monday morning on nothing but delegation and team development. This forced the initial investment and broke the cycle of continuous, reactive execution. Within eight weeks, Sarah reduced her weekly hours to 48. She completed a major strategic review that had been pending for six months, and her team, empowered and trusting, began proactively identifying and solving problems. The delegation "time cost" was quickly converted into team capacity and leadership bandwidth. If the fear of losing control or the feeling that you don't have time to delegate is holding you back from your next level of leadership, let's talk about.

Two weeks into regional turmoil, I am standing today in a room with Hospitality Services’ top management, delivering a training on delegation. And that feels important. Because in times of crisis, many leaders make the same mistake: They tighten their grip. They centralize more. They trust less. They carry more than they should. It feels responsible. But often, it is fear disguised as leadership. The truth is this: In times of uncertainty, investing in your people is not optional. It is strategic. You do not build resilience in the middle of a crisis by controlling everything yourself. You build it by strengthening the people around you before the pressure breaks the system. That is where delegation becomes more than a management skill. It becomes a leadership decision. Real delegation says: • I trust people with responsibility, not just tasks. • I build capability, not dependency. • I create clarity so decisions do not die at the top. • I make the organization stronger than one person’s bandwidth. In unstable times, this matters even more. Because crises expose weak structures. They reveal where leadership has become bottleneck. They show whether a company was built on systems and trust, or on one exhausted person trying to hold everything together. So if you are leading a company right now, ask yourself: Am I trying to protect the business by holding on tighter, or by building stronger people around me? This is why, even in the middle of regional tension, leadership development still matters. Training still matters. Delegation still matters. Because when the pressure rises, the companies that endure are not the ones with the busiest leaders. They are the ones with the strongest teams. #Leadership #Delegation #CrisisLeadership #Management #BusinessResilience

Day 5 — Crisis Decision-Making Under Pressure. People who make the best decisions under pressure aren’t luckier - they follow a repeatable process that turns limited data into clear action. Good crisis decision-making is fast and disciplined: rapid enough to matter, structured enough to be safe and ethical. ■ The OODA Loop — A Practical Mental Model. OODA stands for Observe → Orient → Decide → Act. Use it as a continuous loop during a crisis: 1. Observe — Gather the most relevant facts you can (what happened, where, who’s affected, immediate hazards). 2. Orient — Quickly place those facts into context: what does this mean for life-safety, escalation risk, and critical assets? Consider rules, SOPs, and legal/ethical constraints. 3. Decide — Choose the best immediate action with the information available. Prioritize life-safety and containment. 4. Act — Execute the decision decisively, then return to Observe to assess results and iterate. ■ Prioritization: What to Decide First. When seconds matter, use a simple priority rule: 1. Protect life — People first (staff, visitors, responders). 2. Stabilize the scene — Stop the event from getting worse (contain hazards, isolate areas). 3. Preserve critical operations — Maintain or recover business-critical functions as feasible. 4. Protect assets & evidence — Secure evidence for later investigation once safety is assured. 5. Communicate — Inform command, responders, and affected persons with short, factual updates. If forced to choose, always default to actions that preserve life and enable safe rescue or medical care. ■ Making Decisions with Limited Information. Real emergencies rarely provide full clarity. Use these rules to decide faster and safer: • Use worst-credible-case thinking — Act to prevent the most harmful plausible outcome, not the most optimistic one. • Prefer reversible actions — If you can contain or isolate without irreversible impact, do so while more info is gathered. • Rely on SOPs and checklists — Predefined decisions reduce cognitive load and error under stress. • Delegate authority — Empower trained deputies to act when communication is limited. Clearly assigned authority speeds response. • Ask for a short confirmation — “Confirm: evacuation of Zone B now?” — keeps radio traffic tight and reduces misinterpretation. #CrisisManagement #DecisionMaking #OODA #EmergencyResponse #CrisisLeadership #RiskManagement #IncidentCommand #SafetyLeadership #OrganizationalResilience

How I broke the firefighting cycle as a CTO And the key step you can take to do the same...   When I first became a CTO, I spent my days constantly putting out fires. Every week, I had a plan. By Monday afternoon, that plan was in ruins.   A system crash here, a critical bug there – my entire day was consumed by firefighting.   Instead of leading, I was reacting. Always stuck in yesterday’s problems.   For a while, I thought that’s just what the job was. But the truth is, firefighting can’t be the default. If you’re always reacting, you’ll never have the space to plan ahead and lead proactively.   My turning point? Delegation.   I resisted at first. I thought I could handle things faster myself, and I felt like I should be protecting my team from a burden I alone should bear. But I was wrong. Doing everything myself was slowing down both my team and me.   Learning to delegate didn’t just free up my time. It empowered my team, boosted productivity, and shifted my focus from daily crises to long-term strategy.   Here are the 5 key steps I follow to delegate more effectively:   1. Prioritize what only I can do Not everything needs my attention. I identify high-impact tasks only I can handle, and delegate everything else to my team.   2, Align tasks with team strengths Everyone has a unique skill set. I assign tasks based on those strengths to ensure each person thrives and learns.   3. Be crystal clear with expectations I lay out what needs to be achieved, why it matters, and when it’s due. Clear expectations prevent confusion and reduce assumptions and rework.   4. Trust but verify Delegation doesn’t mean disappearing. I check in regularly to observe progress, and I give the team the autonomy to deliver results or learn from the experience.   5. Offer feedback and support Delegation is about growth. Being available for questions and providing constructive feedback helps my team improve with each task.   Better delegation allowed me to escape the daily grind and focus on what truly matters – leading strategically and driving innovation.   If you’re stuck in firefighting mode, maybe it’s time to take the first step and delegate. Your team – and your future self – will thank you.   P.S. I’m Adam Horner, and I help CTOs, startups, and scaleups accelerate through CTO coaching and fractional CTO services.   Follow and share as I talk about how to excel as a CTO. Click “Visit my website” above to learn more.

Delegation 1) Plan the daily/shift workload Review the occupancy level (rooms to clean), events, special requests, and expected arrivals/departures. Look at priorities: departing rooms first, VIPs, urgent guest needs, public areas, laundry/dry cleaning needs. 2) Divide work into “zones” and “functions” Delegation is clearer when tasks are split like: By area (zones): guest floors, corridors, lobbies, restrooms, back-of-house corridors By function: room attendants, public area team, laundry/linen attendants, supervisors/inspectors, deep-clean task force 3) Assign to the right people (based on capability) Consider each staff member’s experience, speed, attention to detail, and absenteeism. Put stronger cleaners/supervisors on high-standards areas (VIP floors, suites, after departures). 4) Give specific instructions (not just “clean”) For each delegate/team member, the executive housekeeper clarifies: What to do (exact task list) Where (room numbers, floor, area) Standard (quality checklist: bathroom details, bedding setup, odor control, stain removal rules) Time frame (by what time doors should be ready/rooms closed) Chemicals/tools allowed (safety + correct product use) 5) Use clear communication channels Start with a briefing/stand-up meeting (targets for the shift). Use tools like: duty rosters, cleaning sheets, defect/maintenance request forms, WhatsApp/radio (if hotel policy allows). Ensure everyone knows who to report to for problems. 6) Set control points: inspection and feedback Delegation works only with monitoring: Mid-shift check for progress (especially on departure days) Final inspection before rooms are released Immediate corrective coaching (don’t wait until the end if standards drop) 7) Handle urgent issues with escalation Assign one person as “point contact” for emergencies: lost & found major spills, flooding, pest sightings guest complaints, special requests If needed, the executive housekeeper escalates to maintenance/front office quickly. 8) Maintain fairness and documentation Keep updated work allocation and attendance Record delays, recurring issues, training needs Use these records for performance reviews and scheduling.

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