[Sigia-l] which comes first: user scenarios or user personas?

[Dave Harland]

Eric,

It may be easier to work backward from the definition of a 'successful'
experience architecture (on a case-by-case basis).

6. The objective should be to create an architecture that provides each key
user group enough information, no more - no less, to achieve their goals. 

5. Chances are that multiple goals will exist based on different user types
within the target audience. 

4. These distinct user goals require a defined set of tasks in order to be
achieved.

3. Generally the best way to identify the set of tasks for each unique goal
is through explicit user scenarios.

2. In order to make these scenarios explicit, each key user group from the
target audience must be characterized through detailed traits, behaviors,
technological experience, vertical experience, personality types, etc. -
i.e. 'personas'.

1. The target audience should be identified through the business analysis
initially performed to define the business objectives.


Typically I don't care to make generalizations but in this case I believe
it's fairly safe to say one process fits all.


Dave Harland 
Manager of Internet Development 
Compass Technology Management 
Direction You Can Trust 
www.compass.net 
757.233.7348

-----Original Message-----
From: sigia-l-admin at asis.org [mailto:sigia-l-admin at asis.org] On Behalf Of
Eric Scheid
Sent: Sunday, May 23, 2004 2:48 AM
To: sigia l
Subject: [Sigia-l] which comes first: user scenarios or user personas?


I'm curious to know how others go about their practice - do you develop user
scenarios before user personas, or the other way around, or a bunch of
re-iterative cycles?

e.

------------
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable list archive:   http://www.info-arch.org/lists/sigia-l/
________________________________________
Sigia-l mailing list -- post to: Sigia-l at asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l