Shadowing Practice: Trust the Process: How to Design Teams That Actually Work - Learn English Speaking with Video
Ders oluşturuluyor...
1
Swift trust can help your communication and your teams be more effective.
2
My name is Matt Abrahams, and I teach strategic communication at Stanford Graduate School of Business.
3
Welcome to Think Fast, Talk Smart, the podcast.
4
Today, I look forward to speaking with Melissa Valentine.
5
Melissa is an associate professor in the Management Science
6
and Engineering Department at Stanford and a senior fellow at the Stanford Institute for Human -Centered Artificial Intelligence.
7
Her research focuses on how emerging technologies, including artificial intelligence and algorithms, are fundamentally transforming work, organizational design, and team dynamics.
8
Melissa, along with her co -author Michael Bernstein, wrote the fascinating book, Flash Teams, leading the future of AI -enhanced on -demand work.
9
Well, welcome, Melissa.
10
I'm really excited to have you join us.
11
Thank you.
12
This show is so fun, and I love the guests you have, so I'm delighted to be here.
13
Well, thank you.
14
And thanks for being one of them.
15
Should we get started?
16
Let's do it.
17
Excellent.
18
I have to say, I really enjoyed your book, Flash Teams, very much.
19
Really, really interesting.
20
Can you define for all of us what a flash team is and explain what people, processes, and infrastructure enable flash teams to get aligned and execute quickly?
21
So my PhD is in organization science, basically.
22
So I got my PhD at a business school.
23
And then my collaborator is a computer science professor, and he was doing a lot of work on crowdsourcing
24
so what's cool about crowdsourcing is um like the crowd is like millions of people online right
25
and you can get things done quickly
26
because you just like put a task out
27
and then there's millions of people who are available to come work on the task
28
but what he was seeing at the time that he
29
and i started working together was crowdsourcing was sort of stuck
30
because they were doing like really they call them like micro tasks
31
but just really like small tasks and then i had this toolkit organization science
32
and my dissertation had been about how you can use basically like team scaffolds
33
or like sort of lightweight team structures
34
and then like you you populate the team structure with experts
35
and the team structure and the role structure helps them know how to work together
36
so we sort of were able to combine the logic of both of these
37
so you have these like lightweight structures
38
that allow people who are like relative strangers to come together
39
and to work together on really complex stuff this system
40
that we built with like a great team of like a
41
PhD student Daniella Ratelny she organized this great lab at the time we first did our flash teams
42
so we built a platform that basically like took all the logic of organization science
43
and team science and then the speed and scale of crowdsourcing
44
and then like put them together so the way the system works we have this platform
45
where like i'm somebody who like wants to get something done
46
so i go to the platform i like design the team
47
and then the platform integrates with something like we used upwork
48
so there's like 10 million freelancers who are on upwork and then so i'll say here's the task that I need done.
49
Here's the role I need filled.
50
And then the platform can integrate with Upwork.
51
And then it's open call to like the 10 million freelancers.
52
Who's got the right expertise?
53
They join the team.
54
So you can just convene teams really fast.
55
And what we showed with this research is that like you can get things done really quickly.
56
You can pull teams together.
57
They build really complex stuff really quickly.
58
And it was really inspiring.
59
I mean, it's even faster now with Gen AI.
60
So you set a framework and expectations and then leverage a tool
61
that pulls people in and then the Flash team is really the focused, concerted effort that it's all about.
62
Can you talk to us a little bit about the structures that you can set up for teaming?
63
It sounds like you've done some research in that.
64
Give me an example of what a structure for efficient teaming looks like.
65
There's like three structures that are very useful for a Flash team.
66
The first is the role structure.
67
So that's going to be our relative expertise.
68
So let's say that I am I'm a UI designer and you're a front -end developer, like we get together and we know, I know what I'm responsible for.
69
I know the skills I need, I know the tools, the platforms, and you know that too.
70
And since we're both so expert at what we do, we can kind of negotiate it fast.
71
I can say, how is the screen gonna work for you?
72
Or you can say like, where is this functionality gonna come from?
73
And we just like negotiate it quickly.
74
Because we know each other's role.
75
Exactly.
76
Yes, and because we know people of that role, somebody else could plug in if you get sick or move on.
77
Excellent, I really like that.
78
Yeah, so the role structure.
79
So the second one is the team structure.
80
And the team structures are like what help a group know that they are accountable to each other.
81
And so for example, one team structure could be like everyone being responsible together for something.
82
Like maybe there's a team rating instead of individual ratings.
83
So that's what you're going to be looking for.
84
Individual ratings, then everyone is going to be like every person for themselves.
85
If it's a team rating, like everyone pulls together and is like, we're all in this together.
86
So it's how we team and how we assess the teaming.
87
Very powerful.
88
Students don't like group projects, right?
89
Because being all in it together can either be the best thing or the worst thing.
90
So the team structure.
91
And then the last one actually is hierarchy.
92
And hierarchy as a structure is about who has the right to make decisions, right?
93
In some ways, again, people don't necessarily think they like hierarchy, but hierarchy is so useful for coordination because you have...
94
you know five strangers show up together maybe everyone has a different idea of what should happen
95
but if you have this sense it's like another role structure
96
if you have a sense of who's the final decision maker
97
right a good enactment of hierarchy is they take in all the information they understand like what needs to happen
98
and they just communicate it clearly right
99
so like the coordination of the group happens through hierarchy that's fantastic
100
so so three primary roles that you just identified our role that is how we relate to each other in our expertise, the teaming, how we assess and work together and reward,
101
get rewarded, and then hierarchy or decision -making, which really determines how we can actually move forward.
102
That's right.
103
And I think all of us, regardless of if you're putting together a flash team or not, can think about those structures in your team that you currently have to help optimize it,
104
or if you're forming a new team, to think about that.
105
Thank you.
106
That's great.
107
You know, one of the essential elements of any teaming or groups coming together is trust.
108
What are some of the communication skills or other skills that people can deploy to establish trust quickly?
109
I'm assuming part of what flash teams do besides accomplish their work is they're able to coordinate action, perhaps through building trust.
110
Yeah, trust in flash teams is essential and complex, right?
111
Because it is relative strangers.
112
You get together and you work together really intensely and then you disassemble.
113
So I think that there's this idea in the literature called like swift trust.
114
And there's like an assumption that you just assume trust.
115
Like you just meet somebody for the first time, you assume they're competent, you assume that they know how to do their role, you assume you're both there for the same reason, to like work hard, get it done.
116
So that, yeah, the assumption of swift trust is really useful.
117
It doesn't always work out.
118
So I think it's, yeah.
119
But the sort of like offering of swift trust is part of it.
120
And then, yeah, paying attention to when it's not going right
121
and like being willing and able to kind of repair quickly is also important.
122
I love this idea of swift trust.
123
So you approach from a place of trust, assuming that you are trustworthy and I will trust you and you will do the same,
124
can expedite things because there's a lot of this testing that goes into trust and time.
125
And if you start from that place, and obviously, you know, it might fail or people could take advantage of it.
126
But the second part of what you said, I think really is the helpful part is to have
127
that meta awareness and watching for it and then being willing to speak up and try to repair it.
128
Yeah.
129
So I think it's not only swift trust being open to trust, but being open to repair when it's not there.
130
Yeah, exactly.
131
I really like that idea of swift trust.
132
So much in my life I think would be better if we just approached everything with this notion of idea.
133
Yeah.
134
I mean, there is a real difference because I think of the person I wrote the book with, Michael, he and I have worked together for 15 years now, and that is a different kind of trust than swift trust.
135
But swift trust is a tool that's useful.
136
Right.
137
And it's a way to at least initiate, and then you can build deeper trust in a relationship.
138
That can only happen, I think, after repeated exposure and time.
139
Totally.
140
Yeah.
141
You talk about discursive diversity, and I had to practice saying that multiple times, by the way.
142
Can you share what you mean by discursive diversity?
143
And how can teams recognize when they need to shift their communication style from a more open -ended,
144
brainstorming ideating to a very highly coordinated approach yeah so
145
that is from the dissertation of one of my really brilliant PhD students
146
so her name is Katarina Licks and she kind of invented that measure
147
so what she was able to do she had all of
148
the sort of like slack transcripts of different flash teams
149
and she was able to she did this NLP processing
150
and NLP is natural language processing yeah yeah before it was cool she learned how to do it
151
and she was able to create this measure where she was looking at like the similarity of the language
152
that people were using so you have all of the slack interactions
153
and you can basically compare people talking on the team
154
and how similar are the words
155
that they're using the sentence structure right are they using the same adverbs like adjectives sense of urgency gets encoded
156
and all of that
157
and what she was able to show is the the sort of similarity of the language
158
that people are using or the the difference
159
so this is where let's see right discursive diversity yeah
160
so like the diversity of discretion i guess like the diversity different types of words exactly yeah yeah
161
so that sort of would predict the team meeting a milestone in different ways
162
so there were times when you really want the language to diverge
163
so this is a moment of brainstorming ideation right you want
164
a lot of creativity you want a lot of divergence but then as you get closer to the deadline, you really, for the team to meet the deadline, then the language needs to converge.
165
Like people need to start sounding more like each other to hit the deadline.
166
So one, it's a measure really.
167
So you can, you can look at, you know, if I'm a manager or somebody looking back at doing a post -mortem or after a project is done, and I can look at the communication, be it Slack, JIRA, whatever the tool is.
168
And I can actually see the language might be a hint as to where we are.
169
Yeah, totally.
170
And as you're trying to get closer to the decision, more similar language is a sign.
171
What I'd be curious, and I don't know if there's any research on this, is can you actually use language to influence that?
172
So can I, as a manager, encourage more diverse language through ideation?
173
But when I want us to start moving towards a decision, encourage people to start using similar language.
174
I wonder if it's causal in that way.
175
Right.
176
I think that's a great research question.
177
I think that's really interesting.
178
So I encourage everybody listening to think about the language you're using for the different tasks you have
179
and start to notice what that looks like.
180
And maybe you can run your own experiment and play with that.
181
I want to keep on flash teams and then I want to have a broader question.
182
But when flash teams hit a snag, for example, like a miscommunication,
183
what is the most effective way to fix that so they don't fraction and deal with too much friction in those situations?
184
I'm so glad you asked this question.
185
I have an unpublished paper.
186
So we ran three really complex flash teams one summer, and we had all of the DMs.
187
So we had all the Slack front stage and then all of the Slack DMs, the backstage.
188
And the thing that was really interesting in analyzing all of that data is a lot of repairs happen backstage.
189
So something would happen in the public Slack channel
190
and then a dyad would go to the back channel and they'd be like, what is this bug?
191
And they would like kind of sort it out and then come front stage with the solution.
192
Oh, interesting.
193
So it created a lot of like smooth operations.
194
Like the Flash teams, they all, you know, accomplished their goal.
195
There didn't seem to be a ton of conflict.
196
So, this pattern of backstage repair was really interesting to discover.
197
I think, I mean, like any human behavior, it's got different sides to it.
198
So I think it did support smooth operation.
199
But what I saw in the analysis that I have not yet published is
200
that the people who were more involved in backstage repair ended up with more influence over time.
201
So these are the workers and the managers who were really helping make the decisions.
202
So it's something about like access to where the real problems get solved was like creating a lot of influence for people.
203
And I think that I don't totally know what to do with
204
that as someone who is interested in flash teams going well.
205
I would maybe say you need like a postmortem on a flash team.
206
What were the problems?
207
Who helped solve them?
208
What do we learn about this together?
209
It's really, really intriguing that the people involved in that repair or that dealing with those problems end up being more influential.
210
Yeah.
211
Yeah, because it's like they had like the realer story of what was going on, and sometimes it was like in the backstage repair that decisions were made and then presented as if they were quite done,
212
if that makes sense.
213
That's really intriguing.
214
I'm putting on my manager hat and thinking if I were in the midst of any team, be it a flash team or a regular team,
215
how I could be aware that the folks who are involved in helping fix, repair, dive deep into problems,
216
what that means for them in terms of their currency and how we interact on the public stage.
217
And I just think it's interesting that we now have these two channels and ways of communicating that can be measured.
218
I know you think about storytelling and change.
219
How can everyday employees in an organization use storytelling to drive broader systemic change
220
and build coalitions to help achieve whatever it is they're trying to achieve?
221
Yeah.
222
So one of the studies that I did when I first got to Stanford was actually an academic Cancer Center.
223
And I saw stories be really influential in this study.
224
So it feels a little different than what we've been talking about with AI and algorithms and so forth.
225
But it still to me is a study of organizational design, which is what I'm really interested in.
226
So in this, what happened in this study, so I was studying as this cancer center was trying to do a transformation.
227
They were trying to kind of decrease the coordination burden on patients and their families.
228
And during During the study, there was a group of patient advocates
229
or activists who really wanted the Cancer Center to understand how much coordination they were having to do.
230
So the way that they made their case, this is why I'm thinking of it, is they had an initiative they called patient stories.
231
And so they collected, they went to great effort to collect a lot of patient
232
stories where patients just talked about like a family member had
233
to quit their job to become the full -time coordinator for the patient.
234
So they came up with dozens of patient stories.
235
And then in this paper that I have, I analyzed how they basically used the stories to make the case and to kind of spread the movement,
236
spread the message across the cancer center.
237
And at the end of the study, they had kind of convinced the cancer center to take on some of the coordination work.
238
So it ends up being this kind of end -to -end story of like patient stories, patient narratives, actually changing the organizational design, which is why I'm thinking about it.
239
It was like a very powerful thing that these patient activists did.
240
Stories can really resonate and motivate people.
241
Was there anything specific to the stories that you think were really important?
242
Was it the fact that the stories accounted for all the specific coordination events?
243
Or was it the emotionality?
244
Or was it the fact that these people just collected a bunch of stories and the Cancer Center was like, wow, there are all these stories, we should probably do something.
245
I think a lot of us interface with the healthcare system and we could just like see ourselves.
246
So the patient stories were just like, this is us, this is you and me.
247
So there's a connecting piece there.
248
Yeah, really connecting piece.
249
And then it illustrated the problem really specifically.
250
So like somebody is like, you know, sitting in a wheelchair in a hallway cause they'd sort of been dropped or something like that.
251
And so it's like, wait, like I think the cancer center is so full of people who care
252
and then hearing like the specific instance in a really relatable story, they were just like, oh, that's a problem that I can help with.
253
I think you hit on it.
254
It's relatable and real.
255
Yeah.
256
And we can connect.
257
Thank you.
258
Can you take what you've learned about Flash Teams
259
and give us any insight that we can just apply to a normal team?
260
So I've got a team that's been around for a while and we meet regularly.
261
Is there any insight from your work on Flash Teams that could perhaps help my team be more efficient, feel more connected, ideate better?
262
One thing that Michael and I used to say when we were writing the book, we were trying to think of, like, what's the mindset here that, like, any manager would find empowering?
263
And the phrase we came up with is experts everywhere all the time.
264
So you've got your, like, trusted team.
265
Great.
266
You know, keep working together, taking good care of each other, working hard.
267
But, like, really recognize that your organization, the world, the Internet, your friends,
268
like, the world is just full of experts who can help and people like helping and bringing their expertise to something.
269
So it's just like having a mindset of like recognizing how much collaboration is available, how much expertise is available. And yeah,
270
so maybe it like invites you to kind of like think of the boundaries of the team a little more porously.
271
Yeah, exactly.
272
That's funny you said that, because that was exactly the word I was thinking is porous is
273
that it can be very easy to insulate a team and say, this is the team, but being a little more open and pulling in expertise.
274
When I was managing a team, I ran a learning and development group, and we had this very tricky thing we had to train people on,
275
and it turned out that somebody in the company who was an admin was using our tool,
276
and they actually knew how to do things that we were trying to figure out how to train people on better.
277
That person was an expert, and by just dumb luck, we figured that out and incorporated them into the team.
278
and I like that idea.
279
I think that there are a lot of tools that can be very helpful to managers
280
in terms of how the team like works together, coordinates and stuff like that.
281
So, you know, like having an eye towards, the other thing we said in the book is like AI driven team design.
282
So just making use of the tools to be very thoughtful in how you're structuring your team.
283
So AI can help us structure the team and maybe even identify who some of the experts are that we might know.
284
I love that.
285
Melissa, this has been great.
286
Before we end, you know, I like to ask three questions when I make up just for you.
287
And two, I've been asking everybody, are you up for that?
288
Yeah, let's do it.
289
Beyond the academic research you do, you're also a creator and you study the algorithms that serve up information on social media.
290
What advice do you have for others who are creators?
291
Okay.
292
So I love Instagram and TikTok.
293
Like I have, I think it's people have like complicated relationships with social media.
294
So the attention stuff is real.
295
My attention span is shot.
296
But I have learned so much from content creators.
297
I am such a fan.
298
My advice is keep going.
299
If you're an expert, put it out in the world.
300
People will find it.
301
I mean, different life transitions I've gone through, different health stuff, different fitness stuff, different hobbies.
302
I have learned so much from the internet.
303
So thank you, content creators.
304
You know, as a creator myself, and it took me a while to identify as a creator, But, you know, I think many of us are motivated to help people
305
and it's that motivation that actually helps us get through.
306
I mean, it's hard to put out the content and the algorithm can sometimes help you and sometimes not.
307
So it's that passion and that desire to learn and to help, I think, that really motivate.
308
And I can hear that in your voice and see it in the things that you post and create.
309
Question number two, who is a communicator that you admire and why?
310
So I'm at a moment where I'm thinking a lot about communication, where we like really like take each other in, in like a really deep way.
311
So I have a friend who is a therapist and a Buddhist, and she just like, she has like a quality of like listening and expression that,
312
that allows for like.. true communication.
313
So I would say I'm going to nominate her.
314
Excellent.
315
And it's really that presence and listening and being there.
316
It's a fascinating thing about being very aware of yourself that allows you to be very aware of others.
317
It is a lot of presence, as you're saying, a lot of presence and connection.
318
I like that self -awareness and other awareness.
319
Thank you.
320
Final question.
321
What are the first three ingredients that go into a successful communication recipe?
322
Something that I've come to appreciate is how useful a deep awareness of your own experience is, because then you're even more able to take in another's and all of its complexity.
323
So yeah, self -awareness, other awareness, and then working from there, I think what's possible between you is new.
324
It's something that neither of you would have done without that kind of connection.
325
I sort of bristle at the word synergy, but in this case, that's exactly what you're talking about is the power of the two is greater than either individually.
326
But that comes, as you said, from a self -awareness and then another awareness.
327
Well, thank you.
328
Thank you for the three ingredients and thank you for the conversation.
329
Your work to me is really intriguing because it focuses both on technology, but the human aspect of people coming together and the fact
330
that there are structures that we can rely on to help expedite and make things more efficient.
331
Melissa, this has been fantastic.
332
Thank you.
333
And thank you for the work you do totally really fun
334
for me too thank you thank you for joining us for
335
another episode of think fast talk smart the podcast to learn
336
more about groups listen in to our episode 241 with colin fisher
337
and to learn more about social media algorithms please check out episode 268 with angelie christine
338
this episode was produced by katherine reed ryan campos
339
and me matt abrahams our music is from floyd wonder with
340
special thanks to podium podcast company please find us on youtube and wherever you get your podcasts.
341
Be sure to subscribe and rate us.
342
Also, follow us on LinkedIn, TikTok, and Instagram.
343
And check out fastersmarter .io for deep dive videos, English language learning content, and our newsletter.
344
Please join us for our Think Fast Talk Smart Learning Community at fastersmarter .io slash learning.
345
You'll find video lessons, learning quests, discussion boards, an AI coach, and book club opportunities.
346
Again, that's fastersmarter .io slash learning to become part of our ThinkFast, TalkSmart learning community.
📺 Aynı Kanal
B21
Talk Back: Why Arguing With Yourself Can Help You Flourish
Business EnglishUniversity StudentsWorking Adults
B21
Quick Thinks: Network Smarter and Make Better Connections
Business EnglishUniversity StudentsWorking Adults
B21
Communication Has An INVISIBLE Layer And It Is Hiding In Plain Sight!
Business EnglishUniversity StudentsWorking Adults
B21
The Leadership Skills We’ll Need Most When Everything Is Changing: Me2We 2026
Business EnglishUniversity StudentsWorking Adults
B1What 300 Episodes Has Taught Us
Business EnglishUniversity StudentsWorking Adults
B22
Why Every Question Is A Gift
Business EnglishDaily ConversationUniversity Students
B23
Shark Tank's Daniel Lubetzky: The Pitch Mistake That Loses Investors
Business EnglishDaily ConversationUniversity Students
C11
A Matter of Meaning: What Other People Teach You About Your Communication
Business EnglishUniversity StudentsWorking Adults
B2Quick Thinks: A CLEAR Way Through Conflict
B21
Don't Lose the Room: How to Make Ideas Stick
Business EnglishDaily ConversationUniversity Students
B22
The First 5 Seconds: How to Start a Speech the Moment All Eyes Suddenly Turn to You | AMA
Business EnglishDaily ConversationUniversity Students
C14
The Respect Effect: What Stereotype Threat Teaches Us About Communication
Business EnglishUniversity StudentsWorking Adults
B26
Ask Matt Anything: Don’t Let Your Communication Fizzle at the Finish
Business EnglishDaily ConversationUniversity Students
B27
3 Techniques for Managing Speaking Anxiety
Business EnglishInterview EnglishUniversity Students
B23
Message Market Fit: Turning Great Ideas Into Communication That Lands
Business EnglishUniversity StudentsWorking Adults
B21
Quick Thinks: How to Have Better Conversations About Aging
Business EnglishDaily ConversationUniversity Students
C115
Future You: Unconventional Ways in which Your Future Self Benefits You
Business EnglishUniversity StudentsWorking Adults
B21
Communicating the Future: Defining Where We Want AI To Take Us
Business EnglishDaily ConversationUniversity Students
C11
Ask Matt Anything: Authenticity, Anxiety, and Answering Well
Business EnglishDaily ConversationUniversity Students
B21
Happiness And Time Management: Time Track Your Day For A Happier Life
Business EnglishUniversity StudentsWorking Adults
✨ Video Öner
C14
321 cümleler
8 Tech Choices to Lock In Before Agentmaxxing
Business EnglishUniversity StudentsWorking Adults
C1762 cümleler
Building Anthropic | A conversation with our co-founders
Business EnglishUniversity StudentsWorking Adults
B21
83 cümleler
User Flow vs Task Flow in UX Design
Business EnglishUniversity StudentsWorking Adults
B217 cümleler
Did someone say... SecondBrain?
American AccentBusiness EnglishUniversity StudentsWorking Adults
B21
321 cümleler
How One of NYC’s Fastest-Growing Startups Scaled to $5 Billion
Business EnglishUniversity StudentsWorking Adults
B21
305 cümleler
The Secret to Finding Perfect Timing | Daniel Pink
Business EnglishUniversity StudentsWorking Adults
C1549 cümleler
The HR Dialogues #49 | Key Elements of a High-Performance Culture: What HR Needs To Know
Business EnglishUniversity StudentsWorking Adults
C12
20 cümleler
Is prompt engineering dead? Advice on optimizing AI interactions | Amazon Web Services
Business EnglishUniversity StudentsWorking Adults
C12
244 cümleler
Real-Time Digital Twins Using CFD, Sensors & AI - Haris Kokkinos | Podcast #165
Business EnglishUniversity StudentsWorking Adults
B2165
28 cümleler
Weekly Team Meeting: Project Status Update
American AccentBusiness EnglishWorking Adults
C13
17 cümleler
If Your Team Never Fails, It Isn’t Learning
Business EnglishUniversity StudentsWorking Adults
Bu dersin kelimeleri ve konuşma notları
Bu videoda gölgeleme çalışması için 346 cümle ve 4419 kelime var. Konuşma bölümü 22:06 sürüyor. Konuşmacı hızlı konuşuyor, dakikada yaklaşık 200 kelime; bu yüzden birbirine bağlanan ve zayıflayan sesler duyacaksınız. Kelimelerin %85’i İngilizcede en sık kullanılan 3.000 kelime arasında; geri kalanına başlamadan önce bakmakta fayda var.
Bu videodaki önemli kelimeler
Videodan öğrenmeye değer 15 kelime, telaffuzu ve anlamıyla:
| Kelime | Telaffuz | Anlam |
|---|---|---|
| repair fiil | /ˈɹiːpɛɚ/ | onarmak, tamir etmek |
| swift isim | /swɪft/ | ebabil, dağ kırlangıcı |
| awareness isim | /əˈwɛɹ.nəs/ | bilinç, bilinçlenme |
| hierarchy isim | /ˈhaɪ.ə.ɹɑː(ɹ).ki/ | hiyerarşi |
| expertise isim | /ˌɛkspɜːˈtiːz/ | ustalık |
| coordination isim | /kəʊˌɔːdɪˈneɪʃən/ | dayanışma |
| slack sıfat | /slæk/ | gevşek |
| diversity isim | /daɪˈvɜː(ɹ)sɪti/ | çeşitlilik |
| algorithm isim | /ˈælɡəɹɪðm̩/ | algoritma |
| relative isim | /ˈɹɛl.ə.tɪv/ | akraba |
| encourage fiil | /ɪnˈkʌɹ.ɪd͡ʒ/ | teşvik etmek, cesaretlendirmek |
| efficient sıfat | /ɪˈfɪʃənt/ | verimli |
| stranger isim | /ˈstɹeɪnd͡ʒɚ/ | yabancı |
| podcast isim | /ˈpɑdˌkæst/ | podcast |
| deadline isim | /ˈdɛdˌlaɪn/ | mühlet, deadline |
Duyacağınız deyimsel fiiller
| Kelime | Anlam |
|---|---|
| check out fiil | gözden geçirmek |
| get together fiil | toplanmak, buluşmak |
| figure out fiil | açığa çıkarmak |
| look forward to fiil | iple çekmek, dört gözle beklemek |
| put out fiil | çıkarmak |
| put together fiil | birleştirmek, bir araya getirmek |
| show up fiil | ortaya çıkmak |
Bu videodaki dil bilgisi
Konuşmacının en çok kullandığı yapılar, videodaki sözcüklerin aynısıyla:
| Yapı | Videoda |
|---|---|
| Present perfect continuous have/has been + -ing — önceden başlayıp hâlâ süren bir eylem | we've been talking · I've been asking |
| Present perfect have/has + fiilin üçüncü hâli — geçmişte olan ama şimdi de önemli olan bir eylem | you've done · have worked · you've learned |
| İlgi cümlecikleri who / which + cümle — bir kişi ya da şey hakkında ek bilgi | people who are · somebody who like · people who were |
| Edilgen yapı be + fiilin üçüncü hâli — kimin yaptığı değil, ne olduğu önemli | is done · were made · are involved |
Dikkat edilecek telaffuzlar
Konuşmacı I'm, you're, don't gibi kısaltılmış biçimleri 56 kez kullanıyor. Bunları duyduğunuz gibi kısa söyleyin.
- “th” sesleri: algorithm /ˈælɡəɹɪðm̩/, smooth /smuːð/, therapist /ˈθɛɹəpɪst/, thoughtful /ˈθɔːtfəl/, trustworthy /ˈtɹʌst.wɜː.ði/
- “sh” ve “zh” sesleri: flash /flæʃ/, coordination /kəʊˌɔːdɪˈneɪʃən/, efficient /ɪˈfɪʃənt/, organizational /ˌɔː(ɹ)ɡənɪˈzeɪʃənəl/, artificial /ˌɑː.tɪˈfɪʃ.əl/
- Uzun kelimeler — vurguyu doğru yere koyun: hierarchy /ˈhaɪ.ə.ɹɑː(ɹ).ki/, coordination /kəʊˌɔːdɪˈneɪʃən/, diversity /daɪˈvɜː(ɹ)sɪti/, organizational /ˌɔː(ɹ)ɡənɪˈzeɪʃənəl/, coordinate /koʊˈɔɹ.dəˌneɪt/
Bu videoyla nasıl çalışılır
- Videonun tamamını konuşmadan bir kez dinleyin ve bilmediğiniz kelimeleri not edin.
- 0,75× hızla başlayın, cümle cümle tekrar edin ve kolaylaşınca normal hıza dönün.
- Kendinizi kaydedin ve orijinaliyle karşılaştırın; repair, swift, awareness gibi kelimelere özellikle dikkat edin.
Gölgeleme Tekniği Nedir?
Gölgeleme, başlangıçta profesyonel tercüman eğitimi için geliştirilen ve çok dilli Dr. Alexander Arguelles tarafından popüler hale getirilen, bilim destekli bir dil öğrenme tekniğidir. Yöntem basit ama güçlüdür: ana dili İngilizce olan bir sesi dinler ve hemen yüksek sesle tekrar edersiniz — konuşmacıyı 1-2 saniye gecikmeyle takip eden bir gölge gibi. Pasif dinleme veya dilbilgisi alıştırmalarının aksine, gölgeleme beyninizi ve ağız kaslarınızı gerçek konuşma kalıplarını eşzamanlı olarak işlemeye ve yeniden üretmeye zorlar. Araştırmalar, telaffuz doğruluğu, tonlama, ritim, bağlı konuşma, dinleme anlama ve konuşma akıcılığını önemli ölçüde geliştirdiğini göstermektedir — bu da onu IELTS Konuşma hazırlığı ve gerçek dünya İngilizce iletişimi için en etkili yöntemlerden biri yapar.