Deck: “Obviously” is often used by intelligent people to move a conversation faster. In a senior room, it can do something else: turn a knowledge gap into a status test. The person who does not understand now has to decide whether the answer is worth looking stupid for.
Executive Authority Answer
Senior leaders should use words such as “obviously,” “clearly” and “as everyone knows” with care when those words describe what other people are supposed to understand.
The problem is not politeness. It is information access.
Experts routinely struggle to reconstruct what less-informed people know, a bias often described as the curse of knowledge. In teams, asking questions, admitting uncertainty and seeking help can also carry interpersonal risk. A powerful leader who labels a point “obvious” can unintentionally increase that risk at exactly the moment the organisation needs clarification.
Executive Authority calls the correction the Obviousness Check:
Assumption -> Audience -> Cost -> Invitation -> Verification.
What are you assuming? Who may not share it? What does it cost them to admit that? How are you inviting challenge? How will you verify actual understanding rather than polite agreement?
The strategy meeting is moving fast
The CEO is at the screen.
“We obviously cannot enter through a direct model because the regulatory economics do not work.”
The executive team nods.
One person does not understand.
They joined three months ago.
Their experience is in another region.
They have seen direct models work under similar regulation.
They want to ask:
“What specifically makes the economics impossible here?”
But now the question has changed.
It is no longer only:
What do I need to know?
It is also:
What does it say about me if I do not know the obvious thing?
So they stay quiet.
The meeting moves on.
Two weeks later, the same executive raises the issue privately with a colleague.
The colleague says:
“I never understood that either.”
Now the CEO has an information problem disguised as a vocabulary habit.
The word was one second long.
The cost may last weeks.
“Obviously” is not banned
This article is not an argument for language policing.
Some things are obvious in context.
“If the building is on fire, obviously we evacuate.”
Fine.
“If the regulator prohibits the structure, obviously we cannot use it.”
Fine, assuming the prohibition really is established.
The problem is not the dictionary meaning.
The problem is what the word can do socially when the audience is unequal in knowledge or status.
A senior expert says:
“Clearly the second option destroys value.”
A junior executive may hear:
If I do not see that, I am behind.
A board chair says:
“As everyone knows, this is standard governance practice.”
A new director may hear:
Do not reveal that you have a question.
A minister says:
“Obviously the department considered that.”
An official may hear:
Do not tell me we did not.
The leader may intend speed.
The room may receive a competence test.
Expertise makes this more likely, not less
The curse of knowledge is a well-established problem in judgement.
Camerer, Loewenstein and Weber used the term in economic experiments showing that better-informed people can struggle to ignore what they know when estimating the judgements of less-informed people.
More recent work continues to find that a person’s own knowledge can contaminate estimates of what others know.
This matters enormously in senior leadership because experts live inside compressed meaning.
The CFO says:
“The covenant headroom is obviously the issue.”
To the CFO, that sentence contains years of pattern recognition.
The new CEO may understand the words and not the implication.
The chief scientist says:
“The off-target risk is clearly unacceptable.”
To the scientist, an entire evidence chain sits behind “clearly.”
The board may not know which part of the evidence makes the risk unacceptable.
The technology leader says:
“Everyone understands the model risk.”
No.
Everyone may have heard the phrase.
Understanding is another matter.
Experts compress.
That is part of expertise.
Leadership communication has to know when to decompress.
“Obviously” can hide a weak argument too
There is another danger.
Sometimes the point is not obvious.
The speaker simply wants it to be treated as settled.
“Obviously we need to centralise.”
Why?
“Clearly the brand architecture has to change.”
According to what evidence?
“Everyone knows customers want one platform.”
Do they?
The language smuggles consensus into the sentence.
This can happen innocently.
The executive has discussed the issue for six months.
The conclusion now feels self-evident.
But the rest of the organisation did not live through those six months.
Or it can happen strategically.
The leader wants to move past challenge.
Calling the conclusion obvious makes dissent look like ignorance instead of disagreement.
That is dangerous.
A board should be able to reject an “obvious” recommendation.
An employee should be able to question an “obvious” process.
A technical expert should be able to say:
“The conclusion may be right, but the evidence you are relying on is not the evidence I would rely on.”
If your vocabulary makes that harder, your vocabulary is affecting decision quality.
Psychological safety is not a slogan here
Amy Edmondson’s foundational work defined team psychological safety as a shared belief that a team is safe for interpersonal risk taking. Her research linked psychological safety with learning behaviour such as asking for help, seeking feedback and discussing errors.
That concept is frequently watered down into “be nice.”
This is not about niceness.
Asking a senior person to explain something they called obvious is an interpersonal risk.
Correcting a CEO who says “we all agree” is an interpersonal risk.
Admitting “I do not understand that term” in front of peers can be an interpersonal risk.
The more status-conscious the environment, the more expensive the question can feel.
A leader can tell people all year:
“My door is open.”
“I want challenge.”
“Speak up.”
Then destroy the invitation in a meeting with three words:
“You all know this.”
The room learns from micro-signals faster than from values posters.
The expensive assumption
Every high-stakes communication contains assumptions about the audience.
They know the history.
They understand the acronym.
They remember the previous board paper.
They know why the ratio matters.
They understand the legal constraint.
They can see why option B is dangerous.
They know what happened in the last crisis.
Some assumptions are necessary.
You cannot explain everything from first principles.
The leadership skill is knowing which assumptions are expensive if wrong.
A cheap assumption:
Everyone knows the meeting ends at 4 p.m.
If wrong, somebody checks the calendar.
An expensive assumption:
Everyone understands why the company cannot legally make the public claim the CEO wants to make.
If wrong, the organisation may create risk.
Another expensive assumption:
Everyone understands what “AI-ready” means in the capital plan.
If wrong, the board may approve different interpretations of the same investment.
High-consequence assumptions deserve verification.
The Obviousness Check
Executive Authority uses five steps.
Assumption
What are you treating as already known, agreed or self-evident?
Write the sentence without the amplifier.
Instead of:
“Obviously we need to delay.”
Write:
“We need to delay.”
Now ask:
Why?
What evidence makes that true?
What prior knowledge does the audience need to follow it?
Audience
Who in the room may reasonably not share that knowledge?
New director.
Regional leader.
Minister without technical background.
Investor outside the sector.
Employee several levels from strategy.
Expert from another discipline.
Do not design only for the least informed person.
Do not design only for the most informed person either.
Know the spread.
Cost
What does it cost someone to reveal the gap?
Very little?
Or does the question risk making them look unprepared, junior, disloyal or difficult?
Status changes the cost.
A CEO can ask the CFO to explain an acronym with almost no reputational risk.
A newly promoted vice president may feel the same question differently.
Invitation
How will you make challenge possible without making people perform courage?
Not:
“Any stupid questions?”
Not:
“I assume everyone follows.”
Try:
“The conclusion is important, so let me make the reason explicit.”
Or:
“Which assumption in that chain would you challenge?”
Or:
“What part of that does not travel cleanly outside this team?”
The invitation should be specific enough that people know what kind of challenge is useful.
Verification
Do not ask only:
“Does everyone understand?”
A room full of people can nod at the same sentence for different reasons.
Ask for recovery.
“What does that mean for the regional plan?”
“Which threshold would make us reverse this?”
“What would you tell your team changed?”
“What are we assuming about the customer?”
Now you can see whether meaning actually travelled.
The leader who says “as you know” when they know you do not
There is a more political use of this language.
“As you know, the board has always supported the transformation.”
Maybe the listener knows the board has not always supported it.
“As we all agree, the current structure cannot continue.”
Maybe there is no agreement.
“As everyone understands, the decision was necessary.”
Maybe that is exactly what people dispute.
Now the phrase is not merely a curse-of-knowledge error.
It is consensus manufacture.
Senior leaders should resist this because it damages the record.
A better sentence is stronger precisely because it makes disagreement visible.
“Management recommends changing the structure. Two executives disagree on timing, and the board has asked us to return with the implementation risk.”
That sounds less smooth.
It is more governable.
The person who asks anyway is giving you information
A junior leader interrupts:
“Sorry, I know you said this is obvious, but I do not understand why the direct model is impossible.”
How the CEO responds matters enormously.
Weak response:
“We covered this in the last review.”
The room learns.
Do not ask twice.
Another weak response:
“It is complicated, but trust me, the economics do not work.”
The room learns.
Authority outranks explanation.
Stronger response:
“Good catch. I compressed too much. The model is not impossible in principle. It fails our current return threshold because local licensing adds X cost and delays revenue by Y. If either condition changes, the conclusion should be reopened.”
Now the leader has corrected two things.
The explanation.
The overstatement.
That response creates more authority, not less.
“Obviously” can be hostile to cross-functional leadership
Executives are experts in different things.
The CISO lives inside threat models.
The CFO lives inside capital structure.
The general counsel lives inside legal risk.
The chief medical officer lives inside clinical evidence.
The CHRO lives inside workforce systems.
The minister lives inside political and public accountability.
The CEO has to integrate them.
The sentence that is obvious inside one function may be contestable from another.
“Obviously security comes first.”
Always?
What if the proposed control makes the clinical system unusable in an emergency?
“Obviously we should preserve margin.”
Always?
What if the decision destroys a strategic customer relationship?
“Obviously we cannot disclose that.”
Is that a legal prohibition, a preference or a risk judgement?
“Obviously employees need certainty.”
What if certainty would require a promise the board cannot make?
Cross-functional leadership lives in the exceptions.
The word “obvious” can close the space where those exceptions are discovered.
The clarity paradox
Leaders want to sound clear.
So they use certainty markers.
Obviously.
Clearly.
Undoubtedly.
Everyone knows.
There is no question.
The words can create the feeling of clarity while reducing actual comprehension.
Real clarity does not depend on telling people something is clear.
It shows the chain.
“We recommend option B because it gives us the only path that meets all three constraints: regulatory approval, twelve-month cash tolerance and customer continuity.”
No “clearly” required.
The logic creates clarity.
The technical expert who has forgotten what the first day felt like
This is where the curse of knowledge becomes painfully human.
A senior engineer explains a system.
A new executive asks a basic question.
The engineer thinks:
How can they not know that?
Because you have known it for twelve years.
The first day is gone from your memory.
The process that once required effort now feels natural.
Expertise erases the sensation of not knowing.
That is why audience design must become deliberate.
Do not rely on empathy alone.
Use structure.
Define the one term that changes the decision.
State the causal link.
Give the reversal condition.
Ask the listener to explain the consequence.
Experts do not need to become less expert.
They need a mechanism for making expertise cross the gap.
A worked example: board capital discussion
Weak:
“Obviously this should be financed with debt rather than equity given where we are in the cycle.”
Possible problems:
Which part of the cycle?
What assumption about rates?
What leverage constraint?
What happens to optionality?
Is the conclusion really obvious or simply the CFO’s strong preference?
Stronger:
“I recommend debt because the current structure keeps leverage below our board threshold even after the acquisition, while an equity raise at today’s valuation would be materially dilutive. If EBITDA falls below X, that recommendation changes.”
The room can challenge the logic.
That is better than demanding agreement through tone.
A worked example: strategy town hall
Weak:
“As everyone knows, AI is changing every part of our industry.”
The sentence says almost nothing.
Employees in finance, operations, sales and frontline service may have completely different pictures of what “changing every part” means.
Stronger:
“AI is changing three parts of our business already: how customers search, how we price service and how our teams handle routine analysis. It is not replacing every role, and we are not treating every use case as equally valuable.”
Now the leader has removed a sweeping obviousness claim and replaced it with usable scope.
A worked example: government briefing
Weak:
“Obviously the public will not accept another delay.”
That is a political assertion disguised as certainty.
Stronger:
“Our latest public research shows support falling after the second delay, and local leaders have made timetable credibility their central criticism. We should therefore treat a third delay as a major trust risk, not as an automatic impossibility.”
Evidence.
Boundary.
No fake consensus.
The five phrases worth auditing
Not banning.
Auditing.
Obviously.
Clearly.
As everyone knows.
We all agree.
It goes without saying.
For each one, ask:
Does the sentence still work without it?
If yes, remove it and see whether the argument becomes more honest.
If the word is doing necessary work, identify that work.
“Clearly” may be distinguishing an established fact from speculation.
“Obviously” may be conversational shorthand among genuine peers with shared context.
Fine.
But if the word is carrying evidence the sentence does not contain, you have found a weakness.
The meeting reset
If a senior team has developed this habit, use one rule for a month.
Nobody is allowed to defend a recommendation by calling it obvious.
Every strong conclusion must include one of three things:
Evidence.
Decision rule.
Reversal condition.
“We should exit because the unit has destroyed value for four years and no approved plan returns it above the hurdle rate.”
Evidence.
“We should wait because we do not approve investments until regulatory timing is inside twelve months.”
Decision rule.
“We should proceed, but if customer concentration exceeds 35 percent in diligence, we withdraw.”
Reversal condition.
Now disagreement has somewhere to go.
When the room really should know
Sometimes people are genuinely underprepared.
A board member has not read the paper.
An executive repeatedly asks for facts already provided.
A team refuses to learn essential language.
Do not solve chronic preparation failure by explaining everything forever.
Set standards.
But separate the performance conversation from the live information need.
In the meeting, if the decision requires shared understanding, create it.
Afterward, address why the person arrived without the required preparation.
Humiliating the question in real time may feel efficient.
It often protects neither the decision nor the standard.
Questions leaders ask
Is saying “obviously” bad communication?
Not inherently. The risk appears when the word tells other people what they should already understand or agree with, especially in a status-unequal room. Use it when it genuinely adds meaning, not as a substitute for evidence or explanation.
What is the curse of knowledge?
It is the tendency for people who possess information to struggle to recreate the perspective of people who do not possess it. Research shows that a person’s own knowledge can bias estimates of what others know or understand.
Why might employees avoid asking a basic question?
Questions can carry interpersonal image costs. People may fear looking incompetent, unprepared or difficult, particularly around senior authority. Team psychological safety research examines conditions that make learning behaviours such as asking for help and discussing errors safer.
What should a CEO say instead of “obviously”?
Often, state the reason. Replace “Obviously we cannot do X” with “We should not do X because Y, and we would reconsider if Z changed.” That makes the decision logic visible.
How do I verify understanding without patronising the room?
Ask for consequence rather than asking “Do you understand?” For example: “What does this change for your region?” or “Which assumption would make you challenge this recommendation?”
Should senior leaders explain basic concepts every time?
No. Set reasonable preparation standards and use shared references. The principle is to identify assumptions that are expensive if wrong and verify those, not to turn every executive meeting into a beginner lesson.
Key takeaways
- “Obviously” can turn a knowledge gap into a status test.
- Expertise can make it difficult to reconstruct what less-informed people know.
- Seniority increases the interpersonal cost of challenging assumptions in some rooms.
- Do not manufacture consensus with “we all know” or “everyone agrees.”
- Replace certainty markers with evidence, decision rules or reversal conditions where possible.
- Use the Obviousness Check: Assumption, Audience, Cost, Invitation, Verification.
- Real clarity shows why a conclusion follows. It does not merely announce that the conclusion is clear.
Executive Summary
A word such as “obviously” can look trivial. In an unequal room, it can change the social cost of asking a question.
The better-informed speaker may be experiencing the curse of knowledge: difficulty reconstructing what less-informed people know. The listener may be managing a separate problem: the interpersonal risk of exposing a gap in front of senior authority.
When those two forces meet, a leader can accidentally suppress the question that would have improved the decision.
Executive Authority’s Obviousness Check uses five steps: Assumption, Audience, Cost, Invitation, Verification.
Identify what the leader is treating as known. Consider who may not share that knowledge. Estimate the status cost of admitting the gap. Invite useful challenge. Verify understanding through application or consequence rather than a polite “yes.”
This does not require leaders to remove every certainty word from their vocabulary.
It requires them to stop using certainty words as evidence.
The most senior person in the room should make difficult questions easier to ask, not more embarrassing.
Conclusion
The next time you hear yourself say:
“Obviously.”
“Clearly.”
“As everyone knows.”
“We all agree.”
Do not automatically censor it.
Inspect it.
What are you assuming?
What are you trying to move past?
What evidence sits behind the confidence?
Who in the room may know less than you?
Who may disagree?
What does it cost them to say so?
Then make the logic visible.
A senior leader does not prove intelligence by making ignorance expensive.
They prove leadership by making important understanding possible.
For CEOs, boards and senior teams working across expertise, hierarchy and complex decisions, Executive Authority provides confidential communication counsel focused on making judgement clear without suppressing the questions the decision still needs.
Public sources
- Camerer C, Loewenstein G, Weber M. The curse of knowledge in economic settings: an experimental analysis. Journal of Political Economy. 1989;97(5):1232-1254. DOI: 10.1086/261651.
- “The curse of knowledge when predicting others’ knowledge.” Open-access experimental research, 2022/2023, PMCID: PMC9794110, PMID: 36575349.
- Edmondson AC. Psychological safety and learning behavior in work teams. Administrative Science Quarterly. 1999;44(2):350-383. DOI: 10.2307/2666999.
- Shatz I. The curse of knowledge when teaching statistics. Teaching Statistics. 2023. DOI: 10.1111/test.12320. This source is used for the narrow expert-to-novice communication implication, not as direct evidence about executive teams.
Published by Executive Authority
