[Sigia-l] Integrating a UCD approach into an existing process

[Tom Donehower]

On Feb 11, 2008 10:54 AM, Ron <stbasil777 at gmail.com> wrote:

> Tom and Peter: thank you for your input on integrating a UCD process into
> an existing process.
>
> One more question: what are the key deliverables you create? Right now we
> create screen designs or wireframes, screen flow diagrams and UI
> specifications. Obviously for usability testing you create a plan as well as
> a summary. Just wondering what else from a UCD and/or IA perspective would
> be beneficial...
>
> Thanks again.


===

Ron,

The deliverables below span the gamut from Strategy to IA to UX. I don't
know the clear distinctions and never really bothered to outline them
because I think any IA/UX needs to be able to provide them.

Deliverables in order of project development:

1. Project brief (Why are we doing this? Who is it for? How will we know
it's successful?)
2. Stakeholder interviewers (Interview stakeholders to get their take and
more importantly buy-in)
3. User interviews/surveys (Interview/survey potential users)
4. Competitive analysis (Who's the competition? Where are the gaps in the
marketplace?)
5. Analytics analysis (An analysis of existing Web data where you identify
gaps and opportunities in the current user experience based upon
quantitative data)
6. Personas (Create fictitious representations of your users)
7. Task Analysis/Mental Model (How do users think about accomplishing their
tasks today?)
8. Contet matrix (Defines what you're going to fill all those gaps with)
9. Sitemap (Outlines site organization and navigation)
10. User flow (shows highlevel site processes in a flow chart)
11. Card sorts (validate organization and nomenclature)
12. Wireframes (a visual reprensentation of the organization and
prioritization of page level information)
13 Functional spec (defines the site functionality via use cases. Can
incorporate annotated wireframes)
14. Prototype (Can be paper or digital. Used to validate user experience.)
15. Usability test plan (Outlines plan for testing usability of application)
16. Usability screener (used to identify who you want to test)
17. Usabilty test (Usually a guided Q&A session with potential users where
they're asked to complete a series of tasks without being led to do so. Very
important you do not lead!
18. Usability test summary (Summarizes the findings and recommendations from
your usability test.)
19. A/B split/multivariate test (test you design to test user experience
assumptions with quantitative user data)

Those are the ones I've used most often in the projects I've worked on over
the past 12 years. I'm sure I've left some out. And hopefully the group will
add them in. Good luck!

-Tom
 Thomas Donehower
UXConcepts
Ph: 310-463-6800
Fax: 310-338-9057