Main View Sample 1 |
|---|
 | Observation 1: Lack of any "call to action" is the main problem with this view because it violates the recognition rather than recall heuristic. This screen shows a navigation tool (tree) but with an empty content area. Most applications, online or otherwise, will present some form of content, even at the root view, because users are content oriented rather than navigation oriented.
Recommendation 1: If no meaningful content is available or appropriate, often times navigation will simply be repeated in some subtly different way in the content area. Since most users are accustom to navigating content anyway, thanks to Google and Yahoo, this approach presents the user with a meaningful "call to action" in a central part of the screen. |
----Observation 2: Another violation has to do with consistency and standards. While arrows have some conventionality to them, folders have more. Also, folders might be more appropriate since they are used in other uPortal UI's and in general are more meaningful in communicating categories.
Recommendation 2: Swap arrows for a more conventional folder icon in the tree. ----Observation 3: The search tool appears to be unnecessarily complicated and therefore violates the Aesthetic and minimalist design principle. The secondary selector option that specifies "whose name - contains, etc..." can likely be handled transparently by the system.
Recommendation 3: Lose that selector option. Perhaps lose the main selector (channel, group, person, etc.) also. ---- Observation 4: The search tool saves the in the tree, but does not display any metatdata describing what the search was for. This violates the recognition rather than recallprinciple.
Recommendation 4: Display the term which was searched for in the label. E.g. "Search for 'weather'. ----Observation 5: The search also saves all the user's searches in a session which, if not frequently referred to, violates the Aesthetic and minimalist design principle.Recommendation 5: Perform user research to determine how frequently search results are used again. If not used at all, remove from the interface. If used infrequently, move to another page and include a link from this page. If used frequently, separate them in some fashion so they don't appear to be part of the same tree as other unrelated items. ----Observation 6: Displaying the search results in the same tree as the categories also violates the Match between the system and the real world principle. It may even be confusing to group the portlet categories and the user types together in the same tree.
Recommendation 6: Separate the different types of items currently in the tree in some fashion, perhaps by using tabs so they are differentiated visually from the other only indirectly related items. Again, user research should be performed to determine whether users actually need to see the different types of items at once -- if so, it may be best not to use tabs so they remain on the same page.
---- | Error Sample 1 |
|---|
 | Observation 1: Poorly written and presented error messages fail to help users recognize, diagnose, and recover from errors .
Recommendation 1: Analyze all error messages and write them in a language that users (including but not limited to administrators) will understand. |
----Observation 2: Because the text in the error message is so small and uses no visual qeues to help it stand out, it violates the Visibility of system status principle.
Recommendation 2: Explore ways to emphasize the error message. | Bad Language Sample 1 |
|---|
 | Observation 1: There is no match between system and the real world in the language used here. Overall it's very confusing.
Recommendation 1: Re-word to something similar to "Search only within current selection." |
|