SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 25, 2001.

Slides:



Advertisements
Similar presentations
Design, prototyping and construction
Advertisements

User problems, scenarios and storyboards
An introduction to personas
Int 2 Computing Software Development.
2-May-15 GUI Design. 2 HMI design There are entire college courses taught on HMI (Human-Machine Interface) design This is just a very brief presentation.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 30, 2003.
Scenarios and Personas Professor: Tapan Parikh TA: Eun Kyoung Choe
SIMS 213: User Interface Design & Development
SIMS 213: User Interface Design & Development Marti Hearst Tues, Jan 29, 2002.
SIMS 213: User Interface Design & Development Marti Hearst and Tues, Jan 30, 2007.
SIMS 213: User Interface Design & Development Marti Hearst Thur, Feb 3, 2005.
SIMS 213: User Interface Design & Development
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Feb 5, 2004.
SIMS 213: User Interface Design & Development Marti Hearst Thur, Feb 2, 2006.
SIMS 213: User Interface Design & Development Marti Hearst Tues, Feb 1, 2005.
SIMS 213: User Interface Design & Development Marti Hearst Tues, Feb 4, 2003.
Data collection methods Questionnaires Interviews Focus groups Observation –Incl. automatic data collection User journals –Arbitron –Random alarm mechanisms.
Administrivia Turn in ranking sheets, we’ll have group assignments to you as soon as possible Homeworks Programming Assignment 1 due next Tuesday Group.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 20, 2005.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 22, 2004.
2-1©2005 Prentice Hall 2 Individual Differences: Personality and Ability Chapter 2 Individual Differences: Personality and Ability.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 18, 2007.
Ch 5 Specification page 1CS 368 Context Specification one of the most commonly cited reasons for an IT project failure is unclear objectives and requirements.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 27, 2005.
Building Knowledge-Driven DSS and Mining Data
Personas 14 Feb Personas Developed by Alan Cooper A user archetype used to help guide decisions about product features, navigation, and visual design.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 26, 2006.
SM3121 Software Technology Mark Green School of Creative Media.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Feb 6, 2003.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 29, 2004.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 23, 2003.
How to be a GOOD Writer and Speaker. “I don’t like school!” “Okay. Why not?” “I just don’t.” “I know, but is there a particular reason?” “School is stupid.”
Human Computer Interface. Human Computer Interface? HCI is not just about software design HCI applies to more than just desktop PCs!!! No such thing as.
After word User Interface in Games. Principles of User Interface Design Know your user Know your user's tasks Craft an interface suitable to the user.
2505ICT User Interface Design. Course organisation  Course Convenor and lecturer Marilyn Ford, L08 Room 2.20,
1 ISE 412 Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation.
William H. Bowers – Modeling Users: Personas and Goals Cooper 5.
User Modeling Lecture # 5 Gabriel Spitz 1. User-Interface design - Steps/Goals.
MULTIMEDIA What is Multimedia? The word MULTIMEDIA is made up from two words, MULTI meaning more than one and MEDIA meaning a way of displaying or passing.
DMS 546/446 INTERFACE DESIGN AL LARSEN – SPRING 2008 PAPER PROTOTYPING Lecture draws from multiple sources, including: Jakob Nielsen, Shawn Medero (
Chapter 3 Leadership.
CS 4720 Usability and Accessibility CS 4720 – Web & Mobile Systems.
A Template for Creating Buyer Personas. 1. A Brief Introduction to Buyer Personas 2. How to Present Your Buyer Persona 3. An Example of a Complete Buyer.
PERSONAL FINANCE MAKING PERSONAL FINANCIAL DECISIONS.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
1CS 338: Graphical User Interfaces. Dario Salvucci, Drexel University. Lecture 3: Personas.
Allison Bloodworth, Senior User Interaction Designer, Educational Technology Services, University of California - Berkeley October 22, 2015 User Needs.
Doug Mangold ARC – Managing Director, Product Management.
1 Designing Better Software User Centred Design and Usability Adam Smith Director, Design and Usability Flight Level Media Ltd.
User Modeling Lecture # 7 Gabriel Spitz 1. User Interface Design Process Gabriel Spitz 2 Needs Assessment Competitive Analysis Persona Develop Task Analysis/
User Modeling Lecture # 7 Gabriel Spitz 1. User Interface Design Process Gabriel Spitz 2 Needs Assessment Competitive Analysis Persona Develop Task Analysis/
Human Computer Interface INT211
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It describes what is a user doing or will.
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It specifies what functions the user will need.
Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation ISE
Seminar in Computer Science Cooper – Inmates CIS385 January 23, 2007.
The Limits of Personas Peter Bagnall Guy Dewsbury Ian Sommerville.
Interview techniques All interviews are similar in that the interviewer asks the interviewee questions, all interviewers will have a set out structure.
Marketing Strategy & Consumer Behavior Unit 4. Planning a Marketing Strategy  A plan that identifies how a company expects to achieve its goals is known.
Growth Mindset Carol Dweck Ph.D Before we begin please take some time to consider your own Mindset through responding to the statements on the sheet.
Activity Design Goal: work from problems and opportunities of problem domain to envision new activities.
Human Computer Interaction Lecture 10 Interaction Paradigms.
[name] [demographic] [goals] A Template for Creating Buyer Personas.
A Marketer’s Template for Creating Buyer Personas [name] [demographic]
The Marketing Mix and the 4Ps of Marketing
Usability engineering
Human Computer Interaction Lecture 10 Interaction Paradigms
GUI Design 24-Feb-19.
Chapter 10 Marketing.
Presentation transcript:

SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 25, 2001

Tuesday’s HCC speaker Paul Pangaro Advocated Personalization, both – Automatic – User-defined But admitted that – Current attempts don’t work Automatically changing menus not a good idea Artificial intelligence doesn’t work What should we conclude? – We have several readings on this towards the end of the semester

Cooper on Designing for Goals We do tasks to achieve goals – don’t equate them! – Traveling safely in 1849 vs Goal of good design: help users achieve practical goals while not violating their personal goals – No “unnatural acts” Distinctions: – Personal goals – Corporate goals – Practical goals – False goals Example: goal-directed tv news system

Last Time User-Centered Design – Design from the user’s point of view As opposed to the system’s, the company’s – Participatory design involves the potential users, via Observation Interviews Working with these people directly to create and test the design From Johnson: – Software should be designed neither for users nor by them, but rather with them.

Think Outside-in versus Inside-out Do not expect others to think or behave – as you do – as you would like them to Assess the meaning of the displays and controls based on what a user can be assumed to know, not based on what you know

Example: Playing Pictionary Getting into someone else’s head

However (from Cooper) Being a victim of a problem does not necessarily bestow the power to see the solution An individual is not always representative – Company president example

Personas (from Cooper) “Hypothetical Archetypes” – Archetype: (American Heritage) An original model or type after which other similar things are patterned; a prototype An ideal example of a type; quintessence A precise description of a user and what they want to accomplish – Imaginary, but precise – Specific, but stereotyped Real people have non-representative quirks

The Essence of Personas Describe a person in terms of their – Goals in life (especially relating to this project) – Capabilities, inclinations, and background People have a “visceral” ability to generalize about real and fictional people – We can have detailed discussions about what Harry Potter, Scarlett O’Hara, or Donald Trump will think or do. – They won’t be 100% accurate, but it feels natural to think about people this way

Reasons for Personas A compromise design pleases no-one – The broader you aim, the more likely you miss the bulls-eye – 50% of the people 50% happy doesn’t work Car example – soccer mom, carpenter, dot-com exec – “Every time you extend functionality to include another constituency, you put another speed bump of features and controls across every other user’s road.” A targeted design can achieve – 10% people 100% ecstatic – Examples: Ram pickup truck Sony aibo There is no such thing as an average user

Reasons for Personas Examples of results of targeted design – Dodge Ram pickup – Roller suitcases – Sony Aibo Isn’t useful for anything Not fuzzy and warm Too delicate to let children us it, but – Passionate fan clubs – Brisk sales despite steep price – and prices now coming down

Reasons for Personas Avoid the “elastic user” – If the description is not specific, it can easily wiggle to suit the design needs of the moment Piston analogy (movie from Helps prevent designer / programmer from imagining they are the user

Reasons for Personas Puts an end to feature debates – Makes hypothetical arguments less hypothetical Q: “What if the user wants to print this out?” A1: “The user won’t want to print often.” A2: “Emilee won’t want to print often.” User Persona, not Buyer Persona – This is one way HCI differs from marketing – Eventually it pays off in more sales

Case Study using Personas Sony TransCom’s Initial design: Conventional solution – Deep hierarchy of screens “Uninformed consent” Reflected the internal design of the software – This design decision forced them to throw out the natural choice of a touchscreen – 3D graphics, artistic icons, map-and-globe metaphor But no substance “Painting the corpse”

Case Study using Personas Procedure: – Interviews inside Sony What are their goals? What is the project history? – Interviews in the field Airline personnel, particularly flight attendants – Every new story lead to a new persona 30 personas at one point – Eventually, see commonalities, collapse them down 4 passengers, six airline employees Passengers are the hard part

Case Study using Personas Passenger Personas – Chuck Burgermeister – Ethan Scott – Marie Dubois – Clevis McCloud Goal: satisfy all of them, make no one unhappy, but don’t have to make any of them exceptionally happy – (contradiction of earlier point – captive audience) Interesting development: one persona became a “common denominator” and a “touchstone”

Case Study using Personas Interesting design decisions – No navigation Only one screen – This isn’t really accurate – they had different screens for different kinds of entertainment This means – not very many movies to choose from – and is not what a computer scientist would design for – Physical knob like a radio dial – Few clicks means touchscreen is ok – Content provided much of the value Movie vendors surprised the designers by being enthused about having to supply content Consequence of the fact that every movie is carefully marketed already Other interfaces needed for airline personnel

Cooper on Scenarios Daily Use – Fast to learn – Shortcuts and customization after more use Necessary Use – Infrequent but required – Nothing fancy needed Edge Cases – Ignore or save for version 2 Example: image cropping application – It works so intuitively, it feels like magic

Cooper’s Perpetual Intermediaries BeginnersIntermediatesExperts Programmers design for experts

Perpetual Intermediaries BeginnersIntermediatesExperts Marketers design for beginners

Perpetual Intermediaries BeginnersIntermediatesExperts People spend most of their time as intermediates

Perpetual Intermediaries BeginnersIntermediatesExperts Paradoxical Curves

Let’s practice creating personas Situation: BART ticket machines