Практика Shadowing: The Technical, Business and UX Skills Every Product Manager Needs - Изучайте разговорный английский с YouTube

C1
Управление Shadowing
0% завершено (0/213 предложений)
Hi everyone, my name is Liam.
⏸ Пауза
Все предложения
213 предложений
1
Hi everyone, my name is Liam.
2
I'm a product manager at Google.
3
I was a program manager at Microsoft and I founded a few startups in the past.
4
So today we're going to be talking about what technical, business, and UX skills do product managers need.
5
Let's dive into it.
6
So let's start with a refresher.
7
What is a product manager, right?
8
Like let's just go back to the basics quickly and just do a quick recap.
9
So a product manager is three parts, right?
10
You have UX, business, and engineering.
11
And PMs are the little purple spot in this diagram that are smack the middle pms are here and i've had this conversation way too many times
12
right so so this is the conversation that i get with my friends with people that are interested in becoming product managers in my linkedin inbox is it
13
goes exactly like this right so so you're saying i need three master's degrees in each category ux business and eng that seems like too much and my reply is like well no not really but you need to know each category pretty well
14
and then the immediate reply is well liam that doesn't really help me i need specifics How deep do I need to go in each one of these categories to be a very good product manager?
15
And that's what we're going to talk about today.
16
So let's take the next 10 minutes or less, ideally less, and dive into the technical, business, and UX skills required to be a great product manager.
17
So what technical skills does a PM need?
18
Let's start with the tech side, right?
19
You need to know what's possible.
20
You need to kind of have a basic understanding of the impact to effort curve in your head.
21
So I'd say you need to be able to answer these questions.
22
Right.
23
Like how does the Internet work at a high level?
24
Can you diagram it?
25
And here's a crude diagram that I just quickly drew up on my iPad of how the Internet works.
26
When you type in www.whatever.com, it's going to the Wi-Fi router, which goes to a Comcast switch, which goes to a DNS lookup to convert to an IP address, which goes to Amazon.
27
Blah.
28
Right.
29
Like something like this.
30
Go Google it.
31
You'll find a much better version of this.
32
But this is kind of what you're looking for and you should be able to do.
33
Also, an understanding of how data is stored at a high level.
34
right?
35
Like what are some data types?
36
What's a string, integer, double, floating point, file types?
37
And here's a quick diagram of maybe some types, right?
38
So I'd be able to kind of list things out of what's an integer.
39
Well, it's like 10 or one.
40
It's not like 2.7, right?
41
The decimal point there.
42
What scenario would you use each of these in?
43
For example, an integer, maybe you'd store how many views this video got.
44
Hopefully it's a lot.
45
A double is like a 2.7, 2.5 at a decimal.
46
Maybe It's the average star rating for your favorite restaurant, Google Maps.
47
A slight bias because I work on that product, right?
48
But a string, right?
49
Like that would be my name.
50
That would be your name.
51
That's the first name of a user.
52
Just understanding these concepts and these data types is super important.
53
And I've already given you a head start here.
54
I would try to understand what an API is, right?
55
I'm not going to spoil it for you.
56
Go Google it.
57
Application programming interface.
58
What does it look like?
59
What does it do?
60
Why do you need a key to authenticate with an API?
61
Just a basic understanding of what that is.
62
I would also try to understand a few programming languages, not how to build with them, but what they're used for, right?
63
Like you would not use Swift to write an HTML front end web page.
64
You would not use Java to write an iPhone app, right?
65
Like there's kind of, there's specialties for programming languages.
66
I would try to see what the top programming languages are.
67
I'm gonna link below the Stack Overflow Developer Survey for 2022.
68
I forget which year it was.
69
That shows the most popular programming languages that developers are using right now.
70
I would understand what they're good for.
71
What is an app?
72
This is such a hypothetical thing, but what is a client?
73
What are the trade-offs between web apps versus native apps?
74
And I'm giving you again, a nice little diagram, a little bit of a cheat sheet.
75
I keep pointing this direction, but it's actually going to be over here.
76
So you can see there's a native app.
77
You use Swift.
78
It's downloaded on the device as opposed to a web app, which is a cached React, maybe HTML type of thing that you pull as soon as you type in www.x.com.
79
They all connect to an API, and the API is using some Node.js service potentially in the backend.
80
So understanding these concepts and what I'm talking about here is going to be super important, and it's easily Google-able.
81
So just search on the internet what these words mean if you don't quite understand them read the two first sentences on Wikipedia and you're done and finally I'd also
82
try to understand what a server is what what is servers what do they do what is latency how do you build servers right where do you rent them what
83
do they cost right so these are kind of the questions I would be asking and just have that general curiosity for the topics that I just laid
84
out also I'd recommend for the technical side to be able to break down you know with help from your engineering team a problem into smaller high level solutions, right?
85
So breaking down problems into smaller things, that's very basic thing, I would recommend having the ability to own which metrics you're going to track and fully understand the difference between a health metrics, success metric, progress metric, whatever it is.
86
But my advice and rule of thumb is it's never daily active users, that's never your answer.
87
Don't go after that look for specific metrics that will actually help you achieve your goals.
88
As a product manager, metrics are the way you're going to track success and you'll be graded upon those metrics as well.
89
So you should really understand how they're calculated and how to calculate them yourself.
90
Finally, always be learning.
91
Always be curious about technical trends.
92
Read tech news sites, go on Stack Overflow, just look around for answers and questions.
93
See the most popular repos on GitHub.
94
What's the open source community doing?
95
Maybe you even take an intro to a computer science course online.
96
Only do a free one.
97
There's a bunch by Harvard and Stanford, great universities that I'll link below.
98
Like my rule of thumb is don't pay for this stuff.
99
There's so much free content like this on the internet.
100
You need to understand why a technical decision was made.
101
And you can talk to your engineers to learn more about the specifics.
102
But you should be able to understand the trade offs that you made to come to that decision.
103
While you don't need to know any programming languages, I will say the one thing you should understand is SQL or a querying language that's equivalent to it.
104
You need to understand how to get your own data.
105
Sometimes your data science team, your analyst team won't be available.
106
You need to be able to query it and get your hands dirty.
107
I don't know the expression, whatever, to figure it out yourself.
108
I would also avoid unicorn thoughts, right?
109
I call them unicorn thoughts.
110
I don't know what the right word is, but buzzwords.
111
Don't use AI, blockchain, ML.
112
If you don't know what they mean or they're not actually useful in this context, it just looks very bad.
113
Don't do it.
114
And like the diagrams that I've been showing, be able to draw those diagrams with some confidence, right?
115
Be able to draw the boxes that point to the other boxes and see how it all works together.
116
You don't need to know the specifics on how each box works, but know the diagram and the architecture.
117
You can have an opinion on long-term features, but I would really say don't have an opinion on specific technologies, right?
118
Your job as a product manager is to determine why we're doing it and kind of what we're doing, but not how we're going to get there specifically.
119
Leave that to the engineers.
120
They're the experts.
121
Honestly, my rule of thumb is you've gone too far if you're considered to be the best engineer while you're being a product manager, I would say you've gone way too technical, right?
122
So just do what I've outlined here.
123
And I think that is more than enough.
124
All right.
125
So enough with the technical.
126
That was the longest section.
127
What business skills do you need as a product manager?
128
So you need to understand the basics of business economics, right?
129
What is revenue?
130
What are costs?
131
What is profit?
132
What is EBITDA?
133
Here's a cheat sheet that shows you all of those definitions, but you can also Google them.
134
Just knowing these basic definitions and what they do is super important.
135
I would also try to understand pricing strategies and monetization, right?
136
Freemium, ad supported, pay to play, subscription.
137
Here are a couple notes that I took, right?
138
Like freemium, we're thinking Clash of Clans or Afterlight, one of my favorite like photo editing apps.
139
Ad supported, we're thinking Instagram, it's Google search, there's ads and that's how they make money.
140
Pay to play, that's just a one-time upfront fee like Procreate or when you buy like a license of Windows.
141
And then subscriptions, thinking Netflix, Spotify, things like that where you're paying every month for as long as you use the service.
142
You need to understand competition and you need to develop substantial advantages to your product and understand how and why your competitors succeed or failed.
143
For example, I'm a product manager at Google.
144
I work on Google Maps.
145
So I'm looking at Apple Maps.
146
I'm looking at Bing Maps.
147
I'm looking at competitors in other countries.
148
That's what's really important to me and understanding the landscape of competition.
149
Also, I want to emphasize emotional intelligence.
150
It's super critical to being a product manager, having a lot of empathy, having a lot of EQ.
151
I'm going to put a YouTube video below that summarizes this very well.
152
I will do a very bad job of summarizing it, but just look into that.
153
It's very important to being a great product manager.
154
So here are two words that as a product manager, you're thrown out a lot, especially on the business side is storytelling and writing.
155
So do your presentations like each slide have a purpose?
156
So does your story have a problem solution, landing, launching, right?
157
Do you get people excited when you talk about a problem?
158
I would Just look at all of those things to gauge if you're good at storytelling and writing.
159
And honestly, I don't know what the exact definition is, and I feel like most people just make up the definition, but I would look at those as being a gauge of doing good at that.
160
You need to be a leader and have the ability to convince others that the problem that you found is worth chasing, and it is the biggest of the problems, right?
161
Influencing without power is by definition being a product manager, and it just is a good thing in general to practice.
162
You need to understand the marketing message and potential go to market of your product.
163
are consumers or business people or companies going to take the message of why your product is the best product in the world I would be thinking about the
164
marketing side of things early on and how you're gonna position it and honestly this is like really high-level kind of buzzwordy stuff like how to position yourself in
165
the market you can google it to find better guides on this but just think about like are people gonna resonate with what you're saying and what you're producing that's kind
166
of it and again to reiterate where you should be opinionated and where you should kind of back off I would say here you should be very opinionated on the strategy and the long term vision.
167
That is your job as a product manager.
168
That's what people are looking to you for.
169
In terms of specific skills like legal skills, finance, the marketing and advertising folks on like buying Facebook ads or whatever it is, they're going to know best.
170
I wouldn't push against them too hard.
171
Now to what UX and design skills does a product manager need?
172
We're almost there.
173
We're almost to the end here.
174
You should be able able to use Sketch and probably Figma now at a surface level.
175
The rule of thumb is if you can make gray boxes look somewhat like an iPhone app, then I think you're doing fine.
176
That's exactly what you need to do.
177
I wouldn't go any more high fidelity than that.
178
You need to have a basic understanding of terminology in terms of user experience and UI.
179
What's a button?
180
What's a label?
181
What's a text box?
182
What's a menu?
183
Again, Google all of these things.
184
And in terms of like, what does these sketches look like?
185
You can either hand draw them.
186
You can use boxes on Figma, but this is kind of the fidelity level that I think we're looking for here as a product manager.
187
This is Google Maps, right?
188
It's a search bar and a map.
189
Being able to understand what a button is, a text box, a label, a menu, right?
190
Kind of this terminology that's going to be very helpful.
191
But if you can draw this stuff, I think you're doing pretty good.
192
So I would understand these kind of UX slash design concepts.
193
Again, just Google them.
194
What is an affordance?
195
What is kind of user-centered design, what is a critical user journey, understanding the concept behind it and the rationale for it, super critical, but you don't need to go too deep.
196
Another thing that I see a lot of product managers and just people in general is to ask non-biased questions to people using your product, right?
197
Just know how to conduct decent user research.
198
Don't push what you want to be right.
199
Understand what happens, kind of the basics of that.
200
Maybe, you know, you could do some Googling to try and figure out what are actual good questions to ask users.
201
Having a basic understanding of psychology and just focusing on empathy and having empathy for other people and your users and your partners and your collaborators, whoever it may be, that's pretty much the definition of being a great product manager is having an incredible amount of empathy.
202
I can't stress this enough.
203
Go look this stuff up.
204
And as a great product manager, I would suggest not being opinionated on much here.
205
Great designers will likely know the best way to build something.
206
They're going to understand how people work, the flows that people go through, the buttons that people use, whatever it may be, the actual execution of that design better than anyone else.
207
So I would kind of leave your opinions on the table here.
208
You can be opinionated on the requirements from the functionality and the feature set, but the execution of how that's going to look and manifest, I would stay away from that and let your incredible designers do their best work.
209
So finally,
210
to answer the question of do you need three master's degrees in all three of these categories to be a great product manager the answer is no you just
211
need to watch this video and now i can reply to all of your dms saying well here's the video share with people that are
212
asking the same question we've gone over today the engineering skills the business skills and the ux skills required to be a great product manager
213
and hopefully you found it useful thanks again subscribe share this out to people that are asking the same question and thank you so much for watching today it means so much to me have a great day
📱

Shadowing English

Теперь доступно на мобильных устройствах, скачайте сейчас!

5.0
Download on theApp Store
GET IT ONGoogle Play

Почему стоит практиковать разговор с этим видео?

Практика разговорной речи с помощью видео — это отличный способ улучшить ваши навыки английского. В данном видео мы можем услышать практические советы от опытного менеджера продуктов, который делится своим опытом и знаниями. Эффективность такого подхода заключается в возможности не только слушать, но и активно воспроизводить услышанное, что помогает развить уверенность в разговоре на английском языке.

Включение видеоматериала в вашу рутину позволяет вам учить английский с YouTube, а речь спикера работает как идеальный образец для подражания. Вы сможете исследовать различные профессиональные термины и конструкции, а также получить представление о том, как менеджеры продуктов общаются в реальных ситуациях.

Грамматика и выражения в контексте

В видео рассматриваются основные навыки, необходимые для менеджеров продуктов. Ниже представлены несколько ключевых конструкций:

  • "You need to know what's possible" — конструкция, подчеркивающая необходимость базового понимания предмета. Это поможет вам формулировать свои мысли об известных вам темах.
  • "Can you diagram it?" — вопросительная форма, используемая для вовлечения слушателя в обсуждение. Полезно знать, как задавать такие вопросы.
  • "How does the Internet work?" — структура с прямым вопросом, актуальная для любой профессиональной сферы, где нужно прояснить сложные аспекты.

Эти конструкции можно использовать не только в деловых переговорах, но и в повседневном общении, что позволит вам улучшить произношение английского и уверенность в разговоре.

Распространенные трудности в произношении

При просмотре видео обратите внимание на следующие слова и выражения, которые могут быть сложными для произношения:

  • "technical" — может вызывать затруднения из-за сочетания звуков, обратите особое внимание на произношение 'текнИкэ'.
  • "management" — часто неправильно произносят ударение, правильный вариант — 'мЭнеджмент'.
  • "product" — важно произносить эту лексему четко, чтобы избежать недоразумений.

Работа над произношением этих слов с использованием метода shadow speak помогает оттачивать произношение и настраивать ваше ухо на восприятие английской речи. Применяя техники shadow speak, вы сможете значительно улучшить ваше произношение английского и уверенно общаться.

Что такое техника Shadowing?

Shadowing — это научно обоснованная техника изучения языка, изначально разработанная для подготовки профессиональных переводчиков и популяризированная полиглотом доктором Александром Аргуэльесом. Метод прост, но эффективен: вы слушаете аудио на английском от носителей языка и немедленно повторяете вслух — как тень, следующая за говорящим с задержкой в 1–2 секунды. В отличие от пассивного прослушивания или грамматических упражнений, Shadowing заставляет мозг и мышцы рта одновременно обрабатывать и воспроизводить реальные речевые паттерны. Исследования показывают, что это значительно улучшает точность произношения, интонацию, ритм, связную речь, понимание на слух и беглость речи — что делает его одним из самых эффективных методов для подготовки к IELTS Speaking и реального общения на английском.

☕ Угостите нас кофе