Sign up to save your podcasts
Or
Share #167 | Your Best Engineer Is Your Biggest Leadership Problem - Now What?
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
#167 | Your Best Engineer Is Your Biggest Leadership Problem - Now What?
▶︎ #167 | Your Best Engineer Is Your Biggest Leadership Problem - Now What?
In this solo episode of the Leman Tech Leadership Podcast, Aleksandra Lemanska addresses one of the most uncomfortable dilemmas tech leaders face over and over again: what to do when your technically brilliant engineer is also destroying the team around them.
The problem is painfully familiar. Their output looks great on paper. Confronting or removing them feels risky - what if they quit? And yet every other person on the team is paying a daily cost for this person's behavior. Most leaders know it's a problem. Almost none of them know what to actually do about it.
Alex identifies three layers that make this harder than it looks. The first is structural, the second is the leader's own ambivalence, and the third is the absence of contracting. In most teams, the technical bar was clear from day one. The relational bar was implied, and implied contracts are what allow destructive behavior to thrive unchallenged.
From the CQ Leadership Method perspective, Alex walks through how to diagnose what is actually driving the behavior - and why the intervention looks completely different depending on the root cause. This is not a personality problem. It is a systems and leadership problem that a personality is simply exposing.
If you've been avoiding this conversation, this episode gives you the diagnosis and the tools to stop.
✉︎ FOLLOW ME ON: ⤵︎
LinkedIn: @aleksandralemanska
TikTok: @aleksandra_lemanska
X: @lemanskills
Startup Community Poznan: @startup-community-poznan-scp
www.lemanskills.com
Join Leadership Pulse! https://lemanskills.com/pulse/
In this solo episode of the Leman Tech Leadership Podcast, Aleksandra Lemanska addresses one of the most uncomfortable dilemmas tech leaders face over and over again: what to do when your technically brilliant engineer is also destroying the team around them.
The problem is painfully familiar. Their output looks great on paper. Confronting or removing them feels risky - what if they quit? And yet every other person on the team is paying a daily cost for this person's behavior. Most leaders know it's a problem. Almost none of them know what to actually do about it.
Alex identifies three layers that make this harder than it looks. The first is structural, the second is the leader's own ambivalence, and the third is the absence of contracting. In most teams, the technical bar was clear from day one. The relational bar was implied, and implied contracts are what allow destructive behavior to thrive unchallenged.
From the CQ Leadership Method perspective, Alex walks through how to diagnose what is actually driving the behavior - and why the intervention looks completely different depending on the root cause. This is not a personality problem. It is a systems and leadership problem that a personality is simply exposing.
If you've been avoiding this conversation, this episode gives you the diagnosis and the tools to stop.
✉︎ FOLLOW ME ON: ⤵︎
LinkedIn: @aleksandralemanska
TikTok: @aleksandra_lemanska
X: @lemanskills
Startup Community Poznan: @startup-community-poznan-scp
www.lemanskills.com
Join Leadership Pulse! https://lemanskills.com/pulse/
View all episodes
By Aleksandra Lemańska▶︎ #167 | Your Best Engineer Is Your Biggest Leadership Problem - Now What?
In this solo episode of the Leman Tech Leadership Podcast, Aleksandra Lemanska addresses one of the most uncomfortable dilemmas tech leaders face over and over again: what to do when your technically brilliant engineer is also destroying the team around them.
The problem is painfully familiar. Their output looks great on paper. Confronting or removing them feels risky - what if they quit? And yet every other person on the team is paying a daily cost for this person's behavior. Most leaders know it's a problem. Almost none of them know what to actually do about it.
Alex identifies three layers that make this harder than it looks. The first is structural, the second is the leader's own ambivalence, and the third is the absence of contracting. In most teams, the technical bar was clear from day one. The relational bar was implied, and implied contracts are what allow destructive behavior to thrive unchallenged.
From the CQ Leadership Method perspective, Alex walks through how to diagnose what is actually driving the behavior - and why the intervention looks completely different depending on the root cause. This is not a personality problem. It is a systems and leadership problem that a personality is simply exposing.
If you've been avoiding this conversation, this episode gives you the diagnosis and the tools to stop.
✉︎ FOLLOW ME ON: ⤵︎
LinkedIn: @aleksandralemanska
TikTok: @aleksandra_lemanska
X: @lemanskills
Startup Community Poznan: @startup-community-poznan-scp
www.lemanskills.com
Join Leadership Pulse! https://lemanskills.com/pulse/
In this solo episode of the Leman Tech Leadership Podcast, Aleksandra Lemanska addresses one of the most uncomfortable dilemmas tech leaders face over and over again: what to do when your technically brilliant engineer is also destroying the team around them.
The problem is painfully familiar. Their output looks great on paper. Confronting or removing them feels risky - what if they quit? And yet every other person on the team is paying a daily cost for this person's behavior. Most leaders know it's a problem. Almost none of them know what to actually do about it.
Alex identifies three layers that make this harder than it looks. The first is structural, the second is the leader's own ambivalence, and the third is the absence of contracting. In most teams, the technical bar was clear from day one. The relational bar was implied, and implied contracts are what allow destructive behavior to thrive unchallenged.
From the CQ Leadership Method perspective, Alex walks through how to diagnose what is actually driving the behavior - and why the intervention looks completely different depending on the root cause. This is not a personality problem. It is a systems and leadership problem that a personality is simply exposing.
If you've been avoiding this conversation, this episode gives you the diagnosis and the tools to stop.
✉︎ FOLLOW ME ON: ⤵︎
LinkedIn: @aleksandralemanska
TikTok: @aleksandra_lemanska
X: @lemanskills
Startup Community Poznan: @startup-community-poznan-scp
www.lemanskills.com
Join Leadership Pulse! https://lemanskills.com/pulse/