Guidelines for Guidelines

In addition to establishing goals, it's also a good idea to establish guidelines for the user interface style guidelines themselves. Here are some issues to consider:

• Try to avoid repeating what is in the standards The goal isn't to replace Designing for the User Experience but to supplement it. However, some redundancy is acceptable, especially when a guideline is easily overlooked or often violated. It's also acceptable to have some redundancy for completeness or convenience. For example, if you have five guidelines for menus but one of the guidelines is in Designing for the User Experience, you should probably include it anyway to make the guidelines easier to use. You should also cross-reference other documents as needed.

TIP

---

User interface style guidelines supplement, not replace, the standards.

• Try to avoid arbitrary guidelines If a guideline appears arbitrary but has a good rationale, include the rationale in the guideline. For example, rather than saying something like "Don't use yellow," say "Avoid using bright yellow as a foreground color, since it is a distracting color and is often difficult to distinguish on white backgrounds." On the other hand, if a guideline really is arbitrary, don't include it. A weak rationale is a sure sign that a guideline is bad. To be effective, user interface guidelines need support from all developers, and developers will resist guidelines that don't make any sense.

TIP

---

When appropriate, include the rationale in a guideline.