[cadandcookies]

First off, this topic has been around the block (a quick search would turn up quite a few threads). That being said, because I've never actually posted a particularly in-depth summary of my team's structure, I'll bite.

Structure:
Team 2220 has, for the past few years, structured ourselves in "subteams"-- groups of 3-7 students and a few mentors who are responsible for some particular part of the robot or team operations. This structure is a necessity for us, as we have 82 students and 35 mentors this year. Without having a well-defined structure, the team would dissolve into utter chaos (which isn't to say that it's military rigidity, but we at least need a skeleton).

These subteams each have a lead student and mentor, who are responsible for the budget, presenting at design reviews, creating a BOM (if it's a robot subteam), serving as the contact point and "face' of their subteam, and representing their subteam at weekly leadership meetings. These students apply for their position and are then selected by a group of mentors and selected upperclassmen.

Our captains serve on a year-by-year basis, and are required to be juniors or seniors,and have at least one previous year of leadership experience. They apply for the position, and then are voted on by the mentors, alumni, and students from that year. While not everyone on the team agrees with this, the rules and methodology for elections are clearly communicated.

We restructure our team three times-- for build season, for competition season, and for the outreach season. Subteams tend to be relatively concrete for build season, very rigid for competition season, and rather amorphous for outreach season.

I'll try to get an org chart that doesn't have full student names on it. Feel free to ask me any questions about our structure here or via PM.