· By Sajeevan (Saj) Veeriah
Everyday interfaces · 4 min read
In praise of the volume knob
A small control raises a larger design question: how much attention should an everyday adjustment demand?
Someone starts speaking. The music is too loud. A hand reaches for the volume knob and turns it down.
There is very little ceremony in that interaction. The control stays in one place, the movement has an obvious purpose, and the sound tells the person what happened. It is a useful starting point for thinking about interfaces.
The task is elsewhere
The person adjusting the volume is usually trying to do something beyond operating the sound system. They want to hear a conversation, concentrate on another task or make the room more comfortable. The adjustment should take only the attention it needs.
Now imagine that adjustment behind a menu. The user has to find the right screen, identify the control and make the change. The product may have gained a cleaner surface while asking for a longer interruption.
That is the interesting design question. How much of the user's attention does this small action deserve? Counting the controls on the front panel won't answer it.
A dedicated control earns its space when its purpose is stable and its use is frequent. A screen earns its space when people need changing labels, detailed information or choices that would be awkward to represent physically. A useful product can give each a job.
What the hand can tell
A knob has properties beyond its appearance. Its diameter, resistance, grip and position affect how it can be operated. A detent can mark an increment. An end stop can indicate a limit. A raised button can be distinguished from the surface around it.
Those properties need to agree with the behaviour. A dial with an absolute position becomes confusing if software changes the setting while the pointer stays still. An endless encoder avoids that particular mismatch but needs another way to show the value. Even a familiar control involves a choice about what the user should be able to infer.
Physical controls also have costs. A stiff dial can be difficult to turn. Closely packed buttons can be hard to distinguish. A press-and-hold shortcut may remain undiscovered. Replacing glass with plastic doesn't settle accessibility.
The worthwhile comparison is between complete interactions, including the feedback and the person using them.
| Adjustment | Design question |
|---|---|
| Turn something up or down | Can the person make a small change and recognise the result? |
| Choose one of several modes | Can they identify both the available choices and the current mode? |
| Enter an exact value | Can they reach the required value without repeated fine movements? |
Give the screen the same courtesy
A digital control can respect those needs too. Keep frequently used actions in a stable place. Give them enough room. Make the current setting readable. Let people enter a value when dragging to it would be awkward.
W3C's explanation of WCAG 2.2 target sizing describes how size and spacing help people activate a control without hitting its neighbour. Its guidance on dragging calls for a single-pointer alternative, subject to the criterion's exceptions. These are web accessibility requirements and explanations, not dimensions for a physical control panel.
The underlying design lesson travels further: an interface should offer a workable action to the person in front of it. A slider can coexist with a numeric field. A screen can coexist with a dial. There is no need to make every task use the same gesture.
A little less negotiation
Minimalism is easy to judge in a photograph. Living with a product adds movement, distraction, different hands and repeated use. An uncluttered surface is pleasant; so is being able to change one setting without searching.
The volume knob is worth considering because it makes that distinction tangible. It gives a recurring action a permanent home.
When a product gets this right, the adjustment takes its place in the background. The conversation continues.