[ttldomination]

Originally Posted by DJB11

For the upcoming season, our team is organizing the Technical and Non-Technical aspects into a "branch system", in which students manage sub teams appropriate to the category they are leading.

The Project Lead is a non-technical position that manages Chairman’s, Business, Graphics, and Spirit. These sub teams, which not having an official leadership role, will report to the Project lead, and work as a cohesive unit.

The Robot Lead serves as a resource of knowledge and experience for all four tech sub teams, and is responsible for coordinating frequent meetings between the four technical captains(mechanical, electrical, design, programming) , where the five will make all major robot decisions. The robot lead does not make executive decisions alone, but does ensure that important decisions are being made.

The Organizational Lead will keep the team roster and job assignments organized. They attend and assist to the creation of the build season schedule, which the robot lead will enforce. Staying up to date with PR and CD, they will manage the game analysis and strategic design components of build, working closely with the technical captains.

This is our teams format, where Robot lead serves more in the technical field, Project lead attends to Non-technical sub teams, and Organizational focuses on coordination.

Hope that helped.

So, that's a good view into your leadership structure, but how do you structure students within those groups? Do you encourage participation in multiple groups or ask students drill down in their one area?

- Sunny G.