![]() ![]() Developers will mainly look at the functional notes, copywriters the content ones, and everyone else will pick and chose between both. Instead, I separate my annotations into two main sections - content and functionality - and display them both for everyone. Personally, I find this method to be too much effort for too little reward. The IA creates a different layer of annotations for each audience, and then prints out, say, the developers’ version for their use. Some software, like Visio and Dreamweaver, lets you do this through layering. One way of tailoring your annotations to multiple audiences is by creating a different set of wireframes for each. And you - the future you - need to remember why you made that form element a checkbox instead of a radio button. Copywriters want to see what they need to write. Designers want to see what visual elements need to be on the page. Developers want to see what they have to support, and how the site or application works (and doesn’t work: don’t forget to document what happens when an error occurs). All of these have different needs, and addressing them all in the annotations - especially given the small area that annotations typically inhabit on the wireframe - can be difficult.Ĭlients will want to see that you’ve incorporated the business goals they provided. There are typically five audiences for wireframes: clients (internal or external), developers, visual designers, copywriters, and, most importantly, your future self. In theory, when developers or clients want to know just why that link was placed in that spot, they can read the note on the document and understand not just what the thing does, but also why. They have a difficult role: to speak for the wireframe’s designer when she isn’t there. That’s where annotations come in.Īnnotations are brief notes, typically on the side or bottom of a wireframe, that attempt to describe each item on the wireframe. Now that you’ve figured out the navigation, placed the content, and figured out page flows, it’s time to explain just what exactly that collection of “Lorum ipsum” greeking, HTML widgets, and X-ed out boxes are, how they work, and how they meet the site goals. One of the most tedious, yet necessary, tasks of an information architect or interaction designer is annotating wireframes. ![]() “There are typically five audiences for wireframes: clients (internal or external), developers, visual designers, copywriters, and, most importantly, your future self.” ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |