Paper. Usually graphing paper. I write down a quick sentence of what it does and who it does it for. Then I drawn a database scheme - this functions as a short

Paper. Usually graphing paper. I write down a quick sentence of what it does and who it does it for. Then I drawn a database scheme - this functions as a short hand of how I want the logic/features/relationships to work. Sometimes I skip this and just write out a description of actions/features that would be cool. If I start to build it, I usually narrow those down required features. I like this because I can map out an pretty complex app in just a few minutes. I can easily add thoughts, and I don't lose them. I like my brainstorming to accumulate. You generally lose that in a soft form, because you edit out the "bad" thoughts. I like to remember them later when I revisit the idea. Also, if I have any design ideas I can quickly sketch it out. I can't draw but I draw in a pseudo-wireframe way. Downside is the organization and portability. I have a stack of papers I've accumulated over the years in my home office. If I start to work on in code. The paper stays on my desk and I usually end up with 2-3 sheets before I'm done building. If I never build it, it gets filed. I will return to it if I've given it more thought or figured out a solution to a problem I foresaw. I keep post it notes handy for when I get an idea and am away from my workspaces. Post it's get added to the file later.