Article Idea:
The Wireframe Audience
suggested by Chris Poteet on 2008/05/07
We hear so much on whether a wireframe should be interactive with HTML/CSS/etc, or be static as in a Visio diagram.
I’d like to write an article outlining the true audience of a wireframe. The thesis is that wireframes are most helpful for the other developers and less for the customer.
I’m not going to write that they shouldn’t be shared with a customer but understanding IA’s proper role in UX helps alleviate this tension.
Want to see this idea turned into a story?
17 people said yes. | 0 people said no.
Alexander Wilms
63 Reputation points
Posted 2008/05/26 @ 14:48PM with
I agree on the idea that wireframes are a very useful specification for the developers and in most of our development projects today they are an important part of the whole specification. I do not agree that they are less helpful for the clients – from my experience they are indespensible to create, validate and clarify requirements together with the clients. We use wireframes especially to translate functional requirements into technical specifications.
Luke Perman
1 Reputation points
Posted 2008/05/28 @ 04:02AM with
Agreed. The use of wireframes is three fold: To validate ideas and clarify requirements; for prototyping / user testing (in which case HTML wires become useful) and thirdly to form the specification for the dev team so they get visibility on what they are building (once again HTML proving useful – to see exactly what happens when a button is clicked, or a dropdown changed)
Robert Griffin
1 Reputation points
Posted 2008/05/29 @ 09:13AM with
I also concur. I teach a college course in Information Architecture (http://bg411.aisites.com, see WDIM390) and we teach both perspectives, i.e. wireframes are for everyone. I base most of my reasoning on Moreville and Rosenfeld’s tome (Information Architecture, Chapter 12 on BPs and Wfs). We really accentuate that a wireframe should NEVER be presented on its on merit, i.e. you should be there to explain it. We also emphasize that there are different versions for different audiences, but the one that is for the client is meant to foster “buy-in” for the architecture and design.
Colin Dean
1 Reputation points
Posted 2008/05/29 @ 12:59PM with
I definitely think they are useful for client side as well as developers. Allowing the client to focus on the content and functionality of the page rather than that shade of blue or the crop of that photo is invaluable.
Chris Poteet
17 Reputation points
Posted 2008/06/09 @ 10:43AM with
Hello All. I don’t want to denigrate the role wireframes serve to the customer particularly for the reason mentioned above. I just wanted to share some experience on how the IA should cater specifically to developers.
Giacomo Guilizzoni
0 Reputation points
Posted 2008/06/10 @ 23:43PM with
As the developer of a wireframing tool (Balsamiq Mockups: http://www.balsamiq.com/products/mockups ) I am especially interested in this topic, as it would help me refine my message to reach the right audience.
Chris Sainsbury
1 Reputation points
Posted 2008/07/09 @ 07:46AM with
I’d certainly like to hear more on this subject, and even reading the comments here is interesting in itself. I’ve recently written that wireframes are simply facilitators for discussion, but I now know that this does not fully illustrate their usefulness (although I stand by the article). Luke Perman’s point above about 3 uses for wireframes is really useful, and Robert Griffin reminds me to refer to the ‘polar bear book’ for more thoughts on this subject.
http://www.idrawboxes.com/2008/wireframes-are-simply-faci…