UDSKRIFT 🔗
WEBVTT
1
00:00:00.580 --> 00:00:01.300
Hi, everybody.
2
00:00:01.320 --> 00:00:02.120
It is Alex.
3
00:00:02.620 --> 00:00:05.019
Let me ask you something. Do you know Mike?
4
00:00:05.559 --> 00:00:08.599
You know, the best engineer on the team promoted to
5
00:00:08.660 --> 00:00:14.539
lead and suddenly drowning? Nobody trained him to manage others.
6
00:00:15.820 --> 00:00:20.250
Nobody trained you either. This is exactly why I wrote
7
00:00:20.320 --> 00:00:23.809
From Code to People, the CQ leadership method that transforms
8
00:00:23.969 --> 00:00:27.510
technical experts into leaders teams actually want to work for.
9
00:00:27.980 --> 00:00:31.750
It's not another leadership theory book. It is the practical
10
00:00:32.170 --> 00:00:35.630
system that I use with tech leaders every single day.
11
00:00:36.869 --> 00:00:39.570
Built on three main tools that you can start using
12
00:00:39.969 --> 00:00:45.840
right away. Process communication model, PCM, three-level contracting, and the
13
00:00:45.880 --> 00:00:50.820
will of conflict. Real frameworks for real conversations with real
14
00:00:50.979 --> 00:00:54.869
engineers like Mike. If you're a technical expert who got
15
00:00:54.909 --> 00:00:58.950
promoted into people management and nobody handed you an app,
16
00:00:59.590 --> 00:01:10.269
this book is your map. Grab it at from code2people. lemonskills. com.
17
00:01:05.750 --> 00:01:14.010
That's from code2people. lemonskills. com.
18
00:01:13.189 --> 00:01:18.560
Welcome to the Lemon Tech Leadership Podcast. My name is
19
00:01:18.599 --> 00:01:23.079
Aleksandra Lemańska. I'm a former violinist turned management engineer turned
20
00:01:23.159 --> 00:01:28.400
organizational psychologist, speaker and PCM leadership mentor and facilitator. In
21
00:01:28.420 --> 00:01:31.099
this space, everyone is invited to the table where we
22
00:01:31.159 --> 00:01:38.390
have real eye-opening conversations about tech leadership. Two keywords, utility
23
00:01:38.510 --> 00:01:43.640
and real-life implementation. Knowledge, tools, frameworks, ways of working, do's
24
00:01:43.700 --> 00:01:47.069
and don'ts, taken from my personal experiences as a leader
25
00:01:47.209 --> 00:01:50.030
and the experiences of others, is what you are going
26
00:01:50.069 --> 00:01:54.109
to get from every single episode. This is the Lemon
27
00:01:54.150 --> 00:01:58.900
Tech Leadership Podcast. Okay, so let's go and take some action.
28
00:02:00.799 --> 00:02:03.840
Hi, everybody. It's Alex, and I would love to welcome
29
00:02:03.859 --> 00:02:07.920
you all to another episode of the Lemon Tech Leadership Podcast. Today,
30
00:02:07.939 --> 00:02:16.039
I want to... answered a question that I got years ago,
31
00:02:16.719 --> 00:02:20.379
and then it disappeared. And then about a week ago
32
00:02:20.439 --> 00:02:23.430
or so, I got it one more time. So there
33
00:02:23.509 --> 00:02:27.270
is a pattern in this question, but also when you
34
00:02:27.289 --> 00:02:30.150
think about the Radical Candor book or any book about
35
00:02:30.830 --> 00:02:36.060
building a team and building a high-performing team, it is
36
00:02:36.139 --> 00:02:42.469
being there all the time. Somewhere in the shadow. So
37
00:02:42.490 --> 00:02:47.460
I get this question from one leader lately. And it was,
38
00:02:47.960 --> 00:02:51.460
as I mentioned, it was something that was quite similar
39
00:02:51.520 --> 00:02:56.360
to what I've heard about like years ago. Should I
40
00:02:56.400 --> 00:03:01.000
build a team only consists of A players?
41
00:03:02.270 --> 00:03:02.729
Stars?
42
00:03:04.530 --> 00:03:06.750
And the question that I put in today's episode is,
43
00:03:07.580 --> 00:03:11.240
title is why an all-star team might be your biggest
44
00:03:11.360 --> 00:03:17.250
risk because from the first look having all a players
45
00:03:17.270 --> 00:03:22.030
in the team seems amazing all stars a players amazing
46
00:03:22.110 --> 00:03:27.150
team the question is is it really the best idea
47
00:03:27.169 --> 00:03:31.590
when we're building a team to have all a players
48
00:03:31.789 --> 00:03:38.819
all stars because i hear constantly especially in tech leadership circles.
49
00:03:39.560 --> 00:03:42.780
Only hire A players or build a team of stars. And,
50
00:03:43.500 --> 00:03:48.310
you know, I understand appeal completely. Nobody sets out to
51
00:03:48.340 --> 00:03:52.669
build a mediocre team on purpose. But I've watched this
52
00:03:52.729 --> 00:03:59.129
belief taken too literally, quietly write teams that looked incredible
53
00:03:59.449 --> 00:04:02.969
on paper. And today I want to tell you why
54
00:04:03.349 --> 00:04:07.780
and what to actually optimize for instead. So the team
55
00:04:07.789 --> 00:04:15.520
is actually successful, delivering extraordinary results, learning, learning from each other,
56
00:04:15.580 --> 00:04:20.519
sharing knowledge, and building themselves up to the next level.
57
00:04:23.000 --> 00:04:26.420
And before we go into the subject, I would love
58
00:04:26.459 --> 00:04:29.990
to invite you to join the pools, Lemon Tech Leadership Pools.
59
00:04:30.930 --> 00:04:33.750
This is the email that I'm sending every single Sunday.
60
00:04:33.769 --> 00:04:37.949
This is completely free. And I am sharing with you
61
00:04:38.720 --> 00:04:43.860
within the polls the insights, the case studies, questions, tools,
62
00:04:44.459 --> 00:04:50.750
leadership insights, books, podcast episodes, free materials, free courses. So
63
00:04:50.790 --> 00:04:52.810
you don't need to spend time to look for it.
64
00:04:53.730 --> 00:04:57.750
So if it sounds good to save some time, just
65
00:04:57.790 --> 00:05:02.750
go to lemanskills.com forward slash polls, P-U-L-S-E, and just grab it.
66
00:05:03.170 --> 00:05:07.089
and you're going to have ready-to-go email every Sunday. Okay,
67
00:05:07.230 --> 00:05:11.649
so let's get back to the subject.
Load full transcript
Here's the trap
68
00:05:11.790 --> 00:05:16.009
in hiding inside we only hire stars. It usually means,
69
00:05:16.230 --> 00:05:20.100
in practice, that we only hire people who look like
70
00:05:21.139 --> 00:05:26.720
our existing definition of a star, extended version of the
71
00:05:26.759 --> 00:05:31.000
best person that we have plus 20%, which tends to
72
00:05:31.079 --> 00:05:39.980
reward one specific profile. Confident, fast, vocal, decisive. That's a
73
00:05:40.060 --> 00:05:46.779
real and super valuable profile. And it is not the
74
00:05:46.959 --> 00:05:50.129
only profile a functioning team needs and a team built
75
00:05:50.209 --> 00:05:53.310
entirely out of it is more fragile than it looks,
76
00:05:54.209 --> 00:05:58.629
not less. It is interesting to see how it works.
77
00:05:59.720 --> 00:06:02.660
You know, I've sat in rooms full of genuinely brilliant,
78
00:06:02.959 --> 00:06:06.990
individually excellent people who could not make a single decision
79
00:06:07.050 --> 00:06:10.790
together because everyone in a room was wired to push,
80
00:06:11.110 --> 00:06:15.389
to advocate, to win the argument, and nobody was wired
81
00:06:15.430 --> 00:06:20.160
to slow things down, ask the quiet, clarifying question, or
82
00:06:20.680 --> 00:06:23.800
hold the group accountable to a decision once it was made.
83
00:06:24.980 --> 00:06:31.389
On paper, all-star rooster. In practice, it was super expensive
84
00:06:31.550 --> 00:06:35.889
and super thin. The deeper issue of that quote-unquote star
85
00:06:36.269 --> 00:06:39.089
usually gets defined by one narrow slice of what makes
86
00:06:39.189 --> 00:06:46.120
someone valuable. Output, visibility, decisiveness, and quietly discounts the people
87
00:06:46.800 --> 00:06:53.399
whose contribution is steadiness, process, care, maintenance, or challenge. Even
88
00:06:53.439 --> 00:06:57.379
when those contributions are exactly what keeps a fast-moving team
89
00:06:57.399 --> 00:07:03.839
from running itself off a cliff. Because those stars most
90
00:07:03.879 --> 00:07:07.459
of the time are bored with maintenance. And let's be honest,
91
00:07:07.620 --> 00:07:11.060
we have a lot of maintenance work on a daily basis. Repetitive,
92
00:07:11.120 --> 00:07:14.560
boring tasks. Of course, we can automate some of them.
93
00:07:14.730 --> 00:07:19.430
We can AI a lot of them. But let's be
94
00:07:19.470 --> 00:07:21.569
honest here. A lot of those things need to be done.
95
00:07:21.589 --> 00:07:29.139
And I saw a lot of teams that were... built
96
00:07:29.279 --> 00:07:35.220
from one player to another, and nobody wanted to do
97
00:07:35.279 --> 00:07:39.569
the boring stuff. So I saw events, situations where the
98
00:07:39.629 --> 00:07:42.790
leader started to do the boring stuff instead of them
99
00:07:43.769 --> 00:07:49.889
because nobody wanted to do it. They even sabotaged the
100
00:07:49.939 --> 00:07:55.639
case because they unconsciously, they did the
job that wasn't
101
00:07:55.699 --> 00:08:01.509
so good. to sabotage the task. So the manager says, hey, okay,
102
00:08:01.649 --> 00:08:03.990
I'm going to do it. Just focus on your brain
103
00:08:04.009 --> 00:08:12.459
on that. Crazy stuff. So there's where PCM comes in
104
00:08:12.500 --> 00:08:17.120
as well. Because team is a system, not a leader's board.
105
00:08:18.420 --> 00:08:24.430
And a team made up entirely of strong energy, rebel
106
00:08:24.490 --> 00:08:29.540
and promoter will generate huge energy and constant new ideas
107
00:08:29.699 --> 00:08:33.519
and will struggle to finish anything or haunt the boundary.
108
00:08:35.659 --> 00:08:41.139
And the other end, a teammate mostly of strong thinker
109
00:08:41.299 --> 00:08:46.059
or persister energy will be rigorous and principled and will
110
00:08:46.080 --> 00:08:50.070
struggle to move fast or take a real risk. Neither
111
00:08:50.139 --> 00:08:56.129
is quote-unquote better. It is specific. and predictable kind of fragile.
112
00:08:57.980 --> 00:09:03.379
So what actually builds resilience is the mix. People who
113
00:09:03.460 --> 00:09:07.320
push and people who question, people who move fast and
114
00:09:07.340 --> 00:09:10.700
people who insist on a pause to think and reflect.
115
00:09:12.399 --> 00:09:15.690
And people who are stars and just push, push, push,
116
00:09:15.809 --> 00:09:20.190
and people who maintain, do the maintenance. Because this is necessary.
117
00:09:23.350 --> 00:09:31.029
And knowing exactly which personality base is underrepresented or which
118
00:09:31.210 --> 00:09:33.929
energy is underrepresented in your team, in a current team,
119
00:09:34.690 --> 00:09:40.200
is a genuinely practical hiring and team design tool. Not
120
00:09:40.299 --> 00:09:47.779
some abstract personality exercise. Yes, having super, super similar set
121
00:09:47.820 --> 00:09:52.299
of people has a lot of risks. A lot of risks.
122
00:09:53.929 --> 00:09:58.809
And From the first perspective, it can be cool because
123
00:09:58.830 --> 00:10:03.149
people are similar. it's easier to communicate, people have flow,
124
00:10:04.009 --> 00:10:08.629
but it works when things are good and things are
125
00:10:08.980 --> 00:10:13.600
harder and stressful and there's pressure. People go into distress
126
00:10:13.659 --> 00:10:22.039
and then the real battle starts. And One more part
127
00:10:22.080 --> 00:10:27.269
from the CQ perspective, and we are going into conflicts.
128
00:10:27.289 --> 00:10:31.889
And underneath this whole belief, because we only hire stars,
129
00:10:32.929 --> 00:10:37.279
often isn't really the competence at all. It is a
130
00:10:37.340 --> 00:10:44.480
conflict of values, wearing a hiring policy costume. And there's
131
00:10:44.500 --> 00:10:47.980
a belief that individual brilliance is what makes things win
132
00:10:48.399 --> 00:10:53.820
versus a belief that complementary contribution is what makes things win.
133
00:10:55.940 --> 00:11:00.409
So those are genuinely different value systems. And most organizations
134
00:11:00.470 --> 00:11:04.710
have never actually debated which one they believe in. They
135
00:11:04.730 --> 00:11:08.929
just inherited the first one from the start of folklore,
136
00:11:09.350 --> 00:11:15.009
never questioned it. So what I would love for you
137
00:11:15.029 --> 00:11:19.230
to do in practice. So first of all, map your
138
00:11:19.269 --> 00:11:24.389
current team's composition. Do it honestly. See if you have
139
00:11:24.429 --> 00:11:28.279
people who underperform, who are maintenance people doing their job
140
00:11:28.379 --> 00:11:33.200
very well, very steadily, and how many rock stars you
141
00:11:33.240 --> 00:11:36.970
have in your team. I would say it's like 20, 60,
142
00:11:36.960 --> 00:11:44.899
20 or 10 people. 70, 20, or 10, 60, 30,
143
00:11:44.899 --> 00:11:48.679
or something like that. We don't want to have underperformers
144
00:11:48.759 --> 00:11:52.620
in our team, but it happens. And sometimes there are faces.
145
00:11:56.149 --> 00:12:00.509
Sometimes it is just time to split up, to look
146
00:12:00.549 --> 00:12:05.990
for another options for underperforming people, because maybe this is
147
00:12:06.070 --> 00:12:09.070
not the best place for them to work at. So
148
00:12:09.769 --> 00:12:14.450
do the math. Do it honestly. Don't do it by
149
00:12:14.570 --> 00:12:19.029
title or seniority level, but by the kind of contribution
150
00:12:19.490 --> 00:12:24.019
each person actually makes. Who pushes, who questions, who studies,
151
00:12:24.080 --> 00:12:28.080
who finishes. And most teams find real gaps that they
152
00:12:28.240 --> 00:12:31.840
hadn't even noticed at all. And it is not about
153
00:12:31.879 --> 00:12:34.740
the level of experience, the years of experience, and the
154
00:12:34.799 --> 00:12:43.360
level of seniority. It is about the approach to work. Second,
155
00:12:43.519 --> 00:12:49.039
the next time you're hiring, ask the team what they need.
156
00:12:49.059 --> 00:12:56.360
A brilliant candidate who duplicates the strength that you already
157
00:12:56.399 --> 00:12:59.799
have in abundance in a team may add less than
158
00:12:59.840 --> 00:13:02.539
a solid candidate who fills a genuine gap that you
159
00:13:02.610 --> 00:13:04.990
already have in a team and needs to be fulfilled.
160
00:13:06.950 --> 00:13:10.889
So the most impressive candidate on paper might not be
161
00:13:10.970 --> 00:13:17.350
your best choice at the moment. And if something, next time,
162
00:13:17.549 --> 00:13:21.649
if something is not working, there's a team conflict or
163
00:13:21.669 --> 00:13:27.629
a misunderstanding or something that is happening, ask the team
164
00:13:27.649 --> 00:13:32.990
if this is a competence problem or a composition problem.
165
00:13:35.529 --> 00:13:39.009
Whether the friction is about someone underperforming or about the
166
00:13:39.200 --> 00:13:44.929
team simply lacking a specific kind of contribution nobody currently provides.
167
00:13:46.669 --> 00:13:51.460
Because the A player team might come with a cost.
168
00:13:52.559 --> 00:13:55.200
And of course, I'm not saying, as I said at
169
00:13:55.220 --> 00:13:57.720
the very beginning, I'm not saying do not recruit, do
170
00:13:57.759 --> 00:14:04.070
not hire great people. Hire them. Hire them. And be
171
00:14:04.110 --> 00:14:08.340
mindful about the team's composition. You need people who will
172
00:14:08.419 --> 00:14:12.230
maintain work, who will maintain products, who will answer boring,
173
00:14:12.259 --> 00:14:16.210
repetitive questions from clients, who will answer the same time
174
00:14:16.850 --> 00:14:20.049
and the same question all the time. And A players
175
00:14:20.129 --> 00:14:23.409
are just bored with that. And some people love it.
176
00:14:24.070 --> 00:14:28.370
So build your team to have both. Because this is
177
00:14:28.389 --> 00:14:33.019
the success for AlhaLeader. And this is it for today's episode.
178
00:14:33.840 --> 00:14:38.950
Thank you very much for listening in. And I'm going
179
00:14:38.970 --> 00:14:41.610
to see you very soon in the next episode of
180
00:14:41.649 --> 00:14:45.590
the Lemon Tech Leadership Podcast. And if you want more
181
00:14:45.809 --> 00:14:48.340
and don't want to waste time on looking for all
182
00:14:48.500 --> 00:14:52.879
over the internet for things that are actually meaningful and valuable,
183
00:14:52.940 --> 00:14:56.139
just go and be on the Pulse list. Leadership Pulse
184
00:14:56.200 --> 00:14:59.600
is there for you. I'm doing it every Sunday. Elementskills.com
185
00:14:59.620 --> 00:15:03.759
forward slash Pulse, P-U-L-E-S-E. Go and leave your email and
186
00:15:03.799 --> 00:15:06.389
just be on the list. This is the easiest way
187
00:15:06.429 --> 00:15:09.179
you can do it better as a leader. Thank you
188
00:15:09.200 --> 00:15:13.480
very much. And I'll see you soon in the very
189
00:15:13.500 --> 00:15:16.929
next episode of the Lemon Tech Leadership Podcast. Bye, everybody.