Error Messages and Lexical Properties

Error Messages and Lexical Properties

English4 min read

Error Messages and Lexical Properties

Introduction

Dialog design should be separated from the design of presentation details and lexical interface.

  1. Define system functionality first.
  2. Design dialog using cognitive models or task analysis.
  3. Design visual presentation and lexical interface (buttons/mouse ↔ abstract dialog actions).

Error Messages

Dialog design depends on presentation, not its details. Error messages and warnings are crucial, especially for beginners.

What to Avoid

  • "Blaming" tone (harsh sounds/messages).
  • Overly generic messages (e.g.,
    WHAT?
    ,
    SYNTAX ERROR
    ).
  • Hard-to-understand messages (e.g.,
    FAC RJCT 004004400400
    ).

Examples

Poor MessageBetter MessageDescription
SYNTAX ERROR
UNMATCHED LEFT PARENTHESIS
Specific syntax rule violation
ILLEGAL ENTRY
TYPE FIRST LETTER: Send, Read, or Drop
Clear instructions
INVALID DATA
DAYS RANGE FROM 1 TO 31
Explain data range
BAD FILE NAME
FILE NAMES MUST BEGIN WITH A LETTER
File naming rules
DISASTROUS STRING OVERFLOW, JOB ABANDONED
String space consumed. Revise program or expand
Concrete instructions
UNDEFINED LABELS
Define statement labels before use
Next step guidance
ILLEGAL STA. WRN.
RETURN statement cannot be used in FUNCTION
Subprogram explanation

Google Search marks errors with red (hints) and blue italics (correct text).

Types of Errors

  1. Mistakes Actions based on wrong decisions (e.g., dragging hard disk icon to recycle bin).

  2. Slips Unintentional errors:

    • Capture error: Habit-based (e.g., in
      vi
      , intending
      W
      → typing
      WQ
      ).
    • Description error: Clicking wrong object (e.g., clicking 'X' to close different application).
    • Data-driven error: Affected by surrounding window data.
    • Associative-activation error: Influenced by user memory.
    • Loss-of-activation error: Forgetting what was intended.
    • Mode error: Forgetting mode context (e.g., commands in edit space).

  3. Lapses Wrong actions based on wrong decisions (e.g., crop instead of resize).

Appropriate Physical Format

  • Combine uppercase & lowercase; ALL CAPS only for critical warnings.
  • Avoid code-only messages; if necessary, place codes at the end.
  • Position messages near the problem source (bottom of screen or pop-up window).
  • Warning sounds are useful but must be user-controllable.

Effective Message Design

Product Guidelines

  • Specific & precise
  • Constructive: show actions to take
  • Positive tone, don't blame
  • User-focused (use "you")
  • Consistent grammar, terminology, abbreviations
  • Consider layered messages
  • Use consistent visual format & placement

Process Guidelines

  1. Form a message quality team
  2. Include messages in design phase
  3. Store all messages in one file
  4. Discuss messages during development
  5. Reduce need for excessive messages
  6. Conduct acceptance testing
  7. Collect message frequency data
  8. Review & improve regularly

Non-Anthropomorphic Design

  • Avoid "I" for computer; use "you" or neutral words.
  • If displaying characters, use humans/animations appropriate to context.
  • Interface must be predictable & controllable.

Examples

  • Poor:
    I will begin the lesson when you press RETURN
  • Better:
    You can begin the lesson by pressing RETURN
  • Good:
    To begin the lesson, press RETURN

Display Design

  • Show data needed at each transaction stage.
  • Consistent format; short & positive sentences.
  • Labels near fields, with one space.
  • Headers above content, leave blank lines.
  • Alphabetical columns left-aligned.
  • Multi-screen pages: provide page labels.
  • Symbol sizes at least 1.5× height of next symbol.
  • Color for visual ease; blinking 2–5 Hz, duty ≥ 50%.
  • Show column headers & row labels when scrolling.
  • Provide ways to change display requirements as needs change.

Color

Functions

  • Attract attention, emphasize information, emotional reactions.

Guidelines

  • Use conservatively, limit number of colors.
  • Color as visual code, non-disruptive.
  • Color choices under user control.
  • Design monochrome first.
  • Ensure consistency & contrast.
  • Use color changes for status indication.
  • Be aware of color display resolution.

Summary

Effective error message and interface design requires careful consideration of user psychology, clear communication principles, and consistent visual presentation. The goal is to guide users toward successful task completion while maintaining a positive interaction experience.

Key principles include:

  • Clarity: Messages should be specific and actionable
  • Consistency: Maintain uniform terminology and formatting
  • User-centered: Focus on user needs rather than system constraints
  • Progressive: Provide appropriate detail levels for different user types
  • Accessible: Consider visual design elements like color and contrast

By following these guidelines, interfaces become more usable and user-friendly, reducing frustration and improving overall user experience.