OSF/Motif style guide: revision 1.0
OSF/Motif style guide: revision 1.0
The construction of human-computer interfaces considered as a craft
Taking software design seriously
Cultivated eclecticism as the normative approach to design
Taking software design seriously
Information architecture and the design process
Taking software design seriously
Taking design seriously: exploring techniques useful in HCI design
ACM SIGCHI Bulletin
interactions
Who's to say?: essential elements of HCI education
ACM SIGCHI Bulletin
Practical education for improving software usability
CHI '95 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
KidPad: a design collaboration between children, technologists, and educators
Proceedings of the ACM SIGCHI Conference on Human factors in computing systems
Empowering software engineers in human-centered design
Proceedings of the 25th International Conference on Software Engineering
Training software developers in usability engineering: a literature review
Proceedings of the 6th Nordic Conference on Human-Computer Interaction: Extending Boundaries
Hi-index | 0.01 |
User-centered design (UCD) of human-computer interfaces--including task flow and documentation---is gaining acceptance in software development organizations. But managers who want their organizations to start using UCD often do not know what characteristics to look for, in candidates for hiring or retraining to fill UCD roles; this article can help. It has the recommendations from participants in a CHI '92 conference workshop on this topic. The 16 workshop participants were UCD practitioners and managers from companies and a few universities across the United States, Canada, and Sweden. This article first describes some typical roles of UCD practitioners in software development organizations. There follows a list of attributes that UCD practitioners should have. Some attributes should be had by all practitioners, regardless of their subspecialties. The most important of those universal attributes are of three types: knowledge that can be acquired formally (e.g., of the human-computer interaction literature, cognitive processes, experimental design, rapid prototyping), skill that can be gotten from experience (e.g., estimating resources needed to do a job, commitment to users, understanding of the software development process, negotiating ability, enjoyment of working on teams, ability to really listen), and attributes that are harder to acquire (e.g., tenacity, flexibility). Every practitioner needs other characteristics as well, but their importances differ by the practitioners' subspecialties (e.g., a design team leader needs team management skills).