Jump to content
 







Main menu
   


Navigation  



Main page
Contents
Current events
Random article
About Wikipedia
Contact us
Donate
 




Contribute  



Help
Learn to edit
Community portal
Recent changes
Upload file
 








Search  

































Create account

Log in
 









Create account
 Log in
 




Pages for logged out editors learn more  



Contributions
Talk
 



















Contents

   



(Top)
 


1 References  














Use-centered design







Add links
 









Article
Talk
 

















Read
Edit
View history
 








Tools
   


Actions  



Read
Edit
View history
 




General  



What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Cite this page
Get shortened URL
Download QR code
Wikidata item
 




Print/export  



Download as PDF
Printable version
 
















Appearance
   

 






From Wikipedia, the free encyclopedia
 


Use-centered design is a design philosophy in which the focus is on the goals and tasks associated with skill performance in specific work or problem domains, in contrast to a user-centered design approach, where the focus is on the needs, wants, and limitations of the end user of the designed artifact.

Bennett and Flach (2011)[1] have drawn a contrast between dyadic and triadic approaches to the semiotics of display design. The classical 'user-centered' approach is based on a dyadic semiotic model where the focus is on the human-interface dyad. This approach frames 'meaning' as a process of interpreting the symbolic representation. That is, meaning is constructed from internal information processes. From this dyadic perspective, the design goal is to build interfaces that 'match' the users internal model (i.e., match user expectations).

In contrast, the 'use-centered' approach is based on a triadic semiotic model that includes the work domain (or ecology) as a third component of the semiotic system. In the triadic system, the work domain provides a ground for meaning outside of the human information processing system. In this, triadic semiotic system, the focus is on the match between the constraints in the work domain and the mental representations. From this 'use-centered' approach the goal is to design displays that 'shape' the internal mental representations so that they reflect validated models of the work domain. In other words, the goal is to shape user expectations to conform with the validated 'deep structure' of the work domain. In doing this, work analysis (e.g., Vicente 1999[2]) and multi-level means ends representations of work domain constraints (i.e., Rasmussen's Abstraction Hierarchy[3]) are the typical methods used to specify the 'deep structure' of a work domain. By building configural display representations that conform to this deep structure -- it is possible to facilitate skilled interactions between the human and the work domain.

Thus, an emphasis on 'use' rather than 'user' suggests a more problem-centered focus for interface design. Note that it remains important to respect the real limitations of human information processing systems through the use of graphical displays that support efficient chunking of information. However, the main point is that the organization MUST be consistent with the demands of the work or problem domain, if the interactions that result are expected to be skillful. In the end, the representations must be 'grounded' in the use-domain!

Charles Sanders Peirce is the inspiration for the triadic model of semiotics. Peirce was interested in the fixation of belief relative to pragmatic demands of everyday experiences. Peirce also introduced the construct of 'abduction' as an alternative to classical logic (deduction and induction). The 'use-centered' approach assumes abduction as the appropriate model for problem solving. Thus, use-centered design focuses on supporting the closed-loop dynamic of learning from experience. That is, by acting on hypotheses and simultaneously testing those hypotheses in terms of the practical consequences of the actions that they guide. The convergence, stability, and robustness of abduction processes depend critically on the information coupling between perception and action. When the coupling is rich an abduction system will typically converge on 'beliefs' that lead to pragmatically successful (i.e., satisfying) interactions (i.e., skilled interactions). This is the ultimate goal of use-centered design - to support skilled interactions between a person and a work domain.

The term use-centered design was first coined by Flach and Dominguez.[4]

References[edit]

  1. ^ Bennett, Kevin B.; Flach, John M. (2011), Display and Interface Design: Subtle Science and Exact Art, CRC Press, ISBN 978-1420064384.
  • ^ Vicente, Kim J. (1999), Cognitive Work Analysis: Toward Safe, Productive, and Healthy Computer-Based Work, Lawrence Erlbaum, ISBN 978-0805823974.
  • ^ Rasmussen, Jens (1986), Information Processing and Human-Machine Interaction: An Approach to Cognitive Engineering, North-Holland Series in System Science and Engineering, vol. 12, North-Holland, ISBN 978-0444009876.
  • ^ Flach, John M.; Dominguez, Cynthia O. (1995), "Use-centered design: Integrating the user, instrument, and goal", Ergonomics in Design, 3 (3): 19–24.

  • Retrieved from "https://en.wikipedia.org/w/index.php?title=Use-centered_design&oldid=1175819661"

    Categories: 
    Usability
    Ergonomics
    Hidden categories: 
    Articles with short description
    Short description matches Wikidata
    Articles needing additional references from December 2006
    All articles needing additional references
     



    This page was last edited on 17 September 2023, at 17:16 (UTC).

    Text is available under the Creative Commons Attribution-ShareAlike License 4.0; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.



    Privacy policy

    About Wikipedia

    Disclaimers

    Contact Wikipedia

    Code of Conduct

    Developers

    Statistics

    Cookie statement

    Mobile view



    Wikimedia Foundation
    Powered by MediaWiki