
By Gagan Malik
The definition matters because every designer you hire believes they're solving the right problem, when in reality they're solving the wrong one. You've briefed them to make something "beautiful," "clean," "modern," "usable," or "accessible." Usability and accessibility are not the residue of that brief. They are load-bearing disciplines with their own research, testing, and standards, and no attention decision replaces them. But even a usable, accessible screen can still fail if nothing decides, with total intention, where a stranger's attention lands next. In 2017 a group CTO asked me to reskin the dark patterns on a payday loan application rather than state the APR plainly. That was the same decision wearing a conversion brief. The decision is not aesthetics dressed up, and it is not usability restated. It is a separate substance: control.
The incentives above the designer are not neutral either. The senior leadership team is not paid on how beautiful the product looks. It is paid on annual recurring revenue. Annual recurring revenue is a function of how much attention the product claims and holds against everything else competing for it. Shareholder value sits at the end of that same chain: hold attention, grow ARR, grow the number the board actually watches.
Steve Jobs made a stronger version of this argument in 2003: "Design is not just what it looks like and feels like. Design is how it works." nyt-guts-new-machine It's a real improvement over pure aesthetics, and it still stops one step short. A product can work flawlessly, be fully usable, and pass every accessibility audit. It can still fail if nothing directs a user's attention to the function that works. "How it works" already assumes someone knows where to look. Attention control is the layer underneath function: the decision that determines whether "how it works" ever gets discovered at all.
In 2017, consulting for a payday lender, I redesigned their existing loan application to state the APR plainly and remove the pre-ticked consent boxes. The group CTO looked at it and asked if we could just reskin the existing dark patterns instead. He wasn't asking for something more beautiful. He was asking for something that converted better. His bonus ran on loan volume, not on whether the person signing understood what they were signing. I declined and exited the project. I told the fuller story in Someone Designed That Button. That confusion isn't personal to one CTO. It is what happens when the person holding the brief and the person holding the P&L are optimising for two different things. Only one of them says so out loud.
Design schools teach aesthetics because aesthetics can be graded, credentialed, and placed in a portfolio. A designer's ability to direct your eye in a particular sequence, to make you notice one thing before another, is harder to show an admissions officer. So every young designer learns taste before they learn control, and by the time they enter a studio, aesthetics has the first move. That's the gap I traced in Why We Designed Contempt Into Our Interfaces: interfaces execute an intention whether or not anyone names it, and an unnamed intention defaults to whichever discipline got there first.
But strip away the polish and what remains is a sequence. A forced order of decision that determines what a person notices first, second, and not at all. The designer who built a dashboard where the critical alert sits under six rows of healthy status updates didn't fail aesthetically. They failed at the actual job: claiming a user's attention on behalf of what matters most. The alert itself was legible, correctly labelled, and passed every accessibility check. Usability and accessibility are not what failed here. Alert fatigue in monitoring systems nngroup-alert-fatigue is not an edge case. It's the standard outcome when attention hierarchy is ignored.
This is what "clean" design actually does. Fewer elements is not why it works. It works because someone has already resolved the competition for attention before the user had to. They decided what matters most, second most, and least, and encoded those choices into size, contrast, spacing, and sequence. According to cognitive load theory, instructionaldesign-cognitive-load extraneous cognitive load is the mental effort poor interface design imposes. When visual design reduces that load, users perform better and comprehend more. A reader experiences this as simplicity. What they're really experiencing is someone else's attention decision, executed so well it feels inevitable. I've traced the same mechanism from the platform side in The Algorithm Sold Your Next Four Seconds Before You Scrolled: the auction only works if something upstream has already decided which four seconds are worth bidding on.
A human immune system does not treat all pathogens as equally urgent. A paper cut receives a quick cleanup and seals. A bacterial infection triggers a cascade of specific, hierarchical responses. The immune system knows something about order and priority that design's current confusion between aesthetics and attention suggests we've forgotten. When everything screams for your eye simultaneously, your brain does what a body does when it's attacked from all angles: it shuts down and stops listening. Noise is what the brain is evolved to tune out.
There's a genuine argument here that aesthetics matters, and it deserves its full weight. A well-designed typeface does create an emotional response. A colour harmony can make a person feel safe before they've read a word. Cognitive load does decrease when a layout is symmetrical and predictable. A designer trained in aesthetics will produce something that feels more pleasant to inhabit than a designer who hasn't thought about it at all. The client will feel good. The user will stay longer.
But pleasantness and attention are not the same thing. Kurosu and Kashimura's 1995 Hitachi Design Center study nngroup-aesthetic-usability tested twenty-six ATM interface variations on 252 users. It found that perceived ease of use correlated more strongly with how attractive an interface looked than with how well it actually worked. People trust a beautiful interface even when it misdirects them, which means pleasantness can mask exactly the kind of failure this essay is describing. The moment you ask that pleasant interface to do something harder than feel nice, aesthetics becomes secondary. It needs to convince someone, guide them through a decision, or surface exactly what they need before the next swipe. That is when attention control becomes essential, not before. A designer trained only in taste will produce something that feels good and fails completely at its actual task. The task is a sequence of forced choices about what the person in front of it is allowed to notice, and in what order. I made the same distinction from the other side of the screen in The GUI Sells Comfort. The CLI Sells Control.: comfort and control are not synonyms, and interfaces that optimise for one often starve the other.
This isn't unique to interfaces. The logic governs a video title, a thumbnail, a paragraph break, an essay structured like this one. In the attention economy, design transfers control over visibility and pacing to the platform, btrax-attention-economy-ux and algorithmic convenience reshapes how attention is managed over time. A YouTube thumbnail is not "eye-catching" as an aesthetic virtue. It is a mechanism that hijacks the scanning behaviour of someone's eyes moving down a page of options and forces a half-second pause before the next swipe. The hook in the first ten seconds of a video and the first line of a headline do the same job in miniature. They decide, before a viewer has consciously chosen anything, whether attention continues at all. I mapped that exact lever, the swipe-up mechanism trained into TikTok, Reels, and Shorts alike, in The Most Addictive Design on the Planet.
When dark patterns manipulate through misdirection, rawstudio-dark-patterns they do exactly this. They draw the eye toward the option the business wants (the large colourful "Accept All" button) and away from what the user actually needs (the small buried preferences link). None of this is about beauty. All of it is about control: deciding, on someone else's behalf, what deserves their next unit of attention, and defending that decision against everything else competing for it.
But there's a deeper problem hiding in how this plays out in practice. As attention control has become central to design, the industry has created a catch-all title: "product designer." This combines user research, UX thinking, interface design, and business strategy into a single role, uxdi-product-designer often without clarity on which discipline is actually accountable for which outcome. None of those four disciplines is decorative. Research without a place to land becomes a report nobody reads. Interface design without research becomes a guess wearing a grid. Strategy without either becomes a roadmap built for no real constraint. The problem isn't that a company asks for all four. It's that nobody names which one gets to decide when they disagree. The result is role confusion that masquerades as hierarchy. I felt that confusion from the inside, introducing myself as a product designer at a pub full of people who could place "Space Guy" instantly, in Nobody Knows the Difference Anymore.
Compare that to a job nobody confuses. Roger Deakins has shot Skyfall, No Country for Old Men, Blade Runner 2049, and 1917. Nobody on any of those productions ever asked him to also own the sound mix or the casting, because "cinematographer" is not a catch-all title. His job has exactly one owner: where the eye goes, and what it feels when it lands there. Deakins has said the real test of that job is whether anyone notices it at all. As he put it: "I always hate it when you go to a premiere... somebody is saying, 'Oh, I love that shot with the camera, and it was so nice.' And you go, 'Oh God, I screwed it up.'" nofilmschool-deakins Once an audience notices the technique, the attention decision has already failed. Product design invented a title that fractures the same kind of accountability across four disciplines and calls the fracture seniority.
Treating design as attention control instead of aesthetic taste changes how you evaluate your own work entirely. The question stops being "does this look good?" and becomes "does this direct attention exactly where I intend, in exactly the order I intend?" The second question is much harder to fake.
It also explains why so much feels busy without being useful. Busy is what happens when nobody made the attention decisions on the user's behalf. Everything is present, nothing is prioritised, and the user is left to perform their own triage, which they won't. They'll leave instead.
Design was never about beauty: it is the discipline of deciding what a person notices first, second, and not at all, and defending that decision against everything else competing for it. The best designers prove it by what they refuse to keep: a feature, a paragraph, a beautiful shot that does not serve the sequence, because keeping everything is the same as controlling nothing. Roger Deakins named the actual test himself: the moment someone at a premiere tells him they loved a shot, he knows he has failed, because they noticed the camera instead of living inside the story it was built to serve.
View plans, ask a question, or book a call.
Add this link to your RSS reader to get new writings and updates automatically.