The Situation
Your director proposes a plan you believe will fail. A major client demands something that would damage the project. Everyone in the meeting nods, but you can see a serious risk. Saying nothing is safe in the short term and costly later. At C2 you need a range of registers — from the gentlest question to a firm, on-the-record objection — and the judgment to choose between them.
The Directness Scale
| Level | When | Example |
|---|---|---|
| 1. Curious question | early, low stakes, high status gap | "Could you help me understand how we'd handle the Q4 peak with a smaller team?" |
| 2. Raising a consideration | you see a risk others may have missed | "One thing I'd want us to think through is the impact on the Montreal contract." |
| 3. Offering an alternative | you have a better option | "Would it be worth considering a phased approach instead?" |
| 4. Clear disagreement | moderate/high stakes | "I have to be honest — I don't think this timeline is realistic, and here's why." |
| 5. Formal objection | high stakes, ethical or legal risk | "I'd like it on record that I have serious concerns about this." |
Start low and move up only as far as the stakes require.
Strategic Questions
Questions let senior people discover the problem themselves — they keep face, and you keep influence.
- "What would need to be true for this to work?"
- "How would we know early if it isn't working?"
- "What's our fallback if the supplier can't deliver?"
- "How do you see this playing out with the union?"
- "Which of these risks worries you most?"
Reframing
Put your disagreement in terms of shared goals:
- "We both want this launch to land well. My concern is that rushing it puts exactly that at risk."
- "If the goal is retention, I'm not sure a pay freeze gets us there."
- "I'm fully behind the objective. It's the route I'm less sure about."
Firm, Not Hostile
When you need to be clear:
- "I'm going to push back on that, respectfully."
- "I don't think I can support this as it stands."
- "I want to be straight with you, because I think you'd want to know."
- "I'd be doing you a disservice if I didn't raise this."
- "We may have to agree to disagree on this, but I wanted my view heard."
Notice the meta-comments (I want to be straight with you) — they signal that directness is coming, which softens its impact.
After the Decision: Commit or Escalate
If the decision goes against you:
- Disagree and commit: "I've made my case, and I understand the decision. I'll give it my full support."
- Condition your support: "I'll support it — can we agree to review it at the end of Q1 against these three measures?"
- Escalate (rarely, and transparently): "I think this needs a decision above our level. Would you be comfortable if we took it to the steering committee together?"
Never escalate behind someone's back — in most workplace cultures, that destroys trust.
Dialogue 1: Challenging a Director's Timeline
Director: So we'll launch in all five regions on March 1st. Irina: That's an ambitious date, and I can see why — it lines up with the trade show. Could you help me understand how we'd handle training in the Asian offices? They won't have the translated materials until mid-February. Director: They'll manage. We can train them remotely. Irina: Possibly. My concern is that if the first customers there have a poor experience, it'll hurt exactly the reputation we're trying to build at the trade show. Would it be worth launching in the three ready regions on March 1st and the other two in April? Director: I'd rather not split it. Irina: I understand. I'll support whatever we decide — I'd just like us to agree now on what we'd do if the Asian launch runs into problems in the first two weeks. Director: Fair. Put together a contingency plan and we'll look at it Friday.
Dialogue 2: Pushing Back on a Client
Client: We need you to add the reporting module to this phase, without moving the deadline. Marek: I appreciate how important that module is for you. I want to be straight with you, because I think you'd want to know: if we add it without changing the deadline, the testing phase shrinks to a week, and that's where most of the risk sits. Client: Your team is big enough, surely? Marek: Adding people at this stage would actually slow things down. What I can offer is two options: we keep the deadline and deliver reporting four weeks later, or we add it now and move the go-live by three weeks. Which matters more to you — the date or having everything together? Client: The date. Let's do reporting after. Marek: That works. I'll send the revised plan today so it's documented.
Cultural Calibration
Directness norms vary. In many Dutch, German, Israeli or Russian-speaking workplaces, level 4 is normal. In many Canadian, British, Japanese or Thai workplaces, level 4 can sound confrontational, and levels 1–3 do most of the work. In international teams, explicit meta-comments ("I'm going to be quite direct here") help everyone read your intention correctly.
Common Mistakes
- Disagreeing with the person, not the plan: "You always rush things."
- Hinting so softly that the message is missed — then being blamed later for not raising it.
- Repeating the same objection after the decision is made, instead of committing or escalating.
- Using sarcasm or irony — in a second language and across cultures, it's easily misread.
Your Turn: Practise Speaking
- Express the same disagreement at levels 1, 3 and 4 of the directness scale: "Moving the office to the suburbs will make us lose staff."
- Write three strategic questions for a plan you think is risky.
- Practise a "disagree and commit" statement that also sets review criteria.