Pattern Language Analysis for Interaction Design

Description

Analyses recurring design problems as patterns with context, forces, solution and known uses, distinguishing universal problems from product-specific ones to guide design system decisions.

Alexander defined a pattern as a recurring problem in a context, the forces that make it hard, and a solution that resolves those forces, linked into a language of patterns at different scales. Tidwell and Borchers adapted this to interaction design. As a research method, pattern analysis studies many products or many screens of one product to identify recurring problems and their solutions, documents the forces (competing user needs and constraints) behind each, and records known uses and evidence of effectiveness. This distinguishes universal problems with established solutions from genuinely product-specific ones, and exposes where a pattern is used without its forces holding. Today 'patterns' usually means component libraries, losing the problem, context and forces that made Alexander's formulation analytical.

Attributes

Loss type
Vestigial
Stage
Design
Effort
Days

Steps

  1. For any usability problem: formulate it as a pattern:
  2. Context — what situations does this problem arise in?
  3. (2) Problem — what competing forces create this problem?
  4. (3) Solution — what design arrangement resolves the forces?
  5. (4) Consequences — what does the solution compromise? Compare: is this problem-solution pair documented in Tidwell's pattern catalog? If yes: use the established solution. If no: document it as a new pattern for future reference.

Sources

  • Designing Interfaces — Jenifer Tidwell
  • A Pattern Language (Christopher Alexander)
  • A Pattern Approach to Interaction Design (Jan Borchers)

Also known as

  • Interaction pattern analysis
  • Pattern mining
  • Design pattern audit

Categories

  • Content
  • Information Architecture & Content