# Development Process
The most difficult thing you can teach a designer is process. Every time I interview a designer, one of the main things I care to learn is their process: how do you solve problem X, what do you do in situation Y.
I can TEACH you knowledge. But you have to FORM a process. It's a personal thing. I can tell you exactly how I do things (and I will here), but ultimately it's not going to be as effective as the processes that you build for yourself.
So, with that preamble out of the way, each these articles is a breakdown of some real-life process that I use in my work. They are amalgams of scenario, semantic, and economic concepts, which is why they don't really fit into the other categories.
GRIP is a general rule for how I work. You think this of this process more as a philosophy than as a step by step process.
This is a detailed process that I work through when I'm working on a system.