No Summary Overview

You are allowed (or required) to work with a broad range of attributes but are given no concise overview.

You have to scroll through a looooong page in order to find out what's there.

There are no references, no clues and no context.

Redundancy

There are several versions of the same feature.

• They all looked similar
• They all performed variations on the same function
• But they each had different titles.
  

Inconsistency

You see the "same" page at different places in the service - under a different name - but it operates differently in each case.

Action buttons have different names and appear in different positions from page to page.

Terminology varies across the site.

Maintain consistent terminology between control label (buttons & hyperlinks) and the title of the page it invokes. The labels on buttons and hyperlinks are often contradictory, redundant, inconsistent and confusing.

Scale/Scope

Some choices have literally hundreds of items to choose from. But there were no filtering tools to assist in making the choice.

Extraneousness

The navigation structure imposes unproductive pages and extra mouseclicks on vital processes.

Incompatibility

The legacy site maintains totally different - yet functionally incompatible - versions of a feature. This meant that you could perform certain functions on one, but not on the other.

• different management tools
• totally different behavior
• totally different page layout & design

Poor Layout

Many of the pages in the legacy site are simply badly designed. Some of the most common offenses:

• Excessive white space in the upper regions of the page wastes valuable presentation area
• The focal information area is crammed to the bottom and overflows the page boundaries
• Disjointed layout of data boxes
• Distracting use of color (colorful boxes draw attention away from the focal table of information)
• Inappropriate use of color emphasizes information that is not really important
  

Obscurity

There is often no way to tell what to do next - or where relevant tools / information / assistance might be.

Context Issues

Reduce the visual dominance of the menu areas relative to content area. My focus should be on the content materials.

Break the items in the Navigation menu into sensible and manageable groups. These do not need to be labeled, but should be at the very least separated.

The organizational context of the selected document is lost. When you click on a document within a MegaProcess, the Navigation menu sidebar reference item changes to "Index".

Every page should have a title that confirms what it is.

Every page should have visual "design clues" that let you know where you are. Employ appropriate shortcuts.