Elizabeth,
As always the answer is - it depends...:) .. For lack of time I can
only broadly 'sketch' what happens with scenarios in the context of
our work - if we are calling 'scenario' the same thing...
Keep in mind that everything in our world is considered through a
tight lens of time-budget-expected/desired outcome... so here are a
few basic points:
- Often there are a bunch of "use-cases" delivered by the engineering
team during the Discovery phase(as ppt, printed pages etc).
- There is a quick review and analysis of these, we attempt to answer
questions like: are these cases accurate? are they really relevant?
Do they address what application and users are supposed to do? ... a
lot of decisions here are dictated by what we already know, or
learned from engineering team and from user interviews that often
run in parallel. When client has nothing, no scenarios , no
documented use cases -- we create all from scratch (there is a
positive and negative side to it)... we do it quickly and to a
necessary degree (based on Lead designer judgement)
- Based on that analysis there could be a quick preliminary clean-up,
compression (out of 10 use cases only 1-2 may be really important,
relevant) or there could be some important scenarios missing ... or
there could be a partial reframing of scenarios... Quick diagrams are
created, discussed with client to make sure that we are on the same page
- In the following Conceptualization phase there could be a complete
rethinking of scenarios, and new scenarios (flows) created..
- If new proposed flows are so radically different - then we may
create a very rough click-through and run very limited tests with users
Again - most of it decided on the fly and based on lead designer
judgement...
- After detailed wireframes are completed there is typically a quick
walk through with 2-3 users representing major user profiles/
personae ... this helps to quickly uncover small or secondary issues ...
hope this helps,
Yury Frolov
Design Director, Studio Asterisk*
GUI Strategy | User Experience | Brand
415 374 7478 voice
702 446 7840 fax
www.studioasterisk.com
On Jan 29, 2009, at 5:08 PM, Elizabeth Bacon wrote:
Hi Jim,
If you have a second, I have a question about your experience of RED.
To what extent do you & your team utilize scenarios as a rapid
prototyping tool?
Question also extended to Yury and others who've practiced or do
practice the RED approach.
Cheers,
Liz
P.S. My bias is that scenarios are indispensible for RED even if
there's no good or direct user research to utilize.
P.P.S. For the record, I *much* prefer this term to Genius Design,
which is far too pejorative & pretentious sounding. Hey, maybe we can
get Dan Saffer to adjust the term in his upcoming revision of
"designing for interaction"! ;)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=37626
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
