Ryan Romro — Thu, 07 Jun 2007 17:10:16 GMT

Wireframes can be used for usability tests in instances where visual comps have not yet been made or if visual comps are out of scope of the project. Usually clients will want to test wireframes as a first step to seeing how effective the information architecture is presented to the users, without being distracted from visual representation. I found this to be effective in the beginning stages to get a grasp on what significant final decisions need to be made before comps are started.

Usually the wireframes that I’ve developed are minimal in color with an exception for links and icons. I try as much as I can to avoid lorem ipsum, not just for the client but also as a benefit for our copywriters to have something to start off of. Using real information is key in any wireframes, especially when testing the structural layout of the site.

An understanding of what wireframes are should be made during the discussion of the statement of work. Knowing that visual is separate from ID/IA work is key to the client’s understanding before any work has begun and should be reminded in instances when they do go off track.

I do find it however that wireframes and visual comps clash in a way – knowing that most clients will give “LATE” feedback on ID/IA work that has been signed off. Yes – Clients suck. Well most of them at least. =)

Boxes and Arrows: Comments by Ryan Romro