4. ● Brainstorm
○ Write down everything
○ Don’t judge your
ideas, just write
“If most of your ideas suck, are ridiculous, or
unrealistic, don’t be embarrassed. That’s to be
expected. Remember, it often takes 10 or 20 bad
ideas, just to come up with one good one, but that’s
the recognizable process. That’s what brainstorming is.”

5. ● Rank ideas on
○ Ease of development
○ How fun it would be to play
○ How fun it sounds to code
○ Could you make it yourself (ie. Scope)

6. ● Throw out 99% of your
ideas
● Find the core mechanic

7. ● Define the MVP
○ This is what you will
release for your first
game

9. ● Paper prototype

10. ● No art prototype

12. ● Work on only one feature
at a time
● Don’t get caught up with
the art / music / code
○ It can all be changed later
“If you are trying to solve a really hard problem, stop. Solve a simpler problem the
accomplishes the same things.”

13. ● Focus on the MVP
○ Make it look good

14. ● Release early and release
often
● Playtest early and playtest
often

16. ● Celebrate!
Made a game

17. ● Have people play your game
● Keep improving the game
○ Artwork / music / gameplay

18. ● http://gamedev.tutsplus.com/articles/busi
ness-articles/making-your-first-game-a-
walkthrough-for-game-developers/
● http://gamedev.tutsplus.com/articles/gam
e-design-articles/questions-to-help-you-
finish-your-first-game/

19. ● http://gamedev.tutsplus.com/articles/busi
ness-articles/tips-for-a-one-man-gamedev-
team-what-to-do-before-even-touching-a-
computer/
● http://gamedev.tutsplus.com/articles/busi
ness-articles/1gam-how-to-succeed-at-
making-one-game-a-month/

20. ● http://www.gamasutra.com/view/feature/
130848/how_to_prototype_a_game_in_und
er_7_.php
● Extra Credits:
Playtestinghttps://www.youtube.com/watc
h?v=on7endO4lPY