Three little updates

It's been three months since I last posted a blog entry. Just so that my loyal readers don't think this blog is dead (um, any loyal readers out there?), I'm just going to tell you about three little things that have happened in my life recently. In descending order of significance:

3. I've been made Assistant Course Manager

Ngee Ann Polytechnic has been reviewing the organizational structure of the various schools, and there have been a few changes made. As a result, I have been given the new post of Assistant Course Manager for the Diploma in Information Technology, which means that I get to work with the Course Manager to improve the diploma and influence how things are run. This comes hot on the heels of my appointment as Section Head and Cluster Chair, so I'm going to have to print new business cards again. :)

In the short term, this new appointment doesn't mean much. I have a few more day-to-day responsibilities, but otherwise it's business as usual. In the long term, sooner or later (and it may very well be sooner) the Diploma in IT is going to have to go through a review. Modules may be revamped or replaced, teaching methods may change, and the entire course structure could be turned on its head. As the ACM, I will have a decent amount of influence on what changes will be made.

So if you're a Dip. IT student who has some ideas or opinions on the course, I will be happy to have a chat. Your ideas might very well benefit students in the future.

2. I've won the School Teaching Award AY 2013/2014

Woo-hoo!

Every year, NP recognizes the outstanding lecturers in each school. Students are first asked to nominate deserving lecturers. From these nominations, a number of them are shortlisted and asked to prepare teaching portfolios. A panel then goes through the portfolios, and then the award winners are determined based on the portfolios and other criteria (including peer recommendations and student comments). Well, this year the panel has seen it fit to confer the award on little ol' me. :D

This is a big deal to me. Egotistical me has always thought that I'm a pretty good teacher, but I have never won any sort of teaching award. After a while I start wondering whether it's all in my head. Maybe I'm an awful teacher, and the students who say that they like how I teach are just humouring me (or buttering me up for better grades). To finally win an award for teaching serves as a validation of my teaching philosophy and methods, so yeah, I'm inspired to continue teaching in the way I think is best. For those of you who hate how I teach, well, pbththththhth!

By the way, this blog played a big part. Like I said in my first ever post, I started this blog partly to supplement my teaching portfolio, and the portfolio I submitted included lots of links to various posts on this blog, silly jokes and all. Turns out the STA panel has a sense of humour. Who knew?

1. My wife is preggers

We're expecting our second child in September, so there's that.

Advice: on overruling others

This is my second blog post where I give out sage advice (after this one on love and relationships). What makes me think that I'm qualified to tell you how to live your life? Nothing, other than the fact that it's my blog and I can write what I want, so there. :)

Today's advice concerns making decisions where you might overrule others. In my various roles as module leader, cluster chair and section head, I've found myself having to do this quite frequently. It could be as simple as deciding where to have a meeting, or as sensitive as changing the way a lesson is taught when the rest of the team is against the change.

The advice is as follows: "Always consider the possibility that you might be wrong."

Nobody's perfect, and we all make mistakes. The reason we work in teams is so that we have multiple people with different levels of experience, viewpoints and expertise all trying to find the best way to proceed. Just because I'm the module leader or section head does not automatically mean that I'm smarter or better than the rest of the team, and it would be incredibly arrogant of me to dismiss the conflicting views of everybody else without giving them due consideration. It is important to avoid letting the power go to your head.

By the way, the corollary to the above advice is: "Always consider the possibility that you might be right." There is a fine line between giving others' viewpoints due consideration and being spineless and afraid to make the tough decisions. It's actually easiest to go with the consensus, that way you please everyone and the blame is shared should anything go wrong. However, if you have weighed the merits of all arguments and are still convinced that your decision is correct, then you must have the courage to be the villain and overrule everyone else.

When you do overrule, it is imperative that you explain your reasoning as clearly as possible to everyone concerned. I've been on the wrong end of this multiple times in the past. One of my previous bosses would declare an intention to make a big and (in my opinion) wrong decision. I would politely raise my objection, whereupon said boss would casually and completely disregard it. I would press him for his reasoning, and the only reply I would get is "I know what I'm doing." It drove me nuts.

It all boils down to making the best decision you can with the information that you have at that point in time. The trick is to consider all information calmly and objectively, even if it goes against your personal opinion. Besides, if you always reject other people's viewpoints, they'll eventually stop offering them. Then anything that goes wrong would be completely your fault. And you would deserve it.

I've got some new responsibilities

I was appointed Section Head for the Cloud Computing & Data Analytics (CCDA) section in April. At the same time, I was also given the post of Cluster Chair for the Analysis & Design cluster, which is part of CCDA. Since I am relatively new to the organization, I really appreciate my bosses' confidence in my abilities. It does feel like I've been thrown into the deep end a little bit, but I am eager to take up the challenge. Besides, how bad can the deep end be?

The deep end.
(Source: http://www.1000words.com.sg/words/images/2013/shark%20in%20pool.jpg)

So now I find myself with a bunch of new responsibilities. For example:

• We've just announced two new specializations, namely Cloud Computing and Data Analytics, and both of them fall under CCDA. I need to make sure the new modules for these specializations are properly designed and taught, and the first new modules may be offered as early as next April.
• Of course, I also have to ensure the smooth delivery of existing modules under the Analysis & Design cluster (there are currently eight of them).
• To achieve the above, I need to identify and assign lecturers for each module. If required, I must also arrange for them to receive training so that they keep their skills current. This probably requires a more sophisticated system than drawing names out of a hat.

All this really cuts into the time I have to goof off. It's now much harder to justify spending time at work playing games or watching youtube videos (um, not that I do those things anyway. Um.). Or updating my blog. Yeah, I'm making excuses for not updating this blog for weeks (sorry).

On the other hand, I suddenly find myself in charge of all the lecturers in my section because the Section Head is also the Reporting Officer (RO) for everyone in the section. I'm now the guy who will help decide their teaching duties, approve their leave, and conduct performance evaluations that could greatly affect their bonuses and promotion prospects. So... much... power! I won't let it go to my head, I promise.

Kneel, minions.
(source: http://www.ctzine.com/wp-content/uploads/2012/04/King-Joffrey-in-Game-of-Thrones-Season-2.jpg)

While I'm thrilled to be given these responsibilities, I have a problem. Even though I've been here for a year, I haven't had a chance to work directly with many of the people in my section. When you're not in the same teaching team or committee with someone, there isn't much to do besides say "good morning" as we pass each other in the corridors. Furthermore, every single one of the lecturers under my charge have been at ICT longer than I have, and some of them have been here much longer. At this point, the only things they know about me are (a) I've got a PhD; (b) I'm nuts about board games; and (c) I'm now, suddenly, their boss.

This problem has to be rectified as soon as possible. I have to get to know them well enough to make informed decisions about task allocations, and they have to get to know me well enough to feel comfortable about approaching me if they have issues or suggestions. To that end, I have organized a section meeting next week to break the ice.

And it will be an all-you-can-eat buffet lunch at a 5-star hotel restaurant sponsored by yours truly.

In case you're wondering, yes, I'm trying to get into their good graces by bribing them with food. I'm working under the premise that one is more inclined to listen to one's new boss if he's just filled your tummy with yummy out of his own pocket; after all, this tactic will work with me, but maybe that's because I'm a greedy pig. Oh, and I also invited my own RO to this shindig because a little brown-nosing to improve my own bonuses and promotion prospects doesn't hurt.

People management.
(source: http://www.sickchirpse.com/wp-content/uploads/2013/01/Wall-E-2.jpg)

My plan is to get everyone comfortable and relaxed and chatting. Come dessert, when everyone is chilling out over ice cream and chocolate fondue, I'll start the meeting proper by giving a bit of a speech that can be pretty much summarized as "I'm a nice guy, help me out, pretty please?" I will apologize in advance for bugging everyone with lots of silly questions and clarifications in the near future since it will take me some time to familiarize myself with all the modules under my charge. In the meantime, I will defer to their expertise in terms of how the modules are delivered, and I won't be making any huge sweeping changes just for the heck of it (so no, I won't be insisting on open-book exams for all modules). On the other hand, if anyone has any ideas to improve the modules, I'll certainly consider them.

I will also appeal for everyone's help to make the launching of the Cloud Computing and Data Analytics specializations a success. In particular, we need to send staff out to receive training in these relatively new fields so that there are enough lecturers to both design and teach the module materials. I am therefore looking for those who have some interest in adding these new skills to their arsenal (and curriculum development to their performance reviews). Volunteers also get a cookie.

I suspect this upcoming section meeting will have a major influence on the success or failure of my reign as Section Head (I feel like David Moyes). It's important to get off on the right foot, to clarify everyone's expectations and allay any doubts. My job is not to impose a bunch of policies and order people around, it's to get all the talented individuals I have in my section working together so that the modules are taught in the best possible way. It's a cliche, but it really is all about teamwork. In the end, all the lecturers in ICT care deeply about the students, and we all share the common objective of giving the students the best education.

Now if I can only stop myself from abusing my position...

"Thou Shalt Attend All Staff Bonding Tabletop Game Sessions! So Sayeth Thy RO!"
(Source: http://www.overthinkingit.com/wp-content/uploads/2012/04/heston_moses.jpg)