View Single Post
  #5   Spotlight this post!  
Unread 25-06-2011, 01:55
David Brinza's Avatar
David Brinza David Brinza is offline
Lead Mentor, Lead Robot Inspector
FRC #0980 (ThunderBots)
Team Role: Mentor
 
Join Date: Feb 2003
Rookie Year: 2003
Location: Glendale, CA
Posts: 1,378
David Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond repute
Re: FAHA: Dealing with Discipline

Teams can and should set policies for behavior by both mentors and students.

Our team has application forms for mentors and students to be submitted every year.

The mentor application includes a signed "mentor code of conduct" which not only helps remind the mentor of the age group in which he is immersed, but also satisfies an awareness training requirement for our team's NPO insurance policy.

The student application includes a "contract" signed by students and parents. The contract makes it clear that FIRST is not a substitute for school and a grade requirement is in effect for attending competitions. Within the terms of the contract, students are evaluated for productivity and can be asked to leave the team if they do not contribute. Much of our student contract is adopted from handbooks from teams like "Wings of Fire" and TechnoKats.

A common thread between our "code of conduct" and "student contract" is respect among team members. That doesn't mean friction never exists or people don't lose their cool. We just don't want team mates to hurt each other. "Shake hands and make up", "agree to disagree," or "keep them apart" are all options when dealing with conflict.

You ask, "What can I do to improve conditions for our team?" That question suggests what you really want to do is to help lead the team. A discussion with the lead mentor about you helping the team by organizing and tracking students' efforts is a start. Expressing your concerns to the lead mentor about hurtful actions of the "valued" mentor might prompt some changes, too.

Something to consider about mentors (as Jared341 suggests), is being imbedded in a "day-job" where performance expectations are high can make a person really impatient with under-performers. Talented, dedicated people can become frank, "hard-headed" and darn near vicious when frustrated. Part of becoming "thick-skinned" is learning how to dish it out as well as take it. Sometimes, giving one another a hard time is a like a game. That sort of thing happens a lot - even where Dave's "Mars Cars" are built!

Good luck and realize that you're getting acquainted with the real world. Don't let it get you down.
__________________
"There's never enough time to do it right, but always time to do it over."
2003 AZ: Semifinals, Motorola Quality; SoCal: Q-finals, Xerox Creativity; IRI: Q-finals
2004 AZ: Semifinals, GM Industrial Design; SoCal: Winners, Leadership in Controls; Championship: Galileo #2 seed, Q-finals; IRI: Champions
2005 AZ: #1 Seed, Xerox Creativity; SoCal: Finalist, RadioShack Controls; SVR: Winners, Delphi "Driving Tomorrow's Technologies"; Championship: Archimedes Semifinals; IRI: Finalist
2007 LA: Finalist; San Diego: Q-finals; CalGames: Finalist || 2008 San Diego: Q-finals; LA: Winners; CalGames: Finalist || 2009 LA: Semifinals; Las Vegas: Q-finals; IRI: #1 Seed, Finalist
2010 AZ: Motorola Quality; LA: Finalist || 2011 SD: Q-finals; LA: Q-finals || 2013 LA: Xerox Creativity, WFFA, Dean's List Finalist || 2014 IE: Q-finals, LA: Finalist, Dean's List Finalist
2016 Ventura: Q-finals, WFFA, Engineering Inspiration