Some of this was exposed through the comments on a recent blog post regarding wireframes, in particular Chris’ comment on a sketchy wireframe stencil. So we’ve collectively been thinking about documenting and prototyping and how important “sketchiness” is.

To further fuel the discussion, I want to refer to Russell Wilson’s review of 16 user interface prototyping tools. I like how he categorises his “picks” into “Low fidelity mockups for idea exploration and communication”, “Interactive prototypes to test and communicate interactions” and “High fidelity drawing tool”. This is much more useful than saying one uses Axure (for instance) to prototype, like any one tool or technique could ever fit all situations. There are some interesting comments on Russell’s post too.

Also on this topic, Todd Warfel is running a survey on prototyping tools for his upcoming book. Be sure to check it out and have your say, this is adding some clarity around the various characteristics and pros and cons of prototyping techniques that will be of use to the entire community.

And it will help answer the question raised in the title of this post :)

I like the idea of having some sort of templating to help define the sketching process. Thoughts?

About two years ago, Adaptive Path experienced an upwelling of analog approaches. We started using design tools that jumped out of the screen and into the real world. We started using our hands to make things. Alongside our computers there appeared slabs of blank paper. Rather than reaching for a mouse, we started reaching for a Sharpie. Large rolls of paper and drafting dots became part of the lingua franca of client working sessions. Sketching was the new black.