You will be able to raise a disagreement in a meeting in a way that keeps the discussion on the work.
Your director has just presented the plan for the new booking system. Go live on 1 March, all outlets at once, and the vendor will train staff the week before. You've worked with this vendor. Last time they were three weeks late. Everyone around the table is nodding, and you can feel the moment passing.
Saying nothing feels safe, and the plan will probably go wrong in a way you predicted. Saying "That won't work" feels honest, and it will probably make the director defensive and the room uncomfortable. There's a third way, and it is the one most experienced people use. You disagree with the plan in a way that keeps everyone, including the director, focused on the work.
The first rule is about what you point at. "You've underestimated the vendor" points at a person. "The timeline assumes the vendor delivers on time, and last year they didn't" points at the plan. The content is identical. The second version gives the director nothing to defend except a date.
Talk about three things: the plan, the data and the risk. Avoid words that describe the person's judgement, effort or motives, such as "you didn't think about", "obviously" or "that's unrealistic". In a meeting, people hear criticism of their idea as criticism of them unless you work to separate the two. Your wording does most of that work.
A disagreement lands more softly when it starts from common ground. You almost always agree with something: the goal, the reason for the deadline, most of the plan. Say that first, and mean it. Then name the specific concern. Then suggest something.
Here's the 1 March plan, two ways.
Before: "I don't think March is realistic. The vendor is always late."
After: "I agree we need it live before the year-end peak. My concern is the training week. Last year this vendor delivered three weeks late, and our staff would be using a system nobody had trained them on. Could we go live at two outlets on 1 March and the rest a month later?"
The second version is longer, but every part is doing a job. The agreement shows you're on the same side. "My concern is" makes the disagreement narrow and specific. The evidence is a fact, not an opinion about the vendor's character. And the alternative turns a complaint into a choice the director can actually make. A concern with no alternative leaves the person who owns the plan with a problem and nowhere to go. A concern with one gives them a decision.
Keep your voice level and your sentence short. If the director pushes back, you don't have to win the argument there and then. "Okay, could we at least check the vendor's dates before we confirm?" keeps the concern alive without turning the meeting into a contest.
Sometimes a direct "my concern is" feels like too much, especially if you're the most junior person in the room. A question can do the same job with less exposure.
"What happens if the vendor is late with the training?"
That question raises the risk without saying anyone was wrong. It invites the group to think it through, and it often leads someone more senior to say what you were thinking. Other useful versions: "How confident are we in the vendor's dates?" and "What would we do if only half the outlets were ready?"
A question works best when it's genuine. If you already know the answer and ask anyway, people can tell, and a leading question can feel more pointed than a plain statement. Ask what you'd actually want to know.
In more hierarchical teams, which includes many Singapore workplaces, challenging a director in front of their own team can cost them face. Even a polite, well-evidenced disagreement can land badly if it happens in public. In those settings, raising your concern privately before the meeting often works better than raising it during.
A short message the afternoon before can do it:
"Hi Raymond, before tomorrow's go-live discussion, can I flag one thing? Last year this vendor delivered training three weeks late. I'm worried about a 1 March go-live for all outlets at once. Would a phased start, two outlets first, be worth considering? Happy to talk it through for five minutes if useful."
This gives the director time to think, the chance to adjust the plan as their own idea, and no audience to perform in front of. Many will bring your point into the meeting themselves. Some will thank you for it in front of the team.
Private is not always better. If the decision is being made in the meeting and you had no chance to speak beforehand, say it there, using the agree, concern, alternative shape or a question. Lesson 7.3, Give feedback to your peers and your manager, covers the one-to-one version of this conversation in more depth.
Think of a decision at work right now where you see a risk others haven't raised. It doesn't need to be large. Notice who owns the plan, how senior they are, and whether your team usually argues openly or behind the scenes. Those three things tell you whether the meeting or a quiet message beforehand is the better first move.
Write how you would raise a real disagreement you have at work, once as a question in the meeting and once as a private message beforehand.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).