Learning to hold uncertainty again.
In the previous episode, something uncomfortable happened. The engineer discovered that the authority they had been relying on was never fully theirs. The process had approved. The checklist had been completed. The review had been signed. The decision had passed through the organization. But underneath all of it was a question that could not be delegated:
What did you actually believe?
Responsibility returns to where it had quietly been absent. But when borrowed authority disappears, it leaves behind something uncomfortable: a decision that still needs to be made.
The Empty Space After the Illusion
The natural reaction is to search for a replacement. Frameworks do more than organize work—they provide psychological protection. When something goes wrong, the engineer can say, we followed the process. That sentence may be factually correct. But it answers a different question than the one being asked. The process can tell us whether an activity happened, whether evidence exists, whether a requirement was addressed. It cannot tell us whether we understood the real risk, whether our assumptions remain valid, or whether the evidence is enough.
The framework was never the problem. The problem was asking it to carry a responsibility it was never designed to carry.
The paperwork was complete. The hat was still on the ledge. (Gemini generated image)
The First False Escape: Reject the Framework
After discovering the limits of process, some engineers move to the opposite extreme. The process people don't understand reality, they say. The checklist gets in the way. Real engineering happens outside the documents. This feels like independence. It is only a different dependency. Before, the framework said it was correct, therefore it was correct. Now, experience says it is correct, therefore it is correct. The authority changed. The illusion remained.
The discipline is not choosing between process and experience. It is understanding what each one can and cannot do.
The Second False Escape: Experience as Authority
Experience matters. A senior engineer has seen patterns that others have not. They recognize signals earlier. They know where systems usually fail. But experience can become another shield. I have seen this before sounds like wisdom—sometimes it is, and sometimes it is simply confidence borrowed from the past. The important question is what, exactly, you have seen before. The same technology? The same failure mechanism? The same constraints? The same incentives? The same organizational environment? Experience is valuable only when it remains connected to reality. Otherwise, it becomes another shortcut around judgment.
The Tuesday Meeting
A design review is taking place. Nothing unusual. The documents are prepared, the required analyses are complete, the checklist is green. Everyone is comfortable. Someone asks: Are we confident this change is safe? The engineer opens the review package. The evidence is there. The approvals are there. The process has been followed.
Then someone asks a different question:
What are we actually worried about?
Silence.
Not because nobody worked. Because nobody had asked that question. The process had answered whether the required activities were performed. Nobody had answered whether the remaining uncertainty was understood. The process did not fail. It did exactly what it was built to do. The mistake was expecting it to replace judgment.
The Return of Owned Judgment
Judgment is not having the right answer. Engineering rarely works that way. Judgment is the ability to make a defensible decision while knowing the answer is incomplete. The mature engineer does not say, I know this will succeed. They say: Given what we know, what we do not know, and what failure would cost, this is the decision I am willing to own.
That is a very different form of confidence.
Not certainty.
Accountability.
The Test
Here is the uncomfortable test:
If your first move under challenge is to produce a document rather than a reason, the judgment was never yours.
Documents matter. Standards matter. Approvals matter. But they are evidence of thinking. They are not substitutes for thinking.
Judgment is not the absence of a shield. It is knowing when you were never actually wearing one. (Gemini generated image)
The Organizational Contradiction
There is one final problem. Many organizations claim they want engineers who take ownership. But ownership creates discomfort, because an engineer with judgment may say, the process is complete, but I am still concerned. They may ask questions that slow decisions. They may challenge assumptions everyone has already accepted. They may introduce uncertainty where the organization wants confidence.
So organizations often create a contradiction. They ask for ownership but reward agreement. They ask engineers to exercise judgment but punish judgment when it changes the conversation. The result is predictable: people learn to perform ownership instead of practicing it. They produce the right documents, attend the right meetings, and say the right words. But the actual decision remains somewhere else.
Closing
The engineer without a shield is not the engineer who needs no framework. It is the engineer who understands where the framework ends. They still use standards. They still seek evidence. They still value experience. But when no document can decide, no approval can protect, and no precedent can answer, they know where responsibility lives.
Not above them.
Not below them.
With them.
And that leaves the final question:
What kind of organization allows judgment to survive?
Next:
Over eleven episodes, we have dismantled the mechanisms that create the illusion of control.
The final episode asks a different question:
If we stop fooling ourselves, what must we build instead?
This is the eleventh essay in The Discipline of Not Fooling Ourselves — Engineering Reflections on Process, Proof, and Maturity. Each article stands alone. Reading in sequence reveals a deeper arc. The situations described are composites of recurring patterns and are not accounts of any specific organization.
The situations described are composites of recurring patterns and are not accounts of any specific organization.
🔖 I write about corporate culture, engineering discipline, process maturity, Automotive SPICE, quality, and testing. My focus is simple: how organizations know that what they claim is true, and how they avoid mistaking compliance for competence. If you care about building engineering systems that are resilient, evidence-based, and intellectually honest, follow along.
© 2026 Abdul Osman. All rights reserved. You are welcome to share the link to this article on social media or other platforms. However, reproducing the full text or republishing it elsewhere without permission is prohibited.
Top comments (0)