An assumption that must remain true for the strategy to work is already a dependency, even if no failure has occurred.
Every transformation begins with statements that are treated as background conditions.
Specialist employees will remain available. Funding will be released when required. The new site will be suitable. Necessary approvals will be obtained. External infrastructure will be delivered. Customers will respond as expected. Suppliers will have capacity. Technology will perform at the required scale.
These assumptions make planning possible.
They can also conceal the most important risks in the investment.
A conventional risk register tends to focus on uncertain events: something may go wrong in the future. A critical assumption is different. The plan has already chosen to behave as though something is true.
That means an assumption can shape capital commitment, schedule, design and stakeholder promises long before it is formally described as a risk.
The Strategic Context
A business case is built on a model of the future.
It contains explicit forecasts and implicit conditions. Some conditions concern the external environment. Others concern organisational capability. Others concern decisions that have not yet been secured.
Consider a hypothetical transformation that depends on:
- specialist staff remaining available through relocation;
- land being suitable for the intended use;
- no material contamination being discovered;
- government funding being released;
- a local authority funding required access infrastructure;
- sufficient internal resources being available while normal operations continue.
None of these statements is merely administrative.
If one proves false, the transformation may require more capital, more time, a different design, a new operating model or a reconsidered business case.
The more strategy depends on an assumption, the less acceptable it is to leave that assumption unmanaged.
Related article: Business Cases Are Investment Hypotheses, Not Permission Slips
What Leaders Commonly Misread
The first error is treating assumptions as documentation.
Teams often create an assumptions log because the methodology requires one, then focus active management on risks and issues. The assumption remains passive until evidence contradicts it.
By then the organisation may already have spent significant capital.
The second error is assuming that "reasonable" means "safe".
An assumption can be reasonable and still be strategically dangerous. The question is not whether it seems likely. The question is what happens if it is wrong.
A 90% probable assumption that protects the viability of a billion-dollar investment deserves more governance attention than a 50% probable assumption with minor consequences.
The third error is failing to distinguish controllable assumptions from external dependencies.
Some assumptions can be actively tested or secured. Others depend on governments, partners, markets, regulators or environmental conditions. The governance approach should differ.
The fourth is converting assumptions into risks without changing behaviour.
Simply copying "staff may not be available" into the risk register adds little unless someone owns the evidence, trigger points, mitigation and decision response.
Reframing the Issue
Leaders should treat critical assumptions as strategic dependencies with evidence requirements.
The logic is straightforward:
Assumption → Dependency → Evidence → Trigger → Decision
An assumption states what the plan currently believes.
A dependency identifies what the strategy relies upon.
Evidence tests whether reliance remains justified.
A trigger defines when leadership should act.
A decision specifies what changes if confidence falls.
This reframing is powerful because it moves the organisation from passive optimism to active validation.
Related article: Interdependencies Are Portfolio Risk: Why Project Dashboards Miss the System
Not All Assumptions Deserve Equal Governance
A useful classification separates assumptions by what they affect.
Viability assumptions
These determine whether the investment still makes strategic or economic sense.
Examples include market demand, major funding availability, operating-cost improvement or the feasibility of a critical site.
If these assumptions fail, leadership may need to revisit the business case.
Delivery assumptions
These affect whether the planned scope, cost or schedule remains achievable.
Examples include supplier capacity, specialist resource availability or expected construction access.
Failure may require re-planning without invalidating the strategy.
Transition assumptions
These determine whether the organisation can move from current state to future state safely.
Examples include workforce retention, dual-running capacity, temporary facilities or continued access to critical systems.
These assumptions are often underestimated because the future-state design can remain attractive even while the journey becomes unviable.
External dependency assumptions
These concern parties outside direct managerial control: regulators, governments, utilities, councils, partners or infrastructure providers.
The organisation cannot "manage" these dependencies in the same way as internal work. It can secure commitments, build contingencies, monitor evidence and preserve options.
Behavioural assumptions
These concern how customers, employees, partners or other stakeholders are expected to respond.
They are particularly dangerous when treated as facts because behaviour often becomes visible only after implementation.
Decision Framework
Create an Assumption Dependency Register only for assumptions important enough to change decisions.
For each, record:
| Field | Governance question |
|---|---|
| Assumption | What are we currently treating as true? |
| Strategic dependency | What part of the investment relies on it? |
| Consequence if false | What changes if it fails? |
| Confidence | How strong is the current evidence? |
| Validation method | How can we test or secure it? |
| Owner | Who is accountable for maintaining confidence? |
| Trigger | What evidence requires escalation? |
| Response | What decision or contingency follows? |
| Latest responsible decision | By when must uncertainty be reduced? |
The final field is crucial.
Some assumptions can remain uncertain for months without consequence. Others must be resolved before an irreversible commitment such as land acquisition, major procurement, public launch or system cutover.
This creates the concept of a latest responsible decision point: the last moment at which the organisation can preserve options without paying excessive cost.
Related article: Ambiguity Is a Leadership Condition, Not Merely a Planning Defect
From Strategy to Execution
Immediate action
Review the business case, charter, scope and major plans for assumption language.
Look for phrases such as:
- "it is expected that";
- "it is assumed that";
- "will be available";
- "should be sufficient";
- "is anticipated";
- "subject to";
- "dependent on";
- "we expect customers to";
- "the organisation has capacity to".
Do not automatically convert every phrase into governance overhead. Screen them by consequence.
Ask: If this is false, would we change the investment, design, sequence, funding or transition plan?
If yes, it is a strategic dependency.
Medium-term capability building
Integrate critical assumptions into normal executive reporting.
A good dashboard should not only show risks that have increased. It should show confidence that critical assumptions remain valid.
This can be represented as evidence strength rather than artificial precision:
- confirmed;
- strongly supported;
- partially supported;
- weakly supported;
- contradicted.
Assumptions should also be linked to decision gates. For example, a site suitability assumption should be resolved before irreversible construction commitment. A workforce assumption should be tested before a transition plan depends on scarce specialists.
Long-term strategic positioning
Portfolio leaders should analyse recurring failed assumptions across initiatives.
Patterns reveal structural weaknesses.
If projects repeatedly assume that business units have spare capacity, the organisation has a capacity-planning problem. If business cases repeatedly assume customer adoption without evidence, the organisation has an investment-governance problem. If external infrastructure is repeatedly treated as guaranteed without formal commitment, the organisation has a dependency-management problem.
These patterns should influence which initiatives are approved and how much contingency is required.
Signals to Monitor
Warning signals include:
- assumptions remaining unchanged across multiple governance cycles;
- no named owner for a condition essential to the business case;
- major procurement proceeding before critical assumptions are validated;
- external parties being described as committed without formal evidence;
- confidence in customer behaviour based mainly on internal opinion;
- scarce specialist capacity being assumed by several initiatives simultaneously;
- the same condition appearing separately in risk, issue and assumption logs without one accountable decision path;
- teams arguing that an assumption is "not yet a risk" despite rising evidence against it.
These are signs that uncertainty is being documented rather than governed.
Questions for the Leadership Team
- Which assumptions, if false, would cause us to redesign, delay or stop this investment?
- What evidence currently supports each of those assumptions?
- Which dependencies sit outside our direct control?
- What commitments have we mistaken for informal expectations?
- What is the latest responsible point by which each critical uncertainty must be reduced?
- Which initiatives are competing for the same assumed organisational capacity?
- What recurring assumption failures across the portfolio indicate a systemic weakness?
Closing Perspective
Risk management often begins too late.
By the time a critical assumption becomes an obvious risk, the organisation may already have designed around it, contracted against it, communicated it to stakeholders and committed capital on the belief that it would hold.
The stronger discipline is to identify what the strategy needs to be true before failure occurs.
Critical assumptions are therefore not passive notes attached to the plan.
They are strategic dependencies waiting for evidence.
Leaders who govern them early preserve options. Leaders who ignore them often discover that what looked like an unexpected risk was embedded in the investment from the beginning.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.