4 exercises — opening with goal and ground rules, handling dominant speakers, closing with confirmed action items, and managing silence productively.
0 / 19 completed
1 / 19
You've been asked to facilitate a technical decision meeting. There are 8 people attending and you need to open it professionally. Which opening covers all critical elements?
Option C covers the five essential opening elements for a facilitated meeting:
1. Single clear goal: "one goal: decide between Option A and Option B for our API gateway" — not "discuss" or "explore" 2. Scope boundary: "not here to explore alternatives — that session was last week" — prevents topic drift before it starts 3. Time constraint: "decision by 2:30" — creates urgency and focus 4. Ground rules: focused on the decision criteria; no side conversations; every perspective heard 5. First action: "start with a quick summary" — meeting begins immediately, no idle time
Why the others fail: A — No goal, no ground rules, no structure; the meeting will immediately drift B — Introductions are for people who don't know each other; wasting 5 minutes introducing a team that works together daily is agenda time theft D — Jumping to slides without framing means nobody knows what decision they need to make by the end
Meeting opening formula: "Today's goal is [specific decision/output]. We're not covering [out of scope]. We need to [goal] by [time]. Ground rules: [2-3 rules]. Let's start with [first agenda item]."
2 / 19
One attendee has been speaking for 10 minutes without pause. Two other attendees look disengaged. How do you interject as facilitator?
Option C demonstrates the graceful interruption technique for dominant speakers:
Acknowledges the contribution: "There's a lot of useful context there" — not dismissive Creates a bridge: "I want to make sure we capture it and also hear from others" — two goals, both valid Summarises the key point: "[summarised point]" — shows you were listening; the speaker can't feel ignored Directly invites quiet participants by name: "Maya and Chen" — not the passive "does anyone want to speak?" Promises to return: "we'll come back to any remaining context" — the dominant speaker doesn't feel cut off
Why the others fail: A — "That's enough" is dismissive and creates resentment B — "Very interesting" + open invitation rarely works; dominant speakers will continue and silent ones stay silent D — Making time the reason feels like blame; "I want to hear from Maya and Chen" is more graceful
When you must interject: • After 3-4 minutes of unbroken monologue • When you can name a specific point to summarise and redirect from • When you can name the next 2 people you want to hear from
3 / 19
The meeting is ending. Three action items have been discussed but not clearly assigned. Which closing is most effective as a facilitator?
Option C demonstrates the critical meeting close protocol:
Names every action item explicitly: "three action items we agreed" and lists each by number — no ambiguity about what was decided Assigns an owner in real time: "who's owning that, by when?" — forces the room to name a person and a date before leaving Confirms the delivery format: "Confluence page or Slack summary?" — small but important; reduces downstream confusion Commits to a follow-up note: "I'll send a summary note within the hour" — the facilitator takes ownership of the next step
Why the others fail: A — "Good discussion" closes the meeting without accountability; action items dissolve in people's memories B — "Someone" is the word that means nobody; action items without named owners never get done D — "Circle back next week" with no specifics is scheduling theatre
Meeting close checklist: ✓ List every action item verbally ✓ Named owner for each (not "the team") ✓ Concrete deadline for each ✓ Confirm how results will be communicated ✓ Commit to sending a written summary
4 / 19
You asked the group a question and there is 30 seconds of complete silence. Nobody is responding. How do you handle this as the facilitator?
Option C handles meeting silence with the warm direct invite technique:
Normalises silence: "It's a complex question" — removes the social pressure that makes silence worse Extends tolerance: "give it a few more seconds" — a good facilitator can hold silence longer than the group wants to Lowers the bar: "even if it's uncertain" — signals that a partial or exploratory answer is welcome; silence often happens because people feel their answer isn't complete Directs to a specific person with context: "Ana, you've worked closely on [relevant area]" — gives a reason why you're choosing her, which makes the invite feel deliberate rather than arbitrary
Why silence happens in meetings: • The question is too broad ("any thoughts?") — narrow it • People feel their answer isn't good enough — lower the bar ("even an initial instinct is useful") • People are genuinely thinking — hold the silence longer than feels comfortable • Nobody wants to go first — a named direct invite resolves this
Silence management tools: • "I'll give it another 10 seconds." [hold the pause] • "Even a partial answer or an instinct would be useful." • "Let's do a quick round — 20 seconds each, [Name] start us off." • "If you're unsure, start with the word 'maybe'.."
5 / 19
Sarah, the team lead, sends a Slack message to the development team regarding an urgent bug fix. Which phrasing best demonstrates effective facilitation during this communication?
'Everyone needs to address this immediately!'
The best response directly states the issue and requests action without being overly demanding. Options B and D are too directive, while option C doesn't clearly articulate the need for a discussion. Facilitation is about guiding the conversation and assigning tasks, not just issuing commands.
6 / 19
David, during a code review, points out a potential performance bottleneck in a new API endpoint. The developer responds defensively, arguing the design is optimal. How should you, as facilitator, respond to de-escalate the situation?
'Let's just agree that this is the best approach.'
The core of facilitation is managing conflict and encouraging productive discussion. Simply agreeing with the developer shuts down further exploration. Option A prompts a deeper dive into performance concerns, while options B and C avoid addressing the issue, and option D introduces unnecessary complexity.
7 / 19
Maria is leading a stand-up meeting. A developer states, 'I'm blocked on getting access to the database.' The team moves on without addressing this blocker. As facilitator, what's your immediate action?
'That's fine; just keep working on your tasks.'
A facilitator's primary role is to ensure all issues are addressed. Ignoring a blocker prevents progress and demonstrates poor leadership. Option A directly addresses the problem, prompting a discussion about the root cause and potential solutions.
8 / 19
John is drafting a PR description for a significant refactoring of a core module. The description is highly technical and lacks context for reviewers. How should you advise him to improve it as facilitator?
'Just explain the code changes thoroughly.'
A good PR description needs to be understandable for a broader audience. Option A provides guidance on structuring the explanation effectively – focusing on *why* the changes were made and their impact is crucial for successful code review. The other options are either too brief or shift responsibility inappropriately.
9 / 19
Emily facilitates a meeting to discuss migrating to a new cloud provider. After an hour of debate, no consensus is reached. What's the most effective action for her as facilitator to conclude the meeting?
'Okay, let's just keep discussing until we find a solution.'
When a facilitator faces stalemate, recognizing the lack of progress and moving towards a concrete plan is essential. Option A directly addresses the issue by scheduling a follow-up to continue the discussion in a more structured manner.
10 / 19
Sarah, the team lead, sends a Slack message to the development team regarding an urgent bug fix. Which phrasing best demonstrates effective facilitation during this communication?
'Everyone needs to address this immediately!'
The best response directly states the issue and requests action without being overly demanding. Options B and D are too directive, while option C doesn't clearly articulate the need for a discussion. Facilitation is about guiding the conversation and assigning tasks, not just issuing commands.
11 / 19
David, during a code review, points out a potential performance bottleneck in a new API endpoint. The developer responds defensively, arguing the design is optimal. How should you, as facilitator, respond to de-escalate the situation?
'Let's just agree that this is the best approach.'
The core of facilitation is managing conflict and encouraging productive discussion. Simply agreeing with the developer shuts down further exploration. Option A prompts a deeper dive into performance concerns, while options B and C avoid addressing the issue, and option D introduces unnecessary complexity.
12 / 19
Maria is leading a stand-up meeting. A developer states, 'I'm blocked on getting access to the database.' The team moves on without addressing this blocker. As facilitator, what's your immediate action?
'That's fine; just keep working on your tasks.'
A facilitator's primary role is to ensure all issues are addressed. Ignoring a blocker prevents progress and demonstrates poor leadership. Option A directly addresses the problem, prompting a discussion about the root cause and potential solutions.
13 / 19
John is drafting a PR description for a significant refactoring of a core module. The description is highly technical and lacks context for reviewers. How should you advise him to improve it as facilitator?
'Just explain the code changes thoroughly.'
A good PR description needs to be understandable for a broader audience. Option A provides guidance on structuring the explanation effectively – focusing on *why* the changes were made and their impact is crucial for successful code review. The other options are either too brief or shift responsibility inappropriately.
14 / 19
Emily facilitates a meeting to discuss migrating to a new cloud provider. After an hour of debate, no consensus is reached. What's the most effective action for her as facilitator to conclude the meeting?
'Okay, let's just keep discussing until we find a solution.'
When a facilitator faces stalemate, recognizing the lack of progress and moving towards a concrete plan is essential. Option A directly addresses the issue by scheduling a follow-up to continue the discussion in a more structured manner.
15 / 19
Sarah, the team lead, sends a Slack message to the development team regarding an urgent bug fix. Which phrasing best demonstrates effective facilitation during this communication?
'Everyone needs to address this immediately!'
The best response directly states the issue and requests action without being overly demanding. Options B and D are too directive, while option C doesn't clearly articulate the need for a discussion. Facilitation is about guiding the conversation and assigning tasks, not just issuing commands.
16 / 19
David, during a code review, points out a potential performance bottleneck in a new API endpoint. The developer responds defensively, arguing the design is optimal. How should you, as facilitator, respond to de-escalate the situation?
'Let's just agree that this is the best approach.'
The core of facilitation is managing conflict and encouraging productive discussion. Simply agreeing with the developer shuts down further exploration. Option A prompts a deeper dive into performance concerns, while options B and C avoid addressing the issue, and option D introduces unnecessary complexity.
17 / 19
Maria is leading a stand-up meeting. A developer states, 'I'm blocked on getting access to the database.' The team moves on without addressing this blocker. As facilitator, what's your immediate action?
'That's fine; just keep working on your tasks.'
A facilitator's primary role is to ensure all issues are addressed. Ignoring a blocker prevents progress and demonstrates poor leadership. Option A directly addresses the problem, prompting a discussion about the root cause and potential solutions.
18 / 19
John is drafting a PR description for a significant refactoring of a core module. The description is highly technical and lacks context for reviewers. How should you advise him to improve it as facilitator?
'Just explain the code changes thoroughly.'
A good PR description needs to be understandable for a broader audience. Option A provides guidance on structuring the explanation effectively – focusing on *why* the changes were made and their impact is crucial for successful code review. The other options are either too brief or shift responsibility inappropriately.
19 / 19
Emily facilitates a meeting to discuss migrating to a new cloud provider. After an hour of debate, no consensus is reached. What's the most effective action for her as facilitator to conclude the meeting?
'Okay, let's just keep discussing until we find a solution.'
When a facilitator faces stalemate, recognizing the lack of progress and moving towards a concrete plan is essential. Option A directly addresses the issue by scheduling a follow-up to continue the discussion in a more structured manner.
This module focuses on Meetings & Collaboration — real workplace phrasing you'll use on the job. It contains 19 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 19 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.