uar able presentation

TeamableSanghyuk Koh, Rahan Khozein, Gary Suen, Lauren

Wendel

Who is UAR?• Software Development Company

What is ABLE?• Project Management Tool

Who are ABLE’s users?• Project managers• Everyone

Overview Methods Finding Summary Q/A

Interaction Map

Contextual Inquiry

Personas & Scenarios

Comparative Evaluation

Heuristic Evaluation

Surveys

User Testing

Overview Methods Finding Summary Q/A

Interaction Map

Overview Methods Finding Summary Q/A

Contextual Inquiry

Overview Methods Finding Summary Q/A

Personas & Scenarios

Overview Methods Finding Summary Q/A

Comparative Evaluation• 4 direct competitors

• dotProject.net

• Microsoft Office Project

• ACE project

• Creative Pro Office

Overview Methods Finding Summary Q/A

Heuristic Evaluation• Nielsen’s 10 heuristics

• Severity rating scale from 0 to 4

• 0 indicates no or little usability problem

• 4 indicates major usability problem

Overview Methods Finding Summary Q/A

Surveys• Data collected through SurveyGizmo

• 31 surveys analyzed

• Used Microsoft Excel for statistical

analysis

• Sample means, T-Test etc…

Overview Methods Finding Summary Q/A

User Testing• 1 pilot & 4 regular testers

• Recruited users of project management

applications

• Used Silverback to record video & audio

• Users carried out 7 tasks that covered the

main

functionalities of ABLE

Overview Methods Finding Summary Q/A

Simple User Interface

Customizable

Useful for Project Managers

Overview Methods Finding Summary Q/A

Users have difficulty finding certain functions or

information in ABLE

There is little guidance available to help users complete

their tasks

Inadequate system feedback or obscure error messages

Limited inter-feature dependencies lead to fragmented

and unconnected information

Sparse, spread-out layout decreases continuity and readability

Overview Methods Finding Summary Q/A

Evidence

• Not intuitive menu classification

• Inconsistent & confusing labels

Recommendations

• Re-work taxonomy

• Review and standardize vocabulary

Overview Methods Finding Summary Q/A

Users have difficulty finding certain functions or

information in ABLE

Evidence

• Inadequate contextual instructions

• ‘Page Actions’ is not efficient

Recommendations

• Provide direct instructions for how to

interact

Overview Methods Finding Summary Q/A

There is little guidance available to help users

complete their tasks

Evidence• Neither redirects the user to another

page nor provides notifications

• Vague or contradictory error messages

Recommendations• Automatically redirect the user after the

completion

of a task

• Provide clear & actionable error messages

Overview Methods Finding Summary Q/A

Inadequate system feedback and obscure error

messages

Evidence

• Changes made under one feature do not

reflect in

others

Recommendations

• Needs assessment of users

Overview Methods Finding Summary Q/A

Limited inter-feature dependencies lead to

fragmented and unconnected information

Evidence• White space

• Limited use of fonts and sizes of texts

• Lack of icons & colors

Recommendations• Implement different fonts, colors where

appropriate

Overview Methods Finding Summary Q/A

Sparse, spread-out layout decreases continuity and

readability

Identified and prioritized 5 critical problems

Adopting our recommendations would improve user experience of ABLE

Allowed us to experiment gain knowledge of various usability evaluation methods

Overview Methods Finding Summary Q/A

Overview Methods Finding Summary Q/A