Why component choice matters
Choose components for what they mean to users, not how they look

Components work the same way. Users work out what a component means before they read the words in it. When the component and the words agree, users understand straight away. When they do not, the component can tell users something untrue, however well it fits the page.
What users think when they see a component
-
Warning text
Example:Warning Your payments could stop if you do not send your documents by 15 June.A user thinks: “There's a risk here I need to act on.”
-
Panel
Example:Application complete
Your reference number
HDJ2123FA user thinks: “That’s it, I’m done. I can close the page.”
-
Inset text
Example:It usually takes up to 6 weeks to get a decision.A user thinks: “That’s useful to know. There’s nothing I need to do.”
5 steps to choose a component
-
Turn the data into information
Decide what the user needs to know before you choose anything. A caseworker needs a total and a payment date, not every part of an award.
-
Name what the user is doing
Describe the moment from the user's side, such as "taking a risky action", not what the page shows.
-
Pick a component and check what it means
Start with the component you think fits, then check that your content backs up what it means. Warning text means "there's a risk to act on", so the content inside it needs to be a risk the user can do something about.
-
Ask what happens if the user misses it
What is at stake is minor, moderate or serious, depending on whether the user can put it right. Count harm to other people too, such as the claimant a caseworker is acting for.
-
Check how much attention it draws
The more that is at stake, the more attention the content needs. Users learn to ignore components that always stand out, and miss content that is too quiet.
A worked example
A caseworker is about to decide on a change to someone's award. Before they do, they need to see the estimated new award.
Hypothesis: A component that gives context without raising an alarm will help caseworkers weigh up an estimate
Based on our understanding, caseworkers need to see an estimated new award before they decide on a change. They need the estimate, not every figure behind it. We believe this is because the estimate is context for their decision, not something to act on. If they miss it, they may have to go back and change their decision, which costs them time. So if we show the estimate in a component that gives context and sits in the flow… We'll see caseworkers take the estimate into account, without stopping to check whether something has gone wrong.
Here is the example worked through the 5 steps.
- Turn the data into information
- Show the estimate, not every figure behind it.
- Name what the user is doing
- Weighting up context before making a decision.
- Pick a component and check what it means
- The estimate is context, not a risk or news. The component needs to mean the same.
- Ask what happens if the user misses it
- Moderate. They may have to go back and change their decision, which costs time.
- Check how much attention it draws
- At least “sits in the flow”, because the stakes are moderate.
The estimate in 3 components
-
Warning text
Example:Warning Estimated new award: £182.60 a week from 3 MarchThe caseworker thinks: “Is something wrong with this award? I’d better stop and check.”
Warning text means there is a risk to act on. The estimate carries no risk, so the content does not back it up.
-
Notification banner (important)
Example:The caseworker thinks: “Has something changed on this case? When did that happen?”
An important banner means something has changed. An estimate is not a change, so the content does not back it up.
-
Inset text
Example:Estimated new award: £182.60 a week from 3 MarchThe caseworker thinks: “That’s the estimate. I’ll weigh it up before I decide.”
Inset text means this is context to weigh. The estimate is exactly that, so the content backs it up. It sits in the flow, which is enough when the stakes are moderate.
All 3 show the same words, but only inset text means what the content says. It draws enough attention for something the caseworker can put right, so it is the right choice here.
Where to find components
1. GOV.UK Design System
Start here. DWP Design System extends it, so use a GOV.UK component or pattern when one fits.
2. DWP components
For what GOV.UK does not cover, such as showing whose case is open and what has happened on it.
3. DWP patterns
Ways to solve common problems in DWP services, such as finding an address or managing a session timeout.
Could we improve this page?
Send questions, comments or suggestions to the DWP Design System team.
Last updated: