Where Does the Bag Go?

Picture a service counter with a narrow ledge: wide enough for a pen, not a handbag. A form is clipped to a board; an identity card sits between two fingers; the bag strap has nowhere to go. The person signing braces the board against a hip, then searches for the pen that was already there. Nothing is broken. The counter is doing exactly what it was built to do. It is simply asking the visitor to grow another hand.

That missing ledge is easy to dismiss as a minor inconvenience. It is not minor to the person carrying it. A process is made of instructions, but also of objects that must be held, placed, remembered, and retrieved. When the furniture supports none of those actions, the burden has not disappeared; it has moved onto the user.

There may be reasonable explanations. Perhaps the counter had to fit an existing wall, keep papers from spreading, or leave enough reach for the person serving on the other side. The point is not that every counter needs built-in hospitality. Public systems have constraints: cleaning, security, staff reach, and queue movement. A ledge can be a bad idea if it lets papers accumulate or blocks the next person. Good design involves trade-offs. But a trade-off should be visible in the test. If the only person who gets tested is the staff member standing behind the counter, the process may appear efficient while the visitor performs a balancing act.

Try a simple inspection: place a board, a pen, a card, a phone, and a bag in the hands of the person who must complete the form. Do not ask whether each item is technically manageable. Ask which item must be dropped, clenched, or trusted to an unstable surface. Ask what happens when the visitor has a coat, a parcel, a walking aid, or a child’s hand to hold. The question is not whether an unusually awkward case can survive. It is whether ordinary use was imagined with any physical realism.

Two people can receive the same form and the same instructions while facing different levels of difficulty. One has a free hand; another is carrying a parcel; another cannot bend to retrieve a dropped card. Treating them identically does not make the process neutral. It only makes the hidden assumption harder to see. A usable arrangement does not need to advertise its generosity. It simply removes one needless negotiation from the task.

This applies beyond counters. A ticket machine with nowhere to put a suitcase, a clinic chair positioned so a coat slides to the floor, a checkout screen that requires one hand while the other holds a receipt: each arrangement converts a design decision into a small private problem. The individual is then blamed for being slow, disorganized, or inattentive. Enough small problems and the service begins to feel like a test of dexterity rather than a service.

There is also a limit to the argument. No built environment can anticipate every possession, body, delay, or interruption. Adding shelves, hooks, and ledges everywhere would create their own obstacles. The answer is not maximal accommodation; it is deliberate placement of friction. Put the inconvenience where it can be absorbed without making the user improvise under pressure. If a queue must move quickly, provide a clear place to finish the form before the next person arrives. If documents must stay visible, give them a surface that does not compete with the hands holding them.

The next time a process is described as simple, look at what the person is carrying while doing it. Instructions tell us what to do. Objects reveal what the system expects us to manage at the same time. Before calling an awkward interaction user error, inspect the counter. What has it assumed the visitor can carry?