Most design work optimizes the interface and ignores the conditions under which it appears. That's backwards. By the time a user reaches your button, the environment has already done most of the work.

This is what gets skipped in most design work. The button, the label, the layout: all of it gets refined across dozens of iterations. The moment the user arrives at them rarely does.

In the late 1970s, a researcher named Roger Ulrich studied patients recovering from gallbladder surgery at a Pennsylvania hospital. Half of them had rooms overlooking a brick wall. The other half looked out at a stand of trees. The tree-view patients left the hospital nearly a full day sooner. They needed less pain medication. Their nurses filed fewer negative notes.

Ulrich published this in Science in 1984. Hospitals cited it for years in renovation documents. And still, most patient portal interfaces look like they were designed in a windowless room by someone who had never been a patient.

The interface lives inside a context. That context is doing work: shaping what users expect, what they fear, how much patience they have, what they're willing to read. Most usability work treats the context as fixed and the interface as the variable. You test the button. You don't test what the user went through to get there.

A hospital registration form at a 9 a.m. scheduled visit and the same form at 2 a.m. in an emergency department, are not the same. The person the form was designed for, a calm and attentive person, with a few minutes to spare doesn't exist in that room. The environment hasn't made that persona available. What's there instead: fluorescent lights, a muffled PA system, a crying child, a triage wristband. The form lands on top of all of that.

Casinos figured this out early. No windows, no clocks. Carpet patterns designed to push the eye toward the floor and back up toward the machines. The slot machine itself is almost incidental. The real interface is the building.

You could redesign every slot machine in Las Vegas and not move the numbers meaningfully. The environment has already done the work.

This is what goes undesigned in most products. The team owns the interface. Nobody owns the conditions under which it appears. And those conditions shape more than how people feel: they determine what people can conceive of doing. In a high-friction context, certain options simply aren't available, not because the user lacks the skill or the willingness, but because the environment hasn't made that mode of attention possible. You can't reach for something that the moment won't let you reach.

What you can't fully control, you can at least account for. Design for the moment of arrival, not the moment of completion. Ask what state the user is in when this first appears: not which persona they belong to, but what they've probably come from. What they're probably carrying. What they can still see clearly. What kind of attention they have left.

A button matters less than what brought the user to that moment. The context is the whole game.