The Leadership Setup of your Team

[Lisa Perez]

On 830, we basically have it set up so that the students are placed in charge of different projects through the season. For example, there will be the group that will always be working on build, and will take other students and show them what to do. Of the students working on the nonbuild projects, each person is held responsible for organizing something different, be it a bake sale, communication with the sponsors, scouting, etc.

It is a little less formal in that students are not exactly defined as leaders at the beginning of the season. But it also gives each and every single one of the students the opportunity to step up and be a leader while getting advice from the mentors.

If you are looking for something more formal (and something that would probably work better with a larger group), when I was on 573, we had set student leaders for the various subgroups, who would be responsible for communicating with their mentors to create a plan for said subgroups. We had a student project manager, who was in charge of making sure all of the plans were compatible and feasible and served as the main representative for the team.

[FunkyRatDemon]

Originally Posted by beemusicgeek

student leadership mainly but how each individual plays a part.
For example:
Does your team have one or multiple "top leaders"
Is it more of a hierarchy or is everyone equal?
Are there sub-teams and how are they organized?
Are there specific leaders of each sub-team?

This year our Captains were ***es, we kept them there because we didn't want mid-season collapse. It was apparent who took their place (The team recognizes them as Captains)

Next year we'll do this:
3 Captains: PR, Build and Team (Discussed later)
Captains oversee divisons and leads
There is 1 Team lead, and 1 Team co-lead (per division)
Leads decisions can be overthrown by a Capatin (if it falls under there division)
Leads can go to the team for a vote if they don't like Captains choice(s)
Mentors count as 1 vote, however they're choice of what to build counts as 0 when picking what robot to build (Start of season)
Weekly voting meetings start at 5:00, regular start at 6:00PM
3 days a week (before build season to letter)
4 days a week (start build season to letter)
PR Captain-Manages community involvement and leads meeting if Team Capt. is gone: Oversees PR, Marketing and Operations
Team Captain-Leads meeting, has more "authority" in tie breaker votes: Oversees-Animation, Inventor, Field Design, Programming* and Website
*Because of stress on Build Captain
Build Captain-Involved in Robot Construction and robot progress: Oversees Robot Design, Construction/build team, pneumatics and Machining

Animation-Makes animation and images for community
Website-Create/update website for community
Operations-Training of newer members and "utility" crew when others are absent (Up-to-date on all divisions, "fillers")
PR-Sends groups to community meetings (rotary/business conferences)
Marketing-Makes phone calls, sends PR to meets
Inventor-Robot design on computer
Field Design-Creates field for robot trial and "errand" people
Machining-Makes parts for robot
Build Team-robot assembly
Pneumatics-parts assembly
programming- makes sure robot can work/move

[K. Sehgal]

Our team is extremely unorganised, the perosn who was elected to be president dose'nt act like the president. And all of our other elected officers in other positions most don't come to the meetings.

[team 1094]

team 1094 learership lies with the oldest member on are team. this year we chose a team capataion which is usually the oldest member on the team or some that everyone ageers on. For our drive team it is teh person's who have to best drive time/ recation time. Coach gose to the person who was 3rd in reaction time/drive time.

[Vashts6583]

Over the past two or three years, we've altered our hierarchy depending on our student involvement.

Last year, do to our large size, we had a President (Senior) and 2 Vice Presidents (Also Seniors), one for mechanical, and one for business. From that, both auxiliary and drive were under the first VP, and operated seperately from each other. Our business/non-engineering department worked under our other VP. Sadly, our electrical and software group (mainly myself and one or two others) had no representation in the higher ups (but i still made my voice heard).

This year, however, due to our much smaller size, we had one president (Senior with most experience), and then a group-specific leadership based on team experience. This format allowed for less conflict among groups, and also for our new freshmen to learn alot from their older peers. Also, because we were so small, our mentors helped us out alot.

Really, you should base your student leadership around your team size, your subsections, and how you want it to function. If you want, you could even do a Knights of the Round format, where the President just helps get things started, but has equal say with the leaders of each subsection of your team, which I really wish we could implement in our team, but we're just too small as it is.

I hope this helped you out a little.

[115inventorsam]

MVRT has it like this:
Top level: President
Second level: Director of Operations, Director of Engineering
Third level: (Director of Finance, Director of Media, Director of PR) (Mechanical Leader, Electrical Leader)

However, this kind of set up would probably be only good for a big team, like how 115 now has about 90 members(I think), which is extremely huge. This set up has probably been used for a long time, including back when the team wasn't that big, the team grew by like 30 members for this year.

[KF987]

Team 987 has officers and leads.
Officers consist of:

President- keeps everything together/paper work
Vice President helps out president
VP of Build-responsible for timelines during the build, managing build
Secretary-spornsors/letters
Historain- takes pics of everything/ records events
Treausrer- keeps our budget.
those are our officers in a nut shell

Then after the kickoff (or before) we will have Leads for certain aspects of the robot. Ex this year we had a lead for the Arm, Claw, DT, Electronics, Pneumatics, and Progamming. We only have about 20 kids in our club (about 15 who are dedicated) so the officers will sometimes become Leads as well.

Keaton

[SPurekar]

226 has about 50 students, 18 engineers, 2 teachers, and 3 parents that help regularly.

This year we had 2 co-presidents who were the main link between the students and adults. The presidents led the meetings and anything to the team had to go through the two of us (I’d recommend having 2 presidents over 1, because of the workload and availability issues)

Under the presidents were the 4 workgroup leaders (Management, PR, Robot, Digital). We gave the group leaders a to-do list at the beginning of the season, and they had to create their own timelines to accomplish the tasks. The Robotics workgroup was further split according to the assembly of the robot and the Digital workgroup was divided into web, CAD, and animation. The rest of the students were split into workgroups under the 4 leaders, according to their interests.

One thing 226 has had problems with in the past has been communication within the team. This year, the presidents were the only ones who could email the entire team and all information to the team was communicated in person at team meetings, then emailed out as soon as possible. This gave us two ways to present the information and even those who missed meetings knew what was going on.

We had (and still have) full team meetings once a week where workgroup leaders gave updates on what was happening and asked for any help they needed. Every week, we had leadership meetings with the presidents, workgroup leaders, teacher sponsors, the lead engineers and a few parents where we discussed our progress and set goals for the week.

We had one parent who kept the rest of the parents updated. To get anything to the team, the parents could email only the parent lead, who then told the presidents. The presidents also had to go through the parent lead to get anything to the parents.

For those teams that complain about not having enough student involvement in leadership: The 2 presidents found this year that we were given a lot more responsibility and trust simply because we were assertive at the beginning of the season. We drafted a set of rules both the students and adults were comfortable with and made sure everyone followed them. When anyone stepped over the line, we weren’t hesitant to tell them we could handle the situation. (Don't get me wrong, we love the adults and we know we can't function without them) By giving the adults periodic emails on what we were doing (especially at the beginning), we kept them in the loop and they began to trust us to make the right decisions.

All of the students on leadership are juniors right now, so next year, we’ll each have one person under us to train for the year we graduate. What really helps is if the new leadership steps in during the summer, when the old students can guide them for the first month or so.

This sounds like a lot on paper, but it worked wonderfully this year. Feel free to email/pm me with any questions!

Hope this helps! (wow this is a long post)
~Smita

[Simon Strauss]

At the end of last season we too found ourselfs at crossroads at the Sciborgs. With the only remaining origional member graduating and team dynamics shiffting we last summer wrote this constitution to reorganize the team. http://www.chiefdelphi.com/media/search/results/50959 its been working very well so far and if you have any questions about it feel free to PM me.

-Simon

[IMac]

This year I introduced a new team setup (new for us at least)
After kick-off we all met and set up a preliminary design.
Then I split the team up into divisions called PODS.
Why PODS? Mainly cause it sounded cool, but we later figured out it could stand for People On Different Systems...which is essentially what it was.
Each POD covered a different design system of the robot such as;
-Frame
-Objective
-Programming
-Electronics
etc.

We had each POD meet on a different day so as to work with people's schedules and to avoid huge numbers of people in the building

This worked alright but there must be one very vital item in place for this system to work...dedication.
Each POD must be able to complete their objectives effectively.
Otherwise you will end up with people having to work on 2 or 3 PODS to pick up the slack, or having to do most of the work yourself.

It is worth a try though...