You probably don’t inspect a chair before you sit down.
You don’t check that every screw is tight or verify the strength of the joints holding the legs together. You don’t calculate how much weight the materials can support or wonder whether someone loosened a bolt while you were out of the room. You simply sit because every chair you’ve used throughout the day has behaved exactly as you expected.
In that moment, you’re relying on an assumption.
The interesting part is that you almost certainly weren’t aware of it.
Assumptions rarely announce themselves. They operate quietly in the background, allowing us to move through life without consciously evaluating every decision. We assume the light switch will work when we flip it. We assume the faucet will produce water when we turn the handle. We assume the grocery store will still be standing tomorrow morning and that the bridge on the way there will continue supporting traffic for another day.
Without assumptions, ordinary life would become impossible.
Imagine treating every action as though it had never happened before. Every chair would require inspection. Every elevator ride would begin with a careful review of the maintenance records. Every meal would demand an investigation into the origin of every ingredient. The amount of attention required simply to make it through breakfast would leave little capacity for anything else.
Assumptions are remarkably efficient.
They compress experience into expectation.
After enough successful repetitions, we stop consciously evaluating familiar situations because our previous experiences suggest the outcome is highly predictable. The mind quietly fills in information that is probably true so that attention can be directed elsewhere.
Most of the time, this works extraordinarily well.
Occasionally, however, assumptions and reality diverge.
A familiar road is unexpectedly closed for construction. The automatic doors at the grocery store fail to open. The office coffee pot is empty because everyone assumed someone else would make another pot. A trusted coworker retires, and no one realizes they had been quietly performing three undocumented tasks that kept the department functioning.
The assumption wasn’t foolish.
It simply remained invisible until reality challenged it.
This is one reason failures often feel surprising in retrospect.
We tell ourselves that we “should have known” or that the warning signs were obvious, forgetting that the warning signs contradicted years of accumulated experience. We expected today’s chair to behave like yesterday’s chair because nearly every chair we have ever encountered has done exactly that.
The assumption was reasonable.
It just wasn’t correct this time.
Complex systems depend on assumptions in ways that are not immediately obvious.
Organizations assume that employees will continue coming to work tomorrow. Families assume that certain responsibilities will quietly be handled by the same person who handled them yesterday. Volunteer departments assume that enough members will respond to the next call. Software assumes that users will follow instructions. Drivers assume that other drivers will stop at red lights.
Every system contains hundreds of expectations that are never written down because they have never needed to be.
Until they do.
Perhaps the most interesting characteristic of assumptions is that they become visible only after they fail.
No one spends time thinking about electricity until the lights go out. Few people consider the complexity of a supply chain until the grocery shelves begin looking empty. We rarely appreciate the person who always remembers birthdays, schedules appointments, or refills the copier paper until they are absent and no one else realizes those responsibilities existed.
The assumption reveals itself through its absence.
Experience changes the kinds of assumptions we make.
A young driver may assume every green light is safe to enter. An experienced driver has seen enough people run red lights to hesitate for a fraction of a second before accelerating. A new employee may assume the written procedure contains everything necessary to complete the task. An experienced employee quietly knows there are unwritten details that no manual has ever captured.
The assumption hasn’t disappeared.
It has merely changed.
This is where assumptions become especially important in understanding fault lines.
Many disagreements are not actually disagreements about facts. They are disagreements between different sets of assumptions. Two people observe the same situation but interpret it differently because each begins with expectations shaped by different experiences. One assumes the delay is temporary. The other assumes it signals a deeper problem. One trusts that someone else has already checked the numbers. The other has learned through painful experience to verify them personally.
Neither person may realize they are making an assumption at all.
They simply believe they are seeing reality.
The goal, then, is not to eliminate assumptions.
That would be impossible.
The goal is to recognize that they exist.
To pause occasionally and ask what we are expecting to be true.
To wonder which parts of the system we have stopped examining simply because they have behaved reliably for so long.
To remember that today’s certainty may be built upon yesterday’s experience rather than today’s evidence.
Most assumptions deserve to be trusted.
Some deserve to be questioned.
The difficult part is knowing which is which.
And that distinction often becomes visible only after the fault line begins to move.