View Single Post
  #6   Spotlight this post!  
Unread 29-05-2008, 20:02
ttldomination's Avatar
ttldomination ttldomination is online now
Sunny
no team
Team Role: Mentor
 
Join Date: Mar 2007
Rookie Year: 2007
Location: Roanoke, TX
Posts: 2,066
ttldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond reputettldomination has a reputation beyond repute
Re: Team Productivity Issues

Here's my input.

1. I agree with some of the others, that people tend to work better when they feel that they are responsible for a certain part of the robot. Not only robot, but sponsorships, volunteer, community outreach. When team members feel like they don't mean much, they tend to slack off. kinda like communism.

2. Work with the person's interest. Why put a non programmer on the programming team? If someone is interested in building, then he/she should build, not do something else. Same thing for chairman's, spirit, PR, etc.

3. Break people up. If you notice that two people are starting to joke around, break them up. Large groups do have fun, but people are more focused in smaller groups. So, get people working together, but in smaller groups.

4. Maybe the inevitable, sometimes, it is necessary to ask people to leave. There has been many a times, when the programmers have work, and the builders show up and goof off. Thus, if someone is not needed, or if someone's not taking the initiative to work, ask them to leave. It may be harsh, but if it's necessary, it's got to be done.
__________________
1261: 2007-2012
1648: 2013-2014
5283: 2015
Reply With Quote