Exploring user preference for the dashboard menu design

Aaron Read, Alvin Tarrell, Ann Fruhling

Research output: Chapter in Book/Report/Conference proceedingConference contribution

10 Scopus citations

Abstract

User interfaces generally rely on a main menu for navigation and orientation. Therefore, the main (navigational) menu layout design is a determinant of user performance and satisfaction levels. Effective menu designs also help users avoid feeling lost and disoriented when seeking information or finding functionality. Research on menu design finds that an understanding of users' ability to recognize a menu layout through positional and semantic grouping of menu items helps explain design effectiveness and user preference. Our research compares an expandable index menu layout design to a frame-based (dashboard) design, and finds that the positional and semantic groupings of the frame-based (dashboard) design were preferred. Real clients using a live system participated in this study using the Think Aloud usability evaluation method. This research is significant in that it contributes to ongoing work in development of effective user interfaces, and in that it strengthens the findings of earlier researchers.

Original languageEnglish (US)
Title of host publicationProceedings of the 42nd Annual Hawaii International Conference on System Sciences, HICSS
DOIs
StatePublished - 2009
Event42nd Annual Hawaii International Conference on System Sciences, HICSS - Waikoloa, HI, United States
Duration: Jan 5 2009Jan 9 2009

Publication series

NameProceedings of the 42nd Annual Hawaii International Conference on System Sciences, HICSS

Conference

Conference42nd Annual Hawaii International Conference on System Sciences, HICSS
Country/TerritoryUnited States
CityWaikoloa, HI
Period1/5/091/9/09

ASJC Scopus subject areas

  • Computer Science Applications
  • Information Systems

Fingerprint

Dive into the research topics of 'Exploring user preference for the dashboard menu design'. Together they form a unique fingerprint.

Cite this