1

SKODA-AUTO.CZ prototype evaluation

Poznań, 23th of March 2015

2

1

Scope of evaluation

3

• We're not familiar with UX proccess during the project and didn't get any analytics or UX deliverables

• Expert methods used:• Heuristic evalutions – based Nielsen-Molichs heuristics• Krug's Trunk Test

• Evaluation is based on proof of concept/prototype: http://bistroagency.cz/klienti/skoda/maketa/v6/importer-model-overview-summary.php

• Responsive web design implementation has been tested on Responsive view mode in Firefox on a desktop device

Scope of evaluation / Assumptions

4

2

Heuristic evaluation

5

The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

Heuristic evaluation / 1. Visibility of system status

Statement: heuristics satisfied

6

The system should speak the user's language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.

Heuristic evaluation / 2. Match between system and the real world

Statement: heuristics satisfied

7

Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

Heuristic evaluation / 3.User control and freedom

Statement: heuristics satisfied

8

Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.

Heuristic evaluation / 4.Consistency and standards

Statement: heuristics satisfied

9

Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.

Heuristic evaluation / 5.Error prevention

Statement: unknown status

Can't be evaluated at current state of the project – it's a prototpe

10

Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.

Heuristic evaluation / 6.Recognition rather than recall

Statement: heuristics satisfied

11

Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

Heuristic evaluation / 7.Flexibility and efficiency of use

Statement: heuristics satisfied

12

Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.

Heuristic evaluation / 8.Aesthetic and minimalist design

Statement: heuristics satisfied

13

Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.

Heuristic evaluation / 9.Help users recognize, diagnose, and recover from errors

Statement: unknown status

Can't be evaluated at current state of the project – it's a prototpe

14

Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.

Heuristic evaluation / 10.Help and documentation

Statement: heuristics satisfied

15

3

Krug's Trunk Test

16

Krug's Trunk Test / Evaluation

Statement: passed

Usability expert Steve Krug has created a test to determine whether a site has good navigation: the Trunk Test. Tester should be able to answer these questions without hesitation:• What site is this? (Site ID)• What page am I on? (Page name)• What are the major sections of this site? (Sections)• What are my options at this level? (Local Navigation)• Where am I in the scheme of things? ("You are here" indicators)• How can I search?

17

5

Conclusions

18

Conclusions / Final evaluation

• The prototype allows to declare the website as user friendly and usable with no signs of minor usability errors

• Designed user experience can't be evaluted, because no UX deliverables were shared

• The website passed basic expert test – both on desktop and mobile views• The website has modern design and front-end approach• Responsive web design has been implemented

19

Thanks for your attention!