Team Organization

[RamZ]

Here's an excerpt from our team manual, regarding lead positions:

• Team Captain / COO - Avak Archanian
  The COO will serve as the non technical lead in charge of everything that is not the robot including, but not limited to: team logistics, fundraising events, team bonding, community outreach, and team finances.
  
• Team Captain / Lead Engineer - Maddie Magno
  This role serves as the technical leader in charge of everything that is the robot. The role includes but is not limited to: overseeing the part management system, maintaining the manufacturing schedule, managing the Gantt chart, setting the order list, and working with sponsors to get parts made.
  
• Manufacturing - Adam Shrager
  The Manufacturing lead is responsible for maintenance of all the machines in the shop and ensuring all parts are completed to spec. This means going through and measuring every part after the machinist has completed it and signing off on the drawing as well. In addition they are responsible for training on the machines and shop safety.
  
• Public Relations - Rachel Alaynick + Ram Zallan
  This position has three main functions: team to sponsor communication, communication with other teams in FIRST, and community outreach. The functions of team identity go hand in hand with this position so the position will also be responsible for social media and team branding.
  
• Programming - Christian Locker + James Kradjian
  The programming lead is responsible for the robot code. This includes a working drive code, manipulator function, and autonomous mode. Programming is a full time teaching/working position where the lead will have to not only get their own work done but ensure the upcoming programmers are constantly learning more.
  
• Electronics - Sidney Ortega
  The Electrical and Pneumatics lead is responsible for all electrical systems on the robot. This includes procuring batteries and all wiring for the robot as well as drawing full electrical system layouts. In addition to electrical systems the lead is responsible for the pneumatic systems on the robot. Ensuring that all tubing is routed correctly and we are safely operating our pressurized pneumatic system. This lead will work with the mentors to spec correct pneumatic cylinders for robot actuation.

We have 8 leads currently, but this is only because of our larger team size. We try our best not to be departmentalized, as everyone on our team does a little bit of everything. Like others have said, it all depends on the different aspects of your team, for example, if your team doesn't have a dedicated machine shop like our team, you may not need a manufacturing lead. The system of leads updates depending on what your team needs, so it'd be hard to say exactly what you should do.

[GeeTwo]

Tying way back to the first reply post, the bottom line is that the team organization is a means to help you accomplish your goals - if the structure gets in the way, CHANGE IT! 3946 Tiger Robotics has had a slightly different organizational structure (divisions split, merge, just plain change) each year in response to a number of factors (not necessarily complete):

Who are the leaders - make sure that the amount and type of responsibility matches people's abilities and commitment levels (be challenging, but not overwhelming). We have split or merged divisions based on the would-be leader's capabilities. Sometimes you have a good candidate for a single team captain; sometimes not, so you might have two co-captains with complementary strengths.

What worked well last year - keep it, or build/tweak on it slightly.

What failed last year - even if the structure should have worked, change it around. On at least one occasion, we eliminated a division not because it wasn't needed, but because it had become a home for goof-offs the year before. Said (non-robot build) division became a "committee" instead.

On the other hand, don't reorganize just because you can -- while all improvement is change, NOT all change is improvement!