How Not To Lead A Team

Sometimes as a technical lead, you want to do what you're good at. For most leads, we've been promoted after demonstrating our competence as effective individual contributors. , you get satisfaction from solving problems - building things, writing code, fixing bugs. As an effective individual contributor, you want to be in the thick of things, getting things done. When you see your team struggling, you’re tempted to jump in and do it. It’s quicker just to do it yourself. But it's not scalable, and it doesn't leave space for the team to learn It's nice for your ego to be treated like a hero. It's not scalable, and it's not good for your health. The team don't get a chance to learn. This is the mistake that I most frequently make. Good talk on this and other things by Pat Kua at Lead Dev London 2017

Image credits

Egyptian slaves
General behind the lines
General
Balance
Mahatma Gandhi
Napoleon
Washington
Terry Butcher
Martin Luther King
Winston Churchill
Balance
Hammock
Bobby Moore
Superman
Cone of silence
Microphone
Barn
Magnifying Glass
Telescope