Fuzzy Context

01 / UNDERSTAND

The idea

Mentioning an unfamiliar requirement without enough explanation can create questions that interrupt a task. Give people the context needed to interpret the information when it appears. A teaser is a poor substitute for useful guidance.

A partial explanation may raise questions that it does not answer. Mentioning an identity check long before explaining its purpose, for example, can create uncertainty rather than reassurance. Replace vague progress, errors and requirements with the specific context needed at that moment. Where details are uncertain, explain how they will become known.

02 / RECOGNISE

See it in real products.

Examples of how the principle can appear in an interface.

WeBullEXAMPLE 01

Replace vague remaining effort with useful information

WeBull’s exit flow provides context about the work remaining. The design illustrates why a meaningful estimate is more useful than an undefined promise that completion is near.

View detail

FramerEXAMPLE 02

Explain where the missing content went

Framer identifies when content is outside the current view and offers a Show action. The message names the problem and provides a direct way to resolve it.

View detail

04 / APPLY

Put it into practice.

1. 01

   Identify likely follow-up questions

2. 02

   Answer material questions near the message

3. 03

   Use concrete next steps

CONNECT THE IDEAS

Related principles

Context Craving

Sometimes understanding matters more than speed.

Specificity

Concrete language makes consequences easier to predict.

Knowledge Gap

Teach the missing knowledge at the point of need.