Showing posts with label assumptions. Show all posts
Showing posts with label assumptions. Show all posts

Sunday, February 14, 2010

Game on!


I have learned a few lessons this week. I would like to highlight one, mainly because it is a simple yet powerful idea people seem to neglect!


Examining assumptions
I was reminded of this by Prof Wong Poh Kam, director NEC and angel investor. Strangely, I was feeling rather free that one day and I tagged along with Lawrence to a networking cum sharing session. It turns out Prof Wong happens to be the director of BANSEA.

The idea over here is rather simple. After coming up with a business plan, examine closely, at my own assumptions. For example, is it possible that we get 50,000 users a month? Is it possible for some one to clock 100 hrs / week of programming time etc? This simple reflection would reveal the flaws and also forces us to clear of our plan of action. Simplest solutions are the best!

Also, it is not to say that we shouldn't make assumption. They just have to reflect reality. Let's look at some (simplifying) assumptions that I have for final project:
  • Flash can be learned and mastered in a month.
  • The game would be interesting enough for people to want to try
  • The team's effort is synergistic and that everyone is enthusiastic about that we do. 
  • We would be principled in our execution.
  • Everyone in the team can provide the team with as much resources as we need to make project fly at the minimum. 
The next questions (What is there to learn about flash? What do I mean by mastery? What is the usual timeline?...) is of course asked to verify this assumptions, which leads to the next rounds of questions and assumptions. And as computer scientist likes it, this will go on recursively until we are clear on what we want and until we start asking questions that are either too stupid or too general or too specific like "What is the meaning of Life? "

The purpose of this exercise is of course to be clear on what we want. Clarity is the the most important outcome of this theoretical, goggle-aided, ideas bouncing exercise. (= After which we should have a fair idea on what we want and how to achieve it, although the solutions may not be optimise. To optimise is again, other exercise altogether. 

On another note, I was pretty excited by the CS3216 pitching session, which makes me feel like a VC, although I know that this is a mere ego-trip. These are people with real world problems to solve or ideas to implement. Thanks for giving us the flavor at least, prof!

Happy Chinese New Year!