View Single Post
  #11   Spotlight this post!  
Unread 19-10-2011, 23:13
davidthefat davidthefat is offline
Alumni
AKA: David Yoon
FRC #0589 (Falkons)
Team Role: Alumni
 
Join Date: Jan 2011
Rookie Year: 2010
Location: California
Posts: 792
davidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud of
Re: New Team Captain

Do not make all the decisions by yourself; allow the members to makes the decisions. That leads to better productivity and higher morale from the members. I believe the captain should not impose idea, but they certainly do carry weight in their opinions. Do not try to do everything; leave the programming to the programmers, welding to the welder and ect. I believe the captain should be more of a figure head than an actual decision maker. They are there to unify the team toward the same goal; that goal must be chosen and approved by the team members. Listen to everyone's suggestions seriously; you will be surprised what rookies can say. Also, please, do not get that whole superiority complex ego. You, too, are a high school student; captain is just a title. Lead by example and never do a "you stupid". You have many things to learn and mature as well. Never abuse your power; being the captain is a privilege not a right. I believe the captain should minimize the actual building and designing or coding of the robot, but should make the team run smoothly. Perhaps, even do the paper work.


edit: another thing to add: it is not about the robot, but the people. Keep that in mind.
__________________
Do not say what can or cannot be done, but, instead, say what must be done for the task at hand must be accomplished.

Last edited by davidthefat : 20-10-2011 at 21:46.
Reply With Quote