Standards

Creating a standard or guideline helps you to create user interfaces that are consistent and easy to understand. UI standards are very effective for when you are developing, testing, or designing any new site or application or when you are revising over 80 percent of the pages in an existing application or site.

A UI Standard is not just a document. It is a customized process that incorporates your needs and goals into the process and allows you to adapt and extend your UI guidelines and standards over time.

Benefits

• less time spent evaluating design alternatives
• more time for value-added function-specific design work
• share system modules more easily
• reduced cost and effort for system maintenance
• reduced costs for support, user training packages and job aids
• your user or customers see a consistent UI within and between applications
• your users or customers will reduce...
  • time per transaction
  • errors
  • training requirements
  • frustration

Activities

Major activities in the our process:

1. Project Kickoff and planning
2. Gather UI Samples
3. Develop UI Document
4. Review with Team
5. Present Standard

1. Project Kickoff and Planning

BWe collaborate with key members of the project team to define the goals and scope of the UI standards. This includes whether the UI document is to be considered a guideline, standard or style guide, which UI technology it will be based on, and who should participate in its development. We work closely with your team and other stakeholders to identify your key business needs and business flows.

2. Gather UI Samples

Based on the information and direction received from your team, we begin by reviewing your major business applications and extracting examples for the UI standard. These examples are put together in a draft standard which is used as a discussion point with your team and other stakeholders. This is an iterative process that takes feedback from as wide an audience as is appropriate.

3. Develop UI Standard Document

The document itself includes...

• How to change and update the document
• Common UI elements and when to use them
• Common business flows and how and when to use them
• General navigation
• Graphic Look & Feel (or style)
• Error Handling
• Messages

4. Review with Team

The UI standard is put together in a draft which is used as a discussion point with your team and other stakeholders. This is an iterative process that takes feedback from as wide an audience as is appropriate. The standard is reviewed and refined with your team and stakeholders in a consensus building process.

5. Present UI Document

We present the UI Document in electronic form and/or paper form.

> back