4 exercises — polite disagreement, "Yes, and" technique, interrupting to clarify, and steering off-topic discussions back to the agenda.
0 / 15 completed
1 / 15
A colleague proposes using a NoSQL database for the new feature. You disagree — you believe a relational database is a better fit. Which response is most professional?
Option C demonstrates the professional disagreement framework:
Acknowledge first: "That's an interesting direction" — you've heard them; you're not dismissing the idea Name your specific concern: "data consistency" and "our data has a lot of relationships" — not just "I don't like it" Propose investigation, not conclusion: "Could we walk through the schema together?" — opens dialogue Stay intellectually humble: "I might be missing something about the access patterns" — acknowledges you could be wrong
Why the others fail: A — Blunt rejection without reasoning; shuts down the conversation B — "Not sure I agree" is fine but "have you considered?" can sound condescending D — Arguments from tradition ("we've always done X") are the weakest form of technical argument; they prevent improvement
The disagreement framework: 1. Acknowledge → 2. Name specific concern → 3. Provide evidence or logic → 4. Invite dialogue
"That's an interesting point. My concern would be [specific issue] because [specific reason]. What's your thinking on [the key question]?"
2 / 15
A colleague suggests using microservices for the new project. You want to build on their idea by adding a related point about service discovery. Which phrase works best?
Option A uses the "Yes, and" technique for building on suggestions:
"Yes, and" structure: • "Yes" — explicitly affirms the previous idea • "and" — adds to it at the same level (not replacing, correcting, or redirecting) • Adds value: names specific tools (Consul, Kubernetes DNS) — not just naming the problem
Why the others fail: B — "That's OK" is a weak acknowledgement; "but" signals that you're about to invalidate what they said, even if you're not C — "I already thought of that" is ego-driven; it makes it about you being smart rather than advancing the idea D — "People forget" implies your colleague hasn't thought it through; unnecessarily condescending
Building-on phrases for technical meetings: • "Yes, and another dimension of this is…" • "Building on that — if we go in that direction, we'd also want to consider…" • "That connects well to something I was thinking: what if we also…" • "I like where you're going. One additional piece would be…"
3 / 15
Two colleagues are in a technical debate and you need to ask a clarifying question. Which phrase politely interrupts without derailing the conversation?
Option C is the ideal polite interruption technique in technical discussions:
Apologise for interrupting: "Sorry to jump in briefly" — signals awareness that you're cutting in State the purpose: "I want to make sure I follow" — frames it as clarification, not challenge Ask a specific, high-value question: Offers two concrete interpretations and explains exactly why the distinction matters ("changes the UX implications significantly")
Why your interruption is justified here: A confusion about "eventual consistency" meaning seconds vs. minutes is architecturally significant. Letting the debate continue without clarifying this could mean 20 minutes of discussion about the wrong problem.
Polite interruption phrases for technical meetings: • "Sorry to cut in — quick clarifying question…" • "Sorry to jump in briefly — I want to make sure I follow before we go further…" • "One second — I think there might be a definition question here that affects the whole discussion…" • "Before we go further — can we align on what we mean by [term]?"
When to interrupt: When a key term is ambiguous, when two people are clearly talking about different things, or when you need a definition to follow the discussion meaningfully.
4 / 15
A technical discussion about caching has drifted into a general conversation about performance optimisation. You need to bring it back to the original topic. Which phrase steers it most effectively?
Option B demonstrates expert meeting steering with the park-and-refocus technique:
Doesn't dismiss the drift: "We have good material here on performance optimisation in general" — validates the theme, doesn't make people feel they wasted time Suggests a future home for it: "Worth a separate session" — the topic isn't dead, just moved Refocuses specifically: Names the exact decision that needs to be made (Redis vs. Memcached for session storage) Sets urgency: "before the end of the meeting" — reminds people of the time constraint driving the refocus
Why the others fail: A — "Please stop going off-topic" sounds scolding; makes people defensive C — Ending the meeting abandons the agenda item entirely D — "Stick to that" is directive without being warm; can create resentment
Park-and-refocus phrases: • "That's a great discussion — can we add it to our parking lot and come back? Right now we need to decide on X." • "I'd like to bring us back to the original question…" • "Worth a separate meeting on that — for now can we finish on [specific topic]?"
5 / 15
Sarah: 'I'm thinking we should use GraphQL for the new API. It'll be much more efficient than REST.'
Which response best conveys your concerns about potential added complexity while remaining collaborative?
The key here is to acknowledge Sarah's suggestion without immediately dismissing it. Option A raises a valid concern – overhead – framing your disagreement constructively. Options B and C are overly enthusiastic or dismissive, while option D promotes further discussion and testing, aligning with best practices for technical decision-making.
6 / 15
Reviewer Comment: 'This PR introduces a new dependency – lodash. Could you provide more context on why this was chosen and how it integrates with the existing codebase?'
Which of the following responses is most effective in fulfilling the reviewer's request?
The reviewer is seeking justification and integration details. Option 1 is insufficient; it lacks context. Option 2 directly addresses the request by stating a rationale and indicating further information is provided. Options 3 and 4 demonstrate poor communication and fail to satisfy the reviewer's query.
7 / 15
Sarah: 'I'm thinking we should use GraphQL for the new API. It'll be much more efficient than REST.'
Which response best conveys your concerns about potential added complexity while remaining collaborative?
The key here is to acknowledge Sarah's suggestion without immediately dismissing it. Option A raises a valid concern – overhead – framing your disagreement constructively. Options B and C are overly enthusiastic or dismissive, while option D promotes further discussion and testing, aligning with best practices for technical decision-making.
8 / 15
Reviewer Comment: 'This PR introduces a new dependency – lodash. Could you provide more context on why this was chosen and how it integrates with the existing codebase?'
Which of the following responses is most effective in fulfilling the reviewer's request?
The reviewer is seeking justification and integration details. Option 1 is insufficient; it lacks context. Option 2 directly addresses the request by stating a rationale and indicating further information is provided. Options 3 and 4 demonstrate poor communication and fail to satisfy the reviewer's query.
9 / 15
Sarah: 'I'm thinking we should use GraphQL for the new API. It'll be much more efficient than REST.'
Which response best conveys your concerns about potential added complexity while remaining collaborative?
The key here is to acknowledge Sarah's suggestion without immediately dismissing it. Option A raises a valid concern – overhead – framing your disagreement constructively. Options B and C are overly enthusiastic or dismissive, while option D promotes further discussion and testing, aligning with best practices for technical decision-making.
10 / 15
Reviewer Comment: 'This PR introduces a new dependency – lodash. Could you provide more context on why this was chosen and how it integrates with the existing codebase?'
Which of the following responses is most effective in fulfilling the reviewer's request?
The reviewer is seeking justification and integration details. Option 1 is insufficient; it lacks context. Option 2 directly addresses the request by stating a rationale and indicating further information is provided. Options 3 and 4 demonstrate poor communication and fail to satisfy the reviewer's query.
11 / 15
Mark: 'We need to refactor this legacy module. It's a performance bottleneck.'
Which response best acknowledges Mark's concern while suggesting a more detailed investigation?
Option 1 is best because it demonstrates active listening and seeks concrete data. The other options either accept the statement without question (A), immediately challenge Mark's assessment (C), or deflect responsibility (D). Asking for metrics is crucial in technical discussions; simply stating something 'smells bad' isn't helpful.
12 / 15
Slack Message from Alex: 'Just deployed the new feature. Let me know if you spot any issues!'
Which response is most appropriate for a junior developer seeking clarification on a potential bug?
Option 1 is correct because it politely asks for more specifics. The term 'issue' can be vague, so seeking clarification about what constitutes a problem is essential for effective collaboration. The other options are either overly casual (A), demand too much information without context (C) or avoid responsibility (D).
13 / 15
During a standup meeting, David says: 'I'm working on optimizing the database query for the user profile page.'
Which response is most effective in prompting David to provide more detail about his progress?
Option 1 is best because it directly asks for measurable results. Optimization often lacks clear metrics, so requesting specific data helps gauge progress and identify potential roadblocks. The other options are either unhelpful (A), propose an unnecessary meeting (C) or focus on the task without seeking feedback (D).
14 / 15
Reviewer Comment: 'This feature uses a callback function. Could you explain the rationale behind using callbacks instead of promises or async/await?'
Which response best addresses the reviewer's question in a professional and informative way?
Option 2 is correct as it provides a straightforward explanation for the decision. While acknowledging the reviewer's concern, simply stating 'that's what the original developer did' offers context without defensiveness. The other options present subjective opinions or irrelevant justifications.
15 / 15
Emily: 'I'm implementing a new caching layer to improve API response times.'
Which response best expresses your desire for Emily to consider the potential impact on cache invalidation strategies?
Option 1 is correct because it prompts Emily to consider a critical aspect of caching – invalidation. Caching systems require careful management of stale data; asking about this strategy demonstrates a thorough understanding and proactive approach.
What will I practise in "Technical Discussions & Debates"?
This module focuses on Meetings & Collaboration — real workplace phrasing you'll use on the job. It contains 15 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 15 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Meetings & Collaboration exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around meetings & collaboration — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Meetings & Collaboration exercises?
See the Meetings & Collaboration hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.