290 likes | 376 Views
Information System Design Info-440. Autumn 2002 Session #5. Agenda. Reminders & upcoming Last time Exercise: Using trade-offs ( important ) Personas Break Scenarios Next time. Admin. Assignment #1 Will return on Wednesday Assignment #2 Any questions? Does everyone have a team?
E N D
Information System DesignInfo-440 Autumn 2002 Session #5
Agenda • Reminders & upcoming • Last time • Exercise: Using trade-offs (important) • Personas • Break • Scenarios • Next time
Admin • Assignment #1 • Will return on Wednesday • Assignment #2 • Any questions? • Does everyone have a team? • If you want feedback, please task to David or Lydia • Interactive design project • Have you started to think about it? • Any questions? • Quiz on Wednesday
Last time • Getting workplace data • Interviewing principles • Card sorting • How does it compare with affinity diagrams? • Using comics to tell stories • Simplifies communication of complex data • Representing trade-offs • Design options/features always have upsides and downsides
Process: Where we are now? • Week 1: Introduction • Week 2: Requirements Analysis, Part I • How to discover requirements & organize facts? • Week 3: Requirements Analysis, Part II • How to represent users and envision new work? • Conceptual design • Interaction design Prototyping • Evaluation • Information design • Process, project management • The literature, personalities, and history
Methods (so far) • Requirements analysis • Affinity diagramming • Card sorting • Comics for summarizing workplace data • Conceptual models (intro only) • Contextual inquiry, concentrating on interviewing • Design-space analysis (intro this week) • Focus groups • Inspecting objects (Norman’s vocabulary) • Personas (this week) • Scenarios (this week) • Task analysis (this week) • Trade-offs: Representation technique
Recall: In this restaurant, you need a key to use the restroom Solution options • A restaurant decides to lock restroom door – a blocking constraint • Visibility of key is fairly weak (and designed to be weak) • Solutions to this problem exhibit trade-offs… The problem: How to make restroom accessible to customers and not accessible to non-customers?
Situation/feature/ Issue 1. Key required 2. Put sign on restroom door 3. Ask front-desk for keys/buzz people in 4. Put sign in menu Possible Pros(+) or Cons(-) of feature + Non-customers will be blocked - Customers will be blocked Customers have to find key + Customers will have better chance of finding key Non-customers might seek out key in restaurant + Non-customers are not likely to go to front desk Takes time from staff at front desk + Many customers will see message + Non-customers will not see message - Some customers will go to restroom before opening menu
Quick Exercise: Tabs vs. Sections: Which is better? Tabs only Sections (& tabs)
Design choice 1. Tabs only 2. Sections only 3. Tabs and sections (hybrid) Possible Pros(+) or Cons(-) + xxx - xxx + xxx Xxx + xxx xxx
Personas You work on a Home Page Builder website and there are a large number of different kinds of users: teens, business people, college students, retired people, etc. • Question: • How do you design a site for all of them?
Personas • Answer • You don’t. Design the site for two users instead. • A little paradoxical • Consider the metaphor: • You don’t sew an average suit because it will not fit anyone
Example: Heather (part I) • Female, no specific ethnicity, single, 26 year old grad student • From Lincoln, Nebraska; now lives in Berkeley, Ca, grad dorms • 2 brothers – both play football at U of Nebraska • Family is middle class and well-educated, she’s a starving grad student • Goes to Berkeley for Marine Biology, full scholarship, works in the lab • Took time off between to work for non-profit (Greenpeace) • Interests: marine biology, oceans in general, wildlife,… • Advanced web user and builder
Example: Heather (part II) • Brand new laptop (gift from family for grad school) • Uses computer from dorm room, coffee shops, library, lab • Uses computer for homework, writing her journal, maintaining her site • Dorm room connection (T1?) • Main goal: Stay connected with her friends & family -- an avenue of personal expression • Comes to Tripod, because it’s free and has more advanced tools • She has two sites and two usernames: one is her personal site, and the other is her thesis site • Uses our most advanced tools (FileManager, FreeForm, Gear, etc.)
Persona Guidelines • Be specific • Details can be very helpful when debating features • Hypothetical • Personas don’t have to be ‘real’ people • Make them up to include important attributes of your target users • Give personas a name • Avoid using the word ‘user’ in conversations about design
Exercise • Break into groups of three or four • Create a persona for the Catalyst portfolio tool • Spend 10 min
Reading about personas • For more on personas read, Copper, A. (1999). The inmates are running the asylum. Indianapolis, IN: SAMS. • An article on why you should select only two or three personas (not 10 or 15) • Perfetti. C. Personas: Matching a Design to the Users' Goals. Retrieved, October 14, from http://www.uie.com/Articles/Personas.htm
Intro • Personas focus on the people whereas scenarios focus on the situation • Scenarios • Tell a story of stakeholders, activities and artifacts • The stories are often fictional BUT may be based on real data • Use personas within the story
Example scenario Defense Advanced Research Projects Agency (DARPA) See: http://www.darpa.mil/iao/EELD.htm
What do you see in this scenario? • Organizations • Stakeholders • Activities • Relationships • Artifacts
Different kinds of scenarios* • Daily use scenarios • Using the web to check stocks, issue trades, etc. • Necessary use scenarios • Key work that users must carry out • Edge case scenarios • Special cases and activities that occur infrequently * After Copper, Chapter 11.
Different kinds of scenarios* • Problem scenarios • Current practices, activities, stakeholders, artifacts… • Design scenarios • Invent new practices, … • Envision the future * After Rosson, M. B. & Carroll, J. M. (2002). Usability Engineering: Scenario-based Development of Human-Computer Interaction. New York: Morgan Kaufmann Publishers
Problem/daily use scenario Hi. I’m a day trader. I work out my home office. I try to keep life SIMPLE… I LOVE QCharts… I follow ONE stock everyday… Surprise! He follows ONE stock… If I need news, which is rare, I select this bookmark… http://finance.yahoo.com/q?s=ge&d=v1 I record transactions in my notebook… I retype them into a spreadsheet for my tax accountant During slow times, I’ll tinker with websites on computer TWO When something BIG happens I watch…
Design mini-process • You would like to design a better Catalyst message board • What would a process for this problem look like?
Design mini-process • Phase: Requirements Analysis • Collect and organize data on usage (5 days) • Interview stakeholders • Study artifacts, use of space, activities • Affinity diagram • Invent two personas (1 day) • Invent three problem scenarios (1 days) • Invent three design scenarios (2 days) • Based on design scenarios, identify new or changed features and represent trade-offs (2 days) • Phase: Conceptual design…
Next time • Investigate user goals & tasks • Two readings (not on quiz #1) • Cooper, A. (1999). Chapter 11: Designing for people (pp. 179-201). • Lewis, C. and Rieman, J. (1994). Chapter 2: Getting to Know Users and Their Tasks. • Reminder: • Quiz #1 (Wednesday, 16 Oct)