Buttons that looked like trim
The narrow metal bars blended into the machine’s finish. Their appearance gave little indication that they were pressable controls, and the icons above them had no text labels.
A course project examining how a KitchenAid espresso machine communicates its controls and operating states. An interactive browser prototype demonstrates the proposed interface.
Usability Analysis · Norman’s Design Principles · Prototyping · HTML/CSS/JavaScript · Vercel
01Problem
Using the machine regularly drew my attention to four areas where the interface provided little guidance.
The narrow metal bars blended into the machine’s finish. Their appearance gave little indication that they were pressable controls, and the icons above them had no text labels.
Blinking lights could indicate preheating or a cleaning step waiting for input. Understanding the signal required knowing which operation was underway.
The panel gave little guidance on the relationship between choosing a mode, selecting one or two shots, and starting the operation. Button placement did not make that sequence apparent.
The manual explains how to adjust temperature by selecting Espresso and holding the Mode button for three seconds. The panel itself did not indicate that this setting was available.
"They needed a way to designate which parts could be touched, slid upward, downward, or sideways, or tapped upon."
— Donald Norman, The Design of Everyday Things (2013), p. 34
02Process
The framework helped turn observations from daily use into specific design questions.
03Redesign
The proposal retains the machine’s red finish and horizontal bar controls. Changes focus on making those controls recognizable and explaining what the machine is doing.
The original machine already has a Start/Cancel control. In the redesign, grouping and labels make the selection-and-execution sequence more explicit. Selecting a mode highlights it; Start / Stop remains locked until a mode is selected.
I had to watch the indicator lights to know when preheating was complete. In the prototype, three long beeps mark readiness or completion. Two short beeps accompany cancellation or an attempt to use a locked control.
The prototype also includes a simulated Low Water state. A separate yellow indicator blinks, and all controls except Power are locked until that state is cleared.
04My Role
This project was built in collaboration with AI; the design decisions, content, and direction are mine. I used the machine, chose which problems to address, and decided how the redesigned panel should respond. AI assisted with the written analysis and with building the browser prototype.
05Outcome
The deliverable is an HTML/CSS/JavaScript prototype that runs in a browser. It demonstrates the proposed control behavior through simulated heating and operating states.
The prototype provides a way to review the sequence from powering on to selecting and running a mode. Its simulated low-water state also makes the proposed lockout behavior available to inspect.
An evaluation with first-time users would be needed to establish whether the redesign is easier to understand. That evaluation could focus on four tasks:
Select and start a mode. Choose a single or double shot and distinguish selection from starting the operation.
Adjust temperature. Find the setting and change it while the machine is ready.
Interpret machine status. Identify whether the machine is preheating, ready, or running.
Respond to low water. Recognize the warning and understand why the controls are unavailable.
A browser prototype cannot establish how the physical buttons feel or validate the appliance’s safety behavior.
06Reflection
Peer review led me to make the comparison between decorative trim and pressable buttons more explicit. Readers could then connect the analysis to a visible feature of the machine.
The project also helped me separate two questions: whether a control supports an action, and whether its appearance communicates that action. Keeping those questions distinct made the reasoning behind the redesign more precise.