Quote:
Originally Posted by Chak
I'm just a young student with little experience in the world, but I know what I'd do if this happens to me.
I would quietly make a petition basically stating that you don't like where this team is going. From the original post, it seems like such a petition would gather lots of support. Then gather a few core veterans from the team and confront Z in a group, with the petition representing those not there. Then it's not just a single member "revolting", it's the entire team collectively rejecting Z's ideas. After that you guys can have a conversation with Z, and figure out something.
I think you absolutely should not remain quiet. FIRST is for students, not for mentors. If the students disagree about how the team is run, their voices have to be heard. Heck, the opinions of the students should always be part of the decision process, especially for such a big shift like this one.
|
Thanks for your input, Chak. I can say with confidence that I know exactly what all the members think; I've asked each one individually. I have pondered whether to create a petition or not, but I think it may not make a difference. I've already made one, though.
I'm quite frustrated that all these big changes were made without consent of anyone, not even the mentors. It sounds very tyrannic. I'm currently gathering the leads of subteams to come up with a better solution to learning robot concepts than creating lectures for every meeting until Build Season and after Build Season. What I've thought of so far is to assign each subteam a task that pertains to that subteam's specialties. (i.e. Programming is assigned a coding task with an arduino ide) Coach Z's idea makes everyone learn the same thing and gets a basic feel on all the subteams: build, programming, electronics, etc. The problem is, no one will know how to work a specific subteam well enough to troubleshoot.