Last year, I got offered and trust to be a lead in my team. To be honest, that was my first time I become a lead in my career. First thing that come to my mind was,
If I become a lead, then I will have N peoples that will be my responsibility, I will be one of the factor of their good and bad
That was not easy choice, but thanks to my supportive lead and also supportive colleague. I become a lead for about six months and that was a great experiences!
Become a Lead is Not Only About Get the Projects Finished
Projects will finished with good results if you know how to do it well. Unfortunately, to do it well is not always about how good you’re in technical things. My first challenge is to ensure my team get exposured to stakeholder, this is really helpful since it will remove the communication overhead from stakeholder <-> myself <-> my member. Instead, I tried to connect my members to stakeholder directly and observe. After that, we can review or plan accordingly in our planning session.
You Might Fail If You Don’t Know Your Members Well
I found that it’s easier for me to work with my team when I already know the strength and weakness for each member, then I can discuss with my peer or my lead to improve / enhance it. Getting to know and understand your team is important, and this is the part that I really enjoyed when lead the team, understand their interest, their goals, help each other to reach the goals. Thats fun! Your empathy and emotion are important part in here.
There are Something More Important Than Projects
Projects accomplishment usually used to measure the performance. But, not only that, there are more important thing to solve and to improve. Culture and growth mindset, creating positive cultures are not easy as finishing projects. Culture and mindset built incrementally and will not work if only your team have it, it should be propagated to entire company or at least your neighbor team. Invest on building a great culture and mindset might not directly impact in short term, it will be a long term impact / effect.
Collaborative Coaching I Would Say?
There might be a condition where you asked for help from another team about how to develop the team. Don’t get back and think like that their problem. Instead, learn and work together.
But Still, Technical Skill Will Helps If You’re a Tech Lead
I relatively new in term of work experiences. I admit that my technical skill still shallow, so it was challenging to me. Good technical knowledge will very helpful when you review a plan, or give suggestions about some implementations. Since my knowledge still limited, what I’m doing was connect my members with known expert people in the topics. So that I’m not blocking the projects, in the same time I can learn something new from the experts. I suggest to have some technical knowledge first if you’re going to be a tech lead, because it will be relatively easier and others will not see you with half-eye.
Thats all my first experience when become a lead for about six months, it was great experience for me. Previously, I relatively don’t speak too much and it was improved how I communicate with others. Right now, I moved to another role and officially not a lead. But, to me lead is not only about a role but the mental, as we called it leadership.