쉐도잉 연습: Critical Thinking | 6 Key Words + 12 Business English Phrases | Real Podcast [BEL200] - YouTube로 영어 말하기 배우기
C1
Welcome to Business English Podcast.
276 문장
문장이 너무 짧거나 길면 Edit를 눌러 조정하세요.
1
Welcome to Business English Podcast.
2
I'm Tom.
3
And I'm Mary.
4
Today we're talking about critical thinking at work.
5
Critical thinking helps you ask better questions,
6
check your reasoning, and explain decisions clearly.
7
It is especially useful when the answer is not obvious,
8
the data is incomplete, or the team is moving too fast fast.
9
We'll learn six short vocabulary items and 12 practical business phrases you can use right away.
10
Let's build language for careful thinking,
11
respectful pushback, and stronger business judgment.
12
Let's preview today's vocabulary first.
13
These are short words, but they appear in serious business decisions all the time.
14
First, assumption.
15
An assumption is an idea people accept as true without fully checking it.
16
For example, that plan depends on a big assumption.
17
Second, evidence.
18
Evidence means facts or information that support a decision.
19
A great question is, what evidence do we have?
20
Third, context.
21
Context is the wider situation around the issue.
22
A number can look good or bad depending on the context.
23
Fourth, bias.
24
Bias is a thinking habit or preference that can make judgment less fair or less accurate.
25
Fifth, trade-off.
26
A trade-off is a balance between two things,
27
like speed and quality, or cost and flexibility.
28
And sixth, criteria.
29
Criteria are the standards you use to compare options or make a decision.
30
Now listen for those words inside practical phrases that people can actually say in meetings.
31
In Scene 1, John is a strategy director and Sarah is a market analyst.
32
They're in a formal review meeting about a possible expansion.
33
The opportunity looks strong, but they need to think carefully before recommending it.
34
Let's listen in.
35
Sarah, thank you for the market review.
36
Could you summarize the recommendation for us?
37
Of course.
38
The evidence suggests that mid-sized healthcare companies could be a strong segment for our platform.
39
That is promising.
40
But before we move forward,
41
I would like us to question the default.
42
Agreed.
43
The main assumption is that survey interest will turn into actual purchasing behavior.
44
Exactly.
45
Let's compare the signals from the survey,
46
pilot usage, and sales conversations.
47
The evidence is mixed.
48
Pilot users were positive, but several prospects raised concerns about implementation time.
49
Then we should step back first.
50
The context is not only market demand,
51
it is also our support capacity.
52
Right.
53
We should check every angle, including bias.
54
Our team may be focusing too much on the positive pilot.
55
That is fair.
56
We need to name both sides of the trade-off if we launch quickly.
57
The trade-off is speed versus readiness.
58
A fast launch creates momentum,
59
but it could stretch the support team.
60
Before we choose, let's set clear standards.
61
What criteria would make this expansion worth the risk?
62
I would use three criteria – confirmed demand,
63
support readiness, and a clear compliance plan.
64
Please revise the proposal around those points and recommend a phased pilot instead of a full launch.
65
That scene was formal, but the language was direct and useful.
66
Let's unpack each phrase a little more slowly.
67
The first key phrase was, question the default.
68
John used it before accepting the easy answer.
69
This is a professional way to challenge an assumption.
70
You're not saying, this is wrong,
71
you're saying, let's not accept the first answer automatically.
72
Exactly.
73
Those question the default when a team is about to approve something just because it feels obvious or familiar.
74
And if you say it calmly,
75
it sounds careful, not negative.
76
The second phrase was, compare the signals.
77
John wanted to look at the survey,
78
pilot usage, and sales conversations together.
79
I like this one because evidence in business is often messy.
80
One signal may look positive,
81
but another may tell a different story.
82
Right.
83
Compare the signals means don't let one data point control the whole decision.
84
A useful example is, let's compare the signals before we call this a success.
85
Next was, step back first.
86
This phrase brings context into the room before the team decides.
87
Exactly.
88
It tells people, before we go deeper into details,
89
let's look at the bigger situation.
90
In the scene, the bigger context was support capacity.
91
Demand looked good, but the team might not be ready.
92
So step back first is especially useful when people are focused on one exciting number.
93
Sarah then said they should check every angle.
94
That is a natural way to reduce bias.
95
Yes, it is diplomatic because it does not accuse anyone.
96
It simply says, let's make sure our view is complete.
97
You can use check every angle when the team may be too attached to a positive story.
98
And it invites other people to add risks,
99
missing facts, or alternative interpretations.
100
The fifth phrase was name both sides.
101
This is perfect for explaining a trade-off.
102
A trade-off is not just a downside.
103
It is the full picture,
104
what we gain and what we give up.
105
In this case, speed gives momentum, but readiness protects quality.
106
Name both sides makes that balance clear.
107
It's a useful phrase when a decision is not simply good or bad.
108
Finally, John said, set clear standards.
109
That connects directly to criteria.
110
This is a strong decision habit.
111
Before comparing options, agree on what success actually means.
112
If you skip that step,
113
people may argue because they are using different criteria in their heads.
114
So, Set Clear Standards helps the team judge options fairly and explain the recommendation later.
115
Now let's move to a different situation.
116
Scene 2 is faster and more casual casual.
117
Alex is a product manager and Emma is a UX researcher.
118
They're deciding whether to ship a feature this week.
119
The team wants momentum, but the user feedback is unclear.
120
Let's listen.
121
Emma, thanks for jumping on this quicksync.
122
I saw your comments in the doc and it sounds like you're worried about Friday's release.
123
Yeah, I am.
124
The feature works, but the feedback is messy.
125
We need to slow the reaction before we ship it.
126
Fair.
127
My assumption was that a small release means low risk,
128
but that may be too simple.
129
Exactly.
130
Let's test the numbers.
131
The evidence shows power users can use it,
132
but new users are confused.
133
Good distinction.
134
We should add the user story,
135
not just look at the dashboard.
136
Yes, the context is onboarding.
137
If the first experience is confusing, activation could drop.
138
Then let's include missing voices.
139
Who did we not hear from in testing?
140
Mostly new users.
141
That creates bias because our test group already understands the product.
142
OK, we could delay the full launch and run a limited beta instead.
143
That helps us choose a safer path.
144
The trade off is slower timing, but better learning.
145
Marketing needs a decision today,
146
so let's use a decision rule.
147
Good.
148
If new users can complete onboarding without help, we launch wider.
149
If not, we keep it in beta.
150
Those criteria are clear.
151
I'll update marketing and frame this as a controlled beta.
152
Perfect.
153
Better to think clearly now than clean up confusion later.
154
Scene 2 is more casual,
155
but the decision language was still very useful.
156
Let's go phrase by phrase.
157
Emma started with, slow the reaction.
158
That is a simple phrase for challenging a quick assumption.
159
This is useful when the team is moving fast and the first answer feels too easy.
160
Exactly.
161
Slow the reaction does not mean stop the project.
162
It means pause long enough to think.
163
A natural meeting sentence is,
164
let's slow the reaction and check what we actually know.
165
Then Emma said, test the numbers.
166
That is excellent when evidence looks positive but maybe incomplete.
167
Numbers can feel objective, but they still need interpretation.
168
Who was measured?
169
What was missing?
170
What does the number really prove?
171
In the scene, the data showed power users were fine,
172
but not that new users understood the feature.
173
So, test the numbers means don't just quote the data, examine it.
174
Next, Alex said they should add the user story.
175
That gave the data more context.
176
This is a very useful product phrase.
177
It reminds the team that behind every metric,
178
there is a real user experience.
179
Exactly.
180
If the dashboard says one thing but users are confused,
181
the user story matters.
182
You can also use Add the User Story in sales,
183
support, or customer success discussions.
184
Then they used Include Missing Voices.
185
That is a great phrase for reducing bias.
186
It asks, Whose opinion or experience is not represented here?
187
That question can change the decision.
188
In this case, the missing voices were new users.
189
The team had feedback, but it was not balanced.
190
So, include missing voices is a practical way to make the conversation fairer and smarter.
191
The fifth phrase was, choose a safer path.
192
This is useful when every option has a trade-off.
193
Right.
194
Safer does not mean weak.
195
It can mean more controlled,
196
more responsible, or easier to learn from.
197
The beta was slower, but it protected the customer experience and gave the team better learning.
198
So, choose a safer path is a good phrase when speed is tempting but risk is high.
199
Finally, Alex said, use a decision rule.
200
That connects to criteria.
201
A decision rule makes the next step clear.
202
If this condition is met, we do one thing.
203
If not, we do another.
204
Exactly.
205
It reduces vague debate and gives the team a shared standard.
206
In the scene, the rule was simple.
207
If new users succeed, launch wider.
208
If not, keep testing.
209
Let's turn this into practical meeting language.
210
We'll go slowly so you can hear how to use each tip.
211
First tip, ask before accepting.
212
This means you pause before agreeing with the first idea.
213
A good phrase is, can we question the default for a moment?
214
It sounds careful, not confrontational.
215
Use ask before accepting when a decision feels too automatic or when the room agrees too quickly.
216
The key is to ask with curiosity, not with judgment.
217
Second tip, check multiple sources.
218
This is about evidence.
219
Before you say something is true,
220
compare different inputs, data, customer comments, team experience, and timing.
221
You might say, let's compare the signals before we decide.
222
That is, check multiple sources in action.
223
It protects you from making a big decision based on one loud data point.
224
Third tip, zoom out briefly.
225
This brings context into the conversation.
226
You don't need a long analysis.
227
Just ask how the issue connects to customers,
228
cost, timing, or team capacity.
229
For example, let's step back first.
230
What else does this affect?
231
That's a practical use of zoom out briefly.
232
This is helpful when people are stuck on one detail.
233
Fourth tip, invite other angles.
234
This helps reduce bias.
235
A strong question is, who are we not hearing from?
236
Or, what angle have we missed?
237
Use invite other angles when the discussion feels one-sided,
238
or when the same people are driving the decision.
239
It makes the meeting more inclusive and often improves the decision.
240
Fifth tip, state the cost.
241
This is about trade-offs.
242
Every serious decision has a cost.
243
You gain something, but you usually give something up.
244
A clear pattern is, we gain speed,
245
but we give up confidence.
246
That is, state the cost in plain English.
247
It helps people see the decision more honestly.
248
Sixth tip, set the standard.
249
This is about criteria.
250
Before comparing options, agree on what matters most,
251
cost, customer impact, timeline, or risk.
252
You can say, let's set clear standards before we compare the options.
253
That's set the standard in action.
254
Once the standard is clear,
255
the decision feels less personal and more objective.
256
The goal is not complicated English.
257
The goal is clear questions and clear reasons.
258
Try one phrase in your next meeting when the decision feels rushed or unclear.
259
Let's recap today's critical thinking language.
260
Our six vocabulary items were Assumption,
261
Evidence, Context, Bias, Trade-off, and Criteria.
262
From Scene 1, question the default,
263
compare the signals, and step back first.
264
Also remember, check every angle,
265
name both sides, and set clear standards.
266
From Scene 2, slow the reaction,
267
test the numbers, and add the user story.
268
Then include missing voices, choose a safer path,
269
and use a decision rule.
270
For practice, ask before accepting,
271
check multiple sources, zoom out briefly, and invite other angles.
272
Also, state the cost and set the standard before comparing options.
273
Critical thinking is about slowing down at the right moment,
274
not slowing everything down forever.
275
Thanks for listening to Business English Podcast.
276
Keep asking better questions, and we'll see you next time.
앱 다운로드
당신이 말하는 모든 문장을 AI가 채점
TRENDING
인기 동영상
이 수업에 대하여
이번 수업에서는 직장에서의 비판적 사고에 대해 다룹니다. 비판적 사고는 더 나은 질문을 하고, 자신의 논리를 점검하며, 결정을 명확하게 설명하는 데 도움을 줍니다. 이 수업을 통해 업무에서 자주 사용되는 6개의 핵심 어휘와 12가지 비즈니스 영어 표현을 배워보겠습니다. 이번 학습은 세밀한 사고, 존중하는 반론, 그리고 강력한 비즈니스 판단을 위한 언어 능력을 키우는 데 중점을 둡니다.
핵심 어휘 및 구문
- 가정(Assumption): 사람들이 완전히 확인하지 않고 사실로 받아들이는 아이디어입니다.
- 증거(Evidence): 결정을 지원하는 사실이나 정보입니다.
- 맥락(Context): 문제를 둘러싼 넓은 상황을 의미합니다.
- 편향(Bias): 판단을 덜 공정하거나 정확하게 만들 수 있는 사고 습관입니다.
- 균형(Trade-off): 두 가지 사이의 균형을 의미합니다. 예를 들어 속도와 품질 간의 균형입니다.
- 기준(Criteria): 옵션을 비교하거나 결정을 내릴 때 사용하는 기준입니다.
- 세부사항(Details): 논의의 특정 요소나 정보를 의미합니다.
- 신호(Signals): 특정 행동이나 선택을 나타내는 징후입니다.
연습 팁
이번 비디오에서는 정확한 발음과 톤을 연습하는 것이 중요합니다. 영어 쉐도잉 기법을 활용하여, 패턴을 반복하고 발음을 교정해 보세요. 비디오의 속도가 빠르지 않으므로, 처음에는 조금 느리게 따라 해보고, 그 후에 점차 속도를 높여 보세요. 비디오를 시청할 때, shadowspeak를 활용하여 각 대사를 듣고 즉시 따라 해 보세요. 이 과정은 영어 발음 교정에 매우 효과적입니다. 마치 대화를 나누는 것처럼 자연스럽게 표현하고, 필요시 멈추어서 여러 번 반복하세요. 이렇게 하면 영어 회화 연습에 큰 도움이 될 것입니다.
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.
☕ 커피 한 잔 사주기
ShadowingEnglish는 여러분의 지원 덕분에 100% 무료로 운영됩니다. 서버 및 AI 유지 비용이 많이 듭니다. 여러분의 커피 한 잔이 큰 힘이 됩니다! ��