Shame of Not Knowing
He dismisses what he cannot operate and bluffs through what he does not understand. Why the gap feels like failure and how to make asking safe.
Shame of Not Knowing is the fear that a knowledge gap exposes incompetence. He was raised where a man was expected to know things. Competence was currency. Admitting a gap cost standing.
Now the world reprices his knowledge every few months. Each new platform, app, or process is a test he was not told about. When he cannot complete it, nobody else sees. But he does.
How to Spot It
These patterns carry it:
- The Late Adapter: He waits before trying anything new. Waiting is safer than failing in public.
- Experience Shield: He leads with what he knows. That keeps the conversation away from what he does not know.
- Fixer Mode: He solves the problems he understands. The ones he cannot follow get dismissed.
You see it most in:
Signs to watch for:
- He bluffs rather than asking.
- He dismisses tools and platforms he cannot operate. (“Who needs that.”)
- He lets tasks pile up rather than admit he cannot complete them.
- He uses “I am not a tech person” before you have said anything.
- He goes quiet when a conversation moves past his knowledge.
The dismissal is the tell. Contempt for a thing is cheaper than admitting it beat him.
Where It Comes From
He learned early that men were supposed to know things. A father who knew how to fix the car. A boss who never asked twice. Asking was weakness. That lesson ran deep.
He spent decades building real expertise. It earned real respect. Now parts of it date fast. The login screen defeats him. The form times out. The interface changes without notice.
Each small defeat is real. He does not talk about them. They add up in silence.
See Fear of Vulnerability for the broader pattern this belongs to.
What You Can Do
Never expose a bluff in company. He will not recover from that in front of an audience. It confirms exactly what he feared.
Volunteer your own not-knowing first. Do it casually. “I had no idea how this worked until last week.” That opens a door without ceremony.
Make questions cost nothing. Work side by side, no audience. Ask him to show you something he does know well, then let the question come up naturally from there.
Say: “I am still figuring this out myself. What did you do when you ran into it?”
When he asks a question, acknowledge it briefly and move on. Do not make it a moment.
Say: “Good question. Here is what I know.”
See Reverse Mentoring for how to build a relationship where questions flow both ways without anyone keeping score.
At Work
He is in the sprint review, nodding. He lost the thread three slides ago. He will not ask. He will leave with assumptions he cannot verify and make decisions based on them.
This is how wrong assumptions ship. Nobody lied. Nobody withheld anything. The most senior person in the room did not ask a question.
The fix is not to call him out. The fix is to normalize not-knowing from the top. The boss asks the first dumb question. Every time. That licenses everyone else to do the same.
Say: “I want to be honest: I did not fully follow that last part. Can you walk us through it again?”
When the senior person says that, the room relaxes. Questions surface. Assumptions get corrected before they become decisions.
See Reverse Mentoring for the structural version of this move.
More for the workplace: Men Over 50 at Work