Why Good Engineers (Sometimes) Create Bad Interfaces
D. Gentner, and J. Grudin. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, page 277--282. New York, NY, USA, ACM, (1990)
DOI: 10.1145/97243.97287
Abstract
This paper presents a view of system design that shows how good engineering practice can lead to poor user interfaces. From the engineer's perspective, the ideal interface reflects the underlying mechanism and affords direct access to the control points of the mechanism. The designer of the user interface is often also the designer of the mechanism (or at least is very familiar with the mechanism), and thus has a strong bias toward basing the interface on the engineering model. The user, however, wants to complete a task, and an interface that is based on the task is often more appropriate than one based on the system mechanism. We discuss these issues, and also discuss where to position the user interface between the poles of the engineering model and the task model.
Description
Why good engineers (sometimes) create bad interfaces
%0 Conference Paper
%1 Gentner:1990:WGE:97243.97287
%A Gentner, Donald R.
%A Grudin, Jonathan
%B Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
%C New York, NY, USA
%D 1990
%I ACM
%K gui programmers
%P 277--282
%R 10.1145/97243.97287
%T Why Good Engineers (Sometimes) Create Bad Interfaces
%U http://doi.acm.org/10.1145/97243.97287
%X This paper presents a view of system design that shows how good engineering practice can lead to poor user interfaces. From the engineer's perspective, the ideal interface reflects the underlying mechanism and affords direct access to the control points of the mechanism. The designer of the user interface is often also the designer of the mechanism (or at least is very familiar with the mechanism), and thus has a strong bias toward basing the interface on the engineering model. The user, however, wants to complete a task, and an interface that is based on the task is often more appropriate than one based on the system mechanism. We discuss these issues, and also discuss where to position the user interface between the poles of the engineering model and the task model.
%@ 0-201-50932-6
@inproceedings{Gentner:1990:WGE:97243.97287,
abstract = {This paper presents a view of system design that shows how good engineering practice can lead to poor user interfaces. From the engineer's perspective, the ideal interface reflects the underlying mechanism and affords direct access to the control points of the mechanism. The designer of the user interface is often also the designer of the mechanism (or at least is very familiar with the mechanism), and thus has a strong bias toward basing the interface on the engineering model. The user, however, wants to complete a task, and an interface that is based on the task is often more appropriate than one based on the system mechanism. We discuss these issues, and also discuss where to position the user interface between the poles of the engineering model and the task model.},
acmid = {97287},
added-at = {2015-01-08T14:49:02.000+0100},
address = {New York, NY, USA},
author = {Gentner, Donald R. and Grudin, Jonathan},
biburl = {https://www.bibsonomy.org/bibtex/2ebd17512268f0ecb8c49ad5949773194/ji},
booktitle = {Proceedings of the SIGCHI Conference on Human Factors in Computing Systems},
description = {Why good engineers (sometimes) create bad interfaces},
doi = {10.1145/97243.97287},
interhash = {3cbc59309c7b2b7317e722f6b327aa62},
intrahash = {ebd17512268f0ecb8c49ad5949773194},
isbn = {0-201-50932-6},
keywords = {gui programmers},
location = {Seattle, Washington, USA},
numpages = {6},
pages = {277--282},
publisher = {ACM},
series = {CHI '90},
timestamp = {2015-01-08T14:49:02.000+0100},
title = {Why Good Engineers (Sometimes) Create Bad Interfaces},
url = {http://doi.acm.org/10.1145/97243.97287},
year = 1990
}