The Curb Cut

The curb cut was never meant for you. It was cut into the sidewalk for wheelchairs — a small ramp where there used to be a step. Then everyone started using it. The parent with a stroller. The traveler dragging a suitcase. The delivery worker with a hand truck. The runner who doesn’t want to break stride. The thing built for the few turned out to be better for everyone, and now you’d never design a corner without one.

Software has curb cuts too. The ADHD brain is the one that reveals them.

Every screen you can skip. Every timer that doesn’t punish a wandering eye. Every path that doesn’t fork into a decision you didn’t ask for. Every list that forgives you for looking away. These feel, to most people, like minor niceties. To an ADHD brain they are the difference between using the app and abandoning it on the second day. The load that makes one person bounce is a load everyone is carrying — just below the line where they’d think to complain about it.

This is why designing for the most-taxed user is a higher bar, not a kinder one. The easy answer to any problem is addition: another screen to explain the feature, another toggle to cover the edge case, another tip that pops up to teach the thing the last tip didn’t. Addition always feels like progress and almost always makes the app worse. Subtraction is harder. It asks you to find the one path instead of offering five, to delete the explanation by making the thing not need explaining. There is no template for what to remove.

I’ll give you three places it changed what I built.

When I looked at how a new user met the app, I found four different systems competing to teach them at once — an intro carousel, a slowly-revealing dashboard, hints that self-destructed on a timer, a chain of tips. Each was reasonable on its own. Together they were a wall. I deleted all four and replaced them with a single quiet note that appears beside the thing it explains, once, the first time you reach it. The honest version of onboarding turned out to be mostly the courage to remove it.

A paused item used to vanish. You’d set something aside and it would leave every screen — out of sight, which for this brain means out of existence. So pausing wasn’t rest; it was a quiet kind of deletion. Now paused things have a home you can walk back to. Nothing you set down disappears. It waits where you can find it.

And coming back after forgetting the app for a month doesn’t greet you with a wall of overdue. A thing you buy sometimes isn’t late the week you skipped it. The list doesn’t pile up guilt while you’re gone, because the person most likely to forget the app is exactly the person it can’t afford to punish for forgetting.

There’s a trap in all this, and I’d rather name it than pretend it isn’t there. Subtraction has no natural floor. Keep removing and eventually you starve the user who actually wants density, control, the dial turned all the way up. Designing for the ADHD brain is not simply a stricter version of designing for everyone — pushed too far, it becomes its own kind of failure. The resolution isn’t to stop subtracting. It’s progressive depth: a surface simple enough for the most-taxed day, with the depth tucked underneath for anyone who goes looking. Simple by default, not simple by ceiling.

And then there is the part no interface can reach, which honesty requires me to say plainly. No app can make you open it during a stretch when opening anything feels impossible. A brain in hyperfocus does not hear a notification. The hours after the medication wears off are real, and invisible to the software. These aren’t problems waiting for a better screen. They’re the edge of what design can do, and pretending otherwise is its own small disrespect. The most an app can manage is to be the calmest, lightest thing within reach on the day someone finally reaches for it — and to add nothing to the weight the rest of the time.

The curb cut didn’t make the sidewalk worse for the people who could already manage the step. It made it better for all of them, quietly, and the only cost was the discipline of building for the person who couldn’t. Software is no different. The question was never whether you can support your most distractible user. It’s whether you’d design against them as the standard — and discover, the way the sidewalk did, that you’d been building for everyone all along.