Every project is built on a foundation of beliefs.
Some of them are conscious. You know you are assuming that customers will pay a certain price. You know you are assuming that your supplier will deliver on time. You have thought about these things, even if you have not written them down.
But underneath those conscious beliefs is another layer. Assumptions so deeply held that they do not feel like assumptions at all. They feel like facts.
The market wants this.
People will find us once we launch.
Our costs will stay roughly where they are now.
The technology will work the way we need it to.
Our key person will stay.
These are not facts. They are beliefs that have not been tested. And the reason they are dangerous is precisely because they are invisible. You cannot examine what you cannot see.
The Exercise That Changes Everything
Before any significant project commitment, experienced project practitioners do something that takes less than an hour and saves more than it costs in almost every case.
They write down every belief that has to be true for the project to work the way they are imagining.
Not the obvious ones. Those are already on the risk register. The invisible ones. The beliefs so fundamental to the project's logic that questioning them feels almost disloyal to the idea.
Then they ask, for each one: how do I know this is true?
Some will have solid answers. Good. Those assumptions can be marked as tested and set aside.
Some will have weak answers. Those are your early warning system. They are the places where the project is most vulnerable, and they are telling you where to focus your validation energy before you commit.
Some will have no answer at all. Those are the ones that keep experienced project managers up at night. Not because they are necessarily wrong, but because there is no evidence either way.
What to Do With Them
An untested assumption is not a reason to abandon a project. It is a question that needs an answer before the project goes further.
The restaurant owner who assumes corporate clients in her area are underserved can test that assumption with three phone calls.
The engineer who assumes his manufacturing process will scale can test it with a small production run.
The consultant who assumes her methodology is unique in her market can test it with an afternoon of competitive research.
Cheap tests now. Expensive surprises later.
The assumptions you examine before you commit are the ones you get to manage.
The ones you never examine manage you.