Advice for new Technical Lead

[ElliottB]

Hi I am the new Tech lead for #45 and I had found out on relatively short notice a few weeks ago. Do you guys in the FIRST community have any advice that could help? I am getting some help from the prior tech lead and the mentors are very supportive.

[hrench]

Best advice is to read this forum.

Also, use ideas from previous robots that worked.

[StAxis]

Being a lead can be a stressful position, especially in FRC where we only have 6 weeks to build and sometimes only 6 minutes to make a fix in the middle of a competition. I'll give you some advice that a wise friend once gave me when I was putting too much on my own shoulders.

When things get stressful, focus on building your team. You've got a lot of people around you who want to help you. Don't take too much stress on yourself, as a lead it can feel like it's all on you, but whenever you feel like that, remember to build your team.

This year we took a big leap in giving a lead mechanical position to a first year student. We did this because, even though he is new, he has shown dedication and hasn't been afraid to communicate and ask questions. Trust yourself, you were chosen for a reason, and when you feel like you don't know what you're doing, don't hesitate to ask. Us mentors really are here to answer your questions and help, and we love doing it!

Read everything you can, there are dozens of fantastic teams with resources out there (254 technical binders, 1114 has lots, 2056 Ways to Inspire conference presentations, 148 and JVN's design document, just to name a few) and reading those will prepare you pretty well from the technical side.

I'm sure you'll do great, and remember, the greater FIRST community is always here to help out too!

[Peyton Yeung]

Originally Posted by ElliottB

Hi I am the new Tech lead for #45 and I had found out on relatively short notice a few weeks ago. Do you guys in the FIRST community have any advice that could help? I am getting some help from the prior tech lead and the mentors are very supportive.

Elliot,

When I was the tech lead for 45 in high school I think my biggest mistake was not keeping my teammates in the loop throughout the build process. It is easy to get bogged down in what needs to be done and just start doing. The position is technical lead not technical do it all. Be ready to work with your teammates so that everyone is informed on what needs done. There are plenty of resources on this forum you can find but I'd highly look into getting advice from some of the great support channels in INFIRST.

[Thayer McCollum]

I would say that one of the most important things that you can do is to ask questions. Every team is full of excellent, intelligent students and mentors who know a lot individually. But your team as a collective will know a lot more, so find out who knows what. As a freshman I got put in charge of designing our manipulator, and it was awful. I didn't get any help with anything, but a large part of that was because I didn't know how to ask for the help I needed. So I would suggest that you start finding out what people know about different things and make sure that you know how to ask them to help you when you don't know how to do something.

[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.