Attention is a budget, not a resource.
Every interface asks something of someone. A little focus. Another decision. A moment they could have spent elsewhere.
01Start with what you’re asking.
A dashboard can look calm and still ask too much. Five equally prominent cards leave someone to work out the order. A helpful tip becomes another thing to dismiss. A notification pulls them into a task they didn’t come to do.
Calling attention a budget is a design lens, not a claim that everyone has the same fixed capacity. The useful question is specific: what does this screen ask someone to notice, understand, and decide?
Before adding another prompt, name the job it does for the person seeing it. “We need more engagement” describes a business goal. “They need to know their application is waiting for a document” describes something you can design around.
02Give the important thing room.
Imagine a new client opening a business-support dashboard. They don’t need the whole service at once. They need to understand where they are, what happens next, and whether anything needs their attention.
Other features can still be available. Their prominence should reflect when they become useful. That is a question of timing and hierarchy, not simply how many things fit on the screen.
Everything at once
One useful starting point
We’ll help you prepare after you book.
03Try this on one screen.
Take the screen a person sees before they can make progress. Read it as a set of requests. Then decide which one earns the first position.
W3C’s supplemental guidance on focus offers a useful companion: limit interruptions, remove unnecessary content, and use clear headings to help people find their place again. These are practical prompts for a review, not a substitute for testing with the people who use your product.
- Write down the one thing this person came to do.
- Count the decisions competing with it.
- Move one secondary request to the moment it becomes useful.
- Ask someone to explain the next step in their own words.