Items related to the same task should be placed in close proximity. Based on Gestalts proximity principle, items tend to be perceived to be one unified group in they are put close together. The end user might not miss any option or any sub-task and might save their time to purchase the tickets if items related to the same task are placed close together.
The three section containing information about the three main tasks should be of the uniform shape. Based on Gestalts proximity principle, to help people know what distinct objects might be a single unit, then their shapes should be similar. The main interface can be divided into three parts with the same shape but possible different sizes depending the objects needed to be displayed in each section to help the end user know that which task each object or information belongs to.
Information display should be minimal. According to Miller (1956), our working memory is capable of holding only about seven items or elements of information at a time and deal with two or three items of information simultaneously. Too much information display like the current interface can lead to information overload which can leave the end user confused and/or unable to make a decision. The new interface, therefore, should keep no more than seven items of information and for each task and/or sub-task, the end user has to process no more than three items of information at the same time.
Information needed for the purchase performance should appear in a natural and logical order. According to Nielsen (1995), to make a system intuitive to use for the end user, the procedure to complete a task in the system should appear in the order which people might assume it should be.
Error prevention should be integrated. According to Nielsen (1995), a well-designed system should have error prevention system to prevent the end user to make a wrong decision. In this case, the system should let the user who wishes to use the ticket only one time to insert the starting point and the destination of the trip and calculate the fare they have to pay for them. If the end user inserted more value or insufficient value for their fare, the system should send messages to let the end user know if they commit to the action.
The end user should have freedom and control over the system. According to Nielsen (1995), a well-designed interface should let the user have choices over their action. In this case, the system interface should let the end user choose if they want to buy one-time use ticket or multiple trip tickets. If the end user chooses one-time use ticket, the system should let the end user choose the starting point and the destination of their trip and automatically calculate the fare for them.
