Introduction: The Weight of Three Words

In a meeting, someone turns to you and asks, "Why did performance drop here?" The truth is, you do not know the exact reason. In that instant, two paths fork in your mind. One is to state a plausible guess as if it were fact. The other is to say, "I am not certain right now. Let me check and get back to you."

Most people take the first path. They fear that admitting ignorance will make them look incompetent or unprepared. But with experience, you come to realize something. What erodes trust is not ignorance, but pretending to know while not knowing.

This is not an abstract sermon. It is a concrete account of how, when, and in what form to say "I do not know" so that you keep — and even build — trust rather than lose it.

Why Admitting Ignorance Builds Trust

This sounds counterintuitive. If saying "I do not know" should lower trust, why does it actually raise it?

The key lies in **the nature of trust**. To trust someone means "I can believe this person's words without verifying them." But once someone is caught pretending to know something they did not, a question mark attaches itself to everything they say afterward. "Are they actually sure this time? Or is it another guess?"

Conversely, the words of a person who honestly draws the line — "I do not know this" — carry a different weight. When that person says "I am certain about this," we can take it at face value. The act of admitting ignorance paradoxically **vouches for the credibility of their knowledge**.

> Trust comes not from the average of your accuracy, but from the consistency of your honesty.

Research supports this. Social psychology has observed a tendency for people who admit their limits to be rated as more competent — with one condition. The honesty must rest on a foundation of basic competence. Repeating "I do not know" while knowing nothing at all is a different matter entirely.

The Real Cost of Bluffing

The cost of pretending does not surface in the moment. It is always billed later, in a larger form.

Cost 1: A Chain of Wrong Decisions

Suppose you said, without conviction, "That is probably a cache issue." The team spends days investigating the cache based on your word. If the real cause lay elsewhere, your single guess has wiped out the team's time. Had you said "I do not know," the team would have started a proper investigation from the beginning.

Cost 2: Permanent Damage to Trust

The moment a bluff is exposed, recovery takes ten times as long. People forgive mistakes but remember deception for a long time. The memory of "that person once pretended to know without knowing" is surprisingly persistent.

Cost 3: The Loss of a Learning Opportunity

This is the quietest but most fatal cost. The moment you say "I do not know" is the point where learning begins. The person who pretends to know never passes that point. Paper over your ignorance, and growth in that area stops with it.

The table below compares the short- and long-term effects of the two attitudes.

| Situation | Pretending to know | Saying I do not know |

| --- | --- | --- |

| Impression in the moment | Looks competent | Looks slightly uneasy |

| Result a few days later | Wrong direction, wasted time | Right direction, fast fix |

| Trust over time | Slowly erodes | Slowly accumulates |

| Personal growth | Stagnates | Expands |

The Craft of "Let Me Check and Get Back to You"

"I do not know" is, by itself, an incomplete sentence. The person who builds trust connects ignorance to **a commitment to act**.

Compare a poor example with a good one.

Question: "Why did this API's response time get slower?"

[Bad 1 - bluff]

"Oh, that is a DB index issue." (without conviction)

[Bad 2 - dodging responsibility]

"Hmm, I really do not know." (ends here)

[Good - honesty + commitment]

"I cannot pin down the exact cause right now.

The two suspects I have are the DB index and an external call.

I will check the logs by this afternoon and share the result."

A good answer has three parts.

1. **Honest admission of ignorance** — "I cannot pin it down"

2. **Sharing as much as you currently know** — "there are two suspects"

3. **A concrete follow-up commitment** — "by when, I will do what"

The crux of this structure is that it admits ignorance while **simultaneously demonstrating that you are not incompetent**. Not knowing the answer and lacking the ability to find it are entirely different things.

And if you made a commitment, you must keep it. Saying "I will get back to you" and then forgetting becomes a second lie, worse than the bluff.

A Language Habit That Separates Guesses from Facts

In the speech of an intellectually honest person, two things are clearly separated: **facts** and **guesses**. Mixing the two is the start of all confusion.

It helps to deliberately attach markers like these when you speak.

[When stating a fact]

"According to the logs ..." / "When I measured it ..." /

"As the documentation states ..."

[When stating a guess]

"My guess is ..." / "It is likely that ..." /

"I have not verified it, but it seems ..."

[When you do not know]

"I need to check this part" / "This is an unfounded hunch"

Attaching these markers takes less than a second, but it completely changes how the listener receives the information. When a guess wears the label "this is a guess," the other person can calibrate the weight of that information correctly.

> Honesty is the work of putting accurate price tags on information.

From Not Knowing to Learning: The Mechanism of the Shift

Psychologist Carol Dweck's research on the growth mindset offers a useful frame here. A person with a fixed mindset receives ignorance as a signal that "I lack ability," and so hides it. A person with a growth mindset receives ignorance as a signal that "I have not learned this yet," and so makes it the starting point of learning.

The way to practice this shift daily is simple. When the thought "I do not know" arises, add one small word to the sentence.

"I do not know this."

|

v

"I do not know this yet."

That single word, "yet," turns ignorance from an ending into a point along a process. Go one step further and convert ignorance into a concrete question.

Vague ignorance: "I do not really understand this system."

|

v

Concrete question: "In this system, when a request comes in,

which component receives it first?"

Vague ignorance breeds helplessness, but a concrete question makes the next action clear.

The Deeper the Expertise, the Clearer the Boundaries

There is an interesting paradox. The more deeply you know a field, the more precisely you know what you do not know. A real expert does not fear saying "this is outside my area of expertise." Being able to draw that boundary clearly is itself evidence of expertise.

The Dunning-Kruger effect explains this phenomenon. People low in competence fail to notice their own ignorance and are excessively confident, while people high in competence, aware of the complexity of knowledge, become more cautious.

So when the most experienced person in a meeting says, "I am not sure about that part either," it is not a confession of weakness but a sign of maturity. With even one such person present, others find the courage to be honest too.

Two Scenes from the Field

Scene 1: In an Interview

The interviewer asks about a technology you do not know.

[Common mistake]

Candidate: (a term they have never heard) "Oh yes, I have used that..."

Interviewer: "Then could you explain how it works internally?"

Candidate: (cold sweat) "...uh..."

[A better answer]

Candidate: "I have not used that technology directly.

But I have solved a similar problem with X.

May I tell you about that experience?

And I am curious in what way the technology you mention is better."

The second answer admits ignorance while connecting relevant experience and showing a willingness to learn. Many interviewers watch how you behave when you do not know more closely than whether you know the answer.

Scene 2: In a Code Review

You are reviewing a junior's complex code, but you are not familiar with the library used.

[Bluffing type]

"This is no good. Do it a different way." (while not really knowing)

[Honest type]

"I am not familiar with this library, so I want to ask one thing.

Have you checked whether this function is safe under concurrency?

It is an area I do not know, so I would like to look at it together."

The honest review asks a genuinely important question without losing authority. Instead of staying silent because of ignorance or covering it with a bluff, it turns ignorance into a good question.

The Connection to Psychological Safety

Intellectual honesty is not only a personal virtue but also a matter of organizational culture. The concept of **psychological safety**, established by Harvard's Amy Edmondson, touches on this. Psychological safety is a team-level belief that "even if I say I do not know, ask a question, or admit a mistake, I will not be punished or dismissed."

On a team without this belief, everyone pretends to know. As a result, small problems stay hidden until they explode as large incidents. On a team with psychological safety, by contrast, "I do not know this" flows freely, and so problems surface early.

The leader's role is decisive. When a leader says first, "I do not know this either," it is like granting permission to the whole team. When the most senior person shows that admitting ignorance is acceptable, those below them can finally be honest.

Of course, balance is needed. This does not mean answering everything with "I do not know" to dodge responsibility. You must know the areas you own, and if you do not, you must learn quickly. Intellectual honesty is not an excuse for laziness but a starting line for learning faster and more accurately.

Five Grades of Expressing Ignorance

"I do not know" is not a single thing. In reality there are several grades of confidence, and lumping them all into one "I do not know" loses information. Conveying your degree of confidence in stages, like below, lets the listener judge far more accurately.

[Grade 1: I know for sure]

"This is certain. It is a value I measured directly."

[Grade 2: I am almost confident]

"I am almost sure, but I would like to confirm one assumption."

[Grade 3: It is a guess]

"My guess is this, but it needs verification."

[Grade 4: It is a vague hunch]

"The basis is weak, but my hunch points this way."

[Grade 5: I have no idea]

"I have no idea about this part. Who should I ask?"

Even the same "I am not sure" demands completely different actions at grade 2 versus grade 5. Grade 2 ends with one small check; grade 5 means finding an expert. The habit of honestly expressing your confidence level as a grade greatly speeds up team decisions.

This grade language shines especially in a crisis. If, during an incident, someone says "I do not know the cause, but my grade-4 hunch is that it is the deploy," the team can handle that information with the right weight. Had they mixed certainty and guess, it would only have deepened the confusion.

An Action Routine After Admitting Ignorance

Admitting ignorance is only the start. Real trust is decided by what you do next. Here is a small routine that turns ignorance into learning.

1. Admit "I do not know right now."

2. Narrow "Exactly which part do I not know?"

3. Set source "Who/where can I find the answer?"

4. Set a deadline "I will check by when."

5. Share "Tell the answer to the relevant people."

6. Record "So the same question can be answered instantly next time."

The last step, "record," is often skipped but holds the most value. Leave the answer that filled your ignorance in a doc or note, and when the same question returns, you become the person who can answer instantly. In other words, one honest "I do not know" turns, over time, into "that, I know."

A person who accumulates this routine becomes a living knowledge store for a given area — the result of filling ignorance systematically rather than being ashamed of it.

Common Traps and the Balance Point

There are cases where trying to practice intellectual honesty backfires. For a balanced view, let us note a few traps.

Trap 1: Excessive Self-Deprecation

Habitually tacking on "I do not really know" or "it is because I am lacking." When honesty crosses into a look of low confidence, it actually erodes trust. Ignorance can be admitted calmly, as a fact. There is no need to put yourself down.

Trap 2: Using Ignorance as a Shield

Using "that is outside my area" as a tool for dodging responsibility. Real intellectual honesty is followed by a will to learn after admitting ignorance. Admitting without learning is just another name for laziness.

Trap 3: Honesty That Misses the Timing

Blurting out every bit of ignorance on the spot is not always best. In a moment where the team's credibility is on the line in front of a customer, it can be more professional to say "I will answer precisely after checking," then sort it out internally and respond. Honesty and recklessness are different.

| Situation | Healthy honesty | Honesty fallen into a trap |

| --- | --- | --- |

| Expression | "This needs checking" | "I am just bad at this" |

| Next action | Start checking immediately | Simply give up |

| Attitude | Calm | Self-deprecation or avoidance |

| Result | Trust rises | Trust falls |

The key is to admit ignorance but always connect it to learning and action.

Honesty in Writing: The Power of Marking Guesses

Honesty in writing matters as much as honesty in speech. If anything, writing lasts longer, so its impact is greater. Whether in a report, a chat message, a code comment, or a doc, mixing guesses with facts leads later readers to mistake guesses for facts.

A good habit is to make the level of confidence explicit in writing too.

[Bad report]

"This outage is due to a memory leak and will be fixed in the next deploy."

(a guess written as a certainty -> the reader takes it as fact)

[Good report]

"By analysis so far, a memory leak looks like the likely cause (unconfirmed).

We plan to include a fix in the next deploy, but after a reproduction test

we will share again whether it is confirmed."

In code comments especially, this honesty saves a future colleague.

Note: this timeout value (30s) is an estimate, not measured.

The proper value should be re-decided with a load test. (TODO)

Honestly marking "this is a guess" keeps a later reader from carelessly believing the value as fact. One small honesty marker in writing prevents a wrong decision months later.

Building a Culture That Welcomes Not Knowing

For individual honesty to spread across an organization, culture must back it up. In an environment where only one person is honest and the rest pretend to know, the honest person is the one who loses out. So small devices that "welcome not knowing" help.

[Team-level practices]

- When "I do not know this" comes up in a meeting, welcome it lightly.

- Publicly praise good questions that started from not knowing.

- Have leaders regularly share "what I got wrong" and "what I did not know."

- Cover "what we assumed wrongly" in retrospectives.

- Make a questions channel so even trivial questions can be posted freely.

What these devices share is treating ignorance as a learning signal, not a punishment. On a team where ignorance is welcome, problems surface early, and so incidents decrease. On a team where ignorance is punished, everyone clams up, and small cracks grow unseen until they finally collapse badly.

Culture is built not by grand declarations but by small daily reactions. Every reaction you show when someone says "I do not know this" decides whether that person will be honest again next time.

A Phrase Dictionary by Situation

Knowing the theory does not mean the words come out in the moment. It helps to keep a set of phrases you can use right away in the situations you face most often.

[When a manager expects an immediate answer]

"Because I want to answer precisely,

may I check for one hour and come back with exact numbers?"

[When an unknown term comes up in a meeting]

"I am not familiar with that term —

if you could explain it briefly, I could follow along better."

[When you do not know in front of a customer]

"Thank you for the good question. To give you an accurate answer,

I will check and reply within today."

[When you must state your guess]

"This is not a confirmed fact but my judgment;

for reference, I would say ..."

[When admitting a past mistake of yours]

"I had it wrong back then.

Thank you for correcting me."

These phrases share two things. First, they admit ignorance while also showing a sense of responsibility for accuracy. Second, they close the sentence with a next action or thanks, ending the conversation on a positive note. Expressing ignorance is not an ending but a bridge to what comes next.

Self-Check: How Honest Am I?

Intellectual honesty starts less from how you appear to others and more from how honest you are with yourself. Answering the following questions yourself lets you gauge where you currently stand.

| Question | If so |

| --- | --- |

| Have you stated a guess as fact when you did not know? | You need the guess-label habit |

| Have you failed to correct something you knew was wrong? | You need the courage to correct |

| Have you said "I will check" and then forgotten? | You need follow-up management |

| Have you stayed silent because a question felt embarrassing? | You need to overcome fear of looking incompetent |

| Have you pretended to know outside your area of expertise? | You need boundary awareness |

The purpose of this check is not self-blame. Most people answer "yes" to these questions once or twice. What matters is noticing the pattern and choosing differently next time. Intellectual honesty is not an innate trait but a muscle grown through repetition.

Conclusion: The Accumulation of Small Courage

"I do not know" takes a little courage the first time, but once it becomes a habit, it actually puts your mind at ease. You no longer spend energy maintaining the mask of pretending to know. And as that honesty accumulates, at some point people begin to hear your words with a different weight.

Intellectual honesty is not a grand resolution but a small daily choice. In today's meeting, in the next code review, in that one moment, choosing "let me check and get back to you." Those small choices add up to the asset called trust.

Practice Checklist

[ ] Before answering, ask yourself: "Is this a fact or a guess?"

[ ] When stating a guess, attach the label "this is a guess."

[ ] When you do not know, do not stop at "I do not know" — add a follow-up commitment.

[ ] If you said "I will get back to you," always keep it.

[ ] Say "I do not know yet" instead of "I do not know."

[ ] Turn vague ignorance into a concrete question.

[ ] Honestly admit the boundaries of your expertise.

[ ] As a leader, admit ignorance first to create safety for the team.

[ ] But fill ignorance in the areas you own with fast learning.

References

- Carol S. Dweck, *Mindset: The New Psychology of Success* — [https://www.penguinrandomhouse.com/books/44330/mindset-by-carol-s-dweck-phd/](https://www.penguinrandomhouse.com/books/44330/mindset-by-carol-s-dweck-phd/)

- Amy C. Edmondson, *The Fearless Organization* — [https://fearlessorganization.com/](https://fearlessorganization.com/)

- Harvard Business Review, "What Is Psychological Safety?" — [https://hbr.org/2023/02/what-is-psychological-safety](https://hbr.org/2023/02/what-is-psychological-safety)

- Justin Kruger, David Dunning, "Unskilled and Unaware of It" — [https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect](https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect)

- Will Larson, *An Elegant Puzzle / Staff Engineer* — [https://lethain.com/](https://lethain.com/)