शैडोइंग अभ्यास: The Technical, Business and UX Skills Every Product Manager Needs - YouTube के साथ अंग्रेजी बोलना सीखें

शैडोइंग नियंत्रण

0% पूरा (0/213 वाक्य)

Hi everyone, my name is Liam.

⏸ रुका हुआ

गति:

दोहराने की संख्या:

प्रतीक्षा मोड:

सब सिंक:0ms

सभी वाक्य

213 वाक्य

Hi everyone, my name is Liam.

I'm a product manager at Google.

I was a program manager at Microsoft and I founded a few startups in the past.

So today we're going to be talking about what technical, business, and UX skills do product managers need.

Let's dive into it.

So let's start with a refresher.

What is a product manager, right?

Like let's just go back to the basics quickly and just do a quick recap.

So a product manager is three parts, right?

You have UX, business, and engineering.

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

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

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

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?

And that's what we're going to talk about today.

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.

So what technical skills does a PM need?

Let's start with the tech side, right?

You need to know what's possible.

You need to kind of have a basic understanding of the impact to effort curve in your head.

So I'd say you need to be able to answer these questions.

Right.

Like how does the Internet work at a high level?

Can you diagram it?

And here's a crude diagram that I just quickly drew up on my iPad of how the Internet works.

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.

Blah.

Right.

Like something like this.

Go Google it.

You'll find a much better version of this.

But this is kind of what you're looking for and you should be able to do.

Also, an understanding of how data is stored at a high level.

right?

Like what are some data types?

What's a string, integer, double, floating point, file types?

And here's a quick diagram of maybe some types, right?

So I'd be able to kind of list things out of what's an integer.

Well, it's like 10 or one.

It's not like 2.7, right?

The decimal point there.

What scenario would you use each of these in?

For example, an integer, maybe you'd store how many views this video got.

Hopefully it's a lot.

A double is like a 2.7, 2.5 at a decimal.

Maybe It's the average star rating for your favorite restaurant, Google Maps.

A slight bias because I work on that product, right?

But a string, right?

Like that would be my name.

That would be your name.

That's the first name of a user.

Just understanding these concepts and these data types is super important.

And I've already given you a head start here.

I would try to understand what an API is, right?

I'm not going to spoil it for you.

Go Google it.

Application programming interface.

What does it look like?

What does it do?

Why do you need a key to authenticate with an API?

Just a basic understanding of what that is.

I would also try to understand a few programming languages, not how to build with them, but what they're used for, right?

Like you would not use Swift to write an HTML front end web page.

You would not use Java to write an iPhone app, right?

Like there's kind of, there's specialties for programming languages.

I would try to see what the top programming languages are.

I'm gonna link below the Stack Overflow Developer Survey for 2022.

I forget which year it was.

That shows the most popular programming languages that developers are using right now.

I would understand what they're good for.

What is an app?

This is such a hypothetical thing, but what is a client?

What are the trade-offs between web apps versus native apps?

And I'm giving you again, a nice little diagram, a little bit of a cheat sheet.

I keep pointing this direction, but it's actually going to be over here.

So you can see there's a native app.

You use Swift.

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.

They all connect to an API, and the API is using some Node.js service potentially in the backend.

So understanding these concepts and what I'm talking about here is going to be super important, and it's easily Google-able.

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

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

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

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?

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.

But my advice and rule of thumb is it's never daily active users, that's never your answer.

Don't go after that look for specific metrics that will actually help you achieve your goals.

As a product manager, metrics are the way you're going to track success and you'll be graded upon those metrics as well.

So you should really understand how they're calculated and how to calculate them yourself.

Finally, always be learning.

Always be curious about technical trends.

Read tech news sites, go on Stack Overflow, just look around for answers and questions.

See the most popular repos on GitHub.

What's the open source community doing?

Maybe you even take an intro to a computer science course online.

Only do a free one.

There's a bunch by Harvard and Stanford, great universities that I'll link below.

Like my rule of thumb is don't pay for this stuff.

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

YouTube

📱

Shadowing English

अब मोबाइल उपकरणों पर उपलब्ध है, अभी डाउनलोड करें!

5.0

Download on theApp Store

GET IT ONGoogle Play

शैडोइंग तकनीक क्या है?

शैडोइंग (Shadowing) एक विज्ञान-समर्थित भाषा सीखने की तकनीक है जो मूल रूप से पेशेवर दुभाषिया प्रशिक्षण के लिए विकसित की गई थी। विधि सरल लेकिन शक्तिशाली है: आप मूल अंग्रेज़ी ऑडियो सुनते हैं और तुरंत इसे ज़ोर से दोहराते हैं — जैसे वक्ता की छाया 1-2 सेकंड की देरी से। शोध से पता चलता है कि यह उच्चारण सटीकता, स्वर, लय, जुड़ी हुई ध्वनियाँ, सुनने की समझ और बोलने की प्रवाहशीलता में काफ़ी सुधार करता है।

☕ हमें एक कॉफी पिलाएं

आपके समर्थन के कारण ShadowingEnglish 100% मुफ्त है। सर्वर और AI की लागत अधिक है — आपकी कॉफी हमें आगे बढ़ने में मदद करती है! 🙏

PayPal के माध्यम से दान करें

ShadowingEnglish.com – अंग्रेज़ी शैडोइंग अभ्यास

शैडोइंग अभ्यास: The Technical, Business and UX Skills Every Product Manager Needs - YouTube के साथ अंग्रेजी बोलना सीखें

Shadowing English

इस वीडियो के साथ बोलने का अभ्यास क्यों करें?

व्याकरण और संदर्भ में अभिव्यक्तियाँ

सामान्य उच्चारण की जटिलताएँ

शैडोइंग तकनीक क्या है?