ESL Tech
← Portal

Yuri: Meeting Facilitation & Discourse Markers

Student: Yuri (B1)
Duration: 60 mins
Focus: Discourse Markers & Retro Meetings
🔊 Shadowing Pacer: Sprint Retrospective

Shadowing Focus: Listen for discourse markers (First of all, Regarding, However, Having said that, Moving on to, In conclusion) and article prominence.

00:00
Record yourself, then compare with the model
🎯 Key Targets for Yuri (Recycle Focus)

1. Article Omission on Technical Nouns

Remember: "the server", "the deployment", "the database", "the team". Don't drop the article before countable technical items.

2. Conditional + Will (First Conditional)

Use present tense in the if-clause, not future: "If the migration goes well, we will deploy on Friday." Not: "If the migration will go well..."

📖 Grammar: Discourse Markers for IT Meetings

Discourse markers are signposts — they tell your listener where you're going. Use them to structure your meeting contributions clearly.

Function
Discourse Markers
IT Meeting Example
Sequencing
First of all, Firstly, Secondly, Then, Next, Finally
"First of all, let's review the sprint goals."
Adding Info
Moreover, Furthermore, In addition, Also
"Furthermore, we need to update the SSL certs."
Contrasting
However, On the other hand, Nevertheless, Having said that
"However, we faced some database issues."
Giving Examples
For instance, For example, Such as
"For instance, the login endpoint was slow."
Conceding
Admittedly, Of course, Granted
"Admittedly, the timeline was too tight."
Redirecting
Regarding, With respect to, Moving on to, As for
"Moving on to the next sprint..."
Concluding
In conclusion, To sum up, Overall, All in all
"In conclusion, we made good progress."

📋 Rule of Thumb:

"Discourse markers are signposts — they tell your listener where you're going."

🔄 Game 1: Sprint Retrospective Simulator

Click "Roll Retro Round" to spin the roulette and select a retro scenario card. Yuri must lead the discussion using appropriate discourse markers. 60-second speaking timer per round.

RETRO_ROULETTE.EXE STATUS: READY
Roll to select a retro round...
📋 Meeting Phrase Bank
"First of all, let's discuss..." "Regarding..." "Having said that..." "Moving on to..." "In conclusion..." "For instance..." "Admittedly..." "However..." "To sum up..." "Moreover..."
Round 01
🌱 Start
What should we start doing?
Round 02
⛔ Stop
What should we stop doing?
Round 03
🔁 Continue
What should we continue doing?
Round 04
🌟 Praise
What went well this sprint?
Round 05
⚠️ Problem
What challenges did we face?
Round 06
📋 Action
What are our action items?
📝 Grammar Bank: Discourse Marker Practice

Choose the correct discourse marker for each IT meeting context. Click each item to reveal the answer and explanation.

Fill in the Blank (IT Meeting Context)
1. ___ the server migration, we need to discuss the timeline. 👁️
Regarding / Moving on to
"Regarding" introduces a topic. "Moving on to" also works to shift focus. Both are correct here.
2. The deployment was smooth. ___, we had some rollback issues. 👁️
However
"However" introduces a contrast between the smooth deployment and the rollback issues.
3. ___ the project seems on track, the budget is a concern. 👁️
Admittedly
"Admittedly" concedes a point (project on track) before introducing a contrasting concern (budget).
4. ___, I think we achieved our main goals this quarter. 👁️
In conclusion / To sum up
Both "In conclusion" and "To sum up" signal the end of a discussion and summarize the main point.
5. We need to improve test coverage. ___, we should add more integration tests. 👁️
For instance / For example
"For instance" or "For example" introduce a specific example of the general point about test coverage.
6. The API is working well. ___, the frontend needs significant work. 👁️
On the other hand
"On the other hand" contrasts two different aspects (API vs frontend) of the same project.

🔑 Quick Reference

Sequencing: First of all, Next, Finally

Contrasting: However, On the other hand

Conceding: Admittedly, Granted

Redirecting: Regarding, Moving on to

Concluding: In conclusion, To sum up

Remember:

  • Discourse markers structure your speech
  • They signal direction changes to the listener
  • Use a comma after the marker
🎤 Game 2: Speaking Challenge — Lead the Meeting

Yuri must lead a mini meeting on one of the IT topics below. Use at least 4 discourse markers within 2 minutes. Select a topic, then speak.

Topic 01
Weekly standup — discuss current sprint progress
Topic 02
Incident post-mortem — database outage on Tuesday
Topic 03
Tech stack decision — choose between React and Vue
Topic 04
Resource planning — team is overloaded
Topic 05
Code freeze discussion — preparing for release
Topic 06
Tooling upgrade — moving to GitHub Actions

⏱ Meeting Clock

120

📋 Structure Reminders:

  • Open with: "First of all, let's talk about..."
  • Redirect: "Regarding..." / "Moving on to..."
  • Contrast: "However..." / "Having said that..."
  • Concede: "Admittedly..." / "Of course..."
  • Conclude: "In conclusion..." / "To sum up..."
  • Use at least 4 different discourse markers