blog




  • Essay / Sequential and Simultaneous Linear Menus - 2018

    The user's cognitive construction of a task illustrates a set of probabilities as to what the outcome will be as well as what will lead to the outcome. With this in mind, we can see that the structure or layout of menus tends to focus on the cognitive construct of the user. Take for example, when a person goes to the grocery store and while checking out and paying for the purchased item, the person will either pay by cash or use a credit or debit card. Once the person decides to pay with the credit or debit card, after swiping the card, in most cases the machine will ask whether the person will pay by debit or credit. Additionally, if the person decides to pay by debit, the machine will ask them whether or not they want cash back. The same can be said of an ATM. When using an ATM, the machine often asks if the person wants to make a deposit, withdrawal or checking account and many more. With this we can say that the menus are structured in such a way that the flow gives the individual or user a task to achieve their goal or objective. We can understand why it is essential that the user be able to recognize the types of menu layouts and the logic in which the menus flow. 2.0 Menu Selection Many researchers have anticipated theories about the different approaches that people around the world use when they want to locate an entry in an unordered list of options. Norman and Vandierendonck recommended that people could only process one menu at a time. This idea or recommendation that people can only process one item at a time could be related to the sequential linear menu. However, they did not empirically authenticate the low-level hypothesis. Card SK, the author of "Visual Search for Computer Control Menus" proposed that people randomly choose which item is in the middle of the paper......see that for most, the layout of the Simultaneous menus eclipse sequential linear menu designs. However, the choices we can make in choosing what type of design should be based on what you would like to see and have your end users do on a daily or weekly basis. This should be based on the type of task and the desired outcome. For example, if you expect the user to be able to make multiple selections from two or more menus, it would be wise to use concurrent menu designs to improve performance. Additionally, if on the other hand you want your target audience to only use or make one choice at a time, sequential linear menus would be a good deal. Let's say for some reason you want your menu design to be used for survey activities, concurrency would be a good choice in this situation because it provides a continuous flow of summaries..