Как управлять командой, когда всё вокруг меняется / Оскар Конюхов

Business/process summary (team management in uncertainty)

Core message

Managing teams in highly uncertain environments requires:

• Structured risk management
• Multi-plan execution
• Clear authority/roles

Leadership should empower specialists (e.g., meteorologist) rather than micromanaging.

How they organized execution (project “startup” mindset)

• Treated the expedition as a startup / first-of-its-kind program: an international build with cross-functional experts under one mission “flag”.
• Recognized aviation/flight constraints as a high-regulation domain, requiring compliance and permissions management.
• Built parallel plans (explicitly “3–4 plans”) because global projects rarely have a single deterministic outcome.

---

Risk management playbook (explicit pillars)

They repeatedly used a 4-pillar risk framework:

• Human factor: pilot errors, fatigue, mistakes
  • Mitigation: procedures, sleep/rest design, alarms, redundancy
• Hardware/technical failures: system failure and ability to repair/replace in-flight
  • Mitigation: continuous testing of subsystems (burners, valves, instruments)
• Environment/weather: turbulence, jet streams, storms/supercyclones
  • Mitigation: route planning with continuous expert updates
• Force majeure: extremely hard-to-model events
  • Mitigation: contingency decisions and emergency/landing/rescue procedures

Motto / operating principle: “Hope is not the strategy” (explicitly stated as a team doctrine).

---

Leadership & team operating tactics

1) Build decision confidence through “confidence checks”

• On the 10th day (stress peak), the leader convened a cross-functional meeting.
• Each department assessed whether their systems could handle a proposed maneuver.
• Voting/commitment mattered: the leader wanted team confidence to translate into execution quality.

2) Delegate with accountability (no blanket double-checking)

• Trust model: allow experts to own their domains to avoid demotivating constant oversight.
• Accountability: mistakes by experts can risk the entire project.
• Leadership model: assemble the right team + operate under uncertainty, and let the right person take command when expertise is required.

3) “Authority earned” via operational knowledge

• Credibility comes from having done the hard domain work first (permits, operational reality), so the team accepts decisions under uncertainty.
• Example handoff: meteorologist David Dehinao led in crisis because he had uniquely relevant expertise.

---

Scheduling / milestones & KPI-like targets

• Total timeline: ~3 years from planning/contracting to flight preparation.
• Hard launch date target: June 1, 2016 (key milestone: “shell, helium, team—everyone in Australia”).
• Weather window waiting: ~1.5 months on-site.
• Flight duration targets:
  • Objective to beat American record: 13 days (claimed for Steve Fawcett)
  • Planning expectation: ~15 days
  • Framing: “minimum goal = circumnavigate, maximum = break record”
• Budget (business scale indicator): more than $2.5M

---

Operational execution examples (concrete “how-to”)

Multi-stage technical readiness

• Two failed launches/aborts:
  • Meteorologist weather doubt first time
  • Technical problems second time
• Psychological management:
  • Controlled “stress tests” rather than assuming everything is guaranteed

Aviation-grade automation + human fatigue management

• Autopilot designed for single-pilot operation:
  • Triggered based on barometric pressure to maintain flight level
  • Includes alert logic to restart burners when the balloon cools/descends
• Sleep/rest protocol:
  • Pilot sleeps in short windows (e.g., 30 minutes sleep, then 3 hours work)
  • Automation is required to maintain safety margins
• Anti-sleep failure strategies:
  • Extra alarm clocks
  • A “life hack” redundancy (key + metal pan) as a safety mechanism

Reliability under extreme cold: analog instrumentation “fail-soft”

• Electronics vulnerable to -40°C external / -30°C internal freezing.
• Decision: use analog gauges and maintain procedural capability if screens/electronics freeze.
• Benefit: reduces single-point-of-failure risk in “unknown unknowns.”

---

Permits, governance & stakeholder management (GR ops)

International permissions as a “workstream”

• Required entry/overflight permissions for 5 countries in the southern route:
  • Australia (start), New Zealand, Chile, Argentina, South Africa
• Expansion risk:
  • Considering the northern hemisphere could have expanded to ~25 countries
• Process described:
  • Initial aviation authority rejections
  • Escalation through embassy, military attachés, and influential local public/travel leaders
• Example constraint:
  • Uruguay denied permission, requiring contingency planning under force majeure

---

Case-study learning from predecessors (competitive benchmarking)

They compared their plan against prior attempts and extracted “root causes”:

• Steve Fossett / American:
  • Failures referenced included cases like fuel cutoff during sleep and lack of alarm redundancy
• Richard Branson:
  • Failures attributed to poor knowledge of material and tools
  • Their team consulted Branson’s team and applied lessons

Applied lesson

“Any project is always a startup”—but you should start faster by incorporating predecessor mistakes instead of relearning everything.

---

Emergency management case (Uruguay / airspace denial)

• Meteorologist guided route; pilot behavior/altitude changes caused drift leading to illegal airspace crossing risk.
• Authorities threatened:
  • forced landing
  • aircraft scrambling (“landing impossible without major actions”)
• Contingency procurement:
  • Used a specialized permissions service on short notice
  • Initially quoted $25,000; ultimately permission cost was waived (“do it for free… recognition/mentions”)
• Outcome:
  • Route corrected without catastrophic operational consequences

---

Weather crisis decision (supercyclone / Antarctica routing)

Scenario planning under “force majeure”

• Trigger:
  • powerful “supercyclone” in the Indian Ocean near Madagascar, even during winter (unexpected)
• Flight constraints:
  • Oxygen/altitude limit: 10 km practical ceiling (doctor constraint)
  • Fuel and oxygen constraints for survival and performance
• Proposed options:
  1. Drop the balloon capsule into the ocean and run rescue operations
     • Ships arrive in 3–4 days
  2. Move with the cyclone
     • Adaptive pathing risk; could lead to very low probability rescue
  3. Use a jet-stream branch toward Antarctica and pass behind the cyclone
     • Return to Australia after the cyclone clears

Decision governance

• On day 10, cross-department meeting validated feasibility:
  • Burners confidence: equipment tested and expected to keep operating
  • Fuel: enough for ~5 more days
  • Doctors: stressed risk but supported viability
• Meteorologist scrutiny:
  • Survived heavy questioning from “100 pairs of eyes”—a benchmark for leadership assurance

---

Results / KPIs (outcomes)

• World records achieved
  • Fastest round-the-world balloon flight (fastest time vs predecessor; also “greater distance in less time”)
• Awards
  • FAI Pilot of the Year (as stated)
  • “pilot of the year” continuity noted alongside Yuri Gagarin (historical reference)

---

Marketing/communications angle (lightweight but business-relevant)

• Media/stakeholder visibility:
  • Launch in Perth under 15–20 TV cameras
  • Emphasis on international recognition and reputation building for sponsors/partners
• GR/PR integration:
  • Sponsorship + PR positioned as a merged synergy—stakeholder value beyond operations

---

Actionable recommendations distilled (for team leaders)

• Establish a 4-pillar risk model (human + hardware + environment + force majeure) and operationalize contingencies.
• Use a multi-plan strategy (not one plan) and define decision points early.
• Ensure specialist leadership: empower the expert when their domain is decisive (meteorologist in crisis).
• Reduce single-point failures via fail-soft design:
  • analog instruments when electronics freeze
  • sleep automation + alarms
• Treat permitting/regulatory work as a first-class operational stream with escalation paths and stakeholder mapping.
• Require department-level confidence before major maneuvers; don’t delegate decisions without validating feasibility.
• Delegate to earn momentum—avoid constant double-checking that erodes concentration and morale.

---

Presenters / sources mentioned

• Oscar Konyukhov (speaker)
• Fedor Konyukhov (pilot; main mission figure)
• Steve Fossett / Steve Fawcett (referenced predecessor)
• Richard Branson (referenced predecessor; consulted via team)
• Don Cameron (Cameron Balloons founder; balloon builder)
• David Dehinao / Dejinao (meteorologist; key technical lead)
• Bruce Comstock (developer of key autopilot component; referenced)
• John (Australian pilot mentioned as involved during landing/execution)

Organizations/brands referenced:

• Yandex
• Cameron Balloons
• Morn
• FAI Aeronautical Federation (award context)
• Olympic Committee (Lausanne)
• A permissions specialist company (owner waived a fee)