A manager says, "Let's use the full 40-slide deck for tomorrow's client meeting."
One colleague replies, "I can see why we'd want them to have all the detail." Another asks, "How much time will that leave for questions?" A third says, "We could send the full deck afterward." And the manager concludes, "Great. Sounds like we're aligned."
But are they? Nobody said "I disagree." Nobody said "That's a bad idea." Nobody openly rejected the 40-slide presentation, but nobody actually agreed to present all 40 slides, either. One person qualified the idea. Another raised a problem. Another proposed a different plan. The disagreement was not necessarily absent. It was expressed in a form the meeting failed to recognize.
This article, a companion to the Reclaiming Rhetoric video, looks at how people disagree at work without saying "I disagree," why politeness is so often mistaken for approval, what the research on workplace voice actually shows, and how both speakers and leaders can make disagreement easier to see.

Foundations Series · Volume 3
How to Build a Better Argument
A practical visual guide to claims, evidence, structure, and objections.
Why workplace disagreement goes indirect
Workplace communication creates an unusual rhetorical problem, because people are rarely managing only the idea in front of them. They are also managing a relationship that continues after the conversation ends. You may need to question a colleague's judgment and still work with them tomorrow. You may need to challenge a manager without making the conversation about the manager's authority. You may want a proposal to change without humiliating the person who proposed it.
Communication researchers have long pointed out that indirect speech does more than transmit information. It also helps people manage the interpersonal consequences of what they are saying. Penelope Brown and Stephen Levinson's influential theory of politeness describes how speakers soften acts that threaten another person's "face," their public self-image (Brown & Levinson, 1987). Steven Pinker and colleagues have argued that indirect speech lets people negotiate a relationship while keeping the content deniable (Pinker, Nowak & Lee, 2008). In workplace disagreement, the employee may be trying to change the plan without turning the conversation into a contest over the person who proposed it.

Four forms of disagreement that never say "no"
1. The qualification: agree with the goal, question the means
The first response was, "I can see why we'd want them to have all the detail." On its own, that sounds supportive. But suppose the speaker continues: "I'm not sure it all belongs in the presentation." Now the structure becomes clearer. The employee accepts the purpose (give the client complete information) while questioning the proposed means (present all 40 slides). Agreement with the objective is not agreement with the plan.
2. The question that tests the proposal
Then someone asks, "How much time will that leave for questions?" Grammatically, that is a request for information. Rhetorically, in this situation, it may also test the proposal. If a 30-minute meeting includes a 40-slide deck, and the client expects time for discussion, the question introduces a problem without announcing "Your idea is wrong."
A question is not automatically evasive, passive-aggressive, or loaded. Sometimes it opens a relevant issue that the proposal has not accounted for. But it is worth being honest about what the research says here, which is covered below: phrasing a concern as a question is not, on its own, a reliable way to get it taken seriously.
3. The constraint
The disagreement can also move into a constraint. Instead of saying "This presentation is too long," someone says, "We have 30 minutes, and the client asked to spend the last 10 discussing implementation." Now the apparent conflict is not between two personalities. It is between the proposal and the available time. That can make the disagreement easier to evaluate, because the team has something concrete to test.
Constraints are not magically neutral. "The schedule won't allow it" can itself be misleading if the schedule is flexible. The point is that the speaker has shifted the disagreement from a judgment about the person toward a claim about what circumstances permit, which is exactly the kind of claim Lloyd Bitzer had in mind when he described the constraints of a rhetorical situation.
4. The alternative
Finally: "What about five key slides, with the full deck sent afterward?" This does something different again. The speaker is no longer merely resisting the existing proposal; they are putting another plan into circulation. Instead of forcing the manager to defend 40 slides or abandon the idea entirely, the team can now compare two approaches.
Research on real workplace talk supports the general picture. In a study of problem-solving meetings in multinational companies, Jo Angouri found that disagreement was a normal, expected part of getting work done, and that it was often expressed and negotiated gradually rather than announced as outright opposition (Angouri, 2012). Disagreement can unfold through shifts, alternatives, and questions without ever arriving as a clean sentence beginning with no.

The trap: building a secret dictionary of office language
Once you notice indirect disagreement, it becomes tempting to build a secret dictionary. Interesting idea secretly means terrible idea. Let's revisit that secretly means never. I hear what you're saying secretly means I am ignoring everything you just said.
That kind of decoding feels clever, but it replaces analysis with suspicion. The same phrase can do very different things in different conversations. "How much time will that leave?" could be an objection. It could also be a genuine request for information from someone who supports the proposal. "We could send the full deck afterward" could be a counterproposal or simply an additional suggestion. There is no universal translation guide, because workplace cultures, relationships, power structures, and conversational norms differ.
So do not ask, What does this phrase secretly mean everywhere? Ask:
- What was proposed?
- What does this response make problematic?
- What would have to change if the response were taken seriously?
- What happens when someone asks the speaker to clarify?
Indirect is not the same as polite
There is another important correction. Indirect does not automatically mean polite, and direct does not automatically mean rude. Compare:
- "That's ridiculous. We're not doing 40 slides."
- "I recommend a shorter presentation. The full deck would leave too little time for the client's questions."
- "I wonder whether there might perhaps be another way of thinking about the presentation."
The first two both directly oppose the proposal. Only the first attacks it contemptuously. The third may sound extremely courteous, but it leaves the actual recommendation almost invisible.
What the research on employee voice shows
Organizational researchers call speaking up with suggestions or concerns employee voice, and they have tested this distinction directly. In a 2019 paper, Chak Fu Lam, Cynthia Lee, and Yang Sui treated directness (explicit suggestions about what should change) and politeness as separate dimensions, and compared direct voice with indirect voice expressed through hints and reflective questions. Across an experiment and two field studies, direct, change-oriented suggestions were associated with more frequent managerial endorsement when the employee was seen as credible (in U.S. samples) or communicated politely (in a Chinese sample) (Lam, Lee & Sui, 2019).
The lesson is not "be blunt." It is that you can soften the interpersonal threat without softening the substance into invisibility. Politeness and clarity are not trade-offs; the most effective version of the 40-slide objection is likely to be both.
It also qualifies a common piece of advice. Turning every objection into a question can feel safer, and sometimes a question is exactly the right move, but the evidence does not show that questions and hints are generally more persuasive to managers than a clear, respectful recommendation. Often the opposite.
Disagreement in email, chat, and video calls
Indirect disagreement gets even harder to read when the conversation moves out of the room. In a chat thread, a colleague's "ok" may be agreement, resignation, or a sign they have stopped engaging. On a video call, the hesitation, glance, or pause that would have signaled doubt is easy to miss, and a muted participant can look like a consenting one. In email, a carefully hedged reply can read as warmer or colder than intended.
Two habits help. When you disagree in writing, put the recommendation in the first sentence rather than the last paragraph. When you are leading a remote discussion, ask for objections explicitly and give people a second channel (a reply, a comment, a one-to-one message) to raise them. Silence on a call is not a decision.
Rhetorical skill does not erase power
None of this guarantees safety. A perfectly clear, respectful objection can still be punished by a manager who does not tolerate disagreement. That is one reason the burden cannot fall entirely on employees to phrase every concern perfectly. Leaders also shape whether disagreement can become visible.
Amy Edmondson's research on team psychological safety, a shared belief that the team is safe for interpersonal risk-taking, found that teams with higher psychological safety engaged in more learning behaviors, such as asking for help, raising problems, and discussing errors (Edmondson, 1999). Whether people say "I disagree" out loud depends heavily on what has happened to the last person who did.

Replaying the meeting: how a leader can make disagreement recoverable
So replay the original meeting. The manager hears: "I can see why we'd want them to have all the detail." "How much time will that leave for questions?" "We could send the full deck afterward."
But instead of saying "Great, sounds like we're aligned," the manager says: "I hear agreement on giving the client the detail, but concerns about presenting all 40 slides. What would you recommend changing?"
Now someone can answer: "I recommend five key slides and the complete deck afterward. That gives us time to discuss implementation."
That is not a magic workplace script, but notice what has become recoverable: the person's position, the reason for it, and the change they recommend. The team no longer has to infer whether a polite question was actually an objection. And the manager has not forced every disagreement into a confrontation before taking it seriously. A team should not need perfect mind-reading to discover that its members recommend different things.
A practical checklist for both sides
If you are disagreeing:
- Name what you agree with, then name what you would change.
- Make the recommendation explicit: what, specifically, should happen instead?
- Give the reason in terms of shared goals or real constraints, not the other person's judgment.
- Keep the tone respectful; keep the substance visible.
If you are leading:
- Don't treat the absence of "no" as a "yes." Summarize what you heard, including the hesitations.
- Ask directly what people would change, and make it easy to answer.
- Respond to the first disagreement well; everyone is watching what happens to it.
- Close by confirming the actual decision, not just the mood.
These habits connect to the broader skill of arguing like a classical rhetorician: understanding your audience, choosing the strongest available means, and making your position clear enough to be judged.
Did we actually resolve it?
Nobody has to say "I disagree" for disagreement to be present. It can appear as a qualification: I agree with the goal, but not this approach. It can appear as a question that exposes a problem. It can appear as a constraint the proposal has not accounted for. It can appear as an alternative that quietly replaces part of the original plan.
The goal is not to become suspicious of every polite sentence. It is to notice where cooperation and disagreement coexist. Sometimes a colleague is trying to preserve the relationship and change the proposal at exactly the same time. So after the next meeting, do not ask only, Did anyone say no? Ask something more useful: What did people try to change, and did we actually resolve it?
To keep going, browse all articles, explore structured lessons on the Courses page, or see the illustrated guides on the Guides page.

Foundations Series · Volume 3
How to Build a Better Argument
A practical visual guide to claims, evidence, structure, and objections. Opinion in. Case out.
Move from an initial opinion to a clear, well-supported case that can withstand fair scrutiny. Gather evidence that tests the claim, then treat serious objections fairly.
Sources and further reading
- Lam, C. F., Lee, C., & Sui, Y. (2019). Say it as it is: Consequences of voice directness, voice politeness, and voicer credibility on voice endorsement. Journal of Applied Psychology, 104(5), 642–658
- Angouri, J. (2012). Managing disagreement in problem solving meeting talk. Journal of Pragmatics, 44(12)
- Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383
- Brown, P., & Levinson, S. C. (1987). Politeness: Some Universals in Language Usage. Cambridge University Press
- Pinker, S., Nowak, M. A., & Lee, J. J. (2008). The logic of indirect speech. PNAS, 105(3), 833–838
- Reclaiming Rhetoric, Bitzer's Rhetorical Situation: Exigence, Audience, Constraints
Frequently Asked Questions
How do people disagree at work without saying "I disagree"?
Usually through qualifications (agreeing with the goal but not the plan), questions that expose a problem, constraints such as time or budget, and alternative proposals.
Why do people disagree indirectly at work?
Because they are managing an ongoing relationship as well as an idea. Indirectness helps protect the other person's face and their own standing.
Is it better to disagree directly or indirectly with a manager?
Research by Lam, Lee, and Sui (2019) found direct, explicit suggestions were endorsed more often when the employee was credible or polite. Clear and respectful tends to beat vague.
Is indirect disagreement the same as being polite?
No. A direct recommendation can be fully respectful, and a very indirect remark can hide the actual point. Directness and politeness are separate choices.
How can a manager tell if the team really agrees?
Don't treat silence or polite questions as agreement. Summarize the hesitations you heard and ask what people would change.
What is psychological safety?
Amy Edmondson's term for a shared belief that a team is safe for interpersonal risk-taking, such as raising problems or admitting mistakes.
Do phrases like "interesting idea" always mean disagreement?
No. The same phrase can be sincere or critical depending on the context. Ask what the remark is doing in that conversation rather than decoding it.
Reclaiming Rhetoric is independent and reader-supported.
If this helped, you can help keep it free.







