How Project Problems Evolve: From Assumptions to Risks to Issues

Most project problems do not appear suddenly. They usually follow a predictable path

Assumption → Risk → Issue → Escalation

Understanding this concept (Assumptions vs Risks vs Issues in Project Management) helps project teams identify problems early, take preventive action, and reduce delivery impact. 

1. Assumption

An assumption is something the project believes to be true but has not yet fully confirmed.

Example: Security clearance approvals will be completed within two weeks.

At this stage, there is no known problem. The project is relying on the approval timeline as a planning condition.

The assumption should remain valid only while there is reasonable evidence that the timeline can still be achieved.

2. Risk

A risk exists when there is credible uncertainty that could affect the project in the future.

Example: Security clearance approvals may take longer than planned.

The assumption may become a risk when:

• Required documents have not yet been submitted
• The approving authority requests additional information
• Similar approvals are taking longer than expected
• One week has passed without any progress update
• The remaining approval window is becoming too short

The delay has not yet occurred, but there is now enough evidence to question the original assumption.

3. Issue

An issue is a problem that has already occurred and is affecting project delivery.

Example: Security clearance approvals are delayed by three weeks, and vendor onboarding cannot start.

The uncertainty is gone. The impact is real.

The project now requires an issue-resolution plan, a revised delivery approach, or both.

4. Escalation

Escalation is not another RAID category.

It is a management action taken when the project team cannot resolve an issue using its existing authority.

Example: Sponsor intervention is required to accelerate the security approvals.

Escalation may be required when:

• A decision is overdue
• The issue crosses departmental boundaries
• The team lacks authority to remove the blocker
• A vendor commitment requires executive intervention
• The issue is likely to affect a major milestone or contractual obligation

Escalation should have a clear purpose: obtain a decision, remove a blocker, secure support, or accept a defined impact.

Read More: Mitigation Plans vs Contingency Plans: What Project Managers Often Confuse

Practical Example

Stage	Example
Assumption	The vendor will provide all key resources by 1 July.
Trigger	Visa approvals remain pending, travel is not booked, and the vendor cannot confirm joining dates.
Risk	Vendor mobilisation may be delayed.
Risk response	Request daily updates, identify replacement resources, and re-sequence early activities.
Issue	1 July arrives, and the required resources have not joined.
Issue response	Revise the mobilisation plan and assess the impact on project milestones.
Escalation	The Project Sponsor engages the vendor’s executive management to secure committed resources.

The Evolution in One View

Stage	Key Question
Assumption	What are we relying on?
Trigger	What evidence is challenging that belief?
Risk	What could go wrong?
Issue	What has already gone wrong?
Escalation	Who has the authority to help resolve it?

When Does One Stage Become the Next?

An assumption becomes a risk when the project no longer has reasonable confidence that the assumption will remain true.

This transition is not based on a fixed number of days. It is triggered by evidence, warning signs, or changing circumstances.

Common triggers include:

• A supporting activity or intermediate milestone is missed
• A vendor or stakeholder raises a concern
• A required approval remains pending longer than expected
• A dependency starts slipping
• Required resources are not yet confirmed
• New information challenges the original assumption
• The remaining time is no longer sufficient to recover safely

A risk becomes an issue when the uncertain event actually occurs and begins affecting the project.

An issue is escalated when the project team cannot resolve it using its existing authority, resources, or agreed governance route.

Each stage represents a different condition:

• Assumption is something the project expects to be true.
• Risk is uncertainty that could affect delivery.
• Issue is a problem that has already occurred.
• Escalation is a request for authority, intervention, or support.

Final Takeaway

Effective project managers do not wait for assumptions to fail.

They continuously validate assumptions and look for evidence that confidence is weakening.

An assumption should become a risk as soon as credible warning signs appear—not only when the deadline is close.

The earlier the transition is recognised, the more options the project has to prevent or reduce the impact.