|
Re: Members per team vs members who actually work
Obviously, a goal is to get everyone on the team to be productive. Each team has some members who do much more than others, and that is ok. At the same time, there are members who do a few things... and that is ok also.
2 problems arise with this:
1. Some students appear to not care to be productive at all. This could be the result of different things. It could be because they just don't want to work... but it could also be because they have very low confidence in doing the job and they would rather see a more experienced person do this duty. They may actually WANT to do something, but they are scared to screw it up... so they don't say anything.
2. The people who are always doing things tend to just "get er done" when the pressure is on. They don't take the time to teach the inexperienced (and shy) team member to do the job. This teaching is easiest to do before the FIRST season starts, when the pressure is on. But, it can still happen during the build season. If these productive people can find patience and still teach the less experienced members to do things, then the less experienced members become more confident and productive. The end result is a more productive team.
If a team has non-productive members, the responsibility lies on the mentors and the student leaders to get these people to be more productive. You can just blame them for not working. In their eyes, they don't want to screw something up because they see the more experienced (or more ambitious) members do a good job.
I can honestly say that the TechnoKats team has had all of our members be productive for many years. Of course, some are more productive than others.
Andy
|