[joe5joe7]

Team structure is something I've thought about extensively, especially with the structure my team used this year failing to accomplish the intended goal. In my opinion this would be a great system, which I predict my team will utilize next yeat.

Non-Technical leads:

President:O
overseas things, his main responsibility is to make meeting itineraries and make sure that everyone is getting things done on time. Also rus the meating and the head meetings.

Vice-President/Head of media and outreach:
Is there in order to take the presidents place in case something happens. Since there is not always something to do there he also is in charge of non-engineering related things like meda and outreach.

Technical leads:

Control Systems:
Team lead of Programming and Electrical. Will often deligate out responsibilty for one of the departments to a "sub" team lead and manage the other personaly; depending on personal preference.

Hardware:
In charge of the shop and all things in it, will often deligate responsability to people for things like drivetrain, thus creating "sub" team leads.

The way this is structured is that before every meeting the four team leads have a meeting in order to know what is going on in all of the divisions, as well as to discus and evaluate team progress. The main goal of these meetings is to finalize an itinerary for the main team meeting where important decisions are made.

The key to this working is not to expand the roles at the head meetings, as well as to make sure that all important decisions get made by the entire team.

Thoughts?