TRANSKRIPT 🔗
WEBVTT
1
00:00:00.580 --> 00:00:03.839
Hi, everybody. It is Alex. Let me ask you something.
2
00:00:04.320 --> 00:00:05.019
Do you know Mike?
3
00:00:05.559 --> 00:00:08.599
You know, the best engineer on the team promoted to
4
00:00:08.660 --> 00:00:14.539
lead and suddenly drowning? Nobody trained him to manage others.
5
00:00:15.820 --> 00:00:20.239
Nobody trained you either. This is exactly why I wrote
6
00:00:20.320 --> 00:00:23.809
From Code to People, the CQ leadership method that transforms
7
00:00:23.969 --> 00:00:27.530
technical experts into leaders teams actually want to work for.
8
00:00:27.989 --> 00:00:31.739
It's not another leadership theory book. It is the practical
9
00:00:32.159 --> 00:00:35.619
system that I use with tech leaders every single day.
10
00:00:36.869 --> 00:00:39.590
Built on three main tools that you can start using
11
00:00:39.969 --> 00:00:45.829
right away. Process communication model, PCM, three-level contracting, and the
12
00:00:45.869 --> 00:00:50.810
will of conflict. Real frameworks for real conversations with real
13
00:00:50.969 --> 00:00:54.869
engineers like Mike. If you're a technical expert who got
14
00:00:54.909 --> 00:00:58.950
promoted into people management and nobody handed you an app,
15
00:00:59.590 --> 00:00:59.950
this book.
16
00:01:02.090 --> 00:01:14.010
Grab it at from code2people. lemonskills. com. That's from code2people. lemonskills. com.
17
00:01:13.189 --> 00:01:18.560
Welcome to the Lemon Tech Leadership Podcast. My name is
18
00:01:18.590 --> 00:01:23.099
Aleksandra Lemanska. I'm a former violinist turned management engineer turned
19
00:01:23.180 --> 00:01:28.390
organizational psychologist, speaker and PCM leadership mentor and facilitator. In
20
00:01:28.430 --> 00:01:31.109
this space, everyone is invited to the table where we
21
00:01:31.170 --> 00:01:38.390
have real eye-opening conversations about tech leadership. Two keywords, utility
22
00:01:38.510 --> 00:01:43.659
and real-life implementation. Knowledge, tools, frameworks, ways of working, do's
23
00:01:43.700 --> 00:01:47.060
and don'ts, taken from my personal experiences as a leader
24
00:01:47.219 --> 00:01:50.040
and the experiences of others, is what you are going
25
00:01:50.079 --> 00:01:54.120
to get from every single episode. This is the Lemon
26
00:01:54.159 --> 00:02:01.370
Tech Leadership Podcast. Okay, so let's go. and take some action. Hi, everybody.
27
00:02:01.390 --> 00:02:04.640
Good morning and welcome to another episode of the Lemon
28
00:02:04.670 --> 00:02:09.060
Tech Leadership Podcast. Today, I would love to focus on
29
00:02:09.139 --> 00:02:12.039
the thing that is happening on the market right now.
30
00:02:12.979 --> 00:02:17.379
Going back to IC roles by leaders that sometimes they
31
00:02:17.400 --> 00:02:21.400
were leaders for years and sometimes they were great leaders,
32
00:02:21.699 --> 00:02:25.189
very high in the organization, big organization, and they're coming
33
00:02:25.259 --> 00:02:28.819
back to the IC role. So this is interesting. And
34
00:02:28.840 --> 00:02:31.000
I would love for us to have a conversation about
35
00:02:31.039 --> 00:02:34.740
it today. And if you are interested in how the
36
00:02:34.759 --> 00:02:38.599
landscape is changing, there is a great, great, great episode,
37
00:02:39.060 --> 00:02:44.629
another episode that I had about all of the changes
38
00:02:44.650 --> 00:02:47.110
that are happening, the changes that are happening when it
39
00:02:47.189 --> 00:02:55.169
comes to the development teams. So how new expectations from
40
00:02:55.289 --> 00:03:01.030
different levels of companies of engineers are there. So the
41
00:03:01.069 --> 00:03:03.650
changes in developers team, we had a great conversation about
42
00:03:03.669 --> 00:03:07.530
that with Jordan Cutler. It is episode number 166. So
43
00:03:07.680 --> 00:03:09.819
if you are interested, go back to this episode because
44
00:03:09.840 --> 00:03:13.080
this is amazing. And this is one of the best
45
00:03:13.120 --> 00:03:15.840
conversations I have in years about what is changing in
46
00:03:15.860 --> 00:03:19.719
the market. So highly recommend. And I wanted to have
47
00:03:19.740 --> 00:03:24.280
this conversation today because that's used to be so rare
48
00:03:24.990 --> 00:03:28.909
to have that in front of my face. But right now,
49
00:03:29.069 --> 00:03:34.430
it is becoming much more common. So a leader, sometimes
50
00:03:34.469 --> 00:03:38.870
a very good one, telling me quietly that they want
51
00:03:38.930 --> 00:03:43.069
to go back to being an IC, an individual contributor,
52
00:03:44.569 --> 00:03:48.120
and feeling like admitting that outlaw is some kind of
53
00:03:48.199 --> 00:03:53.319
confession or something that they should be afraid of or
54
00:03:53.379 --> 00:03:58.939
just be, you know, they're worried. And, um, It really isn't.
55
00:04:00.509 --> 00:04:03.610
And I think that specific transition is about to become
56
00:04:03.650 --> 00:04:06.229
a lot more common as AI native teams get flatter
57
00:04:06.250 --> 00:04:09.810
and we are going to need fewer layers of management
58
00:04:10.710 --> 00:04:15.370
and value deep specific expertise more visibly than they have
59
00:04:15.389 --> 00:04:19.949
in years. And today's episode is for anyone who's thinking
60
00:04:20.009 --> 00:04:24.250
about that and feeling guilty maybe about quitting the leadership
61
00:04:24.269 --> 00:04:27.250
path that they worked so hard on over the years.
62
00:04:29.279 --> 00:04:32.399
And here's why it feels so loaded for so many years.
63
00:04:33.139 --> 00:04:36.129
Because the entire trajectory most of us were taught is
64
00:04:36.170 --> 00:04:40.949
that leadership is the natural, correct next step up from
65
00:04:41.009 --> 00:04:45.209
technical work. And that moving back towards, I see, work
66
00:04:45.310 --> 00:04:48.509
is a step back, a failure, or at best, giving up.
67
Load full transcript
00:04:49.509 --> 00:04:54.399
And almost nobody frames it as what it often actually is.
68
00:04:55.500 --> 00:05:01.009
A legitimate, sometimes better fit. And the AI moment is
69
00:05:01.089 --> 00:05:05.620
changing the math underneath this too. As tools absorb more
70
00:05:06.000 --> 00:05:10.259
of the coordination and answer giving work leaders used to do,
71
00:05:11.120 --> 00:05:16.000
some of what made leadership roles necessary is generally shrinking,
72
00:05:16.779 --> 00:05:21.319
while deep, specific, technical, or creative expertise is becoming more
73
00:05:21.360 --> 00:05:26.370
visible and more valuable, not less. And for some people,
74
00:05:26.430 --> 00:05:28.870
the hardest answer to where do I create the most
75
00:05:28.930 --> 00:05:32.129
value right now is pointing back toward I see work
76
00:05:33.189 --> 00:05:37.310
and treating that as shameful serves nobody, not the person,
77
00:05:37.490 --> 00:05:40.889
not the organization, losing good judgment to the title they
78
00:05:40.930 --> 00:05:45.470
never actually wanted. And the real obstacle usually is in
79
00:05:45.490 --> 00:05:51.009
the org chart. It's the identity. Because somewhere along the way,
80
00:05:51.610 --> 00:05:56.769
the leader became attached to self-worth Status being taken seriously
81
00:05:56.790 --> 00:06:01.009
and stepping back from it can feel like losing all
82
00:06:01.069 --> 00:06:04.490
three at once, even when the actual work would be
83
00:06:04.529 --> 00:06:10.100
a genuinely better fit. And this is the same move
84
00:06:10.269 --> 00:06:13.259
we talked about in the imposter syndrome episode, but run
85
00:06:13.319 --> 00:06:19.560
in the reverse. So again, contracting with yourself matters here
86
00:06:19.759 --> 00:06:23.980
just as much as contract with your organizations. The all-implicit
87
00:06:24.079 --> 00:06:28.069
contract was probably something like, my worth is proven by
88
00:06:28.149 --> 00:06:32.750
climbing the ladder. Nobody wrote it down, but it's been
89
00:06:32.790 --> 00:06:37.050
running quietly for years. And going back to IC without
90
00:06:37.149 --> 00:06:43.160
renegotiating the contract means carrying the old scorecard into a
91
00:06:43.199 --> 00:06:46.860
role it was never designed to measure and feeling like
92
00:06:46.879 --> 00:06:49.399
you're failing by a metric that no longer applies to you.
93
00:06:50.970 --> 00:06:53.149
So the new contract has to be written on purpose.
94
00:06:54.009 --> 00:06:57.009
My work here is proven by the depth and quality
95
00:06:57.060 --> 00:07:00.100
of what I built, not by how many people report
96
00:07:00.120 --> 00:07:03.939
to me. It's not a consolation prize, if you ask me.
97
00:07:04.199 --> 00:07:08.160
It's a genuinely different valid measure of value, and it
98
00:07:08.259 --> 00:07:11.639
only works if you actually believe and state it, rather
99
00:07:11.680 --> 00:07:15.180
than quietly still scoring yourself against the old leadership ladder.
100
00:07:17.370 --> 00:07:20.389
And bringing PCM in, because we need it, of course,
101
00:07:20.709 --> 00:07:25.569
is the failures, quote-unquote failure narrative attaches differently depending on
102
00:07:25.610 --> 00:07:29.730
your base. So for a presister-based person, the fear is
103
00:07:29.829 --> 00:07:33.990
often about status and being taken seriously by people whose
104
00:07:34.050 --> 00:07:38.529
respect matters to them. On the other hand, for the
105
00:07:38.569 --> 00:07:42.509
promoter-based person, it can be about visibility and recognition and
106
00:07:42.670 --> 00:07:47.110
impact and power, or a thinker-based person, it's often about
107
00:07:47.189 --> 00:07:52.060
whether the decision is logically defensible when everyone around them
108
00:07:52.120 --> 00:07:55.939
assumes it isn't. Knowing which version of the fear is
109
00:07:55.980 --> 00:08:00.540
actually yours makes it much easier to address directly instead
110
00:08:00.579 --> 00:08:02.980
of arguing with the version of the fear that isn't
111
00:08:03.060 --> 00:08:07.170
the one that you're actually carrying. So if you're thinking
112
00:08:07.410 --> 00:08:11.129
about coming back to the IC role in this crazy world,
113
00:08:11.930 --> 00:08:14.649
I have some things for you to think about and
114
00:08:14.790 --> 00:08:17.790
it might be helpful. So just a checklist to the
115
00:08:17.829 --> 00:08:21.629
questions to think about once you are making your decision.
116
00:08:21.649 --> 00:08:25.550
So first of all, if you're considering this move, write
117
00:08:25.629 --> 00:08:30.269
down honestly what you think you'll be losing and what
118
00:08:30.310 --> 00:08:34.889
you think you'll be gaining separately before you talk yourself
119
00:08:35.110 --> 00:08:38.409
out of it or into it based on how it
120
00:08:38.480 --> 00:08:42.710
sounds to other people. So if I will come back
121
00:08:42.730 --> 00:08:46.789
to IC, what will I lose, potentially, and what can
122
00:08:46.870 --> 00:08:51.279
I gain, potentially? So make a list. Just take a
123
00:08:51.299 --> 00:08:55.320
piece of paper, go to the line in the middle
124
00:08:55.340 --> 00:09:02.240
of it, and just fill out the page. Second, have
125
00:09:02.259 --> 00:09:10.059
a direct conversation with your own leadership. rather than letting
126
00:09:10.080 --> 00:09:15.019
the shit happen through quiet disengagement or resignation. But frame
127
00:09:15.070 --> 00:09:19.570
it very well. You can use something like, I think
128
00:09:19.610 --> 00:09:24.169
I create more value doing deep technical work now than
129
00:09:24.210 --> 00:09:28.779
managing others. It is a legitimate, useful piece of information
130
00:09:28.840 --> 00:09:33.659
for an organization, not a resignation letter. You can do it.
131
00:09:33.720 --> 00:09:37.259
You can also talk with somebody else, a coach, a mentor,
132
00:09:37.740 --> 00:09:42.120
a person who'd already done that in your network, stepped back,
133
00:09:42.860 --> 00:09:46.019
quote unquote, step back course, or move to the different
134
00:09:46.059 --> 00:09:51.789
organization within the idea of being an IC. And the
135
00:09:51.830 --> 00:09:54.669
third thing is about new contract that you are going
136
00:09:54.690 --> 00:09:59.769
to have with yourself because you need it to reshape
137
00:09:59.789 --> 00:10:03.950
your brain and your wiring. One specific thing that proves
138
00:10:03.970 --> 00:10:08.580
you're worth in this role, not the old leadership scorecard
139
00:10:08.659 --> 00:10:13.279
that we mentioned. Revisit it in the moments that you
140
00:10:13.960 --> 00:10:18.539
doubt yourself and the old identity voice shows up uninvited
141
00:10:18.799 --> 00:10:21.750
because it will. So you are going to be prepared.
142
00:10:23.710 --> 00:10:27.750
So just make your list, just analyze the situation. There
143
00:10:28.049 --> 00:10:31.820
are not good and wrong answers. This is your answer.
144
00:10:32.480 --> 00:10:37.659
You own your own career. So don't let old beliefs
145
00:10:37.759 --> 00:10:42.679
or beliefs of other people or society's expectations or thoughts
146
00:10:42.700 --> 00:10:47.919
to say to you what to do because you are
147
00:10:47.980 --> 00:10:51.950
the owner and this is your choice. And there's nothing
148
00:10:52.049 --> 00:10:54.190
wrong with coming back to the IC role if you
149
00:10:54.389 --> 00:10:56.470
think that this is a good idea and you really
150
00:10:56.529 --> 00:10:59.519
want to do it because leadership can be exhausting. An
151
00:11:00.840 --> 00:11:04.059
IC role as well, of course, but let's be honest
152
00:11:04.100 --> 00:11:07.820
about it. Leadership is super complex and can be super exhausting.
153
00:11:07.860 --> 00:11:09.620
So if you want to step back out of this role,
154
00:11:10.000 --> 00:11:10.860
you always can.
155
00:11:11.820 --> 00:11:12.179
Always.
156
00:11:12.919 --> 00:11:17.519
Everything is a choice. So this is it. Thank you
157
00:11:17.539 --> 00:11:23.240
for listening to this episode. I hope it was helpful. interesting, game-changing,
158
00:11:23.980 --> 00:11:28.039
and just saying yes to yourself instead of constant no.
159
00:11:29.700 --> 00:11:33.100
And if you are more interested in those things, just
160
00:11:33.120 --> 00:11:35.799
grab a book from Code to People. This is the
161
00:11:35.840 --> 00:11:41.409
source of truth, the source of tools, etc. So go
162
00:11:41.470 --> 00:11:45.710
to grab it from Code to People at lemaskills.com or
163
00:11:45.809 --> 00:11:49.990
any Amazon all around the planet. Until next time. Lead
164
00:11:50.029 --> 00:11:53.320
without burnouts. And I'll see you very soon in the
165
00:11:53.360 --> 00:11:56.019
next episode of the Lehman Tech Leadership Podcast.
166
00:11:56.600 --> 00:11:57.039
Bye, everybody.