[Alex Golec]

While our organization was not rigidly structured, we used the availible students and mentors to take responsibilities to get work done. We did not use democracy nor tyranny, the system worked in a fairly simple manner: the students who came the most would be responsible for certain systems and parts on the robot. The mentors were involved by taking the reigns of a single system and helping out the kids who chose to work with them, and then helping the other teams as well. You do not need a thousand mentors to succeed- a few mentors and dedicated students should give a little push to the rest and get them involved as well. At the same time, students who didn't like working with the mechanical parts formed smaller subteams, like the programming group and used an old robot to try out the camera and write some autonomous modes. Some students tried their hands at animation and a few others worked on our Woodie Flowers nomination. In the end, your exact structure will depend on the number of students, mentors, and resources availible, but you should abide a few ideas to keep the teamwork going:

- Leadership is formed naturally through participation and volunteering; noone needs to be forced into any situation
- Leaders must try their hardest to inspire the involvement of others
- Share responsibilities: find talents and make the best of them
- Allow equal opportunity to those who ask for it. If it's interesting to them, let them try it!
- If ever an arguement begins to ruin cooperation, the team mediate itself and get back on track through discussion. Rash and unthoughtful actions are the most crippling to any team

I hope what I have presented will be useful to your team's reorganization. Inspiring interest in robotics and technology lays the foundation for your team. Building the robot and other functions are just the building that goes on top.

_Alex