IA documentation
- Started
- Last post
- 3 Responses
- rainman
So... trying to create some standards with the wireframes we create internally. I was trying to figure out... when a freelancer is working on a project with a design studio and gets wireframes from them, do they prefer the wires be extremely detailed or more vague? When I worked at agencies, 9 times out of 10 the wires were not being created by the designers... and the wires would be pretty detailed to a point that they started to suggest a layout. Not sure if this is a good thing or a bad thing. Clients kinda use IA processes to start hashing out where content appears on a page but, without a designers input, might not necessarily be the best solution. BEst solution would be to have the designer be more involved in the IA processes... but it usually never happens.
I always try to tell the designers that they should really think about the layout and not go by the wires exclusively... but then I wonder if, by looking at the layout of the IA, it sways the design. Seems like every project with freelancers we get a direct interpretation of the wires.
What are your thoughts? Got any examples of wires that you feel solve interaction issues yet provide a blank canvas to designers?
- subimage0
I think wireframes should definitely define layout and position. What else are they good for? IA should dictate that.
I think what you're looking for is a step in-between called PDDs or Page Description Diagrams.
http://www.boxesandarrows.com/vi…
Read and enjoy...
- ...awaiting pitchforks and fire from designer uprising :psubimage
- rainman0
exactly...
- rainman0
Curious... any of you willing to share your IA examples? Just want to see what level of detail is put into your IA. Care to share?