The Nine States of Design

A 2015 post on the nine states of design, resurfaced, makes the case for thinking through edge cases while building interfaces. The piece is by Vince Speelman, and its central point is that modern UI teams design components first, with interfaces as the thoughtful composition of components. That approach leaves a gap for users on "the unhappy path" — the places where users may, intentionally or not, stray from the idealized flow.

Speelman argues that as teams learn to craft systems rather than pages, they must put effort into shaping these often-missed states and build a component lifecycle that supports everyone. The lifecycle, as he describes it:

  1. Nothing state
  2. Loading
  3. None
  4. One
  5. Some
  6. Too many
  7. Incorrect
  8. Correct
  9. Done

The post's own commentary adds that during the design process, everyone (the author included) tends to focus on the ideal state of a component or interface, leaving important edge cases forgotten until the last moment. Hence the resolution to stick the list to the screen so it isn't forgotten on the next project.

Direct Link →