| When I'm presented with a project (by myself or someone else), my thought flow is usually like this: 1, Is this project interesting to me?
I usually trust my gut on this one and what I'm interested on is temporally-variant. I can only apply my self 100% to things I find an interest in. 2, What is the market viability of this project?
I do a bit googling around to see if there are any existing implementations of this product. I try to think of usage scenarios and I will google for communities who might need this product, read about what they have to say and find out more about their needs so that the implementation of the product can be geared towards them. Even if a product has 0 market-demand, I might still work on it because of step (1) and I simply treat it as a learning experience ( such is the case of kpicturebooth.com ). 3, I work out the logistics
- can I work on this on my own ?
- if the project was presented to me by someone else, what is the team like?
- how long will it take, can I fit it into my school schedule? If I deem the project infeasible, I might try to work on one part at a time or get people to help me. |
1. Try out the existing implementation (a little gap analysis with your idea)
2. Even though analysis from (1) above does not come out with much pros, the project might still be a viable one, depending on the effort needed