Built-in risk
The risks some components carry even when you use them well
Some components carry a risk even when they are the right choice. Warning text is the right way to flag a risk, but every warning a user sees makes the next one easier to ignore. Knowing the risk means you can still use the right component, and design around what can go wrong.
This page is about risks that come with a component. For problems that come from using the wrong one, see common mismatches.
Risks that can do the most harm
A user caught by one of these may act on the wrong person, agree to something they have not read, or miss a real risk. These are hard to put right.
Acting on the wrong person
- Components
- Quick reference
- What can happen
- Every action on the page lands on the person it shows. If it is the wrong record, everything the user does affects the wrong person. Users often miss a change like this, which is known as change blindness.
- What helps
- A clear main reference, with only the details the task needs, helps the user spot the wrong record.
Agreeing without reading
- Components
- Make a declaration
- What can happen
- Users want to get the task done, so they skip the words and agree. This is known as the paradox of the active user.
- What helps
- A short declaration that is specific to the task. Keeping it separate from confirming understanding means users know which one they are agreeing to.
Warning fatigue
- Components
- Warning text, interruption pages
- What can happen
- Each warning makes the next one easier to ignore. Warnings stand out because they are different, which is known as the Von Restorff effect. When there are lots of them, none of them are different.
- What helps
- Warnings work best when they are kept for real risks.
Risks that cost time or attention
These are easier to put right, but they still slow users down or make them miss things.
Banner blindness
- Components
- Notification banner (important)
- What can happen
- Users scroll past banners, especially ones they see often, because they filter out what does not look relevant to their task. See selective attention.
- What helps
- Banners work when something has changed that affects the user.
Thinking they are done
- Components
- Panel
- What can happen
- Users stop reading at the panel, and miss anything that comes after it.
- What helps
- A panel works when the user has nothing else to do. If there is more to do, say so straight after it.
Missing hidden content
Skimming past context
- Components
- Inset text
- What can happen
- Users read past it, even when it holds something useful.
- What helps
- These work for content the user does not need to act on.
Components with little built-in risk
Notification banner (success), tag and timeline answer a question the user already has, and they do not ask the user to do anything. Used for the right content, there is little that can go wrong.
With these, the risk comes from the content, such as a tag that is out of date or a timeline with a heading that does not match its events. See common mismatches.
Where this comes from
These groups are a judgement call, based on what we have seen. If your research shows something different, tell us.
Something missing or does not belong here?
Tell us what you have found when choosing components, or anything this guidance does not cover. Let us know.