Shadowing Practice: Product Management Is Dead, So What Are We Doing Instead? | Lenny & Friends Summit 2024 - Learn English Speaking with Video

Choose a practice mode

Each mode opens a full-screen practice room.

308 sentences
If sentences are too short or too long, click Edit to adjust them.
1
Good morning.
2
I'm very excited to be here and they thought, what should we do bright and early at the product leaders conference.
3
"Let's just go ahead and mix product management entirely.
4
"Let's get rid of it." we can all go enjoy a great San Francisco October morning.
5
So I'm here to tell you, and I believe this to be true, this is not a hot take for the sake of hot takes, Product management is dead, or it will be soon.
6
And so I'm here to talk about what we're all going to do instead.
7
But first, what an amazing conference.
8
OK, everybody smile, because you all never get this.
9
Let's take a picture.
10
OK, we got the picture.
11
We'll see if the smiles are still there at the end of the talk.
12
All right, so I've been saying this a lot, but AI is going to transform the role of product design and engineering
13
Faster than we all expect and whenever I say this people yeah, yeah, Claire and I say no no no I faster than that.
14
And so I want you all to think about the change, the rate of change in technology over the last 18 to 24 months
15
Things
16
that candidly after two decades of Being in a product role
17
I never thought I would see in my lifetime has now become kind of boring to me.
18
I think the rate of chain is very fast in our job is to not be surprised.
19
And so when I tell my team about building product strategy, I say I'm not interested.
20
in building a great product for today.
21
I'm interested in thinking about what our customers are going to need from us in three, five and ten years.
22
and building the product that's going to push towards that future that we believe in.
23
And I really believe the same goes for building product teams.
24
I want to imagine the product team of-- 18 months from now, three years from now, five years from now, ten years from now, I want to think about how that team's really going to operate.
25
I want to place some bets on what I think is going to change.
26
and I want to build that team.
27
But before I go there, I'm just gonna tell a little story about baby Claire CPO.
28
You know, many, many moons ago.
29
And I know you all have maybe started new product leadership jobs and you've got asked this question.
30
You know, you're here, you have some experience.
31
What's our product strategy?
32
Anybody even ask that question before?
33
Yeah, OK, great.
34
One person, great.
35
This is a great, great conference.
36
And I remember doing this exercise of what's our great product strategy.
37
And I went through this exercise where I said, OK, first, I'm going to talk to customers.
38
I'll talk to a bunch of them, I'm gonna take a bunch of notes.
39
And then I'm going to talk to the team I would talk to sales, which is money mouth, cowboy, which might also be sales.
40
"We got CFO in the glasses in engineering, "who's too cool to even look at you.
41
"We're gonna talk to the team, we're gonna say, "What do you think, what have you seen?" And then I'm going to think really hard.
42
Like I'm going to take all that information I'm going to put in my brain so hard, and I'm gonna type.
43
And I'm gonna put it into this doc that says, my amazing strategy, of course it's gonna be in Coda.
44
So I'm gonna do this amazing strategy, and then I'm gonna take it back to the team, but they're now annoyed, 'cause they don't like what I came up with.
45
And I'm gonna get more feedback from this team.
46
And then I'm gonna think really hard again.
47
I'll use my brain, everything I know about the market, all my strategic books that i've ever read in my life i'm gonna you know, think back to play bigger,
48
and then I'm going to do my amazing strategy v1.
49
And then I'm going to give it to the team, and the team's going to give me 8 ,000 comments.
50
And then, you know, the drill, a brain goes back into play.
51
And then I have my really amazing strategy, final, final, this one.
52
with a link to all the drafts at the top.
53
So this, I legitimately remember doing this, it output this like, 10 page document that I think was pretty good.
54
It took me weeks and weeks and weeks, so many conference rooms when we did that sort of thing.
55
And That was how I built a product strategy.
56
The last time I built a product strategy, this is what it looked like.
57
I dropped off my kids at school.
58
I had done the customer calls and talking to people.
59
I put ChatGPT voice on my phone and I just prattled.
60
I just did this.
61
And I asked, hey, what's our product strategy after all my prattling?
62
And guess what?
63
I got the same damn 10 document, 10 page paper, on what our product strategy was.
64
I, of course, sat down on my laptop, made it a little better.
65
But I would say like for like, it was pretty good.
66
And that is the difference in how product can operate.
67
I think it's a perfect metaphor for how product is changing.
68
So before, you know, it took weeks to write and revise and sharpen a long product strategy.
69
Now I'm hanging out in my minivan talking to chat GPT on my way to work.
70
You know, before, you would take these days to write feedback and requirements in a doc and da da da da da.
71
And now you're taking 15 minutes to scaffold out something that's 80 % good, and then 45 minutes to sharpen, and then ship it.
72
You would draw wireframes on paper.
73
I used to use paper, like draw wireframes on paper or balsamic if you're being cute and then wait for design to work on UX.
74
See, this is the audience for a balsamic joke.
75
And now you can share these fully functional prototypes with your teams and customers literally in minutes.
76
You can manually pour through customer feedback.
77
Everybody has the spreadsheet.
78
for ideas and priorities, now you can automate those insights with no code tools.
79
And then finally, there's slides.
80
There's so many slides.
81
We're making slides all the time, and now we're making slides, but they're generated by AI.
82
So this is, you know, before and now.
83
This isn't even the future.
84
And I think now product work honestly takes Less time.
85
Less thought.
86
and maybe less PM.
87
So What does that mean?
88
I think it means it could be become more fun.
89
But in order for it to become more fun, we have to do what all of us are really fabulous at, which is Straight up pivot.
90
So we're gonna figure out something else.
91
We're gonna kill product management, but we're gonna replace it with something else.
92
And so I'm gonna start with a couple pieces of advice on how to get there
93
and the first one is that You need to become an AI -powered product team Now.
94
And I think there are three requirements of an AI -powered PM.
95
They automate themselves to speed up delivery, They add new skills and they do more.
96
and then they multiply their impact by teaching the team.
97
and you know, I really think you need to automate yourself to speed up delivery.
98
That's task number one.
99
And Jay -Z was asking me backstage, she was like, "How do you do it all?" And then she goes, "AI, that's how you do it all." Including how I do this talk.
100
So I was like, "How can I automate chat PRD?
101
How can I automate all the things that PMs do with AI?"
102
And I made this to -do list and you'll see how
103
that to -do list was generated with chat PRD as I go through it.
104
So I'm going to give you a Anti -to -do list, these are things that you should no longer do on your own, you should automate these things immediately.
105
One is Draft documents, don't do that.
106
That's for suckers.
107
Two, get and give feedback, first pass of feedback.
108
you shouldn't have to give.
109
You should get feedback from AI or a tool.
110
Writing updates.
111
How many of you are writing updates daily?
112
A lot, no one's writing updates, no one's writing-- Okay, we got one product leader back here.
113
One guy, one guy and me, okay.
114
Agendas, summaries, and action items out of meetings, prioritizing feature requests, monitoring goals and OKRs, even coming up with goals and OKRs.
115
keeping track of competitors, prepping for interviews, Consolidating candidate feedback if you're doing interviews, telling customer stories, You know, you're the keeper of, oh,
116
this feature is great, because so -and -so does this, or so -and -so did that.
117
Making slides pretty, don't do that.
118
explaining product functionality.
119
We're all just walking support knowledge bases for our product areas.
120
None of this you should be doing.
121
You should think every time I do one of these tasks on this anti to do list, How can I automate it in the moment and help you speed up delivery overall.
122
Clear the deck.
123
And I think there are very easy ways.
124
Basically, my trick here is, Every time I do one of those things, and I think in my heart, I wish I didn't have to do this.
125
I go spend four to seven minutes trying to figure out
126
if I can manifest a way not to have to do it, About 80 % of the time I get it done and I ship it.
127
And this is not about, you know, there's this mix.
128
People say, oh, that saves time, but does it increase quality?
129
And I'm just using this quote from somebody on my team who says, don't look at it as how you can get to 100%.
130
look at how you can get to 75 % faster than starting from zero.
131
And I think people can save days every week by automating themselves.
132
And then I think you really need to use that time to add new skills and do more.
133
So this is where we start thinking about how product management is going to change.
134
To embarrass them, we call out Cody.
135
Cody's on our team.
136
He leads our product innovation and incubation team and Cody actually comes from DevRel, so he's an engineer.
137
And Cody has shown-- and he was in marketing, so he's not a product manager.
138
And Cody has just learned how to be an Edge prototyper, start building product and code, And we said, hey, Cody, I'll give you chat PRD.
139
You want to be a product manager?
140
And he's like, sure, I'll be a product manager.
141
So he already has this propensity to add more skills.
142
This is a non -traditional product manager coming into a product leadership
143
role in using AI to figure out how to be a product Product Manager.
144
But-- Cody got blocked.
145
He was building a product.
146
and It's part of a triad and design had four other priorities Cody was blocked.
147
And instead of saying, I'm blocked, and I'm a marketer, and I'm an engineering prototyper, and I'm kind of a product manager just learning how to do it now,
148
and crying, he Learn how to be a designer.
149
So he started using v0 .dev to actually build wire from like these aren't even wireframes,
150
build beautiful designs and prototypes for his product as part of his package of requirements to the team.
151
And now, I mean, bless him, he's starting to do PRs for front -end code.
152
This guy is out of control.
153
And what I think you need to think about is, these are the kind of people that are going to come for product jobs.
154
These are the kind of people you're going to want to hire, and this is the breadth of skills that you're really going to want on your team and in yourself.
155
And then, of course, none of that matters if it's just one person, if it's just a Cody, as we say.
156
You have to multiply your impact by teaching the team.
157
So we actually have a project building with AI channel at LaunchDarkly, where every day we're sharing different ways.
158
We're automating ourselves, asking for help.
159
building things, and it's the most exciting channel.
160
And I post all the time things that I build, because I think as a product leader you have to normalize using these tools to accelerate and build skills
161
so that people don't feel so bashful about it.
162
You also have to fund it, but we'll get to that in a minute.
163
So this is what I think it takes to be an AI -powered PM and an AI -powered product team.
164
And I think this is how we get to this world, where a product world takes less time.
165
so you can spend more time with users.
166
It takes less thought.
167
So you can actually be more creative with the time that you have, and then has less PMs.
168
Hold on, I don't think you all are gonna like this.
169
So I think maybe we wanna talk about this one.
170
And this is one of my strongly held beliefs about the art of product management, which I've made a career out of.
171
is I think AI will collapse the talent stack.
172
So what I mean is these jobs that have been separate will start to become one.
173
And that's really scary, and it's a big change.
174
But I don't believe, and my experience has been, it doesn't have to break your team.
175
So first a quick exercise.
176
God, I'm trying to do arm raising exercises, and you won't give me nothing, so.
177
Come along with me.
178
How many of you have Give it an update in Slack this week.
179
My God, no one's working, man.
180
Okay.
181
How many of you have written a document this week?
182
OK, we're all writing documents.
183
How many of you have done a design this view.
184
How many of you have written code this week?
185
How many of you have deployed code to production this week?
186
OK.
187
Those five people, that's what's coming for us.
188
You know, before we really loved this idea of the product triad, this product engineering design, these leads.
189
Maybe you had, instead of a stool, you had a table, you got data in there.
190
surrounded by supporting engineering and design resources.
191
I think this is what has been classically the platonic ideal of a product team for quite some time.
192
And I think what's the problem with this is because they're all separate product, operates as a handoff mechanism.
193
I'm going to hand off requirements to you.
194
Design is going to hand off things to engineering.
195
I'm going to make sure they know engineering manager is going to
196
hand off things to engineering and they're going to make sure that they know things.
197
And it means you stay really hands off with what actually gets built.
198
And so what I think we're moving to now is more of this generalist specialist.
199
So you have specialists in product design and engineering, But at least in my organization, they're really expected to participate across the building process.
200
They're expected to do the work that needs to get done to move the project forward.
201
And the operating principle that we embrace at LaunchDarkly, we call this, "There are no lanes." So, you know, there's like stay in your lane.
202
And we're like, there are no lanes.
203
If there's something to get done and you have the skill to do it, Culturally, we embrace getting it done.
204
But that's now.
205
And I think even this kind of freaks people out because people like their lanes.
206
They like to know.
207
Products excellent at product stuff, so they're going to product the hell out of things.
208
And design is great at design stuff, and they're going to design things.
209
And it gets really uncomfortable where you say, well, pretty bang up job at design and design actually knows how to push react code and engineering.
210
Could you please just write a PRD yourself?
211
You know what we need to do.
212
And so I think this already freaks people out.
213
But this This really freaks people.
214
So this is what I think is coming for us very soon.
215
I think you're going to see what I would call an AI -powered triple threat.
216
Basically, one person that can do engineering design product as a lead of a team which includes AI tools,
217
agents, and platforms as part of that team.
218
And I think this is what we're gonna hire for.
219
And what's really interesting is, They may spike in engineering.
220
They may spike in classic product management.
221
They may spike in design.
222
but they're gonna need to know how to do it all, and that triad goes away.
223
And what I think is really interesting about the triad going away
224
is I think we all believe that small teams can generally move faster than big teams.
225
I kind of believe individuals can move faster than small teams.
226
And so this is kind of an exercise in thinking.
227
How fast can opinionated product leadership in a small team move things forward given the tools that they need?
228
And then actually, I think it's like maybe everything.
229
So you saw those guys hiding in the corner.
230
I mean, who knows what we're going to pull into this vortex of this new role
231
But I do think product managers are also going to be expected to be more commercially oriented
232
Think about marketing more use tools for data and so maybe actually we're both dead and reanimated as everything and
233
And it's scary.
234
People don't like this.
235
They don't like it.
236
But it doesn't have to be scary.
237
I have a friend that said this the other day, I thought it was really interesting.
238
The only people that need to be worried are the people acting like they don't need to be worried.
239
If you can imagine this future and you say, you know, Claire's up here trying to give a talk that people tweet out, but I buy into her fundamental thesis that things are going to change dramatically,
240
Think about how that changes for you.
241
Prepare yourself, prepare your team
242
change in advance and make the moves we need to do to be awesome in this new era as opposed to obsolete.
243
And so I think about this, AI will never do this thing as super naive.
244
but AI can help me do anything is really inspiring.
245
And it gets me amped up about how I've gotten some
246
nods gets me really amped up about what is possible to build and put in the market and create.
247
And I just think that's so thrilling.
248
OK, and then this is the last part, which is product leaders.
249
AI is coming for you, too.
250
So you're like, yeah, yeah, product managers.
251
Let's just get them to do a whole bunch more stuff with less headcount.
252
That sounds great.
253
Yeah.
254
And then all the SAS providers are like, yeah, AI agents.
255
My tool is your solution.
256
They love it.
257
But it's never coming for us, right?
258
There's never going to be an AI CPO.
259
No, no, no. It's coming for you too.
260
And I think we all need to be really prepared for this change.
261
And so first thing is we need to be prepared to manage whatever the hell this thing is.
262
I mean, this is totally different than what most of us are thinking about.
263
in terms of what our teams are.
264
And I think this means that we have to get more commercial skills in our teams, especially for my friends out there in B2B enterprise.
265
More technical skills, we are going to be expected to manage people who code.
266
I'm a CPTO, basically.
267
It's already happening.
268
I'm seeing more and more of us that are bringing these functions together.
269
When more and more of the individuals have shared skills, you're going to have to think about how you manage That.
270
You're gonna have to think about budgeting for headcount versus budgeting for agents
271
and tools and how that changes how you think about the investment in R &D that you're making.
272
And then I'm saying we're going to have these artisanally crafted team topologies.
273
which is basically like, the team is going to be built for the thing that needs to get done.
274
We can't all be prescriptive about the triad is the only way to get something done.
275
I say organize around motivated individuals, If somebody comes in with this globule shape of skills, I'm gonna want to build a team around that.
276
If somebody spikes on product and I need that skill on a team, I'm gonna build that team around them.
277
And we're gonna have to get really creative with how we design teams in order to be successful.
278
The other thing I would think about is your experience and your strategy.
279
Remember my minivan story is becoming a commodity.
280
So this is a great
281
article in Lenny's newsletter about how close is AI to replacing product managers
282
and The punchline here is they had like two visions.
283
The AI generated one, One because of quality, even though people knew it was AI.
284
And so I think just thinking about how special is all that hard thinking.
285
um is really important and so i think you need to skill up
286
and build a moat around what you can bring to the table
287
And what you might be able to bring to the table is running and building and scaling these AI -powered teams.
288
And it's going to happen really fast.
289
So start now.
290
The reason why I have the-- dancing funny emojis is, I sat next to the CEO you would have never guessed, wasn't from a fancy tech forward company was sort of like,
291
non -tech company and he was sitting there said what are you doing he's like oh i'm building my digital twin
292
And I don't let anybody in the company ask me questions till they ask my digital Twitter question.
293
And I was like, this guy's got a digital twin?
294
I don't have a digital twin.
295
And so it really made me think it's going to happen fast, and I'm even behind, so you really need to start now.
296
So here's the TLDR on reanimating products.
297
I killed it.
298
You really need to become an AI -powered product team now.
299
AI is going to collapse the talent stack.
300
There are five people here apparently that have already done it.
301
But care for your culture, care for your organization, plan accordingly.
302
and it will be fine.
303
And then Product Leaders is coming for you too, so join me in thinking what that three to five year future can look like and manifest it in your team.
304
And so if I have any advice to you, it's go find those AI powered triple threats.
305
give them power and give them budget, I think you'll be really, really happy you did.
306
Thank you so much.
307
I really appreciate it.
308
Thank you.

Download App

Everything you need to speak fluently

AI PronunciationScore every sentence
IPA PracticeMaster every sound
VocabularyBuild your word bank
Vocab GameLearn while playing
FOR YOU

Recommend Video

What You'll Practice in This Lesson

In this lesson, you'll dive into a dynamic talk about the future of product management, perfect for honing your English speaking skills through real-world conversation. You'll practice following a natural, engaging speech style—complete with anecdotes, humor, and strategic thinking—while improving your ability to mimic rhythm, intonation, and emphasis. By the end, you'll feel more confident shadowing lively, professional dialogue.

Key Vocabulary & Phrases

  • Hot take: A bold, often controversial opinion (e.g., "This isn't a hot take for the sake of attention.")
  • Place bets: To make strategic decisions based on future predictions (e.g., "We need to place bets on how teams will operate.")
  • Candidly: Honestly, openly (e.g., "Candidly, I never thought I'd see this in my lifetime.")
  • Drill: A repeated, routine process (e.g., "You know the drill—revise and get feedback.")
  • Push towards: To work actively toward a goal (e.g., "Build products that push towards that future.")

Practice Tips for Shadowing

The video's tone is conversational yet energetic, with a moderate speed that's ideal for shadowing practice. Here's how to make the most of it: Start by listening to short 10-15 second clips, pausing, and repeating immediately. Focus on matching the speaker's pace—notice how she speeds up during anecdotes and slows down for emphasis. Use a shadowing app to record yourself and compare it to the original; this helps spot differences in intonation, like the playful rise when she jokes about "smiles still being there." For tricky phrases like "money mouth, cowboy," break them into syllables and repeat until they flow naturally. Remember, shadow speak isn't just about words—it's about capturing the feeling of the conversation. Practice daily, and you'll soon find your English speaking sounds more natural and confident.

Grammar in this video

The structures the speaker uses most, with the exact words from the video:

StructureIn the video
Present perfect have/has + past participle — a past action that still matters nowhas now become · have you seen · i've ever read
Passive voice be + past participle — the focus is on what happens, not who does itwas generated · was blocked · be expected
Relative clauses who / which + clause — extra information about a person or thingsales, which is · people that are · person that can

What is the Shadowing Technique?

Shadowing is a science-backed language learning technique originally developed for professional interpreter training and popularized by polyglot Dr. Alexander Arguelles. The method is simple but powerful: you listen to native English audio and immediately repeat it out loud — like a shadow following the speaker with just a 1–2 second delay. Unlike passive listening or grammar drills, shadowing forces your brain and mouth muscles to simultaneously process and reproduce real speech patterns. Research shows it significantly improves pronunciation accuracy, intonation, rhythm, connected speech, listening comprehension, and speaking fluency — making it one of the most effective methods for IELTS Speaking preparation and real-world English communication.

Shadowing technique: read the full step-by-step guide →