More information can reduce uncertainty. It does not automatically resolve disagreement about what the information means or what the organisation should do.
Senior leaders often respond to ambiguity by asking for more detail. Refine the scope. Produce another option paper. Add analysis. Clarify the schedule. The instinct is understandable because some ambiguity is caused by weak definition.
But not all ambiguity is a planning defect.
A program can have excellent analysis and still face stakeholders who value different outcomes. A portfolio can have reliable data but no uncontested answer about which strategic objective deserves priority. A transformation can have a clear destination while leaders disagree about the acceptable pace, distribution of cost or operating-model consequences.
In those situations, more information may improve the discussion without resolving the choice. Leadership must do something planning cannot: create sufficient shared meaning and decision legitimacy to move.
The Strategic Context
The supplied PMI material identifies ambiguity and multiple stakeholders as recurring characteristics of complex projects. The 2013 Navigating Complexity report also contains practitioner comments linking ambiguity to unclear scope and insufficient front-end expectation setting. That is one important source of ambiguity, but the wider source set shows a broader picture.
San Cristóbal's review of complexity models includes Stacey's Agreement and Certainty Matrix. The matrix separates certainty about cause and effect from agreement among participants. That distinction matters because an organisation can be close to certainty but far from agreement, or close to agreement but far from certainty.
The supplied Study Notes also discuss Thiry's HUHA framing, distinguishing uncertainty from ambiguity. In that teaching material, uncertainty is linked to missing information and difficulty establishing causal relationships, while ambiguity relates to multiple possible outcomes and stakeholder interpretations without a clear path.
Levin and Ward add a program-management insight: traditional attempts to reduce uncertainty by collecting more and more information can themselves add complexity. They describe sensemaking as a way to work through conflicting perceptions and diverse expectations.
Taken together, the implication is clear. Leaders should stop treating all lack of clarity as the same problem.
What Leaders Commonly Misread
The first misread is to assume that every unclear situation can be closed through analysis. If the disagreement is about values, priorities or distribution of consequences, no spreadsheet can make the decision apolitical.
The second is to assume that stakeholder alignment means unanimity. Complex programs rarely require every stakeholder to prefer the same option. They require enough shared understanding of purpose, trade-offs and decision authority for coordinated action.
The third is to mistake uncertainty for ambiguity. If the problem is uncertainty, experimentation, evidence and scenario analysis may help. If the problem is ambiguity, negotiation, framing and sensemaking may be more important.
The fourth is to eliminate ambiguity too early. Prematurely forcing a single interpretation can suppress useful alternatives before the organisation understands the problem. This is especially dangerous in innovation, strategy and operating-model design.
The fifth is to leave ambiguity unresolved for too long. The opposite failure is endless consultation without decision. Ambiguity cannot always be removed, but governance must eventually determine who decides and what evidence is sufficient.
Reframing the Issue
Ambiguity is a decision condition.
The practical question is not "How do we remove ambiguity?" but "What kind of ambiguity are we facing, how much must be resolved now, and what can remain open while we learn?"
This leads to an important distinction between avoidable ambiguity and irreducible ambiguity.
Avoidable ambiguity comes from weak purpose, inconsistent language, unclear responsibilities, incomplete scope or hidden assumptions. Leaders should reduce it aggressively.
Irreducible ambiguity exists because legitimate interests conflict, future conditions are unknown, or the organisation is choosing among several plausible futures. Leaders cannot eliminate this through documentation. They must govern it.
Related article: Portfolio Value Is Negotiated Before It Is Measured
Four Different Decision Conditions
High agreement, high certainty
When stakeholders broadly agree and cause and effect are understood, conventional planning and performance management are appropriate. The leadership task is mainly disciplined execution.
Low agreement, high certainty
The organisation may understand the technical choices but disagree about the outcome. Examples include where to locate a facility, which business receives scarce investment or how a restructuring distributes power. Negotiation and decision rights become central.
High agreement, low certainty
Leaders may agree on the objective but not know which method will work. This is common in innovation and emerging technology. Experimentation, pilots and staged commitments are more useful than pretending the method is already known.
Low agreement, low certainty
This is the most difficult condition. Stakeholders disagree and evidence cannot reliably predict the path. Leadership needs sensemaking, option preservation and carefully bounded experimentation. It may also need to reduce the problem into smaller decisions rather than force a comprehensive answer.
These conditions are not permanent labels. A program can move between them as evidence, politics and stakeholder expectations change.
Sensemaking as a Leadership Practice
Sensemaking is not consensus-building for its own sake. It is the disciplined process of helping stakeholders construct a sufficiently shared interpretation of what is happening, why it matters and what decision is required.
In practice, this can involve:
- making assumptions explicit;
- separating facts from interpretations;
- identifying where stakeholders genuinely disagree;
- testing whether different language is masking similar concerns;
- clarifying who bears cost, risk and benefit under each option;
- distinguishing decisions that are reversible from those that are difficult to reverse;
- defining what new evidence would materially change the choice.
This is more demanding than communication because the leader is not merely transmitting information. The leader is shaping the decision environment.
Related article: Stakeholder Engagement Is a Decision System, Not a Communication Plan
Decision Framework
Use an Ambiguity Diagnosis before commissioning more analysis.
Question 1: What exactly is unclear?
Is the problem the goal, the method, the evidence, stakeholder priorities, decision rights or the meaning of success?
Question 2: Would more information materially narrow the choice?
If yes, define the evidence and obtain it. If not, stop pretending the problem is analytical.
Question 3: Where is disagreement legitimate?
Map the interests behind the positions. Finance, operations, customers, regulators and employees can rationally prefer different outcomes.
Question 4: What must be decided now?
Do not resolve future choices earlier than necessary. Preserve options where the decision is reversible or where learning has high value.
Question 5: Who has the authority to decide?
Ambiguity becomes organisational paralysis when decision rights are unclear. Governance must define who decides after consultation and what escalation threshold applies.
Question 6: What conditions would trigger reconsideration?
A decision under ambiguity should not be treated as eternal. Define signals that would justify reopening it.
From Strategy to Execution
Immediate action is to separate uncertainty from ambiguity in major decision papers. Add a short section identifying what is unknown, what is contested and what evidence can actually change the decision.
Medium-term capability involves developing leaders who can facilitate difficult trade-offs without hiding them in technical language. Program managers need negotiation, active listening and relationship capability in addition to planning discipline. Portfolio forums need methods for comparing competing interpretations of value, not only ranking scores.
Long-term positioning means building an organisation comfortable with conditional commitments. Strategy should be clear about direction while allowing some implementation choices to remain open. Programs should be designed to convert uncertainty into knowledge over time. Governance should be able to adapt without creating the impression that every change is failure.
Signals to Monitor
Ambiguity is becoming dangerous when:
- teams use the same words but mean different outcomes;
- decisions are repeatedly deferred for "more information" that does not change stakeholder positions;
- scope documents grow while strategic purpose becomes less clear;
- stakeholders agree in meetings but pursue different priorities afterwards;
- success measures are negotiated only after delivery is underway;
- senior leaders delegate a political choice to a technical team;
- decision papers contain many options but no explicit trade-offs;
- governance cannot identify who has authority to close the issue.
Questions for the Leadership Team
- Which of our current disputes are really about missing information, and which are about competing interests or values?
- What ambiguity could we eliminate immediately through clearer purpose or decision rights?
- Which choices should remain open because further learning is valuable?
- Where are we commissioning analysis because we are reluctant to make a difficult decision?
- Who benefits and who bears cost under each major alternative?
- What evidence would genuinely change our current position?
- When should this decision be revisited?
Closing Perspective
Some ambiguity is waste. Some ambiguity is reality.
Good leadership removes avoidable ambiguity quickly and governs irreducible ambiguity deliberately. It does not confuse a lack of information with a lack of agreement, and it does not hide difficult choices behind increasingly elaborate analysis.
The decisive capability is knowing when to plan, when to experiment, when to negotiate and when to decide.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.
