Roy Kent's Blunt English: Turn Harsh Feedback Into Useful Feedback
You can understand every word of harsh English and still have no idea what to do next. You’re bad. You’re lazy. Your work is boring. Be better. Clear vocabulary, useless feedback.
Roy Kent gives us a perfect way to see the difference between blunt and actionable. The practical filter is:
If a comment never gets past the first box, it may feel direct, but the receiver still cannot improve from it.
Blunt is not the same as clear
[ROY] Because you don't deserve it.
This is brutally clear about Roy’s attitude. It is almost useless as coaching. The receiver learns what Roy thinks of him, but not what behavior created the judgment or what would change the answer.
[ROY] And you're ugly. You're an ugly, ugly boy. With bad hair.
An appearance insult gives the learner nothing to adjust in their work. This is the easiest feedback test in the world: could the person act differently tomorrow because of this sentence? If not, it is not useful performance feedback.
Critique the work, behavior, decision, timing, or result. Do not make the person’s identity the problem.
Level 2: performance criticism is better—but vague labels still trap the learner
[ROY] And the way you play is dull and conformist.
This is already more useful than attacking appearance: Roy has moved from you are bad to the way you play has a problem. But two questions remain unanswered: What exactly looks dull? and What should Jamie do instead?
Vague: “Your presentation is dull.”
Useful: “In the first five minutes, you read almost every sentence from the slide, so the audience has no reason to look at you. Keep the slide to key phrases and explain the examples in your own words.”
The second version is not softer because it uses fancy politeness. It is better because it contains evidence and a next move.
The receiver can force vague feedback to become useful
[JAMIE] If you know how to make me better, I want to hear it.
This is excellent feedback-receiving language. Jamie does not ask Roy to like him. He asks for information that can improve performance.
In work, study, sport, or creative feedback, you can make that move less confrontational:
- “If there’s something specific I could do better, I want to hear it.”
- “I’m open to the criticism. What would you change first?”
- “Can you point to one moment where the problem shows up?”
[TED] Whoa! Okay. Expound.
Expound means explain the point more fully. It sounds a little formal or theatrical as a one-word command, but the communication move is gold: don’t argue with an unclear criticism yet; ask the speaker to unpack it.
The scene becomes real coaching when Roy finally gives a chain
[ROY] You've made him a team player. You've got him to pass and sh*t, and in doing so, you've made him average. 'Cause, Jamie, deep down, at your core, you are a prick. So just be a prick. We need you to score more goals, and we need you to get in the other teams' f*cking heads and drive them up the f*cking wall like only you can f*cking do.
Strip away the profanity and personal labels, and there is suddenly a real coaching structure underneath:
- Observable change: Jamie is playing more like a team player and passing more.
- Claimed impact: Roy thinks the change has reduced Jamie’s distinctive effectiveness.
- Desired result: the team needs more goals and more psychological pressure on opponents.
That does not mean Roy’s conclusion is automatically correct. Useful feedback still needs evidence. But now the receiver can actually discuss the claim.
“You’ve become much more willing to pass, which has helped the team. But in situations where you have a clear one-on-one advantage, you’re passing too early and losing the attacking threat that makes you dangerous. In those moments, be more direct and look to create the shot yourself.”
Same core coaching idea. No identity attack. No profanity carrying the meaning. Much easier to test.
The missing fourth box: define the boundary
[ROY] No. I'm saying sometimes. When it is appropriate... yes, be a prick.
The useful part is not the insult. It is sometimes and when it is appropriate. Advice like “be more aggressive,” “speak up,” “take control,” or “challenge people” becomes dangerous if the learner treats it as an all-the-time personality rule.
Good situational feedback should answer: When should I do this? and, just as importantly, when should I not?
Too broad: “Be more assertive.”
Bounded: “When the client asks for a recommendation, state your preferred option first instead of listing five choices. In brainstorming sessions, keep inviting alternatives.”
Jamie asks the question every learner should steal
[JAMIE] Okay. How will I know when?
This is one of the most transferable lines in the scene. If advice depends on judgment, timing, or context, ask for the trigger.
[TED] Any specifics we need to look out for?
Specifics means concrete details. Look out for means watch for signs or conditions. Together, the question asks the feedback-giver to stop relying on intuition and name what the receiver should notice.
- “What exactly should I change?”
- “Can you give me one example from today?”
- “What would a better version look like?”
- “When should I do that—and when should I avoid it?”
- “What should I look for to know I’m improving?”
Watch out for advice that ends with confidence instead of criteria
[ROY] You'll know it when you see it.
Sometimes experts really do rely on pattern recognition. But this answer is poor teaching if the learner does not already share that intuition. “You’ll know” shifts the burden back to the person who asked for guidance.
If you are the feedback-giver and you cannot explain the trigger, try an example instead: “If X happens, do Y.” Even one concrete scenario is better than pretending the rule is obvious.
The Feedback Filter: rewrite harsh English in four moves
| Harsh / vague version | Observable behavior | Impact | Next action |
|---|---|---|---|
| “You’re careless.” | “Three customer names were copied incorrectly into the final sheet.” | “The support team had to verify them again.” | “Run the name check before you mark the sheet final.” |
| “Your English is confusing.” | “You give the background before stating the request.” | “The listener has to wait to understand what you need.” | “Start with the request, then add the reason.” |
| “You’re too quiet.” | “In the last meeting, you had the answer but waited until the topic had changed.” | “The team made the decision without that information.” | “If you have evidence that changes the decision, interrupt politely before the topic closes.” |
| “Your design is boring.” | “The three sections use the same visual weight.” | “The reader cannot see what matters first.” | “Create one clear focal point and reduce the secondary elements.” |
These are writer-original practice rewrites, not dialogue from the show. Notice that they are still direct. Useful feedback does not have to become vague politeness.
What not to promise when you receive harsh feedback
In a pressured conversation, learners often escape by saying things like “Okay, I’ll fix everything” or “It won’t happen again.” Don’t promise what you do not yet understand or control.
“I understand the concern. Before I change it, can I check that I’ve understood the problem correctly?”
Then summarize: “You want me to keep the teamwork, but be more direct in situations where I have a clear advantage. Is that right?”
That summary does two jobs: it proves you listened, and it exposes misunderstandings before they turn into bad action.
Five role-play repairs
Drill A — “Your work is sloppy.”
You are the receiver. What should you ask first?
Show one model
Writer-original: “Can you show me one or two places where it looks sloppy, so I know what to fix?”
Drill B — “You need to be more confident.”
Turn the personality advice into a request for observable behavior.
Show one model
Writer-original: “What would ‘more confident’ look like in the next meeting—speaking earlier, disagreeing more directly, or something else?”
Drill C — “Stop being so aggressive.”
You agree that something went wrong, but the word aggressive is broad. Repair it.
Show one model
Writer-original: “I want to change it. Which part felt aggressive—the wording, the interruption, or my tone?”
Drill D — You are giving the feedback
Your colleague talks for too long before answering the customer’s question. Use behavior → impact → next action.
Show one model
Writer-original: “When the customer asks a yes/no question, you often give two minutes of context first. They sometimes interrupt because they still don’t know the answer. Give the short answer first, then explain.”
Drill E — The advice is situational
You tell a learner to interrupt more. Add a boundary.
Show one model
Writer-original: “Interrupt when someone is about to act on incorrect information. If it’s just a minor detail, note it and wait for a pause.”
A compact formula you can use at work
For giving feedback:
For receiving feedback:
You do not need Roy Kent’s profanity to get Roy Kent’s directness. Keep the certainty about the problem; remove the attack on the person.
Practice the repair, not the insult
With FunFluen, replay a short feedback exchange and pause before the useful explanation arrives. First classify the line: person attack, vague performance judgment, observable behavior, impact, or next action. Then reveal the subtitle and rewrite the harsh version into professional English. Save the clarification phrases you would actually use, and shadow the repaired version rather than rehearsing the insult.
If you remember only one rule: direct feedback tells me what changed; harsh feedback merely tells me you’re unhappy.
Explore more language-learning guides in Media-Based Language Learning.