Fear vs Power vs Ambiguity: how to diagnose what’s really happening in your steering committee

For CEOs and COOs who need to restore decision coherence when the steering committee is afraid, territorial, or unclear.

Most steering committees do not stall because the program is complex. They stall because the room is operating in one of three modes: fear, power, or ambiguity. Fear shows up as endless risk spirals and “more diligence” requests that never end. Power shows up as vetoes without criteria, re-litigating past decisions, and side deals after the meeting. Ambiguity shows up as debates about definitions, unclear options, and “what are we even approving?” confusion. Diagnose the mode by watching the language, not the deck. Then intervene with the right mechanism: guardrails and exception paths for fear, explicit decision rights and escalation timers for power, and a one-page decision memo with options and tradeoffs for ambiguity.

The steering committee moment you recognize

It is the weekly steering committee.

The deck is “on track”.

Yet every decision turns into discussion, then defers: “We’ll take it offline.”

After the meeting, you get five different interpretations of what was agreed.

This is not a planning problem. It is a diagnosis problem.

Most steering committees are stuck in one primary mode:

• Fear: the room is protecting itself from risk and exposure.
• Power: the room is fighting over control, budget, narrative, or ownership.
• Ambiguity: the room cannot decide because the decision object is not clear.

Key definition: A steering committee is a governance forum where executives make bounded decisions (scope, funding, risk, priorities) that unblock execution.

If the forum cannot reliably close decisions, it stops being governance and becomes theatre.

---

The diagnostic model: signal, root cause, intervention

Do not start with “alignment”. Start with signals.

Use this simple loop:

1. Observe the language (what people keep saying)
2. Name the dominant mode (fear, power, ambiguity)
3. Apply the matching mechanism (not motivation, not pep talks)

Psychological safety research is useful here because it explains why people do not speak plainly about risk and uncertainty. When teams feel unsafe, they avoid interpersonal risk, and learning and candor degrade.

Role ambiguity research is also blunt: when roles and expectations are unclear, performance suffers and friction rises.

Your steering committee is where those dynamics become visible, because it is the highest-pressure room in the program.

---

Mode 1: Fear-driven steering (risk anxiety disguised as rigor)

What it looks like in the room

You hear:

• “What if this fails in production?”
• “We need more validation.”
• “Let’s get legal to review again.”
• “Can we see a deeper risk assessment?”
• “Not comfortable yet.”

The deck grows. The decision does not land.

This can be rational. Transformation carries real delivery and operational risk, and weak governance amplifies it.

But fear-driven steering has a pattern: it expands diligence without defining what “enough” looks like.

The root cause

Fear is usually protecting one of these:

• Reputation risk: nobody wants their name on the “bad call”.
• Compliance exposure: unclear data, unclear controls.
• Career risk: leaders sense the program is a blame magnet.

When fear is dominant, people ask for more process because process feels safer than ownership.

What fixes fear

You do not fix fear by demanding speed. You fix fear by making risk decidable.

Mechanism 1: Pre-agreed guardrails

Write the non-negotiables that turn “risk” into thresholds:

• Data classes that require security sign-off
• Financial exposure limits that require CFO sign-off
• Customer-impact criteria that trigger rollback plans
• SLA impact thresholds that require ops approval

Mechanism 2: A risk exception path

Most committees fail because “exception” has no lane. Create one:

• Default path: decide inside guardrails
• Exception path: name the exception, quantify exposure, decide in a dedicated slot
• Expiration: exceptions auto-expire unless renewed

Mechanism 3: Decision SLAs for risk questions

If risk is the reason for delay, timebox it:

• “Security review decision in 5 business days”
• “Legal position in 10 business days”
• “If not provided, decision escalates to the accountable owner”

Fear calms down when the system proves it can handle risk consistently.

---

Mode 2: Power-driven steering (control conflict disguised as alignment)

What it looks like in the room

You see:

• Decisions re-litigated every week
• “I’m not comfortable” used as a veto without criteria
• People “pre-aligning” in side meetings to win the room
• Forum shopping: taking the same question to multiple leaders until someone says yes

The meeting becomes a proxy battle over ownership.

This is not rare. Governance is always affected by power and influence dynamics.

The root cause

Power mode shows up when decision rights are unclear or contested, especially around:

• Platform ownership (IT vs product vs digital)
• Budget control
• Vendor selection and contracts
• Data and security authority
• Scope tradeoffs that move cost between functions

What fixes power

You do not fix power by asking people to “collaborate”. You fix it by designing decision accountability that cannot be bypassed.

Mechanism 1: One accountable decision owner per decision category

Not a committee owner. A named owner.

The owner can consult others. The owner still makes the call.

Mechanism 2: A single decision lane, with a timer

For any decision, define:

• Where it goes
• Who owns it
• What the input requirements are
• How long it can sit before escalation

Escalation timer is the power antidote. It kills infinite stalemates.

Mechanism 3: Commit-to-execute rule

If you argue in the room, you commit outside the room.

• Debate happens once, in the lane
• After the call, the committee executes the decision as a unit
• New information triggers a change request, not a re-fight

Power games thrive on re-opening decisions. Governance must make “re-open” expensive.

---

Mode 3: Ambiguity-driven steering (confusion disguised as debate)

What it looks like in the room

You hear:

• “What exactly are we approving?”
• “Define customer data.”
• “Is this scope or approach?”
• “Do we mean MVP or full rollout?”
• “What is the baseline metric?”

People are not blocking. They genuinely cannot evaluate the decision because it is not well-formed.

Role ambiguity has long been linked to poorer performance and coordination problems.

The root cause

Ambiguity is usually created by poor decision packaging:

• Options are not explicit
• Tradeoffs are missing
• Decision criteria are not stated
• Definitions are inconsistent
• Economics are absent (cost, risk, benefit, capacity)

What fixes ambiguity

Ambiguity is the easiest mode to fix, and the most neglected.

Mechanism 1: The one-page decision memo

Every steering decision should arrive with:

1. Decision statement (one sentence)
2. Options (2 to 3), each with consequences
3. Recommendation and rationale
4. Impact: cost, timeline, risk, customer, ops
5. What will be true after the decision (commitments)

Mechanism 2: Decision criteria upfront

Before the debate starts, state:

• Margin floor
• Customer promise constraints
• Data constraints
• Delivery capacity constraints

Then evaluate options against criteria, not opinions.

Mechanism 3: Vocabulary control

Create a glossary for loaded terms:

• “Customer data”
• “MVP”
• “Pilot”
• “Rollout”
• “Exception”

Ambiguity dies when words mean one thing.

---

How to run the diagnosis live (without drama)

The chair’s 10-minute checklist

During the meeting, ask these in order:

1. “Are we delaying because of risk, control, or clarity?”
2. “What would make this decision safe enough?” (fear)
3. “Who is the accountable owner for this category?” (power)
4. “What are the options and tradeoffs?” (ambiguity)
5. “What is the decision SLA and escalation path?” (all modes)

What to say in the room

Use scripted interventions:

• Fear: “Name the threshold that would let us decide.”
• Power: “Name the owner. If we cannot, we escalate today.”
• Ambiguity: “We are not deciding until options and impacts are written.”

Simple. A bit ruthless. Very effective.

---

When this advice does NOT apply

There are cases where the “mode” framing is not your main issue:

• You have a real strategy disagreement (different business models).
• There is a genuine regulatory hard stop.
• The program sponsor is absent or disengaged.
• The program is under-scoped and under-funded, so every decision is a trap.

In those cases, fix sponsorship and resourcing first.

---

What to do this week

Pick your next steering committee and instrument it.

• Assign one person to track: deferrals, re-opened decisions, and “offline” items.
• For every deferral, force a label: fear, power, or ambiguity.
• Apply one mechanism immediately (guardrail, owner, or decision memo).

If you do this for three meetings, you will see the pattern. Then you can redesign the forum instead of blaming the people.

Related article

When Pressure Hits, Your Operating Model Behaves Like a Dog Chasing a Squirrel

---

Facts that matter

• Psychological safety is linked to learning behavior in teams, and it helps explain why people avoid speaking up or surfacing mistakes in high-stakes settings. Source: Edmondson research (1999) and HBS Working Knowledge overview (June 14, 2023).
• Meta-analytic evidence shows role ambiguity is associated with lower job performance, supporting the idea that unclear decision roles increase friction and execution drag. Source: Tubre & Collins (2000) and related role ambiguity literature.
• Large firms flag program governance as a driver of delivery risk, including overruns and missed deadlines, reinforcing that governance design materially affects outcomes. Source: PwC Program governance and delivery risk (Aug 15, 2025).
• Transformation success remains elusive and depends on a holistic set of actions, which aligns with the premise that operating mechanisms (like governance) matter, not just strategy. Source: McKinsey transformations research (Dec 7, 2021).
• Power dynamics are a recognized factor in governance effectiveness, especially at board and executive levels, impacting influence and decision-making quality. Source: Russell Reynolds (Jan 16, 2025).

---

FAQ

How do I tell fear from healthy risk management?

Healthy risk management produces a clear threshold: “If X is true, we decide.” Fear produces expanding diligence with no definition of “enough.” If the committee cannot state what evidence would close the decision, you are in fear mode. Fix it by setting guardrails and a risk exception lane with a timeboxed decision SLA.

What if my steering committee has all three: fear, power, and ambiguity?

That is common. Pick the dominant one per decision. For example, vendor selection may be power-driven, while data classification is fear-driven, and roadmap prioritization is ambiguity-driven. Treat each decision with the matching mechanism. Do not try to “fix the culture” in one shot. Fix the decision system.

How do I stop decisions from being re-opened every week?

Make re-opening a formal change request. Require new information, quantified impact, and an owner. Also add a commit-to-execute rule: once decided, the committee executes as a unit. This removes the incentive for side deals and forum shopping, which are classic power-mode behaviors.

What is the minimum artifact I should require before a decision hits steering?

A one-page decision memo: decision statement, 2 to 3 options with tradeoffs, recommendation, impacts (cost, timeline, risk, customer, ops), and what becomes true after the decision. If the memo cannot be written, the decision is not ready. That is usually ambiguity, not resistance.

---

Glossary

• Decision owner: the single accountable person who makes the call for a defined decision category.
• Decision SLA: the maximum allowed time to close a decision before escalation.
• Guardrails: pre-agreed constraints that let teams decide fast without escalating.
• Exception lane: a defined path for decisions that fall outside guardrails, including who decides and by when.
• Role ambiguity: lack of clarity about responsibilities, authority, or expectations, which increases coordination cost.

---

Executive Takeaways

• Diagnose the room before you prescribe a fix: fear, power, or ambiguity.
• Fear needs guardrails and exception paths, not more meetings.
• Power needs explicit decision rights and escalation timers, not “alignment”.
• Ambiguity needs better decision packaging: options, tradeoffs, criteria.
• Instrument three meetings and redesign the forum based on evidence.