From time to time, I will post some interesting resources and tools in the information architectecture field. Today, you will find a list of Deliverables related to the IA process that were discussed on the AIfIA listserv.
Victor Lombardi’s Blue wireframe (looks like a blueprint)
http://aifia.org/tools/download/LombardiWireframe.pdf
Clifton Evans’ all-blue page…
http://www.infostyling.com/examples/Blueprinting_Object1.gif
Austin Govella’s recent samples:
1. Very didactic. Client wanted more communication (59k PDF):
http://grafofini.com/stage/sample_deliverables/eto_wireframe_home.pdf
2. Very sparse. Client didn’t care why or how. Just wanted progress (67k PDF):
http://grafofini.com/stage/sample_deliverables/ubs_home-wf.pdf
Dan Saffer suggested creating the wireframes on computer and tracing them by hand to look unfinished/changeable.
There are some more great samples on the AIfIA Tools page:
http://aifia.org/tools/
And great ideas and pointers on the IA Wiki:
http://www.iawiki.net/DeliverablesAndArtifacts
Process Outline from Thomas Vander Wal:
Initial meetings (discussion):
-gather user types, content types, possible interactive needs (not desires)
-estimate volume of information intially, and volume of information turn-over (how often and how much information is updated and added to).
Deliverable – Project Overview (Word document)
-Results of initial meeting/needs
-Rough persona and/or information use patterns of the user that come to the site (Why do people come to the site? What do they do with the information? Who is the audience? How often do they come to the site?).
-Client signs off once there is agreement
Deliverable FROM client – Content Inventory:
-individual documents they would like included
-current web sites they own, and/or pointer(s) to applications they want incorporated.
Deliverable – Content Inventory (spreadsheet):
This document will be our communication tool to prod the client for content that is missing and to show our work progress.
-category column
-raw content/document delivery column
-document size (words)
-number of images
-number and size of tables
-development status.
Deliverable – Open Card Sort (spreadsheet)
-For larger sub-sites
-client can do it themselves if they want
Deliverable – Content Object Type Inventory (outline format such as Word or PDF of OmniOutliner):
-images
-navigation
-referred links
-data tables
-headers
-sub-headers
-footers
-branding
-cross-branding
-dynamic elements
-rich content elements (where required)
Deliverable – Raw Wireframe:
-HTML with borders turned on and greeking
-one wireframe for each page type
-capture the various content objects and placement with consistency
Deliverable – Semantic Structure
-CSS classes and ids
-naming structure for dynamic and rich elements
Deliverable – Clickable Raw Wireframe
-include names and categories
-start testing it with users (heuristic assessment) and flow (particularly testing when users drop into the middle of a site).
-carved up wireframe into templates for HTML and/or CMS and applications.
Converted Content into the content templates.
Other elements are set as includes or are in the CSS.
Color Palette:
-known items (enterprise branding that is required)
-markup a few pallet options with CSS
-do a few user tests to verify choices/options
-create HTML CSS table listing the CSS attribute, an example, and when it gets used.
Graphic Development and Local Branding
-20 to 50% of the content has been converted
-tweak templates
-test and make adjustments accordingly
Depending on the size of the site, the number of people involved and access to read users, most of the steps in this process are flexible, except the raw HTML wireframe, clickable wireframe, and the content spreadsheets.