Design Notes Diary

As part of my usual development approach I very often post in-process screenshots and ideas to Twitter. This has provided me with a rich sense of community & feedback. With all the recent drama around Twitter, however, it has gotten me thinking about this part of my work process and whether an alternative would be better, at least for now.

The more I thought about it the more I realized that while posting my work likely had some benefit to others in learning from my process and mistakes, there was a fundamental value to me in the capture rather than the share. In many ways it reminds me of the Field Notes slogan “I’m not writing it down to remember it later, I’m writing it down to remember it now.” Or similarly the concept of rubber duck debugging.

There is a tremendous value in having to condense the vague notion of an idea down into words that clarifies, crystalizes and improves it.

So I’ve started to write a diary of my design and development process, my Design Notes Diary. You can find all the posts for it here: