EPISODE · May 26, 2026 · 15 MIN
#163 | “I Know I Should Say No. So Why Can't I?”
from Leman Tech Leadership Podcast · host Aleksandra Lemańska
#163 | “I Know I Should Say No. So Why Can't I?”In this solo episode of the Leman Tech Leadership Podcast, Aleksandra Lemańska takes on one of the most persistent gaps between what tech leaders know and what they actually do: saying no.Almost every leader Alex works with already knows, intellectually, that they should say no more often. They've read about it. They've advised their own team to do it. And then a stakeholder drops something on their desk, a peer asks for support just outside their remit, or their manager adds one more thing to the quarter, and they say yes. Again. The frustration afterward is real. And it's almost never about weakness or conflict avoidance.Alex identifies the three real roots of the problem. The first is identity: for most tech leaders, saying yes was the behavior that built their reputation and career as individual contributors, and the psychological cost of saying no now feels like a betrayal of who they are. The second is the absence of a clear enough set of priorities to say no to: a Contracting failure that leaves every incoming request feeling equally valid. The third is simply not having the language: knowing what you want to decline but having no way to do it that doesn't feel like a fight or a relationship risk.If you've ever walked out of a meeting having said yes to something you knew you shouldn't have, this episode gives you the understanding and the tools to change that pattern.✉︎ FOLLOW ME ON: ⤵︎LinkedIn: @aleksandralemanskaTikTok: @aleksandra_lemanskaX: @lemanskillsStartup Community Poznan: @startup-community-poznan-scpwww.lemanskills.comJoin Leadership Pulse! https://lemanskills.com/pulse/
What this episode covers
#163 | “I Know I Should Say No. So Why Can't I?”In this solo episode of the Leman Tech Leadership Podcast, Aleksandra Lemańska takes on one of the most persistent gaps between what tech leaders know and what they actually do: saying no.Almost every leader Alex works with already knows, intellectually, that they should say no more often. They've read about it. They've advised their own team to do it. And then a stakeholder drops something on their desk, a peer asks for support just outside their remit, or their manager adds one more thing to the quarter, and they say yes. Again. The frustration afterward is real. And it's almost never about weakness or conflict avoidance.Alex identifies the three real roots of the problem. The first is identity: for most tech leaders, saying yes was the behavior that built their reputation and career as individual contributors, and the psychological cost of saying no now feels like a betrayal of who they are. The second is the absence of a clear enough set of priorities to say no to: a Contracting failure that leaves every incoming request feeling equally valid. The third is simply not having the language: knowing what you want to decline but having no way to do it that doesn't feel like a fight or a relationship risk.If you've ever walked out of a meeting having said yes to something you knew you shouldn't have, this episode gives you the understanding and the tools to change that pattern.✉︎ FOLLOW ME ON: ⤵︎LinkedIn: @aleksandralemanskaTikTok: @aleksandra_lemanskaX: @lemanskillsStartup Community Poznan: @startup-community-poznan-scpwww.lemanskills.comJoin Leadership Pulse! https://lemanskills.com/pulse/
NOW PLAYING
#163 | “I Know I Should Say No. So Why Can't I?”
No transcript for this episode yet
Similar Episodes
Mar 26, 2026 ·1m
Jan 2, 2026 ·47m
Dec 21, 2025 ·46m