|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: Advice for new Technical Lead
Delegate.
Surround yourself with teammates who know what they are doing, and let them do it. Learn from them and teach them, as needed, but let them 'own' their subsystem and be the expert. This is how projects work in the real world: The Lead just keeps things moving and helps overcome problems, but doesn't actually own any of the subsystems. They're the players, you're the waterboy. Bring them water. Your team has the depth and breadth of talent where this will work. A very small team may need something different. Have fun, and please let us know in March how it worked out for you. |
|
#2
|
||||
|
||||
|
Re: Advice for new Technical Lead
Your success as a technical lead is not judged based on your performance this season, but on the success of the team in the seasons following your graduation.
Take time to ensure as many people as possible are engaged and helping the team move forward, the more leverage and man power you create the more your team will accomplish. |
|
#3
|
||||
|
||||
|
Re: Advice for new Technical Lead
There has been a lot of excellent advice given thus far, I don't want to change any of it.
I will add: As tech lead, you will need to guide you team through successes and failures. Successes are easy, identify what you did right and repeat it (or even improve on it). Failures are even better. Yes, I did say that and I believe it. We as humans always seem to learn more through failure than success. Do this by anylizing the failure and don't repeat it. Figure out what caused it and figure out how to prevent it from happening again. Many times you will find that what you figure out will allow you to improve way more than your original approach would have yielded. This applies to more than just design, it applies to strategy and game play too. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|