[Sigia-l] Elements of Documentation

[christina wodtke]

It is much as I thought: the constants are site map and wire. Conceptual
models and user flows seem to be next, with audits/content inventories,
prototypes of various sorts following behind. (BTW, this is also drawn from
wiki and a couple other dug up sources, not just the answers here.)

Some raw data for you....

- site map
 - IA style guide
 - wireframes
 - tables

At Datek, after Discovery/Exploration we use Conceptual Models, Sitemaps,
Wireframes, Use Cases, and Storyboards. Pretty standard fare. :)

For deliverables, depending on the scope of services, I'd add message
catalog, common vocabulary and content inventory/matrix (mostly because
these are top-of-mind from a current project).

task flows
concept model
wireframe/screen detail
functional specification (in X situation, dropdown Y says Z, A, & B)
content matrix
experience flows (wireframes meet task flow to show people how users step
through a series of screens)
usability testing plan/results

all the time:
conceptual model
sitemap
wireframes

depends:
site index structure
taxonomy

To be honest, the only deliverable that matters in my company are the
wireframes ... Everything else is for my own internal purposes, if I create
them at all.

Concept maps
Task Model diagram
Block diagrams - these are the lowfi interaction/flow maps done in
visio/omnigraffle with no detail other than path
Wireframes
Flow maps - these would be the big ones with detailed screens
Functional spec - documents the user behavior of each element on each screen

Some people on some of our teams also do:
Story boards to flesh out particular paths
Clickable mockups - interactive prototype done in Powerpoint that walks
through one user scenario


christina wodtke
"le mieux est l'ennemi du bien"
www.eleganthack.com : : www.boxesandarrows.com