Advice for new Technical Lead

[AlexanderLuke]

Originally Posted by hrench

Best advice is to read this forum.

I cannot stress the importance of learning from CD. So much of my understanding has been developed through independent study and research outside of my own scope of work on my team. There are posts, threads, and information from over a decade ago on this site. Information from teams of all spectrums can be found here, and with time and diligence, Chief Delphi can be an invaluable resource for anyone.

Originally Posted by Thayer McCollum

I would say that one of the most important things that you can do is to ask questions.

This too. Never be afraid to ask questions. We have all been a rookie once. We get into new leadership positions now and then. There are people out there who will share their experience and knowledge with you.

[ElliottB]

Maybe I should clarify.The tech lead oversees the technical side of the team and acts as a team captain.

[Harman341]

I had a similar position on 341 my senior year and found out at roughly the same time (one week before build season)

My tips:
Watch gamesense's video on how to prototype, it's life changing.

If you think someone's idea is dumb, you probably don't understand them

Try your best not to build anything without teaching someone what you're doing

Always remember, as a build team leader, you have a lot of credibility. If you are about to do something stupid, nobody is going stop you.
-watch MAR champs F2, it was my idea to try hanging on one hook

As a follow up, don't worry about getting more credibility, you already have plenty, feel free to admit mistakes or that some/most of your ideas are bad.

If you need a good idea, watch videos of old matches

Always keep an eye on the room, who is there, who isn't, who looks like they're not contributing, who looks bored, who is telling the rookies to sweep the floor while they build fancy stuff. Those are all easily solvable problems, but addressing them can really change your team for the better.

Lastly, my biggest regret, it was said before, but it can't be said enough, ask your mentors questions. Here's why:
1-It makes them feel respected
2-You two will become friends
3-They will be happy that they taught someone about robots
4-You will learn about robots
5-You are less likely to do the stupid thing that everyone was going to let you do
6-Mentors also do stupid things, being friends makes it easier to stop them
7-Newer members will see you asking questions and do the same

Making this thread was a great start to your new job. Keep it up and you'll be fine.

[DonRotolo]

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.

[Conor Ryan]

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.

[billbo911]

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.