Evidence-based design for discoverability: A case study.

Saved in:
Bibliographic Details
Title: Evidence-based design for discoverability: A case study.
Authors: Fallas, Andrea1 andrea.fallas@semantico.com, Tatham, Suzanne2
Source: Learned Publishing. Jan2017, Vol. 30 Issue 1, p55-64. 10p.
Subjects: Library browsing, Database searching, Library automation, Computers in libraries, Academic libraries, University of Sussex, User-centered system design
Abstract: Key pointsLean methods can give rich insights: Even a few, short sessions with a handful of users can generate useful inputs for a user ‐ centric design process.Design for beginners: An interface that supports novices will also support experts.Keep it simple: Focus on functionality that supports core search and discovery tasks.Popular or high ‐ value features should have prime position and rarely used or low ‐ value features should be hidden or removed.Visual cues are important for usability, as is balancing the visual space. [ABSTRACT FROM AUTHOR]
Copyright of Learned Publishing is the property of Wiley-Blackwell and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)
Database: Engineering Source
Full text is not displayed to guests.
Description
Abstract:Key pointsLean methods can give rich insights: Even a few, short sessions with a handful of users can generate useful inputs for a user ‐ centric design process.Design for beginners: An interface that supports novices will also support experts.Keep it simple: Focus on functionality that supports core search and discovery tasks.Popular or high ‐ value features should have prime position and rarely used or low ‐ value features should be hidden or removed.Visual cues are important for usability, as is balancing the visual space. [ABSTRACT FROM AUTHOR]
ISSN:09531513
DOI:10.1002/leap.1075