Back to all writing

Design the default path

Most people follow the route a product makes easiest. That makes defaults one of its most consequential design decisions.

BY TIAGO BALABUCH
A branching interface path with one clear highlighted route.

Every interface has a default path: what happens when someone opens a page, presses Enter, or keeps using the settings already in place.

Defaults are quiet. They do not ask for attention, and that is exactly why they matter. A confusing default makes every new user do extra work. A thoughtful one lets people get to the point.

Reduce the number of decisions

An interface can offer many choices and still feel simple if the common task is clear. The goal is not to remove control; it is to avoid demanding a decision before that decision is useful.

For a writing tool, a sensible default might be:

  1. Open the most recent draft.
  2. Keep the editing area focused.
  3. Make save status visible.
  4. Leave advanced options available but out of the way.

People who need a different workflow can change it. Everyone else can begin writing.

Defaults include more than settings

They also include language, contrast, focus order, and motion. If a page uses animation, respecting a reader’s reduced-motion preference is a default. If a button is the obvious next step, keyboard users should be able to reach and activate it too.

Good defaults do not predict every preference. They provide a considerate starting point, and make it easy to choose something else.

This sample post demonstrates headings, lists, and topic filtering in the archive.

Share this post