Sunday, March 18, 2007

the two hour solution

Our technology plan is due! We wrote comparatively little, but we hope we achieve what we set out to do - to be clear and concise. With the AmaSingRace, we implemented only entry-level technology as we want to appeal to a mass audience that might not be as up to date as most technophiles. All you need, is a mobile phone with internet access. And all we need, is a web server that houses our database and maintains our website, which is our interactive interface.

We talked quite a bit on scenario planning. "Plan for the worst, but expect the best." An overused cliche that is grossly misleading. Many a times we are tempted to speak of extremes, when what actually happens is something that lies within the grey spectrum in between best and worst. For practice, we were given a case to discuss - Pacific Internet providing free wireless hotspots. My group first discussed how PacNet would generate revenue from this, to better understand such a venture. We then discussed the various factors and motiations surrounding this business model Once we had a clearer picture, we came up with the possible scenarios and the various factors of our scenario matrix. Resources (both capital and labour) and knowledge/technology seem to always come up in most scenarios. We discussed briefly with the class on this before we were driven out of the special applications lab due to some error in booking the venue.

We ended up in SR6, where we were given Presentation 101: How to impress in 2 hours. I thought this was really helpful! I've always thought a presentation should be widely understandable, but actually you only ahe to target important individuals who will influence the opinions of his peers. With such new perspective, it's not just easier to create a presentation, one is also able to be more specific in areas that will interest this particular target. It would also naturally become more personal, like reaching out to a person rather than orating to multitudes. (One still has to be eloquent, but the approach would be slightly different.) This 2 hour solution is really useful and I took home quite a number of great and very applicable tips.

Next up, is our final business prospectus. Oh, and the wiki! I guess one of the reasons why the wiki hasn't be updated a lot is because the entire concept of the wiki is slightly flawed. We are told that the wiki is our textbook. Textbooks are something people fall back on when they don't understand the lecture notes. It's like the last resort, the ultimatum, the final solution. And our assignment here, is the rewrite and add new content to something so revered. I think the idea of rewriting the textbook puts a lot of people off and seems like a rather daunting and wholly intimidating task. That's one of the reasons why the wiki hasn't been as hot as it supposed to be. Perhaps, in future, one could say this wiki is some random text, and then ask the students enrolled in this module to go 'correct it' and make 'appropriate changes' so it's more 'accurate'. This way, to the student, it would be like 'Spot the mistake" or 'find out what's wrong' instead of 'rewrite the holy book'.

Well, I believe that would solve another Education 2.0 problem. One step closer to revamping the system! (I think currently, this course is somewhere at Education 1.762, but soon enough, if the school administration allows, this would probably be THE module the be in.) Cheers. (:

2 comments:

cellprof said...

Sorry I missed this, James. A very insightful contribution. "Revered" text is not how I think of them, more like less wrong (in content or design) than the one I used last year. I like your idea of not telling them its a text.

cellprof said...

In my view, MB362 (2006-7) was much nearer Release 1.2.1 than 1.7ish. But thanks, it should improve.