| NIELSEN'S HEURISTICS |
SEVERITY |
H1 SIMPLE & NATURAL
DIALOG
|
| Scenario 1: The date search options
are overwhelming. Start with a simple text search. Allow
users to click on column titles and have them sort. Include
an arrow icon next to the title indicating if the sort is
ascending or descending. If user’s want advanced search
functionality, such as the date options being initially presented,
include a link to an Advanced Search area. |
Severity 2
|
| Scenario 2: Having all the Add Event
sections presented initially is overwhelming. Consider minimizing
them, so they take up less space until the user needs a section
and expands it. Or place the sections in a wizard. Allow
the user to navigation through the steps using a drop down
menu. Then they could click directly to the steps they need
and skip ones that are not needed. |
Severity 4
|
| Scenario 2: Seeing the word “Calendar” twice
in the navigation might cause confusion (Calendar, Format
Calendar). The Calendar link should remain. Then, once in
the Calendar window, there should be a link to Format Calendar.
Placing the Format Calendar link as a sub-task of Calendar
would help to put the functionality into context. |
Severity 3
|
| Scenario 3: If the only option in
the Search drop down is Keyword, than a drop down is not
necessary. |
Severity 2
|
| Scenario 4: The steps should be reordered
to reflect the way users will probably think about events.
Most likely they will identify the sponsor first. Then they
will identify specific keywords. Essentially keywords are
a subset of the sponsor’s events and consequently should
come secondary. |
Severity 2
|
H2 SPEAK
USER'S LANGUAGE
|
| Scenario 1: Source is too close in meaning to Sponsor.
User’s may find it confusing. A different word should
be used to identify the Origin or Status of the event. Note:
Severity level reflects assumption that some testing was
performed and UI reflects feedback |
Severity 2
|
| Scenario 1: View and clicking on the event’s name
are similar actions. View should be eliminated. Note: Severity
level reflects assumption that some testing was performed
and UI reflects feedback |
Severity 2
|
Scenario 2: Meaning of “Link Sponsor's Name To” is
unclear
|
Severity 3
|
| Scenario 3: Subscribe implies the page would be focused
on subscribing to events. Instead the screen appears to contain
information about current subscriptions as well as functionality
to subscribe to new events. Having these features near each
other is useful, but there should be a clearer distinction
on the screen. |
Severity 1
|
| Scenario 3: The labels in Step 2: Select Options are confusing.
Specifically - “I want to receive events that occur
X weeks ahead or less.” Ahead of what? “2 Weeks
Expiration Date (optional):” expire from where? |
Severity 4
|
H3 MINIMIZE
USER'S MEMORY LOAD
|
| Scenario 1: As UCB is in PST, I’m guessing the events
are PST. But it would be useful to include such information
as visitors to the calendars / web sites may be from out
of town. |
Severity 1
|
| Scenario 1: There isn’t any indication what “today” is.
As this is a “calendar” application, today’s
date should be prominently reflected. Also if I had just
returned from holiday, having today’s date visible
would put the age of the pending events into context. |
Severity 3
|
| Scenario 2: There isn’t any indication of which color
is currently selected. The current color should be highlighted
in some manner. |
Severity 3
|
H4 CONSISTENCY
|
| Scenario 1: The Post and Delete buttons were at the top
of the screen on the Pending window and in yellow. After
clicking through the Guidant Information Meeting title, they
are on the bottom of the window and in blue. The location
and color should be consistent. |
Severity 2
|
| Scenario 1: Most websites where users have to locate information
contained in potentially long lists contain a text oriented
search box. User’s will expect this functionality.
It should be included on the Posted tab. |
Severity 2
|
| Scenario 1: The word “Owner” is used in the
Search drop down whereas the word Sponsor is used as a column
heading. |
Severity 3
|
| Scenario 2: The inclusion of two Location sections with
different fields for data entry is very confusing. The sections
should be labeled different or combined in a simpler manner. |
Severity 3
|
| Scenario 2: The “post event” confirmation screen
should be consistent with the one used in Scenario 1. |
Severity 2
|
H5 FEEDBACK
|
| Scenario 1: There isn’t any indication what “today” is.
As this is a “calendar” application, today’s
date should be prominently reflected. Also if I had just
returned from holiday, having today’s date visible
would put the age of the pending events into context. |
Severity 3
|
| Scenario 1: Headings should be provided to indicate the
various aspects of an event. For example after clicking through
the Guidant Information Meeting title, there should have
been labels for Date, Time, Title, Event Type, and Location.
The source of the event – including name and email
address should be provided. Users will also want to know
if there is a cost. |
Severity 3
|
| Scenario 2: Which, if any, fields are required? Most likely
some fields are required. If not, bogus data will be entered
into the system. [Note Scenario 3 – Select Options
includes an “Optional” indicator. So are all
fields without this Optional indicator required?] |
Severity 4
|
| Scenario 2: Having real text included in the Format Calendar – Calendar
Event preview might confuse users. The preview should be
clearly identified as an example. |
Severity 3
|
H6 CLEARLY
MARKED EXITS
|
| Scenario 1: There doesn’t appear to be
a place where “deleted” events go. This implies
once they are deleted they are eliminated from the event
calendar. What happens if a mistake is made? How can you
get the event back? |
Severity 3
|
H7 SHORTCUTS
|
| Scenario 2: Having two Location sections is confusing.
Only one should be presented initially. If users want to
enter in more Location details, the appropriate fields should
be presented after a user indicates more location details
are available. |
Severity 2
|
| Scenario 2: It would be helpful to have a “Clone” option.
If there are two events which share most of the same details,
the user should not have to reenter the information twice.
S/he should be able to copy the details from the first event
s/he entered. |
Severity 4
|
| Scenario 2: There doesn’t appear to be a way to indicate
or set-up a repeating event. Having this functionality would
eliminate the user from having to enter the same details
multiple times. |
Severity 4
|
H9 PREVENT
ERRORS
|
| Scenario 1: Include a dialog stating “Forgot your
password? Click here” |
Severity 2
|
H10 HELP & DOCUMENTATION
|
| Scenario 2: Context sensitive help would be useful next
to the Event Type drop down. Users may not know how to classify
an event. Even thought a Help link exists, it seems very
far away when one is working in a specific screen |
Severity 1
|
