Introduction: Two Colleagues
I think of two memorable colleagues. One was always self-assured. He would declare "this absolutely has to be done this way," but when asked for evidence, the answer came back "just in my experience." At first he seemed charismatic, but after being wrong a few times, people began to filter out his words.
The other was quiet. He would say "I'm not certain, but the data shows this tendency," always presenting evidence alongside. He admitted he could be wrong, yet was clear in the face of facts. Over time, people sought his opinion first when facing hard decisions.
This piece is about the attitude of that second colleague — **how to speak humbly yet sharply**. We often see humility and confidence as opposites. But the people who are truly trusted hold both. At the heart of that secret is "speaking in facts."
Humility and Confidence Do Not Collide
Many people fall into the dilemma that "humility makes you look like a pushover, and confidence makes you look arrogant." But this misunderstands both.
What to Be Humble About and What to Be Confident About
- **Humble about yourself**: "I can be wrong. There are things I don't know."
- **Confident about the facts**: "This data says this. This much is clear."
This distinction is the core. Humility about ego and conviction about verified facts do not collide. In fact, they are most powerful together. The stance "my thinking may be wrong, but at least this measurement is clear" is neither arrogant nor a pushover.
The Concept of "Intellectual Humility"
This is what psychology calls "intellectual humility." It is the attitude of admitting the limits of your knowledge and staying open to counter-evidence, without being so spineless that you waver. It is also a common trait of the most trusted experts.
Why Speaking in Facts Builds Trust
Let's look a little more deeply at the effect of fact-speech.
Verifiability Is the Foundation of Trust
"In my experience" can't be verified, but "this measurement" can be checked by anyone. A verifiable claim, even if wrong, can be fixed together. An unverifiable claim, right or wrong, yields no learning. People instinctively trust verifiable words more.
Clarity of Responsibility
Speaking in facts makes accountability clear. "It'll probably work out" is vague about whose responsibility it is if it later goes wrong. "From this data it's X, so I recommend Y" leaves the basis of the judgment, so the outcome can be learned from together.
Less Emotional Drain
Fact-based discussion reduces emotional fights. Instead of the endless loop of "you're wrong / no, I'm right," switching to "let's look at the data" turns an argument into learning. Facts have the power to turn an ego contest into joint inquiry.
Separate Opinion from Fact
The first step to speaking sharply is knowing yourself whether your words are opinion or fact.
Mixing Them Is Dangerous
"Users hate this feature" sounds like a fact but is often an opinion. "In last week's survey, 140 of 200 respondents expressed dissatisfaction with this feature" is a fact. Mix the two and the opinion borrows the authority of fact and gets exaggerated. Separate them, and the listener can decide for themselves what to believe and what to judge.
Distinguishing Through Language
Make the signal clear when you speak.
- Fact: "When I measured it, the response time was 800ms."
- Inference: "So I suspect this part is the bottleneck."
- Opinion: "I think we should look at caching first."
Layering it this way lets the other person see how far you're certain and where your judgment begins. This is how you satisfy sharpness and humility at the same time.
Speaking with Data and Evidence
The core of "speaking in facts" is ultimately accompanying your claims with evidence.
Attach Numbers to Claims
Weak claim: "The server's been slow lately."
Strong claim: "Over the past 7 days, p95 response time
rose from 320ms to 540ms, about 69%.
It's especially pronounced on the payment API."
For the same problem, the second leads immediately to action. Numbers turn an emotional argument into a fact-based discussion.
Cite Your Source
"I saw it somewhere" is weak. Cite the source — "according to last quarter's incident report," "per section X of the official docs" — and trust rises. At the same time, if the source is uncertain, honestly saying "I'm not sure, but" is both humility and trust.
Be Honest When You Have No Evidence
Not every claim can have data. When it can't, say plainly "this isn't data but intuition." Not dressing up intuition as fact — that is the honesty of someone who speaks in facts.
Remove Ambiguity
Sharp speech has no ambiguity. It keeps the listener from asking "so what do you want me to do?"
Drop the Vague Expressions
- "I'll get to it soon" → "I'll share a draft by this Friday."
- "It's almost done" → "Core features are finished; two tests remain."
- "There's a bit of a problem" → "The payment failure rate rose from 0.3% to 4.1% yesterday."
Vague expressions blur responsibility and breed misunderstanding. Concrete expressions create action and trust.
Clear Uncertainty over Silence
Don't be afraid to say "I don't know." But don't stop there. "I don't know right now. I'll check and let you know by tomorrow morning" is a sharp form of not knowing. Even uncertainty can be handled clearly.
Strong Opinions, Loosely Held
This is the core attitude of someone who speaks in facts.
Split It into Two Parts
- **Strong opinion**: take a clear position with the information you currently have. "I believe option A is right."
- **Loosely held**: be ready to change your position immediately if better evidence appears.
This is different from indecision. The indecisive can't take a position. Someone who speaks in facts takes a clear position but changes it cleanly in the face of new evidence. The strongest person is the one who can say "looking at this data, I was wrong. Let's go with B."
Changing Your Mind Is Not Defeat
Some organizations have a flawed culture where "changing your mind means you lost." But changing your position in the face of new facts is not weakness but intellectual honesty. Stubbornly clinging to a wrong claim to the end is the real defeat.
The Trap of Political Speech
There is a manner of speaking you often see in organizations: dodging responsibility, trying to satisfy everyone, blurring conclusions. It looks safe in the short term but erodes trust.
Patterns to Avoid
- **Conclusion-dodging**: ending with "well, it depends" without stating a position.
- **Diffusing responsibility**: hiding your own opinion behind "everyone seems to think so."
- **Post-hoc justification**: saying "actually, I thought so too" after the result is out.
This manner avoids conflict, but makes decisions harder and ultimately leaves the reputation that "that person's words have no substance."
The Fact-Based Alternative
Instead of political speech, speak clearly based on facts, but express it courteously. "I recommend option B. The reasons are these three pieces of data. That said, if condition X changes, we'll need to revisit." Clear yet open, confident yet humble.
Delivering Feedback as Fact
One of the hardest kinds of speech is feedback. Here too, fact is the core.
The SBI Framework
A framework for structuring feedback on a factual basis.
- **S**ituation: when and where. "At yesterday's sprint review"
- **B**ehavior: the observed fact. "you explained the customer-data slide for three minutes, and"
- **I**mpact: the result. "the sales team in attendance started asking deeper questions. It was effective."
The key is to convey the fact of observed behavior and its impact, not a character verdict like "you're good/bad at presenting."
Behavior, Not Character
Bad feedback: "You're too defensive." (character verdict)
Good feedback: "Earlier in the code review, when I offered an opinion,
you immediately replied 'I already considered that' (behavior),
and from where I sat it became harder to keep talking (impact).
Was there context I might have missed? (openness)"
Good feedback starts with fact, presents an observation the other person can't dispute, and at the same time stays open to the possibility that you're wrong. It's the union of sharpness and humility.
Receive Feedback as Fact Too
If you get defensive first when receiving feedback, you miss the facts. Confirm the facts first: "what specifically was the situation?" Gather facts instead of reacting emotionally, and you can judge for yourself whether the feedback is right.
Fact-Speech for Difficult Situations
The principle is the same, but its application differs by situation. Here are a few tricky ones.
Dissenting to a Superior
With a power gap, dissent is more delicate. But facts cut across rank.
Weak: "I don't think that's quite right..." (vague + emotional)
Strong: "Before we decide, may I share one piece of data?
Last year's project that went this direction
has a record of churn rising 12%.
Are conditions different this time?"
The latter is courteous yet clear and, above all, grounded in fact. Even a superior finds it hard to override data with rank.
Asked for an Opinion on a Topic You Don't Know Well
Bad: pretend to know and answer vaguely. (risk of trust collapse)
Good: "I don't know that part deeply.
On the surface what I see is X,
but X would know it more precisely.
If needed, I'll verify and reinforce this today."
Admitting you don't know does not harm your sharpness. It actually builds trust that "this person distinguishes what they know from what they don't."
When You Must Give an Estimate
Even when data is lacking, you sometimes have to give an estimate for a decision. Then make clear it is an estimate and state its basis and the range of uncertainty. "It's not exact, but roughly two to three weeks. The external dependency is the variable; if that slips, it could go to four."
Handling Data Honestly
Speaking in facts also means using data honestly. Numbers don't lie, but the people using them can.
Common Data Distortions
- **Cherry-picking**: choosing only favorable numbers and hiding the unfavorable.
- **The ratio trap**: "300% increase!" when it's just 3 cases rising to 9.
- **Confusing correlation and causation**: "B rose after we did A" is not "A raised B."
- **The sample problem**: asking 10 people and generalizing to "users..."
Someone who speaks in facts guards against even self-favoring distortion. Honest data use is the core of long-term trust.
Present the Context Too
A single number invites misunderstanding. Is "2% conversion" good or bad? It only gains meaning alongside the industry average, last quarter's trend, and the measurement period. A number without context can be an opinion that looks like a fact.
A Case: The Difference Between Two Reports
Two people reported on the same outage.
A's report:
> "We had a fairly big outage yesterday. A lot of users seem to have been affected, and we recovered quickly, but the cause is probably traffic. I'll be careful going forward."
B's report:
> "Yesterday from 14:32 to 15:10, a 38-minute payment-API outage occurred. About 1,200 users were affected, with roughly 340 failed payments. The cause was confirmed as DB connection-pool exhaustion. Traffic was 2.3x the usual, and the pool size fell short. We recovered by temporarily increasing the pool, and as a root-cause fix I propose adjusting the autoscaling threshold. Details are in the postmortem doc."
A looks humble but has no substance, and you can't tell what to do. B doesn't look self-assured, yet everything is clear. Trust goes to B. This is the power of speaking in facts.
The Structure of Facts That Persuades
The same facts persuade differently depending on how you arrange them.
Conclusion → Evidence → Caveat
1. **Conclusion**: "I propose introducing caching."
2. **Evidence (fact)**: "60% of p95 responses are repeats of the same query."
3. **Caveat (humility)**: "That said, where data-consistency requirements are high, we'd need to revisit."
Give direction with the conclusion, back it with fact, and admit the limit with the caveat. This three-beat rhythm holds sharpness and humility at once.
Address the Counterargument in Advance
Good fact-speech mentions the likely counterargument first. "You may worry about cost, but when measured, the added cost is about X per month, smaller than the savings." Resolving the counterargument the other person would raise, with facts, in advance, greatly raises your persuasiveness.
Pitfalls and Balance
Emphasizing facts comes with traps you can fall into.
Beware Data Absolutism
The attitude of judging everything by numbers alone is dangerous. Many important things aren't measured. Team morale, long-term trust, a user's subtle discomfort — numbers can't capture them all. Respecting facts while acknowledging the limits of measurement is real intelligence.
The Difference Between Coldness and Firmness
Speaking in facts is not being coldly inhuman. "The data says this, but I know you worked hard on it" — the clarity of fact and warmth toward people can go together. Sharpness is not a license for rudeness.
Honesty That Fits the Context
You don't have to say every fact in every setting. Honesty and tactlessness are different. The discernment of choosing what, when, and how to say something is also part of maturity.
Delivering Facts in Writing
As much as spoken facts, facts captured in writing matter. Writing is more accurate and permanent.
The Structure of a Good Report / Proposal
1. One-line conclusion : first, so busy people see the gist
2. Key facts : numbers and evidence (cite sources)
3. Analysis/inference : interpretation drawn from facts (mark as opinion)
4. Proposal : a concrete next action
5. Uncertainty/limits : unknowns, assumptions, risks, honestly
This structure holds sharpness (1, 4) and humility (5) in one document. The reader grasps the conclusion quickly, verifies the evidence, and judges while aware of the limits.
Separate Opinion and Fact Visually
In writing too, separating the two with labels like "measured result:" and "my interpretation:" keeps the reader from confusion. In tables, splitting a "fact" column from an "estimate" column reveals honesty.
| Item | Fact (measured) | Estimate/interpretation |
|---------------|-----------------|-------------------------|
| Response time | p95 540ms | cache miss is the cause |
| Error rate | 4.1% | DB pool exhaustion est. |
A Record for Later
Capturing the rationale for today's decision in writing lets you, months later, retrace "why did we do it that way?" as fact. Decision records (ADRs and the like) are a gift of fact to your future self and team.
Building a Culture Where Facts Land
No matter how much an individual speaks in facts, it's useless if the organization's culture won't receive them. Fact-based communication is also a matter of culture.
An Environment That Doesn't Punish Being Wrong
In an organization that derides someone who changed their mind in the face of new evidence as "spineless," no one changes their position. Conversely, in an organization that praises "changing your view after seeing the data," facts flow freely. It starts with the leader being first to say "I was wrong, looking at this data."
A Shared Language That Separates Opinion from Fact
When a team shares a language to naturally distinguish "this is data, this is my guess," the quality of discussion rises. The key is an atmosphere where you can gently ask in a meeting, "is that a fact or an opinion?"
Deciding by Evidence, Not Authority
An organization is healthy when "this data says so, so let's do this" prevails over "I'm the manager, so let's do it this way." Aim for a culture where the best evidence wins, not the opinion of the highest-paid person (the HiPPO).
Here is an example of a dialogue that builds a fact-based culture.
[Situation] A leader's hypothesis is refuted by data
Member: "I tested the direction you proposed,
and conversion actually dropped 0.4 points. (fact)
The sample is about 50k sessions over 2 weeks." (evidence)
Leader: "Oh, really? That's the opposite of what I expected.
Good data. My hypothesis was wrong. (admits being wrong)
Then let's leave it as is, but dig together
into why it dropped." (turns to learning)
When a leader responds this way, team members bring uncomfortable facts with confidence next time too. That is a culture where facts land.
Frequently Asked Questions
**Q. Won't speaking in facts look too rigid and cold?**
The clarity of fact and the warmth of expression are separate. Add "you worked hard on this" to "the data says this." What's cold isn't the fact but a delivery without empathy.
**Q. What about areas with no data at all?**
Honestly say "this isn't data but an experiential judgment" and give your opinion. Not everything can have data. What matters is not dressing up an opinion as a fact.
**Q. I worry that voicing a strong opinion looks arrogant.**
Arrogance comes from attitude, not the strength of the opinion. "I may be wrong, but with the current data I recommend B" is strong yet humble. Pair a strong opinion with humility about yourself and it isn't arrogant.
**Q. I can't recall facts on the spot in meetings.**
That's fine. Just say "I'm not sure of that number; I'll verify and share." It earns far more trust than insisting on a guess. And the habit of preparing key data before the meeting reduces on-the-spot scrambling.
A Practical Checklist
Before speaking:
- [ ] Did I distinguish whether my words are fact or opinion?
- [ ] Did I attach numbers or evidence to my claim?
- [ ] If the source was uncertain, did I say so honestly?
While speaking:
- [ ] Did I speak concretely instead of vaguely?
- [ ] Did I take a clear position while staying open to new evidence?
- [ ] Did I avoid dodging the conclusion?
Feedback:
- [ ] Did I speak to observed behavior, not character?
- [ ] Did I structure it as situation-behavior-impact (SBI)?
- [ ] Did I stay open to being wrong myself?
Attitude:
- [ ] Was I humble about myself, confident about the facts?
- [ ] Did I avoid falling into data absolutism?
- [ ] Did I keep clarity from becoming coldness?
The Courage to Face Uncomfortable Facts
The real test for someone who speaks in facts is facing a fact unfavorable to themselves.
Trying to Disprove Your Own Hypothesis
Good thinking doesn't defend your opinion but actively tries to disprove it. "If I'm right, what data should appear? And is there no contradicting data?" Someone who asks this of themselves falls less into confirmation bias.
Not Hiding Uncomfortable Data
When data unfavorable to your recommendation appears, the temptation is to hide it. But the person who honestly presents that data alongside earns trust in the long run. The honesty of saying first "my recommendation has this weakness" is the highest form of sharpness.
Grace When Wrong
When being wrong is exposed, the person who says "I missed it, I learned" instead of making excuses or shifting blame actually earns trust. The courage to admit being wrong completes the attitude of speaking in facts.
Closing: Trust Comes from Accuracy
I think again of the two colleagues. The first, self-assured but evidence-less, gradually lost trust; the second, humble but clear in the face of facts, became the most trusted person.
The difference wasn't rhetoric. It was the attitude of holding both humility about oneself and confidence about facts — that is, "how to speak in facts." This attitude is not innate but grown through practice: practicing to separate opinion from fact, attach evidence, clear away ambiguity, and change your position in the face of new evidence.
Humble yet sharp. The two are not a contradiction but the two faces of the most trusted person. In today's meeting, try once to clearly separate opinion from fact. That small habit will, over time, make you "a person whose words carry weight."
References
- Annie Duke, *Thinking in Bets* — decision-making under uncertainty and probabilistic thinking: [https://www.annieduke.com/books/](https://www.annieduke.com/books/)
- Adam Grant, *Think Again* — rethinking and intellectual humility: [https://adamgrant.net/book/think-again/](https://adamgrant.net/book/think-again/)
- Center for Creative Leadership, the SBI feedback model: [https://www.ccl.org/articles/leading-effectively-articles/closing-the-gap-between-intent-vs-impact-feedback-step/](https://www.ccl.org/articles/leading-effectively-articles/closing-the-gap-between-intent-vs-impact-feedback-step/)
- Harvard Business Review, "The Art of Giving and Receiving Feedback": [https://hbr.org/2022/03/the-art-of-giving-and-receiving-feedback](https://hbr.org/2022/03/the-art-of-giving-and-receiving-feedback)
- Kim Scott, *Radical Candor* — combining directness and care: [https://www.radicalcandor.com/the-book/](https://www.radicalcandor.com/the-book/)
- "Strong Opinions, Weakly Held" (Paul Saffo): [https://www.saffo.com/02008/07/26/strong-opinions-weakly-held/](https://www.saffo.com/02008/07/26/strong-opinions-weakly-held/)
- Overview of intellectual humility research (APA): [https://www.apa.org/monitor/2022/06/news-intellectual-humility](https://www.apa.org/monitor/2022/06/news-intellectual-humility)
- Will Larson, lethain.com — engineering decisions and writing: [https://lethain.com/](https://lethain.com/)
현재 단락 (1/159)
I think of two memorable colleagues. One was always self-assured. He would declare "this absolutely ...