ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: English for Professionals: How to Give Criticism Without Offending

เลือกโหมดฝึก

แต่ละโหมดจะเปิดห้องฝึกแบบเต็มจอ

289 ประโยค
หากประโยคสั้นหรือยาวเกินไป กดที่ Edit เพื่อปรับแก้
1
Hi, everyone.
2
Welcome back to High Level Listening, your place for real English conversations at work and business English lessons.
3
So imagine your colleagues show you something they've been working on.
4
But it's not very good.
5
Maybe there are mistakes, or maybe it's completely different from what you expected.
6
You want to be honest, but you don't want to sound rude, harsh, or unprofessional.
7
Yeah, it can be a tricky balance.
8
So today we thought we'd show you exactly what to say to give clear, constructive feedback in polite business English.
9
And this will be included in all of our PDF transcripts for our business English bundle and the full phrase list.
10
We've got MP3 downloads and everything will be in the study pack.
11
So you can check that out in the description below.
12
okay for the first section we're just going to be pointing out a couple of small mistakes now
13
if you are just pointing out a couple of mistakes you
14
can say yep here's a problem we've got a problem here
15
but if you wanted to soften your language a little bit we're going to start positively
16
and we're also going to soften the problem
17
so let's give you an example of what that sounds like okay
18
so for dialogue one i'll be reviewing a document
19
that mark has worked on okay yeah all right okay overall
20
this looks pretty solid i really like how it's structured great
21
okay thank you i did however notice a couple of details
22
we should double check before sending it out okay yes of course let me know what I've missed.
23
All right, so let's follow the structure that we gave you guys earlier.
24
You're going to give them a compliment or say something positive about it, and then we're going to soften the problem.
25
So this is how we gave them a compliment.
26
Overall, this looks pretty solid.
27
I like how it's structured.
28
Okay, so I'm giving Mark a compliment.
29
I'm saying something positive about what he's given me for work.
30
I did, however, notice a couple of details we should double check before sending it out.
31
Now, I could have said, I noticed some problems.
32
That would have been very direct.
33
I noticed some problems.
34
It just doesn't sound very nice and it doesn't sound very productive, okay?
35
So I did, however, notice a couple of details.
36
Now, I'm even changing the grammar of my sentence from I noticed to I did, however, notice.
37
Why am I doing that?
38
Because my first sentence was positive and my second sentence is not so positive.
39
So I want to show with I did, however, I want to show a difference between the positive and the negative.
40
I did, however, notice a couple of details we should double check before sending it out.
41
Now, the final thing we did was I said we, not you.
42
If I can remove the word you, you, you, you made a problem, you did a problem, you, you, you, you.
43
If I can remove you from the sentence, it sounds so much more collaborative.
44
We.
45
I did, however, notice a couple of details we should double check before sending it out.
46
When Kat pointed out the problem softly, I responded quite softly as well.
47
I didn't say, oh, what's wrong?
48
I said, of course, let me know what I've missed.
49
So you can open yourself up to criticism and that makes you sound professional and open to changes as well.
50
It's win-win.
51
So let's go through another dialogue with the same scenario and we'll use the same structure to give a compliment, start positively and then soften the problem.
52
We're reviewing a presentation So, okay.
53
Yeah, I think this is a good start.
54
I think it's about 90% there.
55
Okay.
56
What do you think's missing?
57
One thing, the figures should be Q3 instead of Q2.
58
Right, right.
59
Good catch.
60
And there's a small typo.
61
It says manager, manager instead of manager.
62
Oh, wow.
63
Yes, I will fix that right away.
64
But apart from that, I think we're in good shape.
65
It's okay.
66
We use the same kind of structure i started positive this
67
is a good start in the previous one cat said this is solid and yes
68
when something is about 90 percent there i think it's almost perfect it's almost finished it's about 90 there means it's
69
almost good enough and then i introduced the problems one thing i didn't say the word one mistake
70
or one problem again we want to avoid the words problem mistake or bad so one thing
71
the figures should be q3 instead of q2 and there's a small typo small again i'm reducing
72
the size of the problem oh there's a little thing uh there's a little error oh there's one small change
73
if you can make problems smaller that's good too a typo is a spelling mistake i think
74
when we're talking about typing things on computers that's where it came from
75
but there is a spelling mistake there's a small typo i
76
do this too manger instead of manager it's missing an a and then the The final thing is also quite positive.
77
But apart from that, we're in good shape.
78
It's almost perfect.
79
Things are going well.
80
We're in good shape.
81
We have made a good start.
82
And I think with a little bit extra, we'll be ready.
83
Okay.
84
Our second topic is going to be about something that you did not expect.
85
So I thought it was going to be a little more like this, or I was expecting something else,
86
sometimes you receive something and it is not what you expected.
87
So we're going to be talking about this and we're going to do it in a similar way.
88
We are going to acknowledge the person working on the product.
89
We are going to say, okay, I see that you did some work here,
90
but then we need to show our expectations and tell them directly what you expect it.
91
Okay.
92
But we don't just want to say, this is not what I expected.
93
Change it.
94
Right.
95
Because that doesn't, that's not very helpful.
96
That's not very constructive.
97
So let's go through the dialogue.
98
All right.
99
Okay.
100
Thanks.
101
Thanks for getting this done so quickly. Of course.
102
Although after reviewing it, it is a bit different from what I had in mind.
103
I was expecting something more data-driven.
104
Could you revise it with that in mind?
105
Sure.
106
Yeah, no problem.
107
Thanks for clarifying.
108
So remember that since we're balancing positive with negative, we can say, thanks for this.
109
That's the positive one.
110
Thanks for getting this done so quickly.
111
Thanks for finishing it in time.
112
But we're going to kind of balance that out with the negative thought.
113
So then we could say, thanks, although.
114
Thanks, however.
115
And just like the last one where I said I did notice, I'm saying, although after reviewing it,
116
it is a bit different from what I had in mind.
117
So I could say it's a bit different.
118
But remember, we're balancing it out.
119
Thanks for this, although it is a bit different from what I had in mind.
120
Something I had in mind was what I was thinking, what I was expecting.
121
And then I'm going to tell them what I want.
122
I was expecting something more data-driven.
123
We kind of go down this path, but we do need to directly say what we want.
124
Otherwise, we're never going to get it, right?
125
I was expecting something more data-driven.
126
Could you revise it with that in mind?
127
Okay, so this is what I had in mind.
128
And with that in mind, can you revise it?
129
Revise too.
130
It's better than fix or change or stop.
131
Revise is a very professional word for that.
132
OK, well, here's a second dialogue.
133
Same scenario, same structure.
134
Thanks for putting this together.
135
I can see you put a lot of work into it.
136
Yeah, sure. Of course.
137
I think what you've done is useful, but the format isn't quite what the client asked for.
138
Could we restructure it to focus on quarterly figures? Of course.
139
Got it.
140
I will rework it.
141
Okay.
142
Did you hear our strategy again?
143
Appreciate their work first.
144
I said, thanks for putting this together.
145
Thanks for finding all this different data and collecting it into one.
146
Thanks for putting this together.
147
Thanks for doing this.
148
Thanks for working so hard.
149
I can see you put a lot of work into it.
150
or I can see you put a lot of effort and time into it.
151
So start with a compliment, then say what you would like to change.
152
What you've done is useful.
153
So another compliment, another bit of appreciation.
154
But the format isn't quite what the client asked for.
155
So again, like Kat said earlier, we want to avoid the word you.
156
I want to focus on the problem most.
157
The problem is the format how the information is laid out.
158
The format isn't quite what the client asked for.
159
Again, we want to soften the problem.
160
So making problems smaller is one and saying quite is another way.
161
It isn't quite what the client asked for.
162
This is much nicer than saying you didn't listen to the client.
163
The format isn't quite what the client asked for.
164
Could we restructure it?
165
Again, we Let's work together.
166
It's not all on you.
167
We're a team.
168
Could we restructure it?
169
Again, like revise in the previous dialogue, restructure is another softer word to say change.
170
Could we restructure it to focus on quarterly figures?
171
Some other useful phrases if you find yourself in the same situation.
172
This is close, but I was picturing something a little different.
173
Another one.
174
What I had in mind was slightly different.
175
Now, I may not have explained it clearly.
176
I was thinking of a different approach.
177
I think we need to go in a different direction.
178
Honestly, I was thinking along slightly different lines.
179
Alright, so our final situation is when something just is not possible.
180
We have lots of good ideas all day long, but sometimes things cannot work out.
181
They are physically impossible.
182
We don't have the money.
183
This is not feasible.
184
So I don't want to completely shut someone down, but sometimes we have to.
185
It's just not possible.
186
So let's look at dialogue one and let's show you some good, clear, professional phrases to help you in this situation.
187
So I was thinking we could rebuild the whole system before the launch.
188
Well, I see what you're going for.
189
And in an ideal world, that would be great.
190
But I don't think that's realistic for us right now.
191
Oh, you don't think so?
192
No, just with the timeline we're working with, we wouldn't be able to deliver that properly.
193
Yeah, fair enough.
194
So let's focus on a few key improvements that we can actually get done before the launch.
195
okay so mark's creative mark's thinking mark's telling us some information
196
but it's just not going to be possible right
197
so what i've kind of done is what we've been doing
198
this whole time we've given a compliment we've said what we
199
like about it we've said why we can't do this
200
and then maybe we've offered a new direction to go in or something smaller something easier that we can actually do.
201
So I see what you're going for.
202
I see where you're going with this.
203
I can see you thinking, you know, you're thinking big, right?
204
We're thinking big.
205
And in an ideal world, that would be great.
206
But I don't think that's realistic for us right now.
207
This is a common word.
208
It's not realistic.
209
It's not logical.
210
It just can't happen.
211
We just don't have the time, the money, the resources.
212
I don't think that's realistic for us right now.
213
And then at the end, I say, let's focus on a few key improvements we can actually get done before launch.
214
So some real world things we can actually do, things we can actually accomplish.
215
Here's a second dialogue with the same situation.
216
What if we launched in three separate markets at the same time?
217
I like the thinking.
218
It's very ambitious, but I don't think we have the resources to support that right now.
219
Why not?
220
We'd just be stretching ourselves too thin.
221
Yeah, fair enough.
222
Let's start with one market, do it properly, and then expand from there.
223
Okay, so yes, Mark got shot down again.
224
And he has great ideas.
225
They're just not possible.
226
So I said, I like the thinking.
227
It is ambitious.
228
But I don't think we have the resources to support that right now.
229
When you don't have the resources, you don't have the time, money, manpower.
230
You don't have enough.
231
You don't have enough.
232
We just don't have the resources to support that right now.
233
another explanation on top of that we'd be stretching ourselves too thin
234
if I have two workers
235
and they are working on five different projects they are stretching
236
themselves too thin I would rather have two workers working on one project
237
or two workers working on two projects
238
that feels like a normal amount of work not stretching ourselves too thin so let's start with one market, here's my solution, do it properly,
239
and then expand from there.
240
Okay, then we've got one final dialogue, and we're using the same method again.
241
We acknowledge and appreciate, explain the problem, and then redirect with a solution.
242
So I think we should add a few more features before the launch.
243
Okay, I get why you're suggesting that.
244
More features always sounds good, but I think it might slow us down too much at this stage.
245
You think so?
246
Yeah, we risk overcomplicating things.
247
Okay, yeah, I see what you mean.
248
Let's just keep it simple for now and build on it after the launch.
249
Okay, so again, the same method.
250
Appreciate and acknowledge the work.
251
Kat had a bold suggestion.
252
More features.
253
Maybe we're working on an app or program.
254
I get why you're suggesting that.
255
I get is another way to say I understand.
256
I get why you're saying that.
257
I get why you're suggesting that.
258
I get why you're thinking that is a way to acknowledge. But here's the problem.
259
I think it might slow us down too much at this stage.
260
Like before when we suggested we, I'm using that again, it might slow us down.
261
We're a team.
262
We need to work together.
263
I think it might, again, we're softening the problem, it might slow us down too much.
264
My further explanation, we risk overcomplicating things.
265
Risk is a good word.
266
It's not certain, but when you can think about the future or think about the next stages, you can see a potential problem.
267
We risk hitting that problem.
268
So this is my advice based on what I think will happen.
269
We risk is also good because that's me and you.
270
Again, we're collaborating.
271
We risk over-complicating things or making it too complicated.
272
And again, lastly, redirect, suggest an idea instead.
273
Let's keep it simple for now and build on it after launch.
274
Again, we, the team, let's keep it simple for now.
275
For now implies that maybe we can use your idea in the future, but not yet.
276
So still acknowledging Kat's idea.
277
And maybe I like the idea.
278
We're just not ready for it right now.
279
So let's keep it simple for now and build on it after launch.
280
OK, so now you know how to give feedback that's honest, clear and professional without sounding rude or overly negative.
281
Yeah, we think these are the kinds of phrases that make a real difference in workplace conversations.
282
And you can get the full Business English study pack with PDF transcripts, phrases, dictionaries for all of our Business English videos here on High Level Listening.
283
And you can find that in the link in the description below.
284
Yes, which phrases would you like to use at work?
285
Let us know in the comments.
286
We read and reply to every single one we get here on YouTube.
287
And thanks everybody for watching.
288
We'll see you next time on High Level Listening.
289
Bye-bye.

ดาวน์โหลดแอป

ทุกอย่างที่ต้องใช้เพื่อพูดได้คล่อง

AI ให้คะแนนการออกเสียงให้คะแนนทุกประโยค
ฝึก IPAเชี่ยวชาญทุกเสียง
คำศัพท์สร้างคลังคำของคุณ
เกมคำศัพท์เล่นไปเรียนไป

ช่องเดียวกัน

FOR YOU

วิดีโอแนะนำ

คำศัพท์และข้อสังเกตด้านการพูดสำหรับบทเรียนนี้

บทเรียนฝึกพูดระดับ B2 นี้ใช้วิดีโอ “English for Professionals: How to Give Criticism Without Offending” เป็นสื่อ วิดีโอนี้มี 289 ประโยค และ 2726 คำ สำหรับฝึกพูดตาม ช่วงที่มีเสียงพูดยาว 18:13 ผู้พูดพูดด้วยความเร็วเป็นธรรมชาติ ประมาณ 150 คำต่อนาที ใกล้เคียงกับบทสนทนาในชีวิตประจำวัน 87% ของคำอยู่ใน 3,000 คำที่ใช้บ่อยที่สุดในภาษาอังกฤษ คำศัพท์จึงตามได้ง่าย

คำศัพท์สำคัญในวิดีโอนี้

คำที่ยากที่สุด 15 คำในวิดีโอ พร้อมคำอ่านและความหมาย:

คำศัพท์คำอ่านความหมาย
compliment คำนาม/ˈkɑmpləmənt/คำชมเชย
typo คำนาม/ˈtaɪpəʊ/คำผิด, พิมพ์ผิด
realistic คำคุณศัพท์/ˌɹɪəˈlɪs.tɪk/สมจริง
ambitious คำคุณศัพท์/æmˈbɪʃ.əs/ทะเยอทะยาน, มักใหญ่ใฝ่สูง
quarterly คำคุณศัพท์รายไตรมาส
scenario คำนาม/sɪˈnɛəɹioʊ/ฉากทัศน์
manger คำนาม/ˈmeɪ̯n.d͡ʒɚ/รางหญ้า
collaborate คำกริยา/kəˈlæb.ə.ɹeɪt/ร่วมมือ, ประสานงาน
imply คำกริยา/ɪmˈplaɪ/หมายความ
clarify คำกริยา/ˈklæɹ.ɪ.faɪ/ชี้แจง
polite คำคุณศัพท์/pəˈlaɪt/สุภาพ
bundle คำนาม/ˈbʌn.dl̩/มัด, กำ
colleague คำนาม/ˈkɒliːɡ/เพื่อนร่วมงาน
dictionary คำนาม/ˈdɪk.ʃəˌnɛ.ɹi/พจนานุกรม, ดิกชันนารี
workplace คำนาม/ˈwɝkˌpleɪs/ที่ทำงาน

ประโยคที่ควรฝึกพูดซ้ำ

ประโยคสั้น ๆ ที่สมบูรณ์จากวิดีโอ ซึ่งนำไปใช้ในบทสนทนาประจำวันได้:

  • Why am I doing that?
  • I didn't say, oh, what's wrong?
  • What do you think's missing?
  • Could you revise it with that in mind?
  • Could we restructure it to focus on quarterly figures?

ไวยากรณ์ในวิดีโอนี้

โครงสร้างที่ผู้พูดใช้บ่อยที่สุด พร้อมคำพูดจริงจากวิดีโอ:

โครงสร้างในวิดีโอ
Present perfect continuous have/has been + -ing — การกระทำที่เริ่มก่อนหน้านี้และยังดำเนินอยู่they've been working · we've been doing
Present perfect have/has + กริยาช่อง 3 — เหตุการณ์ในอดีตที่ยังเกี่ยวข้องกับปัจจุบันhas worked · I've missed · have made
Passive voice be + กริยาช่อง 3 — เน้นสิ่งที่เกิดขึ้น ไม่ใช่ผู้กระทำwill be included · is laid

การออกเสียงที่ควรระวัง

ผู้พูดใช้รูปย่อและรูปลดเสียง 93 ครั้ง เช่น we're, don't, you're ให้พูดแบบสั้นตามที่ได้ยิน

  • เสียง “sh” และ “zh”: ambitious /æmˈbɪʃ.əs/, expectation /ˌɛk.spɛkˈteɪ.ʃən/, dictionary /ˈdɪk.ʃəˌnɛ.ɹi/, accomplish /əˈkɑm.plɪʃ/, appreciation /əˌpɹiː.ʃiˈeɪ.ʃən/
  • คำยาว — ลงเสียงหนักให้ถูกพยางค์: positively /ˈpɑ.zɪ.tɪv.li/, collaborate /kəˈlæb.ə.ɹeɪt/, collaborative /kəˈlæb.ə.ɹə.tɪv/, expectation /ˌɛk.spɛkˈteɪ.ʃən/, dictionary /ˈdɪk.ʃəˌnɛ.ɹi/

เสียงที่คนไทยมักออกเสียงยาก:

  • เสียงท้ายคำ — ออกเสียงให้ครบ ไม่เปลี่ยนเป็นตัวสะกดแบบไทย: revise /ɹɪˈvaɪz/, acknowledge /əkˈnɑ.lɪd͡ʒ/, constructive /kənˈstɹʌktɪv/, ambitious /æmˈbɪʃ.əs/, feasible /ˈfiː.zɪ.bəl/
  • /v/ — ไม่ใช่ /w/ ให้ฟันบนแตะริมฝีปากล่าง: revise /ɹɪˈvaɪz/, constructive /kənˈstɹʌktɪv/, positively /ˈpɑ.zɪ.tɪv.li/, collaborative /kəˈlæb.ə.ɹə.tɪv/
  • /z/ — เสียงก้อง ไม่ใช่ /s/: revise /ɹɪˈvaɪz/, positively /ˈpɑ.zɪ.tɪv.li/, feasible /ˈfiː.zɪ.bəl/

วิธีฝึกกับวิดีโอนี้

  1. ฟังวิดีโอให้จบหนึ่งรอบโดยยังไม่ต้องพูด แล้วจดคำที่ยังไม่รู้จัก
  2. เริ่มที่ความเร็ว 0.75× พูดตามทีละประโยค แล้วกลับไปใช้ความเร็วปกติเมื่อเริ่มคล่อง
  3. อัดเสียงตัวเองแล้วเทียบกับต้นฉบับ โดยสังเกตคำอย่าง compliment, typo, realistic เป็นพิเศษ

เทคนิค Shadowing คืออะไร?

Shadowing เป็นเทคนิคการเรียนรู้ภาษาที่ได้รับการรับรองทางวิทยาศาสตร์ พัฒนาขึ้นสำหรับการฝึกนักแปลมืออาชีพ วิธีการนี้เรียบง่ายแต่ทรงพลัง: คุณฟังเสียงภาษาอังกฤษจากเจ้าของภาษาและพูดตามทันที — เหมือนเงาที่ตามผู้พูดด้วยช่วงเวลาห่าง 1-2 วินาที การวิจัยแสดงว่าเทคนิคนี้ปรับปรุงความแม่นยำในการออกเสียง ทำนองเสียง จังหวะ การเชื่อมเสียง การฟังเข้าใจ และความคล่องแคล่วในการพูดได้อย่างมีนัยสำคัญ

เทคนิค shadowing: อ่านคู่มือฉบับเต็มทีละขั้นตอน →