053Pattern

Visible Lifeboats

The presence of a feature can be reassuring, even if the user doesn't use it.

Why it matters

Occasionally you'll want to over-promote a feature that has very low usage, but reassures the user that it exists if they ever do need it.

i.e., the expected utility is low, but the presence is still reassuring.

Imagine a cruise ship, with lifeboats hanging off the side.

Presumably, they could design lifeboats that nestled discreetly into the ship. But their visibility serves another purpose: to reassure the passengers that they exist, and are ready to go .

Because their usage is actually very rare, the majority of the collective benefit will be psychological, rather than objective.

What to inspect

  • Map each visible element to how it supports or undermines: The presence of a feature can be reassuring, even if the user doesn't use it.
  • Walk the primary task once with time pressure; note where attention drops.
  • Ask a colleague unfamiliar with the product to paraphrase the screen in one sentence.

Common anti-patterns

  • Assuming users consciously notice every place where "The presence of a feature can be reassuring, even if the user doesn't use it" could apply.
  • Dense copy and parallel actions that increase mental effort unrelated to the user’s goal.
  • Ignoring downstream effects on feature usage when shipping this pattern.

Critique prompts

  • Where on this screen would "Visible Lifeboats" show up as friction or misunderstanding?
  • What would a first-time user misunderstand here in under five seconds?