Task Analysis – Input to Interaction Gabriel Spitz Task Analysis – Input to Interaction Lecture # 6

Gabriel Spitz What is task Analysis It is the way of systematically describing the how people go about achieving specific tasks

Objective of Task Analysis To provides the input information for Interaction Design It specify what functions the user will want to perform and how each function will be achieve It describes the Steps that users will perform and their sequence It does it within the bigger context of users’ Activities

Context of task Analysis Gabriel Spitz Context of task Analysis

Context for Task Analysis Within the UI context Task Analysis contributes primarily to Interaction Design Interaction Design - Is focused on enabling the user to use the application capabilities in an effective and efficient way Interface Design – Is focused on guiding the users on how to use those capabilities to achieve their related user tasks and obtain the desired results Conceptual Model Design – Is focused on Informing the user what capabilities a specific application has

Utilizing Task Analysis Gabriel Spitz Utilizing Task Analysis Steps associated with adding Header to slides 3 1 1. Interaction 6 2 4 5

Why task Analysis? What actions are needed? Gabriel Spitz Why task Analysis? Product Manager: UX: UX: User shell be able to add “Date and Time” to Slides What does it mean to add “Date and Time” to slides How do people add “Date and Time” to slides Today What actions are needed? How should they be organized?

Gabriel Spitz The Context of Tasks

Interaction within Context Actions people take are done within context Context provides constraints and expectations The context for interaction can be conceptualized as a Hierarch composed of Activity Tasks Steps (Actions) The boundaries between these layers is fuzzy

Hierarchy of Actions Activity Task Step or Action Is often associated with a high level goal that is desired and satisfies a user intent. It has clear intrinsic value to the user Task Is an element of an activity that is meaningful by itself. It has little intrinsic value by itself, but it contributes to the attainment of the Activity Step or Action Is an atomic component that by itself has no intrinsic value to the user, but it contributes to task task

Example – Formatting Text Activity Format Bullets Tasks Navigate to Bullet Formatting Dialog Specify Desired Bullet Format Apply Selected Format Step – Within Bullets & Numbering Select Style Select color Select Size of Text Click on OK

Activity – Format Text Task – Add Bullets Steps 1 2 3

Task Analysis - Details Gabriel Spitz Task Analysis - Details

Gabriel Spitz Tasks Tasks are derived from user’s goals – For what reason would they buy or want to use a specific product Different goals could suggest different tasks and therefore different design

Characteristics of Task Analysis Gabriel Spitz Characteristics of Task Analysis Task analysis is a method we use to describe and represent how and to what end the functions of application or a website will be used It is systematic in nature It is analytic rather the intuitive or speculative We often feel that we understand users task, but this understanding is frequently incomplete and wrong e.g. the lath operator that used cloth pin to lock one of the safety buttons

Example of a Website Why would somebody view a Web Page Gabriel Spitz Example of a Website Why would somebody view a Web Page Potential Users’ Tasks Gain Understanding Search for specific info. Be enticed Fill out forms Contact a person

Yes No Gain Understanding Scan home page Gabriel Spitz Gain Understanding Scan home page Notice interesting content/link Decide to get more info Go to/Open page Scan content of page Is content interesting? Read in depth Yes No

Gabriel Spitz Uses of Task Analysis

Gabriel Spitz Uses of Task Analysis Describe how people currently perform specific tasks Describe how people in the future will perform a task Help develop training material Help identify good tasks (representative or critical) for usability evaluation

Motivation for Task Analysis Gabriel Spitz Motivation for Task Analysis Ensure that what we design is congruent with users need Customers often forget their bank card in the ATM machine Ensure compatibility with users’ characteristics Displaying date as Nov, 12, 2002 (for 12/11/02) Ensure compatibility with users’ activity flow Do not forces the user to perform a task in an uncommon way such as reverse polish notation

Expected Outcomes of Task Analysis Gabriel Spitz Expected Outcomes of Task Analysis A set of functional requirements Functions that are needed and desired by end users A set of non-functional requirements for UI design A Metaphor or a conceptual model Users describe contacts as items in a Rolodex Specification of the task flow Focus areas for UI evaluation Benchmark tasks for usability testing

Extracting Conceptual Models Gabriel Spitz Extracting Conceptual Models

Questions asked using TA Gabriel Spitz Questions asked using TA What tasks do users perform and in what order What tasks are desired What happens when things go wrong What tools are used in conjunction with task performance Who else can impact task performance and how E.g., when using ATM consider the next person in line

Performing Task Analysis Gabriel Spitz Performing Task Analysis

Include in Task Analysis Gabriel Spitz Include in Task Analysis Start-up tasks Power-down tasks Maintenance tasks Miss use tasks

Example – Task Hierarchy Gabriel Spitz Example – Task Hierarchy Hierarchical task decomposition describes what is done and why (the level above)

Gabriel Spitz Example – Procedure Procedural analysis describes how a given task is executed and the decisions involved

Selecting Tasks Start with tasks that are meaningful by themselves Gabriel Spitz Selecting Tasks Start with tasks that are meaningful by themselves E.g. Replace a tire, not unbolt tire screws Select real tasks that users have faced Make sure that selected tasks provide reasonable coverage of what users need to do Select mixture of simple and complex tasks When we transition to the design stage Discard features that do not support users’ tasks Add real task that exercise the features

Structure of Task description Gabriel Spitz Structure of Task description Specify the users Roles and their characteristics Specify where inputs come from and outputs go to Working with other tools Reflect on the interest of potential users Illustrate functionality in context of work users really want to do Focus on the system users will need Not systems users say they want Remember, Users are not always right, they often do not anticipate new technology accurately

Gabriel Spitz Describing Tasks Technology neutral - Say what the user wants to do, but not how the user would do it E.g., contact department head, but not send email to department head This allow comparing different design alternatives E.g., Letter, Email, Facebook, Skype, etc. Specific Forces us to consider how features work together Include The information that the user need for a task Both related and unrelated to software What the users sees and interacts with

Using Tasks in design Write up description of task Gabriel Spitz Using Tasks in design Write up description of task Run by users and rest of the design team Get more information where needed Rough out interface design Major screens and functions (not too detailed) Hand sketches Produce scenario for each task What user has to do and what they would see Step-by-step performance of the task use-case

Gathering Task Analysis Data Gabriel Spitz Gathering Task Analysis Data

Methods for gathering Task Data Gabriel Spitz Methods for gathering Task Data Review documentation Observations – preferably in the workplace Interviews - preferably in the workplace Questionnaires and surveys

Usage of Data Gathering Methods Gabriel Spitz Usage of Data Gathering Methods Documentation review Develop a high level understanding of features, task, and procedures – what is there Observation Develop a detailed understanding of tasks, and procedures in the real world – How is it used Interview Explore issues and develop use scenarios – What is missing Questionnaires Gather specific information

Once we Have the Data Describe the workflow graphically Gabriel Spitz Once we Have the Data Describe the workflow graphically This helps ensure that the task flow smoothly All or most possibilities are accounted for Tasks have a defined start and end points Verify the flow with end users

Summary Answer questions before designing Selecting tasks Gabriel Spitz Summary Answer questions before designing Who, what, where , how often Relationship between users and data What other tools do users have What happens when things go wrong Selecting tasks Real tasks with reasonable functionality coverage What should tasks look like Complete, specific tasks of what users want to do