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.
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.
All Gain and No Pain
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.
Held up as a trio of “must have” books for the Information Architect, Tufte’s books are the quintessential resource for information design. But many IAs may wonder how Tufte’s principles can be applied to their daily work. Dan Brown offers three lessons from Tufte.
Defining requirements and features can be a daunting task under the best of circumstances. The Vision Prototype allows the user-centered vision to be seen—and discussed—by all team members and then easily translated into a set of functional requirements.