How to disagree with your manager constructively

Your manager proposes a decision and you spot a problem. You could stay silent and resent it later, or open with “that will not work” and end up arguing about tone. Prepare something the other person can examine: a fact, a possible risk and another way forward.

Separate a fact from a guess

“You do not care about users” assigns a motive. “On a small screen, the keyboard covers the button” describes an observation. If you have not checked the issue, name the uncertainty: “There is a risk that… Let us check.” A firm voice does not replace evidence.

Choose the setting. A question affecting the team’s current work can be raised briefly in the meeting. If it needs detail or becomes personal, suggest a separate discussion. No wording guarantees agreement: the decision may remain unchanged.

Dialogue 1: questioning a decision

These conversations are fictional practice examples. Do not borrow their facts for your own situation without checking.

Manager: “Remove the phone field; it is unnecessary.” Lena: “Yesterday support dealt with three requests where email got no reply. A phone number could help, but a required field makes the form harder to fill in. I suggest making it optional and explaining why we ask. Could we consider that?” Manager: “I do not want another field for three cases.” Lena: “Understood. I will first ask support how often this happens and bring the data back before changing the form.”

Lena offered an option without presenting three cases as a general pattern. After the objection, she clarified the next step. Disagreeing does not mean defending your first idea at any cost.

Dialogue 2: a risk was overlooked

Manager: “Launch the form today; it works on desktop.” Timur: “We tested desktop. We have not tested phones, so we do not know whether a request can be sent with the keyboard open. I suggest an hour to check two devices before publishing.” Manager: “We have no time for full testing.” Timur: “I am not proposing a full test now. I will check submission on two phones and report by 3 pm. If there is a bug, we can decide what that means for launch. Would that work?”

Timur narrowed the suggestion to a checkable action. He did not promise to find every bug in an hour or describe an untested risk as a failure that had already happened. Keep “we know”, “we suspect” and “we will check” separate in your own reply.

What to do after an objection

First clarify the constraint: “Which matters most here: the date, the scope or this particular approach?” Then offer an option within it. If the decision is made, briefly restate your concern and ask about the next step: “I have raised the risk. Who will check the result after launch?” Do not use the question as a disguised accusation.

State your disagreement in 30 seconds

Choose a small work decision you are ready to discuss. Write one verified fact and one workable alternative. In 30 seconds, say the fact, consequence, option and question. Then imagine the objection “We do not have time for that now” and answer in one or two sentences. Repeat the opening more briefly, keeping the fact.

• Can the fact be checked, and is the risk clearly a possibility?
• Does the option fit the team’s time and resources?
• Have you removed “you always” and guesses about motives?
• Does the question help reach a decision rather than prolong the argument?

When the disagreement comes down to date and scope, use the deadline article below. For intrusive questions or pressure on personal boundaries, see the difficult questions article. This guide addresses a work decision you disagree with.

Open the Persuasion demo and try its general task about shortening a meeting. It does not record audio or provide AI feedback. To continue, open Ritora in Telegram: in Practice, choose persuasion training, the situations section. Choose a suitable situation from the available list. Check access and remaining feedback attempts before recording. The app interface is in Russian.