
Describe the specific thing you saw, propose an alternative you could carry out yourself, say what it costs, and leave the decision with the person who owns the plan. Keep the disagreement about the plan, not about the person who made it.
Two lines you could say, and one you keep to yourself
In a Thursday meeting, your manager, Renata, announces that the weekly team meeting will drop from sixty minutes to thirty, and that the open-bugs review will be cut to make room. You are a junior developer, and you have noticed that two of the last three customer-facing bugs were caught in that review because someone else recognized them.
You have three options in the next ten seconds. You can say nothing. You can say “that’s going to backfire”, which is a prediction about Renata’s judgment. Or you can say what you saw and what you could do about it. In our judgment, only the third gives her something she can use without losing face in front of the team.
Why speaking up can feel risky, and sometimes is
Detert and Edmondson studied what they call implicit voice theories: taken-for-granted beliefs about when speaking up at work is risky or inappropriate. The authors, in the paper’s abstract, report that such implicit voice theories are widely held and help explain workplace silence. In our inference, some of the hesitation you feel may be a rule you absorbed, not a fact about Renata.
But the risk is not imaginary. Burris reported, in the Academy of Management Journal, that managers view employees who engage in more challenging forms of voice as worse performers. That is one paper, from particular samples, and we read only its abstract. It is a reason to take care over how you disagree, not a prediction about Renata.
It also helps to know what kind of disagreement you are having. A 2003 meta-analysis of team conflict by De Dreu and Weingart found task conflict negatively related to team performance and satisfaction. A 2012 meta-analysis of 116 studies (De Wit, Greer and Jehn) did not find a strong negative link between task conflict and group performance. Both found task conflict did less harm when it was weakly tied to conflict about the people. The inference for you, which the studies do not test, is to keep the argument about the plan.
Four parts that make the objection usable
These steps are practical guidance drawn from the situation, not a protocol that has been tested. They are meant to avoid what the studies above point to as a risk, reading as an attack on the person, though that fit is our reading, not a test.
- What you saw: a specific, checkable event, with the date or the example. “Two of the last three customer bugs were caught in that review” can be verified. “Meetings matter” cannot.
- An alternative you can carry out: something you would do or run, not something you want Renata to do.
- The cost, stated by you: what your alternative gives up or adds.
- The handoff: “it’s your call” is only true if you are willing to follow either answer.
A version that is hard to answer
This reply may be accurate, and it gives Renata only two ways to respond: defend the plan or give in. It offers no evidence she can check and no alternative, and “people” in the first line invites her to ask who. The tone also reads as a challenge to her competence; whether that is the “challenging” voice Burris studied is our inference.
“Honestly I think cutting the bug review is a mistake. People rely on it, and we’ll regret dropping it.”
A version that gives her something to decide
The stronger version works in a meeting or a message. It keeps the concern to one specific event, offers to do the work of the alternative, and says out loud what the alternative costs, so Renata does not have to find the weakness herself.
In a meeting, you can say a shorter form out loud and offer the details afterward. In a message, you can lay out the three parts as written below. Either way, end by saying that you will follow her decision.
“One thing before we change the format. Two of the last three customer bugs were caught in the bug review, because Sam recognized them from an earlier ticket. Could we keep the review but move it to a shared document that people comment on during the week, with five minutes in the meeting for anything unresolved? I’d set up the document and keep it tidy. The cost is that quick questions would wait for comments instead of being answered live. It’s your decision, and I’m happy to try whatever you choose.”
If she says no, or does not answer
She may say the plan stands. That does not mean your concern was wrong or that you spoke badly. Managers weigh things you cannot see, such as complaints about meeting length, and a no today does not close the question if the bugs keep arriving.
If she is curt, take the answer and offer a way to check it later. If she does not reply to a message, a short follow-up a few days on is reasonable, and it should add something rather than repeat the argument.
If she dismisses you in front of colleagues, you can leave the point there in the meeting and raise it privately afterward.
“Understood, we’ll go with thirty minutes. Would it help if I kept a note of any bugs that would have come up in the review, and we looked at the list in a month?”
What the evidence does not show
The studies cited are a paper on how managers rate challenging voice, a paper on beliefs about speaking up, and two meta-analyses of team conflict. None of them tests the wording above, and none shows that bringing a solution protects the person who speaks. Renata, the bugs and the meeting are invented for this example. Leetsoul has not been shown to cause better workplace outcomes.
Some managers penalize any challenge however carefully it is made. If you are being bullied, discriminated against, or asked to do something unsafe or unlawful, use a formal route such as HR, a union or a regulator, instead of trying to word a better objection.
The linked practice lets you rehearse this kind of reply in a different scene, with different facts.
Practice disagreeing with a plan and offering a fix
Try your response to a fictional conversation, then read the guidance and decide what you would change.
Open the practiceThree starter practices are free. Soulful opens the full library.Sources and limits
Renata, the meeting change and the bug review are fictional, written for this article. The sources show that managers can judge challenging voice harshly and that task conflict showed negative links with team performance in one meta-analysis and weaker or mixed links in a later one; they do not show that this wording protects anyone.
- Burris: The Risks and Rewards of Speaking Up (Academy of Management Journal, 2012)
Abstract only (one field study and two experimental studies): managers view employees who engage in more challenging forms of voice as worse performers and endorse their ideas less. Effect sizes and samples are not used.
- Detert and Edmondson: Implicit Voice Theories: Taken-for-Granted Rules of Self-Censorship at Work (Academy of Management Journal, 2011)
Abstract only: taken-for-granted beliefs about when speaking up is risky or inappropriate are widely held and significantly augment explanation of workplace silence.
- De Dreu and Weingart: Task Versus Relationship Conflict, Team Performance, and Team Member Satisfaction
Abstract of a 2003 meta-analysis: task conflict was strongly and negatively correlated with team performance and satisfaction, and less so when task and relationship conflict were weakly correlated. It covers teams, not one employee challenging a manager, and a later meta-analysis (below) qualifies it.
- De Wit, Greer and Jehn (2012): The paradox of intragroup conflict: A meta-analysis
Abstract only (Journal of Applied Psychology, 116 studies, 8,880 groups). Unlike the 2003 meta-analysis, it did not find a strong negative association between task conflict and group performance; task conflict and performance were more positively related where task and relationship conflict were weakly associated. About groups, not individuals.
Published by Leetsoul. Sources checked . Examples are fictional. Read our evidence approach.