Deliverables

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.

June 9th, 2003

Deliverables and Methods: Special Deliverable #8

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.

March 31st, 2003

Writing Smart Annotations

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.

March 10th, 2003

IA Library Quick Reference: Special Deliverable #7

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.

February 24th, 2003

Getting Creative With Specs: Usable Software Specifications

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.

January 13th, 2003

Using Site Evaluations to Communicate with Clients

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.

November 24th, 2002

Three Lessons From Tufte: Special Deliverable #6

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.

November 11th, 2002

Defining Feature Sets Through Prototyping

Page 4 of 512345