Monday, November 01, 2010

Response to Week 2, EVO training, Pitfalls

Hi All,

I'd just like to respond to Holly's and Sandra's messages regarding this thread.

First, I like what Holly wrote about getting balance, support, and most importantly, the ability to forgive ourselves when we fail to do what we're supposed to do. Increasing/adding items to our 'things to do' list is really not a pitfall, but it becomes one when we stuffed in too many things at the same time. This is my common pitfall. I tend to over commit myself, to the point that I don't get enough rest, I produce a pretty mediocre job (which I could've probably done better), etc. A glance at how we all performed in Week 2 is a good benchmark in looking at our commitments. We are all committed to this training, yet not all of us shared with the group what we have accomplished so far. Are you like me? Have you over-comitted yourself this time around? Your session participants would probably do the same thing. So instead of producing/participating in making use of the learning opportunity, they'd tend to not fully commit themselves since they've probably had tons of other things to do in their 'to-do' list.

Sandra mentioned 'enforcing' people to participate. We all do want them to participate. But unlike her course, our participants are not graded. This isn't a pass or fail thing. We just kinda provide this learning service for free and we just hope that they somehow would benefit from this experience, one way or another. But this training session, although free and voluntary, we do have standards. And this year, as mentioned in Week 1, we do have some pending sessions. Your participation in this training i.e. evidence of meeting the tasks/benchmarks will be used to assess whether your session is ready for offering or not. I don't want to sound like the strict-principal that all teachers hate, but EVO has got a name to keep. And I hope that we are all in the same boat and using the same sculls so we can row it smoothly.

Have a great Week 3 everyone!

Aiden Yeh

No comments: