Shadowing-Übung: How to Build An MVP | Startup School - Englisch Sprechen Lernen mit Video

Übungsmodus wählen

Jeder Modus öffnet einen Übungsraum im Vollbild.

260 Sätze
Wenn Sätze zu kurz oder zu lang sind, klicke auf Edit, um sie anzupassen.
1
All right, today I'd like to talk to you about how to build an MVP or a minimum viable product.
2
So if you haven't seen this before, this is a meme that we love to talk about when trying to help founders with their MVP.
3
It's called the Midwit meme.
4
The person who is the Jedi, the super intelligent, the founder who's doing all the best things and knows all the best things and the idiot,
5
the first time founder, the founder who has no idea what's going on.
6
Many times these two founders will actually come to the right decision before the founder who is really smart
7
and is trying to work really hard and do everything right.
8
And so in this situation with the MVP, the best advice is to actually launch something quickly and iterate,
9
get a product into the hands of your customers and then learn whether it helps them or doesn't and then iterate it, improve it over time.
10
The wrong answer is to do a hundred surveys
11
and 600 user interviews and contact every single one of the competitors and spend,
12
you know, a year fundraising and hire a hundred people and,
13
you know, all these other things that you can distract yourself with that it might appear like other smart things,
14
but in reality, they really don't highlight the most important point about an MVP,
15
which is you'd only really start learning about your user when you put a product in front of them.
16
That doesn't mean that the thing you build in your MVP is going to work, right?
17
It's probably not going to work.
18
It's just the best way to start the conversation with the user and how you can solve their problems.
19
So to summarize that point, The goal
20
that you should have as an early stage founder is you should be getting a product out into the world quickly, minimum viable product.
21
Second, you should be talking to some initial customers
22
and trying to figure out what you can do to make that product useful for them.
23
You should care about how to help them accomplish their goals.
24
And you should try to figure out how can I change
25
and iterate my product so that it actually helps them accomplish those goals.
26
And then rinse and repeat.
27
Talk to more users, iterate your product, talk to more users, iterate your product.
28
More often than not, after three, four, five, six iterations, your VP is going to be very different.
29
You have learned so much.
30
But by having that conversation with users and by letting them see your product evolve, you can actually make them more excited,
31
more likely to use your product, more likely to pay for your product.
32
And you can learn 10 times more than just talking to your co -founders or thinking about in your head.
33
So the challenge today is that a lot of people are knocking MVPs.
34
A lot of people are talking about minimum lovable products or minimum useful products.
35
And honestly, a lot of founders actually just want to build, you know, God level products, you know, the Steve Jobs level,
36
make the iPhone and change the world.
37
There's this misconception that starting with something small that might not work very well is a bad idea.
38
There are a lot of people who worry that
39
if you start with something small and you give it to a customer and the customer doesn't like the product,
40
you'll never be able to talk to them again.
41
What I will tell you is this.
42
In most cases, the people who are interested in talking to a startup are early adopters.
43
They're used to using products that don't work very well.
44
and the reason why they're talking to you is not
45
because they think your product's going to work great it's
46
because they have a real problem and they're open to using new software
47
so you don't have to worry about losing these people these
48
are the kinds of people who try new products all the time these are the kinds of people
49
if you tell them hey look I can't promise it's going to work perfectly from day one
50
but if you keep working with me we'll make it better
51
and make it better
52
and I'll make sure it works for you over time these are the kinds of people who respond to that pitch.
53
It turns out the people who will run away after seeing your product break and never use you again,
54
they're never going to try your product in the first place.
55
They're not early adopters.
56
They don't use new software.
57
So you don't have to worry about losing those people because you never had them.
58
You're not going to get them to get started.
59
Now, one of the things we have to work on at YC a lot is fear.
60
And this is the biggest fear that founders have is a non -specific fear of,
61
oh my God, if I give people my product and they don't like it, boom, my company dies.
62
And it's always like hilarious because when we think about this, it's like, well, your company doesn't actually die, right?
63
Like it doesn't die tomorrow.
64
It's not like game over.
65
You haven't run out of money.
66
All your co -founders aren't going to quit.
67
Whenever we encounter these fear scenarios, we like to dig in and kind of ask like, well, what would actually happen?
68
Like imagine the worst case scenario.
69
You do talk to a customer.
70
You do demo your product.
71
It doesn't work.
72
They don't want to use it.
73
You wake up the next day, is anything that different?
74
Can't you reach out to someone else?
75
Can't you reach back out to that customer who you demoed to a week later when you've made the product better?
76
Is your startup actually dead?
77
More often than not, when you have this fear, what you should be doing is kind of leaning into it and asking yourself,
78
is this fear real?
79
Is my company actually going to die if this scary thing happens?
80
And it's not bad to feel the fear, but it is bad to act on it.
81
It is bad to spend one year building your MVP because you're afraid the first customer might not like it.
82
Now, there's another group of folks who thinks, I know what the perfect product is, and I know it's going to take a year to build.
83
Why would I build shitty versions of it?
84
I like to call these folks fake Steve Jobs, and it's really a massive misconception of what great product people do.
85
A lot of people thought of Steve Jobs as the kind
86
of person who could just imagine great products in his mind and then bring them out into the world.
87
But what's funny is that most of the time when people think about the products that Steve Jobs is most known for,
88
let's say the iPod and let's say the iPhone,
89
people don't take enough time to look at all of the different iterations of those products over time.
90
Often when someone tells me like, oh, well, you know, Steve Jobs released an amazing phone first time,
91
I say, well, do you remember that the iPhone started without an app store?
92
Do you remember you couldn't take video with the first iPhone?
93
Do you remember the first iPhone only had 2G and not 3G.
94
So really, really, really bad internet.
95
Like most people don't remember that.
96
Most people, the iPhone that they actually think of as iPhone was like the third or fourth iteration of the iPhone.
97
The first version of the iPod had like an actual physical
98
scrolling device where like sand would get stuck into it and it would break all the time.
99
Even the great Steve Jobs iterated his products over time.
100
So if you find yourself being a fake Steve Jobs thinking, I know exactly what the customer needs.
101
I just need to raise $10 million, spend a year building it and then launch it.
102
Think again, right?
103
Like if Steve Jobs needed multiple tries to get his products right, maybe you need to as well.
104
Next, let's look at some examples.
105
And in all these examples, you're going to see three pretty simple points.
106
First, all of these products were fast to build.
107
They could get out of the market quickly.
108
Second, they all had very limited functionality.
109
The third, and interestingly enough, all these products appealed to a small set of users.
110
These founders realized that just making something
111
that a small group of people's loved was far more important than making something
112
that could address all the needs of all potential customers from day one
113
so here's what the first version of airbnb looked like and
114
if you were a user when airbnb first launched here are some of the fun things
115
that you didn't get to experience
116
there were no payments
117
if you found a place on airbnb
118
you couldn't pay for it there you had to arrange for payment some other way there was no map view
119
so there was no way for you to actually see where the places were in the city.
120
That's a pretty basic one.
121
Three, even more funny, you had to stay on an airbed.
122
Like you couldn't rent out your whole house.
123
You couldn't rent out a room in your house.
124
Then fourth, the first version of Airbnb only worked for conferences.
125
They would literally spin it up in a city when there was a conference.
126
And when the conference was over, they'd spin it down.
127
That was Airbnb to start.
128
That was the MVP.
129
Here's a second example.
130
This one's my company, Twitch.
131
Twitch started as a site named JustinTV, where my co -founder Justin had a camera on his head that broadcasts 24 -7.
132
In the first version of Twitch, there was only one page, the page that you're seeing here.
133
There was only one streamer.
134
His name was Justin.
135
There was no video games, except for like we randomly would play video games sometimes like
136
Guitar Hero or something like that.
137
And streaming was ridiculously expensive.
138
We were paying a CDN.
139
We hadn't built our video system yet.
140
But this was the first version of our product.
141
Now, when you go to Twitch, it's completely different.
142
But this is where it started.
143
Finally, we have Stripe.
144
This was the first version of Stripe.
145
Back then, it didn't even have the name Stripe.
146
It was called slash debt slash payments.
147
Back then, they had no fancy bank deal.
148
They were working with a tiny bank.
149
There was literally no direct APIs with that bank for setting up accounts
150
so they'd have to call the bank and every night file manual paperwork for you to get your account set up.
151
And there are almost no features in their API.
152
The first version of Stripe was so basic
153
that even us back in the day at Twitch couldn't use it because it didn't have enough features.
154
But the folks who could use it were early stage YC startups who all
155
they wanted to do was accept simple credit card payments from their customers.
156
That's all Stripe did in the beginning and that was more than enough to get started.
157
So you might ask yourself, who are these people who actually want to use crappy MVPs?
158
You're telling us that they're going to be built fast.
159
They're going to probably not work that well.
160
And we're going to have to iterate the hell out of them in order to actually make them good.
161
Who are these early adopters who'd want to go through that experience?
162
There's this fun analogy that I was told as an early stage founder.
163
It was, you want to build your first version for customers who have their hair on fire.
164
And I never quite understood what that meant.
165
I mean, it makes sense, I guess, but I always found it more useful when I attached a story to it.
166
So imagine that you are a person and your hair is on fire right now as you're watching this.
167
Now imagine if I was sitting in the room next to you.
168
What is the thing that you wish I could sell you to solve this problem?
169
Your hair is currently on fire.
170
Probably most of you will think some version of a bucket of water, a hose, some kind of water thing.
171
Now that is a great product.
172
That's like the iPhone today.
173
That would solve your product immediately.
174
I don't have that.
175
I'm a founder.
176
I've got an MVP.
177
What I'm selling is a brick.
178
Now, what would you do if I was selling you a brick?
179
Now, some of you are like, well, I would leave the room.
180
I couldn't use a brick.
181
Bullshit.
182
Your hair's on fire.
183
You would buy that brick and you would hit yourself on the head with the brick to smother the fire.
184
That's an MVP paid.
185
It's not the perfect solution, but you are in so much pain as a customer, you will use a non -perfect solution to solve your problem.
186
That's the customer you should be going after.
187
For customers who are not desperate, you can wait.
188
You don't have to go after them now.
189
Just go after the desperate ones first.
190
It'll make your life a lot easier.
191
Now, I know some of you, especially those who've gone to business school, I know a lot of you have said, I can skip this step.
192
Instead of building an MVP, iterating, iterating, why don't I just survey my users?
193
Why don't I just talk to 100 users and they'll tell me what to build?
194
I wish this is the case.
195
I wish that users could just tell you what to build.
196
And then if you built those things, you'd win.
197
In fact, I think every business wished that was the case.
198
Here's the problem.
199
Your customers are experts in their problem, but they actually don't have all of the answers on how to solve their problem.
200
That's your job.
201
That's the job of the person who's building a new product.
202
Surveys might help you understand the pain that your customer is going through, but they will never help you figure out how to solve that pain.
203
The only time that you start having that conversation with the customer is
204
when you can put a product in front of them, preferably a crappy MVP, and start saying, does this solve your problem?
205
I haven't really seen a shortcut to this step.
206
I haven't seen a shortcut of building something pretty fast that's pretty crappy to get started.
207
And even for larger companies, even for enterprise software companies, if you go back in time, the first versions of their product, they were not perfect.
208
They were far from it.
209
They were the minimum that those customers as we're willing to use.
210
So across the entire board, you got to start with the minimum viable product.
211
I think one of the most important points
212
that I want to leave you with is that you don't start your startup with all the answers.
213
Building a startup, especially the first phase of building a startup pre -product market fit, is all about learning.
214
It's all about taking some of the insights
215
that you start with bring them to the market
216
and learning most of the solutions most of the best parts of products
217
we use today were discovered after those products were launched
218
when those founders were learning from their users and building
219
and launching mvp is the fastest way to start the process of learning
220
and the faster you learn the more likely you are to build something that people love before anyone else.
221
So let's say I've convinced you that now you actually want to build an MVP.
222
How do you make sure you do it quickly?
223
Here's some tricks.
224
One, give yourself a very specific deadline.
225
It's a lot easier to make sure
226
that you're building something that's the minimum viable product
227
if you give yourself two weeks or a month or a month
228
and a half to complete it versus
229
if you don't give yourself a deadline second write down your spec
230
if you think that there are five
231
or ten features required in order to launch an mvp write
232
them all down don't put yourself in the position where you're constantly trying to figure out should we have
233
that feature should we not have that feature i don't remember the feature we talked about the other day?
234
How should it look?
235
How should it work?
236
If you write it down, then you can just focus on building instead of continuously debating what should be built.
237
Number three, cut that spec.
238
After you write all that stuff down, go through each one of those items and ask yourself,
239
does a truly desperate customer need that feature to start?
240
You'd probably be surprised at how many features you can leave off for the second,
241
third, or fourth version of your product and just get the basic stuff out first.
242
And then number four and most important, don't fall in love with your MVP.
243
It's going to change.
244
You're going to iterate it.
245
It's going to get very, very, very different over time.
246
You want to do it fast and you don't want to fall in love with it.
247
You want to fall in love with your customer,
248
with your user, not in love with the crappy initial product that you're building to start learning from that user.
249
All right, so hopefully you don't need any more convincing.
250
You understand that the simplest and easiest path and the smartest and most
251
Jedi path is to build and launch your product and then iterate it.
252
And so I wish you all a lot of good luck.
253
And while you're building, remember one thing,
254
it's far better to have 100 people love your product than 100 ,000 who kind of like it.
255
So when you're releasing that MVP, it's totally okay to do things that don't scale and recruit those initial customers one at a time.
256
If you care about those customers, I promise you they will talk to you,
257
that you can work with them and you can help them figure out how to solve their problems and as a result,
258
help figure out how to build a great product for them.
259
Thank you very much and good luck.
260
Thank you.

App herunterladen

Alles, was du zum fließenden Sprechen brauchst

KI-AussprachebewertungJeder Satz bewertet
IPA-TrainingJeden Laut meistern
WortschatzBaue deinen Wortschatz auf
VokabelspielSpielend lernen

Gleicher Kanal

FOR YOU

Empfohlenes Video

Wortschatz und Sprechhinweise zu dieser Lektion

Diese Sprechübung basiert auf dem Video „How to Build An MVP“. Diese Wörter kommen am häufigsten vor: product, customer, mvp, founder, user. Dieses Video enthält 260 Sätze und 3102 Wörter zum Nachsprechen. Der gesprochene Teil dauert 16:37. Der Sprecher spricht schnell, etwa 187 Wörter pro Minute – rechne mit verbundenen und verkürzten Lauten. 89 % der Wörter gehören zu den 3.000 häufigsten im Englischen, der Wortschatz ist also leicht zu verfolgen.

Wichtiger Wortschatz in diesem Video

15 lernenswerte Wörter aus dem Video, mit Aussprache und Bedeutung:

WortAusspracheBedeutung
founder Substantiv/ˈfaʊ̯n.dəː/Gründer, Gründerin
solve Verb/sɒlv/lösen
startup Substantiv/ˈstɑɹtˌʌp/Inbetriebnahme
brick Substantiv/ˈbɹɪk/Backstein, Ziegel
viable Adjektiv/ˈvaɪəbəl/lebensfähig
desperate Adjektiv/ˈdɛs.p(ə.)ɹɪt/verzweifelt bemüht, sehnsuchtsvoll verlangend
folk Substantiv/foʊk/Volk
spin Verb/spɪn/rotieren, schleudern
convince Verb/kənˈvɪns/überzeugen
scenario Substantiv/sɪˈnɛəɹioʊ/Szenario
deadline Substantiv/ˈdɛdˌlaɪn/Stichtag, Frist
demo Substantiv/ˈdɛm.oʊ/Demonstration
accomplish Verb/əˈkɑm.plɪʃ/vollenden vollziehen, ausführen
meme Substantiv/miːm/Mem
guitar Substantiv/ɡɪˈtɑɹ/Gitarre

Phrasal Verbs, die du hören wirst

WortAusspracheBedeutung
figure out Verbherausfinden
set up Verb/ˌsɛt ˈʌp/aufbauen, für den Einsatz vorbereiten
run away Verbwegrennen, davonlaufen
turn out Verbsich herausstellen als/dass, sich erweisen als
wake up Verb/ˌweɪk ˈʌp/aufwachen, erwachen
write down Verbaufschreiben

Sätze zum Wiederholen

Kurze, vollständige Sätze aus dem Video, die du im Alltag wiederverwenden kannst:

  • You're not going to get them to get started.
  • You haven't run out of money.
  • Can't you reach out to someone else?
  • Do you remember you couldn't take video with the first iPhone?
  • How do you make sure you do it quickly?

Grammatik in diesem Video

Die Strukturen, die der Sprecher am häufigsten verwendet, mit den genauen Worten aus dem Video:

StrukturIm Video
Bedingungssätze if + Satz, will/would + Verb – eine Bedingung und ihre Folgeif you keep working with me we'll make · if you built those things, you'd win
Present Perfect have/has + Partizip Perfekt – eine vergangene Handlung, die jetzt noch wichtig isthaven't seen · have learned · haven't run
Relativsätze who / which + Satz – eine Zusatzinformation über eine Person oder Sacheperson who is · people who worry · people who are
Passiv be + Partizip Perfekt – wichtig ist, was geschieht, nicht wer es tutwas called · be built · was told

Aussprache, auf die du achten solltest

Der Sprecher verwendet 85 Kurzformen und abgeschwächte Formen, zum Beispiel don't, you're, they're. Sprich sie in der kurzen Form, so wie du sie hörst.

  • Die Laute „sh“ und „zh“: accomplish /əˈkɑm.plɪʃ/, iteration /ˌɪt.əˈɹeɪ.ʃən/, misconception /ˌmɪs.kənˈsɛp.ʃən/, shortcut /ˈʃɔːtkʌt/
  • Lange Wörter – auf die Betonung achten: intelligent /ɪnˈtɛlɪd͡ʒənt/, hilarious /hɪˈlɛə.ɹi.əs/, continuously /kənˈtɪnjuəsli/, competitor /kəmˈpɛt.ɪ.tɚ/, analogy /əˈnæləd͡ʒi/

Laute, die Deutschsprachigen schwerfallen:

  • Stimmhafter Auslaut — /b/, /d/, /g/, /z/, /v/ am Wortende nicht verhärten: solve /sɒlv/, sand /sænd/, enterprise /ˈɛntəˌpɹaɪz/, arrange /əˈɹeɪnd͡ʒ/, evolve /ɪˈvɑlv/
  • /æ/ — offener als „ä“: sand /sænd/, fancy /ˈfæn.si/, manual /ˈmæn.j(u)əl/, randomly /ˈɹændm̩li/, attach /əˈtæt͡ʃ/
  • /dʒ/ — stimmhaft, nicht „tsch“: intelligent /ɪnˈtɛlɪd͡ʒənt/, arrange /əˈɹeɪnd͡ʒ/, analogy /əˈnæləd͡ʒi/

So übst du mit diesem Video

  1. Höre dir das ganze Video einmal an, ohne zu sprechen, und notiere die Wörter, die du nicht kennst.
  2. Beginne mit 0,75-facher Geschwindigkeit, sprich Satz für Satz nach und wechsle zur normalen Geschwindigkeit, sobald es leichtfällt.
  3. Nimm dich auf und vergleiche mit dem Original; achte dabei auf Wörter wie founder, solve, startup.

Was ist die Shadowing-Technik?

Shadowing ist eine wissenschaftlich fundierte Sprachlerntechnik, die ursprünglich für die professionelle Dolmetscherausbildung entwickelt und durch den Polyglotten Dr. Alexander Arguelles populär gemacht wurde. Die Methode ist einfach aber wirkungsvoll: Du hörst englisches Audio von Muttersprachlern und wiederholst es sofort laut — wie ein Schatten, der dem Sprecher mit nur 1–2 Sekunden Verzögerung folgt. Anders als passives Hören oder Grammatikübungen zwingt Shadowing dein Gehirn und deine Mundmuskulatur, gleichzeitig echte Sprachmuster zu verarbeiten und zu reproduzieren. Studien zeigen, dass es Aussprachegenauigkeit, Intonation, Rhythmus, verbundene Sprache, Hörverständnis und Sprechflüssigkeit signifikant verbessert — was es zu einer der effektivsten Methoden für die IELTS Speaking-Vorbereitung und reale englische Kommunikation macht.

Shadowing-Technik: die vollständige Schritt-für-Schritt-Anleitung lesen →