Background
A couple of years ago, I was thinking about promotion to Senior Consultant role, which required me to demonstrate my leadersh...
For further actions, you may consider blocking this person and/or reporting abuse
You can use this mentality every day, regardless of role. The only point I would disagree with is "pulling your weight and even more". It's not good to be that guy that has too much on his/her plate, you're a leader not a worker. You need to be freely available and ready to make decisions and provide support. You can't do that if your workload is too high. Further it sends mixed messages to your team, should they be working like you? Why didn't you just say if that's what you expected? It's setting up a bunch of problems that will tick away until they explode. And they will explode.
Just do your job. Do it well. Don't over think things.
Oh and if someone asks you to lead a team AND do a team member job - say no. That's a mug's game and you'll be setting yourself up for a kicking. Respectfully decline.
Agreed. It's easier to fall into the temptation of displaying your bravado by doing the team members work but it comes with a heavy price of neglected responsibilities of a leader.
Have you ever been in the situation where the team you're leading has a developer who's quite out of their depth? I've been in a situation where a developer who was employed as a senior, but worked at a more junior-mid level. How do you go about leading there? I found they were often quite headstrong (as I once was as a mid-level who "knew it all").
Not been in such situation, but I'd say you wouldn't know until they show their willingness to try.
Even then, with some mentoring and coaching you will help them grow and also understand their gaps and start filling them.
This article was for those who believe they're ready but don't have a chance to prove themselves because they think they should have a title to be able to lead
Thank you. I must admit, it was very difficult, and something I always considered a failure on my part. For my part, the most success came from repeating spoken agreements in writing, and documenting all procedures, practices, and guidelines as best as possible. It did feel a little overkill as all of that was effectively for only one person in the team, and the vast majority of it had no benefit for other team members (e.g. when it was documentation on a ticket of work that was not going to be looked at once completed), but it did help get some other good practices going in the team with documenting against the dreaded "bus" situation.
This couldn't have come at a better time. I've been made team-lead of a very young project yet I have close to zero leadership experience. Thank you
Good luck 👍🏽
Hello, wow thanks a ton for this! Very good article, I have the same thoughts :)
Glad you enjoyed it ☺️