7 Comments
User's avatar
Om Prakash Pant's avatar

The hero creating dependency instead of capability - that one landed. I've seen it play out in delivery teams. The architect who never lets anyone else make a call ends up becoming the bottleneck nobody talks about. The team gets faster at waiting than at deciding.

Diamantino Almeida's avatar

This is one of the topics I discuss in my newsletter and on my upcoming book, among other stuff. The narrative of one to rule all, as it’s pros and cons.

Adela Grama's avatar

Wow…I can so much relate to your text. It is such a perfect description of the corporate world and being part of it.

Diamantino Almeida's avatar

Thank you Adela, I have had my time in the corporate world. And I have so much to tell.

Diamantino Almeida's avatar

A few things I do with my team.

Sit in on a technical meeting but commit to not saying a single word for the first 20 minutes. Observe how the team solves problems when your "talent" isn't an option.

Diamantino Almeida's avatar

We are addicted to the hit of dopamine we get from solving a hard bug or closing a ticket. But as a leader, your dopamine should come from seeing your team solve a bug you didn't touch.

Diamantino Almeida's avatar

I’ve had a few EMs reach out saying this post felt like a mirror.

If you're feeling this talent fatigue, check your social debt.

Often, we do the work ourselves not because the team is incapable, but because we are afraid of the messy conversation that comes with holding someone else accountable.