The general who never left his office
There's a type of leader that every organization knows but nobody dares name publicly. The one who defers decisions ad infinitum. Who delegates excessively without ever transferring real responsibility. Who claims credit for successes and vanishes at the first sign of trouble.
This leader thrived for decades in stable, predictable, hierarchical environments. Five-year plans worked. Budgets were met. Surprises were rare.
That world no longer exists.
The acronym VUCA (Volatility, Uncertainty, Complexity, Ambiguity) is not a consultant buzzword. It's an analytical framework formalized by the US Army War College at the end of the Cold War to prepare officers for a world where the enemy is no longer identifiable, where alliances recompose in real time, and where the plan doesn't survive first contact with reality.
Transpose that description to the daily life of a CIO in 2026: budget trade-offs under pressure, product strategies upended by AI, time-to-market as the difference between leader and follower, cyber threats evolving faster than defenses. VUCA isn't a metaphor. It's your weekly report.
And the desk-bound leader, the one who manages by PowerPoint and approves by email, is doomed. Not out of malice. Out of structural inadaptation.
The pathologies of pre-VUCA leadership
Before building the alternative model, let's name the pathologies I still encounter massively in European IT organizations:
Decisional paralysis. "Let's wait for more data." Every week of deferral is a week gifted to the competition. The imperfect decision made today is worth more than the perfect decision made in six months.
Phantom delegation. "I'll let you handle it, but keep me informed about everything." That's not delegation. It's surveillance in disguise. The team knows it, and they respond by minimizing risk and asking permission for every micro-decision.
Selective ownership. When the project succeeds: "We achieved a major transformation." When it fails: "The team didn't execute properly." This behavior destroys trust faster than any restructuring.
Management by abstraction. Endless dashboards, dozens of KPIs, and zero contact with the ground. A leader who hasn't opened a terminal or attended a post-mortem in two years has lost the right to talk about "digital transformation."
Aversion to constructive conflict. Soft consensus is the graveyard of innovation. When nobody dares contradict the leader, bad decisions blow up in production.
The military triptych: VUCA, OODA, Mission Command
The military has developed, often through blood and failure, leadership frameworks specifically designed for uncertainty. Three of them form a coherent system that I apply concretely in my engagements with IT leadership teams.
VUCA as an organizational lens
The first instinct when facing VUCA is to treat it as a problem to solve. That's a mistake. VUCA is an environment to operate in, not an obstacle to eliminate.
Each component calls for a specific response:
- Volatility (rapid and unpredictable changes): respond with vision. A team that understands the strategic heading can navigate turbulence without waiting for instructions at every turn.
- Uncertainty (causes and effects that are hard to anticipate): respond with understanding. Invest in telemetry, observability, meaningful SLOs. The more you understand your system in real time, the less uncertainty paralyzes you.
- Complexity (multiplicity of interconnected factors): respond with clarity. Simplify the architecture, reduce dependencies, decouple systems. Technical complexity amplifies organizational complexity.
- Ambiguity (unclear meaning of events): respond with agility. Accept that you won't understand everything before you act. Launch short experiments, measure, adjust.
Replace exhaustive reporting with clarity of intent and disciplined initiatives. That's how you get executive committee buy-in on ambitious roadmaps : by aligning technology with business stakes rather than risk management.
The OODA Loop: deciding faster than the adversary
John Boyd, US Air Force fighter pilot and one of the most influential military strategists of the 20th century, formalized the OODA loop: Observe, Orient, Decide, Act. His fundamental insight: whoever cycles through this loop fastest wins, regardless of the adversary's initial advantage.
Boyd wasn't talking about raw speed. He was talking about decision tempo : observing the field faster, orienting the analysis more quickly, deciding with less friction, acting without delay.
Applied to IT, the OODA loop transforms operations:
Observe : Real-time telemetry, meaningful SLOs measuring actual user experience, intelligent alerts that distinguish noise from signal.
Orient : The most underestimated phase. Contextualizing the observation: is this latency spike an infrastructure issue, a change in user behavior, or the sign of an attack? Orientation requires field experience, not dashboards.
Decide : At the level closest to the problem. The SRE engineer who sees the issue at 3 AM must have the authority to decide and act, without escalating to the CIO.
Act : Action without rollback capability isn't courage. It's recklessness. The loop only works if the action is reversible and its effects feed the next observation.
In cybersecurity, the OODA loop is literally vital. The attacker who cycles faster than the defender wins.
Mission Command: centralized intent, decentralized execution
Mission Command (Auftragstaktik) is the most counterintuitive command framework for a leader trained in a culture of control. Its principle: the commander defines the desired effect and the constraints. Subordinates choose the means and execution.
This doesn't mean anarchy. Mission Command rests on five non-negotiable conditions:
- The intent is crystal clear. Not a vague objective like "improve customer satisfaction." A precise effect: "Reduce the customer portal response time below 200ms at P99 by June 30."
- Constraints are explicit. Budget, authorized technologies, acceptable risk thresholds, dependencies with other teams. Everything that's forbidden is stated. Everything else is permitted.
- Trust is built on the ground. The leader knows their teams' capabilities because they've worked with them, not because they've read their job descriptions.
- Prudent risk is accepted. Perfection is the enemy of maneuver. A team that isn't allowed to fail isn't allowed to innovate.
- After-action review is systematic. Every action, successful or not, feeds collective learning. The post-mortem isn't a trial. It's a briefing.
The hands-on model: five VUCA leadership rules
From these three military frameworks, I extract five rules that I apply as an IT leader and recommend to the executives I advise:
Build a living vision. Not a strategy document frozen in a drawer. A vision in perpetual evolution with the teams, recalibrated every quarter against reality. The vision isn't a decree. It's an ongoing conversation.
Show your doubts. A leader's vulnerability creates the team's psychological safety. "I'm not sure this architecture is the right one. What do you think?" That sentence, said sincerely, unleashes more collective intelligence than ten formal brainstorming sessions.
Share decision-making power. Not phantom delegation. The real transfer of authority, with the means to back it up. The team decides, the team owns the outcome, the team learns. The leader provides the framework and support.
Be a player-coach. The VUCA leader doesn't sit in an ivory tower. They're on the ground. They read code. They attend post-mortems. They know their teams' real constraints because they live them, not because someone reported them in a committee meeting.
Explain the why, constantly. Every decision, every trade-off, every priority shift must be accompanied by its "why." Not to justify ; to enable ownership. A team that understands the strategic rationale behind a decision can adapt it intelligently when conditions change. A team that executes an order can only wait for the next one.
Control is an illusion
In a VUCA world, centralized control is a comforting illusion. The more you try to control everything, the more you slow down, the more you lose touch with the ground, and the more vulnerable you become to surprises.
Only autonomous and aligned teams survive. Autonomous because they have the authority and means to act. Aligned because they understand the intent and share the vision.
Military strategy doesn't offer silver bullets. It offers thinking frameworks forged by centuries of confrontation with uncertainty : frameworks that accept that the perfect plan doesn't exist and that the only viable response is speed of adaptation.
Is your leadership model built for yesterday's world or for the world you actually operate in?