The Quiet Risk: Where Project Assumptions Go Wrong
Every project plan rests on a stack of things you have decided to treat as true without proof: that the permit will come through, that the vendor can deliver by July, that the client will be available to sign off. These are assumptions, and they are not optional — you cannot plan without them. The trouble is that most teams make assumptions silently, never write them down, and only discover which ones were wrong when the schedule has already slipped. The past year sharpened this: assumptions about supplier lead times and staff availability that held for years suddenly failed. Here is where teams go wrong, and what to do instead.
The most common mistakes
Treating assumptions as facts. The fastest way to be blindsided is to fold an unverified belief into the plan as if it were settled. 'Materials arrive in two weeks' becomes a hard date in the schedule, and no one remembers it was a guess.
Never writing them down. An assumption that lives only in a planner's head cannot be reviewed, challenged, or tracked. When that person is out — increasingly likely with hybrid teams — the assumption disappears with them.
Confusing assumptions with risks and constraints. A constraint is a fixed limit you must work within; a risk is an uncertain event; an assumption is something you are choosing to treat as true for now. Blurring them means none gets managed properly.
Setting them and forgetting them. Assumptions decay. One that was reasonable at kickoff may be false two months in, but if no one revisits it, the plan keeps running on stale information.
Hiding the shaky ones from sponsors. Teams often bury the assumptions they are least sure about, precisely the ones a sponsor most needs to see in order to fund a contingency.
How to manage them properly
The fix is not complicated, but it does require discipline. Make assumptions explicit and keep them in front of the team.
Keep an assumptions log alongside your risk register — each entry stating the assumption, who owns it, how confident you are, and what happens if it proves false.
Rate each one for impact and likelihood, the same way you triage risks, and validate the high-impact ones early instead of hoping.
Convert assumptions into actions: if you are assuming a permit by a date, someone should be confirming that date, not waiting.
Review the log at every status checkpoint and close out assumptions as they are confirmed or disproved.
An assumption you have written down and assigned an owner is no longer a hidden hazard — it is just another item you are managing. The discipline costs an hour a week and routinely saves projects from the surprises that no estimate could have caught.
For help building assumption and risk discipline into the way your projects are planned and governed, XNM's program & project delivery advisory brings a practical, audit-ready approach.