Framework Note
Fog Filter Visuals

FOG FILTER: A Decision Logic for Leading in the Fog Zone

When first responders arrive at a medical emergency, they do not improvise. They follow a practised sequence of checks and actions. Those steps are designed to override panic, focus attention, and move people into skilled response. Over time, those sequences are taught as simple mnemonics that can be recalled under pressure.

In organisational life, there is no equivalent for the kind of emergency leaders face in the Fog Zone - moments of high uncertainty and high urgency when it is impossible to see clearly and impossible to wait. These are the moments when leaders must make consequential choices under pressure without the benefit of full information or rehearsed expertise.

The FOG FILTER was created as a leadership analogue to those emergency mnemonics. It offers a small set of steps and questions to pull decision-making away from amygdala hijack and back into a deliberate logic.

The Fog Zone: When Every Leader Becomes an Emergency Responder

The Leadership Challenge Framework describes the Fog Zone as the quadrant where uncertainty and urgency are both high. It is distinct from the Expert Response quadrant.

In Expert Response, emergencies are familiar enough to be careers: firefighters, paramedics, emergency physicians, aviation incident teams, cyber incident responders. The underlying problems are known, the response pathways are practised, and leaders specialise in those events.

The Fog Zone is different. It is not a profession. It is a moment in time that can land on any leader, in any sector, without warning. For example:

  • A pandemic emerges and leaders must decide whether to shut down schools or campuses.
  • A company’s production halts because new tariffs suddenly cut access to a critical component.
  • A research team’s stage-three funding for a cancer trial collapses when a donor goes bankrupt.
  • An organisation is suddenly pulled into a political social media storm.
  • An industry is hit by a new automation tool that can do most of what its firms provide, faster and cheaper.

Each of these is different in content. What they share is intensity and uncertainty.

Leaders feel responsibility to staff, clients, communities, or patients. The stakes are high, the timeline is compressed, and there is no established playbook. In that combination, anxiety, stress, and pressure narrow thinking. Common reactions include:

  • freezing or “turtling” - withdrawing and hoping the moment passes
  • acting without forethought because the urgency itself feels intolerable
  • losing composure in public, with staff, or with the media
  • swinging between over-promising and silence

In physiological terms, these are variations of the fight-flight-freeze response. The FOG FILTER is designed as a way back out of that reflexive mode into a sequence of steady, prefrontal decisions.

The Design: Two Stages, One Discipline

The FOG FILTER has two stages:

FOG - Frame, Orient, Gauge
a way to create enough order to think and act together

FILTER - six questions to test potential moves
a way to decide what to do and how to do it without pretending to have more certainty than exists

The tool does not eliminate uncertainty. It organises attention so leaders can move while learning, rather than react from panic or avoid action altogether.

FOG FILTER OVERVIEW
Two-stage logic for high-uncertainty, high-urgency conditions
FOG
Frame
Name what is known, what is unknown, and what matters in the next time window.
FOG
Orient
Align who is responsible for what, how information flows, and who speaks.
FOG
Gauge
Triage where the system is under strain and what must not be allowed to fail.
F
Fast
Is speed essential, or can we wait to refine the frame?
I
Inaction is worse
What deteriorates if we do nothing in this window?
L
Learn
What will this move teach us about the system or the problem?
T
Trust
How will this affect confidence in leadership and the institution?
E
Enable
Does it preserve or expand our room to manoeuvre later?
R
Reversible
If this is wrong, can we adjust or undo it without disproportionate damage?

Stage One: FOG - Frame, Orient, Gauge

The purpose of the first three steps in the FOG FILTER is to provide direction, order, and protection at the moment when the system is most vulnerable to drift, speculation, and fragmentation. In fog conditions, the absence of clear leadership can create a vacuum that accelerates anxiety and undermines coordination.

Frame-Orient-Gauge serves as a stabilization mechanism. It signals that someone is taking responsibility, that there is a process underway, and that the work of making sense of the situation has begun. Human systems rely on authority in moments of crisis; these steps help meet that need without overpromising certainty.

1. Frame

Frame establishes a provisional structure for understanding the situation. It anchors attention and reduces the risk of spiraling narratives.

Leaders:

  • articulate what is currently known
  • name what remains uncertain
  • identify the time horizon that matters immediately
  • establish the top priorities guiding early decisions

The frame is not final. It is a first stabilizing point - something people can gather around instead of filling the vacuum with assumptions.

2. Orient

Orient aligns people enough that they can move together, even while clarity is incomplete.

Leaders:

  • identify who needs to be part of the central response
  • clarify who is monitoring which parts of the system
  • establish simple, reliable channels for updates
  • set expectations for when and how new information will be shared

Orientation ensures that staff, partners, and, when necessary, the public know where coordination sits and how information will flow. It reduces drift and prevents parallel, conflicting responses.

3. Gauge

Gauge is the moment where leaders take stock of where the system is under the greatest strain and where early attention is most needed. It plays a role analogous to triage in emergency response: identifying what must be addressed first because delay would cause irreversible or cascading damage.

Leaders:

  • look for forms of deterioration that may not yet be visible but are accelerating
  • identify which relationships, processes, or functions cannot be allowed to fracture
  • distinguish between noise and true signals of risk
  • scan for pressure points where a small move now could prevent significant harm later
  • assess the system’s current capacity - who is overloaded, what structures are brittle, where existing routines are breaking down

Gauge provides the early prioritization required to stabilize the situation. It focuses attention on what must not be neglected in the first hours or days of a fog-zone moment, allowing leaders to act in ways that protect the system while clarity develops.

Stage Two: FILTER - Testing Potential Moves

Once a basic picture has been formed, leaders face the core Fog Zone challenge: deciding whether to act, when to act, and how to act, without pretending to know more than they do.

The FILTER provides six questions that any proposed move should pass through:

  • F - Fast
  • I - Inaction is worse
  • L - Learn
  • T - Trust
  • E - Enable
  • R - Reversible

The aim is to pull the brain into a structured conversation before committing scarce attention, reputation, or resources.

F - Fast: Is speed essential in this case?

This question asks whether delay will allow harm, cost, or fragmentation to grow.

  • Will waiting make the situation harder to stabilise?
  • Is there a risk of losing critical options if action is postponed?

If speed is truly essential, that affects how much time can be spent refining the frame before moving.

I - Inaction is worse: What happens if we do nothing right now?

Fog can produce hesitation. Leaders may wait for clarity that does not come.

This test asks whether inaction itself is a decision with significant downside:

  • Will silence be read as indifference or confusion?
  • Will people fill the gap with their own assumptions?
  • Is something deteriorating that will be harder to repair later?

If doing nothing is likely to worsen the situation, that strengthens the case for making a move, even if that move is limited in scope.

L - Learn: What will this move teach, even if it is only partially successful?

In the Fog Zone, action is also inquiry.

Leaders ask:

  • What hypothesis does this move test?
  • What can be observed about how people respond?
  • What data will this generate that is not available now?

A move that reveals something important about how the system behaves under strain has added value. A move that produces no new insight carries more risk.

T - Trust: How will this move affect trust?

Trust is often under pressure in fog conditions. The way leaders act and communicate can either reinforce or erode the belief that they are paying attention and acting with care.

Questions here include:

  • How will affected groups interpret this move?
  • Does it align with stated values and past commitments?
  • Does it transparently acknowledge uncertainty where it exists?

A move that significantly damages trust usually requires a very high threshold of necessity.

E - Enable: Does this move create more room for future action?

Some actions preserve options, strengthen relationships, or add capability. Others lock the system into a narrow path.

Leaders consider:

  • Will this move expand or shrink the choices available later?
  • Does it free up resources, capacity, or information?
  • Does it keep critical infrastructure or partnerships intact?

When conditions are foggy, preference is given to moves that enlarge the space for later, better-informed decisions.

R - Reversible: Can this move be adjusted or undone?

Reversibility recognizes that fog conditions are dynamic.

Leaders ask:

  • If this turns out to be the wrong call, can it be corrected?
  • What would unwinding this decision require?
  • Can the move be staged so that commitment increases only as clarity increases?

In situations of deep uncertainty, high-irreversibility actions require extremely strong justification.

Why the FOG FILTER

Fog Zone moments compress time and raise stakes while reducing clarity. In that combination, instinct is unreliable.

FOG FILTER provides the minimum structure required to:

  • steady the system
  • prevent contradictory action
  • think under pressure
  • move without pretending to have certainty
  • preserve options while learning
  • maintain trust during highly visible moments

It does not produce perfect decisions. It produces leaders who can still lead when the conditions for good decision-making are least available.

Case Study
Using the FOG FILTER When a Critical Medical Monitoring System Fails

It is 2:14 a.m. The COO is calling. A core component of the company’s medical monitoring system - used by hospitals to track critical patients and integrated into a large-scale research study with serious financial and scientific stakes - has gone offline.

The failover servers have come online only partially. They are unstable and producing inconsistent data. The specialist who normally leads these escalations is unreachable.

The phone begins to pulse with simultaneous incoming calls: hospital administrators demanding guidance, a partner research institution reporting that their emergency alarms are blaring, and internal teams asking whether they should issue an immediate system-wide alert instructing all users to shut down dependent services.

This is the Fog Zone: high uncertainty, high urgency, and no safe delay. Every instinct is activated - to shout for action, to shut everything down, to over-reassure, to freeze, to choose the first available option simply to relieve pressure.

The goal of the first three steps is to provide direction, order, and protection - for the internal team, the hospitals, the research partners, and, if appropriate, the public. In high-stakes environments, leadership vacuums produce fragmentation, fear, and contradictory instructions. Frame-Orient-Gauge prevents that drift and stabilizes the system long enough to think.

1. Frame

In the first five minutes, Frame establishes a provisional structure. It does not attempt to solve the problem. It prevents spiraling.

A frame might sound like:

  • “Primary servers are offline; failovers are unstable.”
  • “Specialist unavailable; escalation protocols are being engaged.”
  • “Two domains are affected: hospital patient monitoring and continuous research data capture.”
  • “Immediate priorities: data integrity, patient safety, clarity for hospital partners, and continuity where possible.”
  • “Expect the next update in 30 minutes.”

A frame does three things: reduces speculation, demonstrates that someone is taking responsibility, and anchors attention on what matters most in the next hour.

2. Orient

Hospitals, researchers, and internal teams need direction about who is coordinating what.

Orientation might include:

  • Confirming engineering’s lead escalation path and identifying who is reachable now.
  • Assigning one channel for all external partner communication to avoid contradictory messages.
  • Setting a 15-minute internal update cycle.
  • Asking the COO to designate someone to monitor patient-risk reports from hospitals.
  • Identifying who will communicate with the research consortium.
  • Determining when to notify regulatory or compliance contacts, if required.

The point is coherence: one central alignment point, not a dozen independent reactions.

3. Gauge

Gauge functions like triage in emergency medicine: early identification of what cannot be allowed to fail.

Leaders ask:

  • Patient Safety: Are any hospitals reporting compromised monitoring for ICU or neonatal patients? If so, which ones, and what time-sensitivity risks exist?
  • Data Integrity: Is unstable failover producing corrupted or misleading data?
  • Research Continuity: How much data loss can the research partner tolerate before the study incurs irrecoverable cost or must restart segments?
  • Rate of Deterioration: Are more hospitals losing access? Are error frequencies increasing?
  • Capacity: Is engineering stretched beyond its ability to diagnose? Should secondary teams be woken immediately?
  • Communications Load: Are hospital calls multiplying faster than the communication team can respond?

Gauge identifies the elements of the system where delay would cause severe harm. It also reveals which actions must happen within the next 10-20 minutes and which can wait for clearer information. At this stage, the CEO now has temporary stability, clarity about priorities, and enough alignment across the team to evaluate next moves.


Possible actions a CEO could take in this Fog Zone scenario are not one decision but a landscape. Below are examples of proactive moves that satisfy FILTER and moves that look smart on the surface but do not.

1. Immediate System Stabilization Moves
Passes FILTER

Shift engineering bandwidth by pulling senior engineers from nonessential work, waking secondary teams, or borrowing from partner organizations.

Increases diagnostic capacity quickly without closing options.

Passes FILTER

Force a rollback to the last-known-stable state, even if it temporarily reduces functionality.

Stabilises the system, buying time for deeper analysis.

Fails FILTER

Redirect engineering to focus first on crafting a detailed root-cause report for the board.

Logical for governance, but diverts scarce capacity when speed and learning matter most (fails Fast and Enable).

Fails FILTER

Begin upgrading server infrastructure immediately since this failure proves it's outdated.

Strategic instinct, but a long-cycle, non-reversible move mid-fog (fails Reversible and Fast).

2. Protecting Patients and Research Integrity
Passes FILTER

Call the chiefs of staff at the three hospitals most dependent on real-time streams and ask for their on-the-ground assessment of clinical risk.

Targets the highest stakes and improves real-time situational awareness.

Passes FILTER

Request that hospitals temporarily shift to in-house redundancy tools and provide a clear time window for reevaluation.

Protects patients without unnecessary system-wide shutdown.

Fails FILTER

Request that all hospitals send detailed logs and full diagnostic packets before taking any local action.

Reasonable instinct to gather information, but delays safer backup moves (fails Fast and Inaction-is-worse).

Fails FILTER

Ask the research consortium to pause the entire study until clarity is reached.

Protective on the surface, but may trigger irreversible protocol issues and large cost (fails Enable and Reversible).

3. High-Learning-Value Moves
Passes FILTER

Ask engineering to produce two hypotheses in the next 20 minutes - even if tentative - to narrow the search space.

Accelerates focused learning and directs effort.

Passes FILTER

Assign someone to map failure patterns across regions or customer types to see if the outage is clustered.

Transforms noise into usable pattern recognition.

Fails FILTER

Instruct engineering to run every available diagnostic tool to cover all possibilities.

Looks thorough, but overwhelms capacity and slows insight (fails Fast and Learn).

Fails FILTER

Wait for the escalation specialist to be located because they will give the most accurate insight.

Feels prudent, but postpones essential learning steps (fails Inaction-is-worse and Fast).

4. Moves That Build or Protect Trust
Passes FILTER

Call the most influential hospital administrator personally to communicate presence and seriousness.

Signals that leadership is fully engaged and listening.

Passes FILTER

Bring the COO and head of engineering into one unified update call so they speak with a single voice.

Reduces mixed messages and internal misalignment.

Fails FILTER

Share an internal “do not worry” memo to calm staff until facts are clear.

Intended to soothe, but risks credibility once the seriousness is known (fails Trust and Learn).

Fails FILTER

Tell external partners that the team “has narrowed the issue” before that is true, to buy time.

Premature reassurance that is hard to unwind (fails Trust and Reversible).

5. Moves That Enable Future Action
Passes FILTER

Request a temporary engineering “quiet zone” - reducing inbound Slack/email traffic to protect cognitive bandwidth.

Protects the conditions for good technical work without closing options.

Passes FILTER

Pre-authorize overtime or emergency stipends so engineering can call in trusted contractors immediately.

Expands available capacity without adding complexity.

Fails FILTER

Redirect comms to draft a detailed public post-mortem immediately.

Appears transparent, but anchors explanations before facts exist (fails Reversible and Learn).

Fails FILTER

Authorize teams to begin planning major architecture redesigns right now.

Strategic instinct that drains capacity from stabilization (fails Fast and Enable).

6. Moves That Address the Human System
Passes FILTER

Ask the COO or CHRO to check on engineering’s physical and emotional state - exhaustion creates real risk.

Directly supports the people doing the hardest work.

Passes FILTER

Pull one calm, seasoned leader into the communication team to distribute pressure.

Balances cognitive and emotional load during the response.

Fails FILTER

Tell the team to hold all questions until the next scheduled update, to reduce noise.

Reduces chaos but blocks critical upward signal (fails Learn and Enable).

Fails FILTER

Ask engineering to stop communicating until they have a firm diagnosis.

Removes distraction but increases fog for everyone else (fails Trust and Fast).

8. Moves That Recognize Institutional Politics & External Realities
Passes FILTER

Alert major partners whose own reputations may be implicated if misinformation circulates.

Prevents surprise and builds alignment under pressure.

Passes FILTER

Coordinate with the communications director to map which stakeholders would feel blindsided if they heard about the outage through external channels first.

Focuses relationship management where it matters most.

Fails FILTER

Alert all regulators immediately out of an abundance of caution.

Reasonable instinct, but premature escalation can trigger complex protocols and reduce maneuvering room (fails Enable and Reversible).

Fails FILTER

Tell partners the outage is likely tied to a known industry-wide issue.

Provides a plausible narrative, but plants a guess as fact (fails Learn, Trust, and Reversible).

Share
Email LinkedIn