Quote:
Originally posted by Jeff Waegelin
It's an interesting idea, M. It might be a little too much for a small team, but I could see how a larger team could benefit from things like your punch-card system. My only concern is, is it too much organization, yet too little at the same time? It seems like there's a lot of stuff to keep track of, yet without a defined structure. It could very well be a better system, though. Until somebody puts int into practice, that remains to be seen. I have my doubts, but I'd be willing to give it a try. At the very least, it's a fresh, new approach.
|
For someone with better organizational skills than me, it might be redundant and unnecessary. I know from my experiences that I tend to take on more work and responsibility for the team and its robot than I probably should, and I think the people I've worked with would agree. This would help me and people like me to back off a bit and turn things over to the students more while still ensuring that they were gaining knowledge of meaningful skills that they can use in college and at work.
It was an idea for a way I could delegate work to people other than me when I couldn't just say, "You, do this." It also helps that the students are deciding on their own what level of work they're comfortable with. There's no need to worry about saddling a student with more work than they can handle or are comfortable with, and it means that I won't get upset with them if they don't complete the assignments that I give them.
The responsibility for getting things done lies squarely on their shoulders instead of their teachers and mentors.
It's really a whole new of doing things for me. After a season of being responsible for the entire design of every aspect of a robot, with very few checks on me, I got back to thinking about what benefits this could have.
Of course, if you have a team of unmotivated students who aren't willing to own up to their responsibilities, this entire system could also be a spectacular disaster.
