Article 01 · UX Principles
The Best Interface May Be No Interface
Why removing a step can be more valuable than redesigning it.
Core principle
Minimize cognitive load, prevent unnecessary work, and design around the user's goal.
A polished confirmation modal can still be the wrong solution. Before improving an interface, ask whether the interaction needs to exist at all.
The instinct to redesign
When teams encounter a confusing workflow, the first reaction is often to improve the screen: rewrite the message, reorder the buttons, strengthen the hierarchy, and make the interaction more accessible. Those changes matter. But they may still optimize a step the user should never have been asked to complete.
A familiar example
Imagine a feedback workflow that asks a nurse to confirm that no issues were marked. The interface presents multiple yes-or-no actions, forcing the user to read, interpret, and confirm something the system already knows. A better version might use explicit labels such as “Add Feedback” and “Submit.” The strongest version may remove the confirmation entirely and use passive signals to determine that the task is complete.
Every interaction has a cost
A click is not merely a click. It requires attention, interpretation, memory, motor effort, and confidence. In high-pressure environments, unnecessary interactions compete with the user's real work. The design question is not “How can we make this modal better?” It is “Why does the user need this modal?”
Design the outcome, not the screen
Start with the outcome the person is trying to achieve. Identify what the system already knows, what can be inferred safely, and what truly requires human judgment. Automate the obvious. Surface exceptions. Ask only when the answer changes what happens next.
A practical decision test
Before adding a UI element, ask three questions: Does the user need to make a meaningful decision? Does the system lack the information to act responsibly? Would removing the step create risk or reduce control? If the answer is no, the interface may be unnecessary.
Design should remove work — not create more of it.
Design takeaways
- Improve the flow before polishing the interface.
- Use passive signals when the system already has the answer.
- Reserve interruptions for meaningful decisions and exceptions.
- Measure success by reduced effort, not increased screen activity.
Categories: UX Principles · Design Leadership · Human-Centered Design