Imagine Cup 2010 Malaysia Video Submission Tips & Tricks

Closing date for Imagine Cup 2010 Malaysia Semi Finals is just around the corner. I bet every competitors now are burning midnight oil to complete develop as much as possible on their system in order for them to show case in their video demo. While busy developing the system, competitors might want to start writing their proposal and thinking a script or scenarios for their system video demo.

Today I want to share my personal experience (team experience too) on creating video demo for Imagine Cup video demo submission. This is my personal point of view and it is NOT related with any Malaysia final round selection guide or what so ever. I would said, take it as a reference only.

  • Come out a script or scenarios for the system demo. Competitors might want come out a script on what to present and what to say in the video before start recording. This can help to avoid forgetting or missing some important element when recording. (When start recording, everyone will get panic).
  • Record in multiple smaller part and compile into one later. It is easier to record part by part first because you might not want to record everything all over again when something when wrong (such as system crash, mispronounce, interruption, messenger popping out!). Combine into one after finish record each part. Please don’t submit multiple part, because it is irritating and judges might miss one or two video clip (they have ton of video watch you know).
  • Record in well-known video format (such as AVI or WMV). I highly suggested record your video into avi or wmv format which able to play directly using Windows Media Player or any other common available video player. I guess no one wish to get disqualified because of their video fail to view by judges.
  • Narrative / Voice over on video demo. Having a sweet voice explaining the system and problem definitely is a plus point. Not recommend to use computer voice narrator, because the voice is irritating to listen for 15 minutes long. Not recommend to use subtitle instead of voice because judges will be too busy reading the subtitles and cannot concentrate on the system demo, but you can have both if you want and free. Highly not recommend to submit a video without any voice or subtitle explanation, audience cannot read competitors’ mind!
  • Be creative, but not over creative. Add some creativity into the video demo to attract the attention of judges. Competitors might want to come out a story line for video demo to make the video more lively. Some animation or effect will be good to have, but don’t take too much time on that, because it is not the main presentation point. Don’t create a video with super visual effect and loud background music, it make the judges dizzy only.
  • Add some research element. Show some research data in order to make the audience believe how serious the problems are or how much impact the solution can make . It is better to say like this disease had kill XXX,XXX number of peoples every year instead of this disease had kill many many people every year. Please don’t present your own created number or unclaimed research data!
  • Make it simple, the audience may not have a computer sciences background. Try to explain the system in a simple way and easy to understand. Judges might come from different fields and they might not understand some scientific term.
  • Keep the video demo in time. It is recommended to follow the time limit given by Imagine Cup Malaysia website. Don’t present a lengthy video demo as the audience might fall asleep before finish it.
  • Concentrate on your system demo. The video is all about the system. The video should show the feature of the system and how it can solve the problem or how it archive the millennium goal. It is alright to show some user feedback research or interview, but not too much. Audience has no interest on how competitors develop the system, where competitors go and get the data, not interested in competitors’ university’s view as well.
  • Simple introduction will be nice. This is optional as it should be written in the proposal submit together with the video, but it is good to have some introduction. The video might want to have a few minutes telling the audience what problem the system is targeting and which millennium goal the system is trying to archive.
  • Skip unimportant part. Competitors might want to fast-forward some unimportant part such as data entry. Audience do not have that much patient to wait competitor to finish filling up all the form (with irrelevant data). Skip the loading time of a website or data will give more time on other demo of the system too.
  • Hide the bugs! If the system is yet to complete, competitors doesn’t need to tell the audience that they have what module, and which of them yet to develop or fail to show. This will just give audience a bad impression on the system as the system might crash anytime. Just show whatever the system currently got, if not, tell the audience what it might become when it complete.
  • Remember to give credit. Although this is not much about the competition, but give credit to the author of the song or research data obtain is good practice. Who knows one of the judges is the author and s/he didn’t see any credit given to him/her.
  • Practice before real recording. It is good to have a round of practice or two before go for the real recording. Although competitor can direct read from the script they prepare when recording, but not everyone can read the script as smooth as normal way of speaking, they sure got a lot of half way full stop. Practice also can reduce Manglish or Singlish (those “eh”, “ah” and etc). It doesn’t sound nice when audience hear those “ah”, “eh”, “oh” and half way full stop. Although it is hard for most of us to reduce Manglish to zero, but reduce is better than did nothing.
  • Grammatical error and spelling check. Please don’t learn like me who bad in English writing skill yet didn’t have some one to look for grammatical error in my blog post. If competitor decided to add subtitle or some introduction, or any statement in their video demo, be sure to find someone who strong in English writing and spelling to check for grammatical error and spelling error. If possible, gramme check on the script for video demo as well. Some audiences / judges are very particular to English spelling and grammar.
  • UI design. Thank you koekoe for pointing this out. As every competitor know interface design is very important because most people like clean and nice UI design. It maybe too late for competitors to redesign their UI before video demo submit. But if competitor has done some UI design research or user acceptability research such as interview doctor on how to position some control to suit their need or why need to place particular control here for what reason, feel free to tell the audience in the video. If the system have all the cool effect and audience doesn’t find the usefulness, it is useless and gain no point for design.

Those are the tips and tricks I can think of currently. I will edit and add more if I can think of any. Suggestion can be make at the comment too.

I fail to get back any video submitted on last year Imagine Cup Malaysia final because Soap Box delete everything already. Furthermore, I fail to upload my team’s last year creation to YouTube due to the video length cannot excess 10 minutes, too bad. I have successfully upload my team’s last year created video into 2 part on Youtube, you might want to have a look for example. You might want to check out on YouTube on other country’s Imagine Cup video demo (past and present).


Update on 3rd March 2010: After I viewed one of this year competitor’s video demo, something strike my mind. I added some point (in blue color font) and upload my team’s last year created video.

by Ooi Keng Siang

8 thoughts on “Imagine Cup 2010 Malaysia Video Submission Tips & Tricks

    1. Well, only one person narrative is enough. Other doesn’t really need to show up actually. It is up to your whatever want to show your face or not. πŸ™‚
      It doesn’t hurt to show all member’s face.

      Like

  1. Great tips to follow. I am not an avid blogger so I am going to add some important points here in KS’s blog.

    1) Since you have a time limitation, focus on showing the uniqueness of your system. Don’t waste time showing how to log in or enter user details in registration forms. Cool features capture attention (this is your goal – to keep viewers/judges interested to learn more about your system). Try to maintain a meaningful flow from one feature to another.

    2) Identify your target users (very important).

    3) A storyboard would be very helpful to make sure that the flow of your video is smooth. The storyboard also ensures that you won’t miss out anything important.

    4) As highlighted by KS, creativity is highly encouraged. I always liked the problem-solution approach. Instead of jumping into the demo of system features right away, introduce the team and do mention about what kind of problem you are trying to solve (a short intro would do – try not to drone on and on about the problems!). Tie in the system features to the potential IMPACT of your solution to the target users and to the society as a whole. The focus on IC is to create technologies with an impact on the lives of people.

    5) For the sake of consistency, use only one narrator. It takes time for listeners to get familiar with a voice so a sudden change of voice in the middle of the demo video is a major distraction. Narrate your story in a clear but lively manner. Try to avoid a mono tone.

    I hope this helps. Keep your creative juices flowing!

    Jasy

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s