Design is a Job should be required reading for anyone making a living doing Design. I will write […]
After an extensive search, I find I have not written this down (at least in a blog– I have referenced it in talks.) Now, most of these points can be/have been addressed in one way or another. But one might ask yourself, what other deliverable is as criticized as wireframes, and could there be something better?
Firstly, wireframes emasculate the designer. Wireframes have often had a place in multi-disciplinary teams where the graphic designer had come from print, and didn’t really understand interface design. The interaction designer came from software and was making ugly terminal-esque interfaces. So in order to make sure the end result was palatable, the interaction designer (or information architect; I’ll use this term interchangeably in this post) would make a pig, and then the graphic designer would put lipstick on it. This was 1998.
But as designers got savvy to interface, they started resenting the restrictions on their ability to creating compelling and useful designs. After all, a designers toolkit is essentially font, color and layout. The web browser stole the first, if the IxD steals the third they are relegated to the sorry position of kid with crayons handed a coloring book. Think hard of the last wireframe you saw. Didn’t it look a lot like a paint-by-number, with only the numbers missing?
Anders says The first time I heard about designing with XHTML was in 2005 at an IA retreat […]
Nate has posted our natek: Web Visions Presentation, which makes a simple proposal to make wireframes more meaningful […]
Boxes and Arrows: The Devil’s in the Wireframes came at the right time. I’ve been thinking about wireframes, […]
In Dan’s Brown’s latest Special Deliverable, Where the Wireframes Are, he discussed one of my favorite sticking points: […]
strange systems: Using Wireframes is a terrific essay on wireframes. I’m bummed that I can’t tell anything about […]