Next 0me. Visualiza0on center - C. Expecta0ons (förväntningar) Human- System Interac0on TNK067

Transcription

1 Next 0me Human- System Interac0on TNK067 HT 2013, Lecture 2 Monday 18/11 at 8:15-10:00 Seminar (lek0on) Ac0ve par0cipa0on If you are not amending I want to know beforehand the ac0vity will be conducted by yourself and a wrimen assignment will be handed in (arer the seminar) Part of the introduc0on to Assignment 1/group assignment Visualiza0on center - C Tuesday November 26th 10:15 12:00 Lecture in TP51 Visit to the Visualiza0on Center - C We meet in the entrance at 10:15 sharp! Exhibi0ons 10:15 11:15 Dome show 11:15 12:00 Expecta0ons (förväntningar) Do not know what the course is about but hope I ll learn things that will be valuable in the future Psychology, percep0on, how we experience things Technology related to humans is interes0ng Get to know more about everyday problems, what are the simple things that make it work/not work? Learn why things are designed they way they are Usability, understand it bemer Design principles Learn how to do things Get new perspec0ves Work more with theory and knowledge than mathema0cs and sta0s0cs 1

2 Concerns (farhågor) Not being allowed to take the course (late registra0on) The language. I am afraid I will not understand everything at the lectures and most important, not understand instruc0ons for assignments, and the book. English terminology Swedish home exam, hard if the exam is in English and we will answer it in Swedish Not being able to meet the criteria for grade 5 Not choosing my group (graded assignment) To much work? Never had a home exam before Why is the book needed for the exam? Today Human- centred design/development/evalua0on concepts, methods, processes Cogni0on and frameworks for MSI/HCI understanding users of technical systems Use and Users Use and Users Use and Users There are not two people doing the same thing. There are no stupid users only incidental use (oförutsem användande). People make mistakes. Use and Users Understanding users of technical systems What do they want and/or need (do not always correlate). For what purpose? In what context (sammanhang)? What are their prerequisites (förutsämningar) and limita0ons (begränsningar). Etc. It is usually not their fault. 2

3 Usability Usability Sugges0ons? Opinions? effective easy satisfying usable intuitive valuable desirable Social acceptability Utility Usability Usefulness The Interna0onal Organiza0on for Standardiza0on (ISO) addresses guidance on the specifica0on and measurement of usability and defines usability as: System acceptability Physical acceptability Usability Cost Compatability Easy to learn Efficient to use Easy to remember Few errors The extent to which a product can be used by specified users to achieve specified goals with effec9veness, efficiency and sa9sfac9on in a specified context of use. Etc Reliability Subjectively pleasing (Nielsen, Usability Engineering). Usability ISO 9241 Effec0veness accuracy and completeness with which users achieve certain goals measures whether they were met successfully: error rates, magnitude of errors Usability always? Some things are not that good to use but really pretty Norman, Emotional Design - Why we love (or hate) everyday things. Efficiency resourses consumed in rela0on to accuracy and completeness measures 0me spent: task comple0on 0me, learning 0me Sa0sfac0on opinions, preference, comfort, confidence ra0ng scale, statements 3

4 Norman, Emotional Design - Why we love (or hate) everyday things. For example, esthe0cally pleasing objects appear to be more effec0ve for the user thanks to their appeal. It depends on the "closeness" user feels for an object, since you are forming an emo0onal bond (to the object). Aims at crea0ng interac0ve systems that are: funny entertaining mo0va0ng aesthe0cally pleasing rewarding, etc. User experience (UX) User experience is defined by ISO as follows: "A person's percep0ons and responses resul0ng from the use and/or an0cipated use of a product, system or service." Usability vs. User Experience I some0mes get the ques0on what the difference is between Usability and User Experience (UX). One may think that User Experience doesn t necessarily imply that something is usable (whether it s good or bad, it s s0ll an experience), and hence Usability is superior to User Experience. However, the emerging trend is to refer to User Experience as the wider perspec0ve and Usability as being part of User Experience, as illustrated. User experience (UX) As the NeoSpot slogan states; IT s all about the User Experience, not about the technology itself. User experience (UX) As the NeoSpot slogan states; IT s all about the User Experience, not about the technology itself. 4

5 User experience (UX) Usability and UX As the NeoSpot slogan states; IT s all about the User Experience, not about the technology itself. Please note that a basic concept of the ISO defini0on is that usability/ux is not a property in itself but dependent on: The users - who is using the visualiza0on? e.g. are they highly trained and experienced users, or novices? Their goals - what are the users trying to do with the visualiza0on- does it support what they want to do with it? Their a<tude - how do they perceive it's capabili0es, aesthe0c appeal etc? The usage situa=on (or 'context of use') - where and how is the visualiza0on being used? Lind, Bingham & Forsell Metric 3D Structure in Visualization. Journal of Information Visualization, 2(1): What s the pattern? 5

6 Total sale, in thousand $ A good system Total sales, in thousand $ Allows the user to focus on tasks in certain usage situa0ons Is effec0ve and efficient for (daily?) use Contains relevant informa0on and func0onality Is intui0ve and natural/straightorward to learn Is amrac0ve Ask yourself: Can I do what I need/want to do Can I do it in a good way. Without great effort, without errors etc. Did I experience using it as fun, s0mula0ng and without feeling unpleasant? If yes? Great usability J How to do? By applying/using user- centred development/design/ evalua0on. User- centred design User- centred design (UCD) can be defined in many ways, but all defini0ons are characterized by a focus on the user, and on incorpora=ng the user s perspec=ve in all stages of the design process. Donald Norman describes UCD as a philosophy based on the needs and interests of the user, with an emphasis on making products usable and understandable (Norman 2002, p.188). By this defini0on, actual user involvement is not a part of UCD by necessity. However, involving the users in the user- centred design process is a common way of ensuring that their needs and interests are being met. 6

7 User- centered design (development) How to do? There are four essen0al user- centred design ac0vi0es which should be planned for and undertaken in order to incorporate usability requirements into the development process. These are: understand and specify the context of use specify the user requirements produce design solu0ons to meet user requirements evaluate the designs against requirements The ac0vi0es are carried out in an itera&ve fashion, with the cycle being repeated un0l the par0cular usability objec0ves have been amained. The human-centred design process, ISO How to do? The chief difference from other product design philosophies is that user- centered design tries to op0mize the product around how users can, want, or need to use the product, rather than forcing the users to change their behavior to accommodate the product. How (not) to do (in most cases). Waterfall development methodology A sequential design process in which progress is seen as flowing steadily downwards like a waterfall trough the phases. Itera0ve processes/methods Agile sorware development is a generic term for a number of methods using itera9ons to avoid the problems described with the waterfall model. Agile (vig, lämrörlig) development is flexible and handles change well! One itera0on usually lasts from one to four weeks and op0mally comprises planning, analysis, design, coding and tes0ng. One of the main points is that evalua0on is done many 0mes during the project, which enables change in direc0on and/or redesign at an early stage, saving 0me and resources. Agile development The key principles of agile development are found in the so called Agile Manifesto. It states that priority should be given to: Individuals and interac0ons over processes and tools Responding to change over following a plan Working sorware over comprehensive documenta0on Customer collabora0on over contract nego0a0on 7

8 Tradi0onal process visualized Sekvential vs. overlapping development Requirements Design Code Test Instead of doing one thing at the time......the Agile team does a little bit of everything all the time Source: The New New Product Development Game by Takeuchi and Nonaka. Harvard Business Review, January Agile process visualized Agile development Is Agile development only for sorware development? Agile HR Advantages from a HR perspec0ve Agile methods inspire us to think in new ways around collabora0on, recruitment, goals and feedback. Desired product What the customer wanted Specified product Delivered product Agile development Agile development Build projects around mo0vated individuals. Give the team the environment and support they need, and trust them to get the job done. Business analysts, managers, developers and testers must work together daily throughout the project. The best architectures, requirements, and designs emerge from self organizing teams. Companies without boss and structure? Structure happens Flatland See Handbook for new employees: 8

9 How to do? In the previous figures we saw a schema of the itera0ve user- centred design process as defined in ISO In order to make the users an ac0ve part of each step in this process there are a number of empirical methods, such as: Interviews Surveys Workshops Focus groups Field studies Usability tes0ng Etc. Cogni0ve frameworks Understand how and what users think and why they think in a certain way. Cogni0on and frameworks for MSI/HCI explain human behavior understanding users of technical systems Cogni0on A number of conceptual frameworks have been developed to explain and predict user behavior based on theories of cogni0on. Influen0al ones for human- computer interac0on and interac0on design are (Preece, Rogers & Sharp, 2007): Mental models Theory of ac0on Informa0on processing External cogni0on Distributed cogni0on Cogni0ve frameworks Mental models Mental models Psychological representa0ons of real, hypothe0cal or imaginary situa0ons 9

10 Mental models - example The hea0ng has just come on but the room is cold. The room thermostat is set where you normally have it (higher than the current temperature). Do you: 1. Turn it up hoping that the room will heat faster? 2. Leave it where it is and just wait? Mental models - example A room thermostat is not like a tap (valve - ven0l) A room thermostat is like a switch Mental models Do people use erroneous models? Yes! It is common. In everyday life we develop a core set of abstrac0ons of how things work which we apply to a range of devices irrespec0ve of whether they are appropriate. Models How can user s acquire the right mental model? interac0on with a system, experience training documenta0on, guides or online help personal assistance Mental models Web Usability Do people use erroneous models? Yes! It is common. In everyday life we develop a core set of abstrac0ons of how things work which we apply to a range of devices irrespec0ve of whether they are appropriate. Many people s understanding of how (computer- based) technology and services work is poor. Their mental models are oren incomplete, easily confusable, based on inappropriate analogies and supers00on. As a consequence they find it difficult to iden0fy, describe, or solve a problem and lack the words or concepts to explain what is happening. 10

11 Models Models Models Norman s views it as communica0on/interac0on between two parts: The user and the designer. The communica0on takes place trough the system image. How can a designer acquire and understand the right mental model? The core of user- centred design According to this model, the designer s task is divided in to two problems: Know the user! Design and evaluate Itera0ve design To understand the user s mental model and create a good design model based on this knowledge. (This lecture and more). To build a system image that is consistent (konsekvent) and clearly conveys (förmedlar) this model to the user. (Next lecture and more). Exercise Ac0vity ATM Cogni0ve frameworks Know the user Elicit (få fram) and understand mental models from people. The goal is for you to understand the nature of peoples knowledge of an interac0ve product in terms of how it works and how to use it. 11

12 How did it go? Your mental models How similar? How shallow/deep? How accurate? Models The design model/conceptual model and your (representa0ve users) understanding of it do they match? Is saying and doing the same thing? Is it really a persons mental model that we get during such analysis ac0vity? Get to know the user (more in other lectures e.g., about evalua0on). for example would the outcome have been different if you had done it while having access to and ATM? The point If people could develop bemer mental models of interac0ve systems they would be in a bemer posi0on to know how to carry out their tasks and know what to do when they encounter problems. Ideally they should be able to develop a mental model that matches the designer model. To what extent is that realis0c? (Training, experience by interac0ng with a system, reading manuals or other documenta0on, tutorials, personal assistance etc.) The point Transparent includes how to elicit peoples models and know about what affects them. Transparent includes providing the right kind and level of informa0on, interac0on, guidance, and response etc. Alterna0vely, if interac0ve technologies could be designed to be more transparent then it might be easier to understand them in terms of how they work and what to do when they don t. Next 0me 12