The hallway is the real viewport
Designing for the moment of use rather than the moment of demo. What point-of-care software teaches about every product built for people in motion.
Every interface gets designed twice. Once in the quiet of the design tool, at full attention, on a large screen, by someone who already understands every state. And once in the place it is actually used, which is almost never quiet, rarely full attention, and often a hallway. The gap between those two settings is where most products quietly fail, and closing it is most of what product design actually is.
I learned this in the sharpest possible setting: clinical software, where the user is a physician documenting a patient between rooms, and the real viewport is not a 1440px canvas but thirty seconds of divided attention in a corridor. But the lesson is not about healthcare. It is about the difference between the moment of demo and the moment of use, and which one you are really designing for.
The demo lies
Software is sold, reviewed, and approved in demo conditions. Someone presents it on a big screen, walks through the happy path slowly, and everyone nods. The demo is a controlled setting, built to make the product look considered. And the demo lies. Not on purpose, but by design, because it strips out every condition that makes the real moment hard: the interruption, the noise, the fatigue, the fact that the user has done this task four hundred times and resents step three.
A form that is perfectly reasonable in a demo can be genuinely hostile in use. Ten fields is fine when you are presenting them one at a time to an attentive room. It is real friction when it stands between a clinician and the next patient. The design did not change between those two settings. The setting did, and the setting is the part the demo cannot show you.
Designing for the moment of least attention
The fix is to design for the worst moment, not the best one. For the real point of use, ask: how much attention does the person actually have here? Usually far less than the tool implies. Then build for that number, not for the demo's generous one.
In practice this means firmly separating what must happen now from what can happen later. The moment of use gets only what it requires: the fast, clear, low-attention path. Everything else moves to where there is more attention to spend: a review screen, an audit view, a later pass. Completeness is not removed. It is moved to a moment that can afford it. The person in the hallway gets the fast surface. The person reviewing at a desk gets the full record. Same information, sorted by how much attention each moment actually has.
That reframe, sorting by attention rather than by the data model, is the whole move. Most dense interfaces are dense because they mirror the underlying record rather than the person's situation. The record wants completeness. The hallway wants speed. Design for the hallway, and send the completeness somewhere the record can still have it.
It applies everywhere
None of this is specific to medicine. The commuter approving an expense on a train, the warehouse worker logging a pallet, the parent booking an appointment while making dinner, all of them are in some version of the hallway. All of them have less attention than the design tool implies. And all of them are served by the same discipline: find the real moment of use, measure the attention honestly, and design for that instead of for the room where the product gets approved.
The products that feel effortless are not the ones with the fewest features. They are the ones that correctly guessed how much attention you would have when you actually showed up, and asked for no more than that.
Takeaways
Describe the real moment of use before you design the screen: where the person is, what else they are doing, how many seconds they have. Design for the moment of least attention, not the demo's controlled one. Separate what must happen now from what can happen later, and move completeness to a moment that can afford it. And be suspicious of any flow that looks great in a walkthrough, because the walkthrough is exactly the condition that hides the flaw.
The canvas is not the viewport. The hallway is. Design for the hallway, and the demo takes care of itself.