[Mark Sheridan]

We used a committee structure where most major technical (drivetrain, programing, etc) and non-technical (fundraising, media and etc) responsibilities were given a committee. Every student must be part of one technical and one non-technical committee. Often key members will be on more than two committees. Each committee issue action items so rarely there are issues with responsibilities. Each committee has a chairperson who ensures action items are carried out. Thus it is plausible for the drivetrain chair to design the shooter mechanism, with that action item being issued by the shooter chair.


As for our president, he's probably on chief delphi somewhere, he can fill in more later, was responsible for coordinating all the team's major resources. The main gantt chart was his responsibility. The committee chairs and the vice-presidents reported to him. So rarely he was in the dark. He was also technical oriented, so once the meeting was underway, he would jump in and work on his specific action items for the robot. He also took on a lot of non-technical and business action items and help manage struggling committees or committees who simply need more people.

He did a fantastic job. He knew how to keep busy and go where the help was needed most. He still found time to know the robot backwards and forwards.

Dcarr where are you?