The Knob Problem

Turn the volume knob on an old stereo. You know, without looking, roughly where it is. You feel the resistance. You feel the position. You can reach over in a dark room and move it a quarter turn and know — with your hand, before your eyes — what you've done. Now try the same thing with a volume slider on a phone screen. Eyes closed. You can't. The information isn't there.

This is the knob problem. It's not about nostalgia for analogue objects or discomfort with digital interfaces. It's about what happens when you remove proprioception from an interaction — the body's ability to sense where it is and what it's doing without external feedback.

Physical controls give you proprioceptive feedback. Touchscreens don't. And in many interactions, that difference matters enormously.

What your hands know

Your hands contain more sensory nerve endings per square centimetre than almost any other part of your body. They are extraordinarily good at understanding the world through touch — texture, resistance, position, weight, temperature. When you interact with a well-made physical control, you're using all of that capacity. When you interact with a flat glass surface, you're using almost none of it.

This matters in two ways. First, physical controls are faster for many tasks. Reaching for a knob and adjusting it takes less cognitive load than finding a slider on a screen, positioning your finger, and dragging with enough precision to land where you want. Your hands know how to find a knob. They have to search for a slider.

Second, physical controls work without attention. You can adjust the volume while watching the road. You can change the heat setting while talking to someone. You can operate a camera dial while looking through the viewfinder. The control is there, in space, with a defined position — and your hands can find it without your eyes.

"Good design makes a product understandable. Its structure should communicate its function."

A knob communicates its function through its form. You reach for it, grip it, and you already know what to do. A slider on a screen requires you to locate it, interpret it, and then interact with it — three steps where the knob required one. That gap is not trivial. Multiplied across every interaction, every day, it is the difference between a product that disappears into use and one that you are always slightly aware of operating.

What was lost and why

The shift to touchscreen interfaces was, in many ways, a genuine improvement. Infinite configurability. No dedicated hardware for each function. Software-updatable layouts. Lower manufacturing cost. For many categories of device, these benefits are real and worth having.

But the shift happened faster than the thinking that should have accompanied it. Functions that had been physical — and were physical for good reason — became digital by default, because digital was the direction. Not because it was better for the person using it.

Car manufacturers replaced physical climate controls with touchscreens. Audio equipment moved volume to apps. Cameras buried their exposure controls in menus. In each case, the decision was driven by the product team's logic — cleaner aesthetics, fewer parts, more flexibility — rather than by what the person actually needed in the moment of use.

The person who needs to adjust the temperature while driving doesn't benefit from a touchscreen. They benefit from a knob they can find without looking. The loss of that knob is not a feature. It's a failure to think about what the interaction actually requires.

The right question

The knob problem is really a question-framing problem. When a product team asks "should this be physical or digital?", the answer often defaults to digital — because digital is newer, cheaper, more flexible, and easier to explain in a presentation. When they ask "what does the person need in the moment they use this?", the answer is sometimes different. Sometimes very different.

Good design asks the second question. It doesn't default to the medium that's easiest for the manufacturer. It defaults to the interaction that works best for the human — and then uses whatever form, material, and technology that interaction requires.

Sometimes that's a touchscreen. Sometimes it's a knob.