Giving a junior honest feedback without crushing them
You are the student coordinator for a symposium and a first-year volunteer has sent a sponsor email with three mistakes in it, including the sponsor's name spelled wrong. They are keen, they worked late on it, and you have to say something before the next one goes out. Freshers in their first job are asked to do exactly this within a year, and almost nobody is taught how.
An intermediate-level session of about 7 minutes.
The email has already gone out; what you are protecting is the next one. You have thanked them, you start the second half, and their face changes: the email they stayed late on was wrong, and a sponsor name was part of it. What you do in the next few seconds decides whether they argue, go quiet, or actually take it in. Finding a polite way to say the name was misspelled is the easy half. Staying in the conversation once they have gone silent, without softening the point back into nothing, is where it slips. You are also not their manager, which removes the authority that usually carries a conversation like this. Here you run it against an AI volunteer who reacts the way a real one does, defensive at first and recoverable depending on how you handle it.
Angles worth taking
- Name one mistake rather than all three; the other two keep, and only so much lands in a single conversation.
- If they start explaining how it happened, let them finish, because the fix is usually somewhere inside that explanation.
- Check they can say what they will change next time; agreeing with feedback and knowing what to do about it are different things.
- Keep the misspelled name as a fact about the email, never as evidence about how careful they are.
- Do not close by saying it was no big deal; taking the point back teaches them the feedback was optional.
- Hand them the next draft before you part, so being corrected does not feel like being quietly replaced.
Who is in the room
You play
The student coordinator giving feedback
You speak with
A first-year volunteer who is eager, takes criticism personally at first, and either shuts down or recovers depending on how it is said
Phrases to reach for
These are shown to you before the session starts. They are what you are asked to use, not a list the scorer is checking off.
Ready to speak?
Free to start. You need a TalkDrill account to speak — reading this page does not.
Browse all roleplay scenariosThe format
Modes
Learn (guided) · Mock (exam-real)
How a roleplay session works
Read your brief
Your role, the situation, and what a good outcome looks like. The counterpart has their own brief, and you do not get to read it.
Open the conversation
You speak first in most scenarios. How you open sets what you can ask for later, which is most of the exercise.
Handle the turn
Somewhere in the middle it stops going your way — a refusal, a counter-offer, a rebuttal you did not prepare for. That moment is the scenario.
Read the report
Outcome, the phrases you used and the ones you missed, fluency and clarity, and the specific line worth rewriting.
What you're scored on
Across every roleplay, the report looks at the same four things — because they are what makes a real conversation work or fail.
Give one clear piece of feedback about the work rather than the person, check they have understood it, and end with them still willing to send the next email.
Task outcome
Whether you got what the brief asked for: the refund, the extension, the concession, the point conceded.
Appropriacy
Whether the register fits. A complaint that is too soft gets nothing; the same complaint too hard gets a manager and no refund.
Recovery
What you do with the unexpected turn — repair, rephrase, push back, or stall. This is where most of the marks move.
Delivery
Fluency, pronunciation and pace, judged in conversation rather than in a prepared monologue.
More roleplay scenarios
All roleplay scenarios · Placement scenarios · All speaking practice