I have posted this in the past, but have reflected on it (and gone searching for it) a couple times in the recent past,
http://eightshapes.com/blog/2010/08/09/8-essential-elements-of-every-ux-document/
It’s a nice summation of the “basics to include in your user experience documentation” (or at least, elements to discuss whether or not to include). I think UX has evolved (and continues to evolve) to the point where a UX “deliverable” can mean a whole host of things, and there are contexts in which this list doesn’t make sense, but when you think of a UX document as something the document’s creator passes off to someone else (client, client service rep, designer, developer, your mom (that’s right, I went there), then this list makes a whole lot of sense.
(Side note to self: Maybe the fact that I’m equating document with deliverable here means I need to start mentally parsing the difference between deliverable and documentation?)
These basics include things like:
- Give your document a title
- Give your document page numbers
- Make versioning simple
- Reveal key properties on every page
Basics that would seem somewhat self-evident, yet also end up getting dropped in a number of UX documents I have seen (and, yes, worked on in the past).
This information was posted by Eight Shapes, whose Unify project is “A documentation system to produce wireframes, maps, flows, storyboards, plans, style guides, specs, usability testing reports, and prototypes too.”
arduanne liked this
observedexperience posted this