...
Rob looks over the bills for the "MyHouse" household. Alice, one of his suitemates, has already entered a couple of the bills for the household, and Rob decides to check over them. The bills are ordered by due date, and also show the amount of the bill, as well as whether or not payment has been made. Rob clicks the "+" next to the water bill he recently created, expanding the listing and giving details. He sees that Alice has already paid her share, and decides to do the same.
He clicks the "Pay Now" button next to the $20 dollars that he owes for the water bill, which takes him to a Confirm Payment Page. He sees the name of the bill, the amount, his username, and the last four digits of his credit card number. Everything looks correct, so Rob clicks the "Confirm" button to submit his payment.
Once back at his User Page, Rob clicks the tab to go into Calendar View, which shows him all of his bills laid out by date. He sees that his next bill is not due for a while, and decides that he is ready to log out of Housebill.
Analysis 2
Learnability
A frequent user will be used to navigating only the left column of the site, which is where all of the login fields are located. Buttons that allow users to perform actions on a bill (edit, pay, etc.) are clearly labeled and placed next to the listing for that bill. Links to other main pages on the site are displayed prominently in the taskbar at the top of the user page. This lets users access the bills, user, and calendar views. A new user will be able to understand the overall structure, although some functions need to be better grouped. For instance, the Household display in the lower left hand column could use some "change" or "add new" buttons so that the user does not need to search for the Household View in the main User Page to make these types of edits.
Visibility
Information about users and frequently accessed households is visible in the left sidebar. The other pages the user can view (user details, calendar, etc.) are listed in the taskbar at the top of the page. On the pages that list bills and show how much money the user owes, lines of data can be expanded to show further details, but by default they are collapsed to maintain visual simplicity. Clickable links are underlined; the user's current page is highlighted in the taskbar. Any information that needs to be entered has an associated text field, which provides the appropriate affordances. However, some of the pages contain too much information, which could be a hindrance to the user. The User Page faces this issue.
Efficiency
There is a bit of redundancy, which users may find confusing. For example, the User column on the left displays information that is simultaneously displayed on the middle of the User Page. This real estate may be used for other means so that the information in not doubly presented. Users can find a bill from the user page, the bill listing page, or the calendar. This makes is easier for the user to find a piece of information, but the information scent used to get to it may need more fine-tuning.
Error Prevention
Not great. Does This design does not allow the user to undo transactions, although before a transaction goes through the user must review a confirmation page. In addition, information tends to be clustered together, so mis-clicks could be an issue. To deal with this, it would be a good idea to place less information on a screen.
Design 3
Storyboard 3
Analysis 3
...