Use without training
This paper reviews intuitive software design and outlines the development of an instrument for analysts to evaluate the intuitiveness of software design. Current intuition research outlines three requirements for intuitive use: (a) existing experiential domain knowledge and skills, (b) an unexplaina...
Main Author: | |
---|---|
Format: | Article |
Language: | English |
Published: |
University of Jyväskylä
2019-02-01
|
Series: | Human Technology |
Subjects: | |
Online Access: | https://humantechnology.jyu.fi/archive/vol-15/issue-1/use-without-training |
id |
doaj-f3f9d30e4b884b498249ccb2eb2aa4f4 |
---|---|
record_format |
Article |
spelling |
doaj-f3f9d30e4b884b498249ccb2eb2aa4f42020-11-24T21:36:41ZengUniversity of JyväskyläHuman Technology1795-68892019-02-0115110013510.17011/ht/urn.201902201610Use without trainingPatrick Lehane0University of Southern Queensland, AustraliaThis paper reviews intuitive software design and outlines the development of an instrument for analysts to evaluate the intuitiveness of software design. Current intuition research outlines three requirements for intuitive use: (a) existing experiential domain knowledge and skills, (b) an unexplainable perception that a novel situation is contextually familiar, and (c) successful application of users’ previously acquired experiential knowledge and skills. A case study illustrates how these requirements can be specified, implemented, and evaluated. Questions to evaluate the characteristics of intuitive design and use resulted in an intuitive use evaluation of 3.2 on a scale of 0–4, indicating a perception of intuitive use. Subsequent factor analysis exposed three factors describing intuitive use: (a) Familiar User Expectations, (b) Confident Interactions, and (c) Leverage of Prior Learning. These factors map one-on-one to the requirements for intuitive use: providing an earlyhttps://humantechnology.jyu.fi/archive/vol-15/issue-1/use-without-trainingintuitionintuitive designinteraction designusabilityaffordancesuser experiencesystem analysis |
collection |
DOAJ |
language |
English |
format |
Article |
sources |
DOAJ |
author |
Patrick Lehane |
spellingShingle |
Patrick Lehane Use without training Human Technology intuition intuitive design interaction design usability affordances user experience system analysis |
author_facet |
Patrick Lehane |
author_sort |
Patrick Lehane |
title |
Use without training |
title_short |
Use without training |
title_full |
Use without training |
title_fullStr |
Use without training |
title_full_unstemmed |
Use without training |
title_sort |
use without training |
publisher |
University of Jyväskylä |
series |
Human Technology |
issn |
1795-6889 |
publishDate |
2019-02-01 |
description |
This paper reviews intuitive software design and outlines the development of an instrument for analysts to evaluate the intuitiveness of software design. Current intuition research outlines three requirements for intuitive use: (a) existing experiential domain knowledge and skills, (b) an unexplainable perception that a novel situation is contextually familiar, and (c) successful application of users’ previously acquired experiential knowledge and skills. A case study illustrates how these requirements can be specified, implemented, and evaluated. Questions to evaluate the characteristics of intuitive design and use resulted in an intuitive use evaluation of 3.2 on a scale of 0–4, indicating a perception of intuitive use. Subsequent factor analysis exposed three factors describing intuitive use: (a) Familiar User Expectations, (b) Confident Interactions, and (c) Leverage of Prior Learning. These factors map one-on-one to the requirements for intuitive use: providing an early |
topic |
intuition intuitive design interaction design usability affordances user experience system analysis |
url |
https://humantechnology.jyu.fi/archive/vol-15/issue-1/use-without-training |
work_keys_str_mv |
AT patricklehane usewithouttraining |
_version_ |
1725939995887271936 |