Not so much is wrong with wireframes

In her article about wireframes Christina Wodtke, the author of “Information Architecture – Blueprints for the Web” discusses the use of wireframes in the design process. I agree with some of her thoughts, but in my view she missed one.

The first argument against wireframes is that they emasculate the designer. Yes, they do and I think no designer wants to get your wireframes and just paint by numbers. On the other hand designers need to have something to design. And that’s what from my experience should be in wireframes. The should inform the designer about the content that should be on the page, in the form etc. I have been working with some good designers, one of them Nina Wilke, who sometimes tell the IA that they missed this function or that information. But that should be the IAs job – to gather and structure the content – not to visualize or design it.

In addition, if you already have a good visual design and an running site, wireframes are sometimes just enough what a developer needs to get the page done. There’s no need to create designs for every aspect and thus be faster in the design process.

One Comment

  1. japatu said:

    I have read Christina’s book and it has some valuable information contained therein – well worth a read for those who are looking for a book on web IA (chapter 11 are rules to live by.)

    Moving on however, I think that wireframes are best done as a team with good communication between the BA, IA and the Designer as everyone needs to understand and interpret the brief from the client. In cases where the IA is also the designer, this is not so much a problem.

    I do agree that wireframes need to take the client and context into perspective as lo-fi wireframes are not useful in all cases as clients cannot always visualise the final product. Combined with hi-fi wireframes, they might prove to be much more useful to the client. The key is to effectively communicate what you are trying to visualise to the client in whatever form that is manageable and understandable for them.

    Nice follow up to http://ux4dotcom.blogspot.com/2010/01/why-and-why-not-wireframing.html

    December 21, 2011
    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *