"When in doubt, make it simple. Pare the feature list to the minimum and create an application that does one simple thing. When you see how people use and respond to the application, you might choose to create another version of the application with a slightly shifted focus or altered presentation. Or, you might discover a need for a more (or less) detail-oriented version of the same concept."

"Design your games as play experiences, not visual experiences."

"Limit yourself to one major innovation per game."

""Let's get some code up and running, then we'll get to designing the game!"  = FAILURE"

So what we need to do is to always ask:

• What does the user do?
• What do you expect to be the user’s motivation for using the application? 
• What do you intend to be the user’s experience while using the application? 
• What is the goal or focus of your application? 
• How does your application organize and display the information people care about? Is there a natural organization associated with the main task of the application? 

Then identify "three types of requirements:

• Normal – if present customer is satisfied
• Expected – if absent customer will be significantly dissatisfied
• Exciting – goes beyond customer expectations "

And finally "write a product definition statement by first defining users followed by distilling the list of features into a single statement with the image of your user audience in mind."