TITANMATTER
0%
Loading

Interfaces that guide attention rather than compete for it

Interfaces that guide attention rather than compete for it — TITANMATTER insights

Motion, contrast and hierarchy are attention budgets. Spending them everywhere is the same as spending them nowhere.

/ In this article:

Every element that moves, pulses or glows is making a claim on a visitor's attention. A page where everything makes that claim is a page where nothing does.

The attention budget

Treat contrast as a budget. Each screen gets one primary focus, and everything else is arranged relative to it. When a stakeholder asks for a second element to be "made to stand out more", the honest answer is that something else has to stand out less. There is no version of "everything is emphasised" that a visitor's eye actually experiences as emphasis — it experiences it as noise, and noise is what a visitor's attention skips past on the way to finding something that actually looks important.

Emphasis is relative. You cannot add it to everything.

/ TITANMATTER

Why this is hard to enforce internally

Every stakeholder in a project has a reason their element matters. Marketing wants the promotion badge visible. Sales wants the phone number prominent. Product wants the new feature callout to stand out. Each request is reasonable in isolation, and a page built by approving each one in isolation ends up with a dozen things fighting for the one slot a visitor's eye can actually land on first. The fix is not saying no to any individual request — it is making the trade-off visible: agreeing, before the page is built, on the one thing this screen is for, so that every other request is evaluated against what it is stealing attention from, not just what it adds.

Motion with a job

Motion earns its place when it explains a relationship: where a panel came from, what a control just did, which item is now selected. Motion that exists to demonstrate that motion is possible costs load time and, on a long page, costs patience. A parallax effect on a hero image tells a visitor nothing about the page they are on. A transition that shows a card expanding into the detail view it opened tells them exactly where they are and how to get back — that is the difference between decorative motion and motion doing a job, and it is usually visible in one question: if this animation were removed, would the interface be harder to understand, or just less busy?

Interaction

Hierarchy is a sequence, not a layout

Visual hierarchy is often treated as a layout problem — bigger text at the top, smaller text below. It is really a sequencing problem: in what order does a visitor's eye need to encounter information for the page to make sense? A pricing page where the price is the same size as the feature list has not failed at layout; it has failed to decide what a visitor needs to see first. Once the sequence is decided, size, weight and position are just the tools that enforce it — and they only work because everything that is not first in the sequence has been deliberately made to look like it is not first.

Practical rules we keep

  • One primary action per screen, visually unambiguous — if a visitor could reasonably ask "what am I supposed to do here," the hierarchy has not done its job yet.
  • Animation under 300ms for anything on the interaction path, because anything longer reads as the interface being slow rather than the interface being polished.
  • Respect the reduced-motion preference — it is a stated choice, not a hint, and building around it as an afterthought usually means the interface breaks for exactly the visitors who asked not to be shown motion.
  • If a hover state is the only way to discover something, it is undiscoverable on half your traffic — anyone on a touch device never triggers a hover in the first place.
  • Group related actions, and put unrelated ones far enough apart that a misclick is hard. A delete button next to a save button is a design decision that will eventually cost someone real data.

Mobile makes the budget stricter, not looser

On a small screen there is less room to spend attention on anything that is not the primary action, which means the discipline that is optional on desktop becomes mandatory on mobile. A secondary call to action that sits comfortably beside the primary one on a wide screen has to actually compete for the same thumb-width of space on a phone, and a hierarchy that was never firmly decided shows up immediately as a cramped screen with three buttons of similar visual weight and no clear next step. Most sites are now majority mobile traffic, which makes this the harder constraint to design for, not the secondary one — mobile is not a smaller version of the desktop layout; it is the version with the least room for indecision.

Where this goes wrong at scale

A single screen designed with a clear attention budget is not hard to get right. The failure mode shows up over time, as a product accumulates features and each new one gets added with its own reasonable-seeming call to action, badge or highlight. Six months later the homepage has four "primary" buttons, three animated elements, and a notification dot on something nobody remembers adding a notification for. Nobody made a single bad decision. The system simply had no mechanism for asking what the new addition was displacing, and attention that is not actively defended gets spent by whoever asks for it most recently.

Colour is doing more work than most teams admit

A brand palette with several accent colours creates a temptation to use all of them on one screen, because each colour individually looks correct against the brand guidelines. The guidelines rarely say what happens when four of them appear together, competing for the same visual weight. In practice we treat colour the way we treat motion: one accent per screen for the thing that matters most, with everything else pulled back to neutral tones until it is that screen's turn to matter. A brand that looks vibrant across a whole site and restrained on any single screen has usually done this correctly. A brand that looks vibrant on every screen individually usually has not — it has simply moved the noise from one screen to all of them.

Testing hierarchy without a user study

You do not need a lab to check whether a screen's hierarchy works. Squint at it, or shrink the browser window until the text blurs into shapes, and note what your eye lands on first. If it is not the thing you intended, no amount of copywriting or colour tweaking downstream will fix it — the shapes are making a claim the words have not caught up to yet. This is a five-second check and it catches a category of problem that is expensive to diagnose once a page has shipped and the numbers just look worse than expected without an obvious reason why.

In short

Attention is a fixed resource on any given screen. Every element that claims some of it is taking that share from something else, whether anyone intended that trade or not — so make the trade on purpose, decide what matters most on this screen, and let everything else visibly, deliberately, matter less.

Related reading