To date this column has focused on how to make deliverables more effective, either through their content or through the tools to create them. For this issue, I would like to explore the relationship between deliverables and methodology. Unfortunately, this calls for a definition of IA methodology, which may challenge the definition of IA as the hardest question in our field.
Good organization, complete information, and clear writing are, of course, key to the success of any design document, but there are some other, less-obvious techniques you can use to make your documents more readable and understandable. Here are a few of them.
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.
In this column, you’ll find an overview of three IA books from a deliverables point of view. The purpose of this article is not to say whether one book is better than another, or even to comment on the overall quality of the books, but to provide a guide to what kind of deliverables information you can find in each book, and where.
Building architects don’t have to think much about what the actual deliverables are to contractors and their clients, because their industry has traditions and standards for blueprints, balsa wood models, and computer-generated renderings. As user interface consultants, we have to think about this anew for every project.
We need a way to document and express mental models that is as simple and robust as personas for user profiles and scenarios for tasks. By laying out users’ current mental models and a target mental model, we can clarify our thinking and communication about the user interface’s objects, metaphors, and interaction.
Design organizations inevitably run across the debate of Visio versus HTML wireframes. The decision for one over the other is never a clear-cut one since, as with all things IA-related, it depends. This article seeks to sort out the issues by describing the pros and cons of each and identifying situations where one may be more effective than the other.
How do you prove your worth to clients in today’s difficult economy? Performed as part of a sales proposal or the discovery phase of a project, a site assessment can uncover opportunities for improvement and help you speak knowledgeably about solutions to your potential client’s problems.
All Gain and No Pain
Mention the use of HTML for wireframing or prototyping, and some information architects and interaction designers frantically look for the nearest exit. In some circles, HTML has acquired the reputation of being a time-consuming, difficult undertaking best left to developers. This is very far from the truth.
So, you’ve read the article, “HTML Wireframes and Prototypes: All Gain and No Pain” and now want you want to make an HTML wireframe or prototype. This an easy and pain-free process, using Macromedia Dreamweaver 4.0. Follow this step-by-step guide and you’ll be up and prototyping in a jiffy.