Flag

We stand with Ukraine and our team members from Ukraine. Here are ways you can help

Get exclusive access to thought-provoking articles, bonus podcast content, and cutting-edge whitepapers. Become a member of the UX Magazine community today!

Home ›› Business Value and ROI ›› 6 Key Questions to Guide International UX Research ›› Simplicity, It’s Complicated

Simplicity, It’s Complicated

by John Boykin
5 min read
Share this post on
Tweet
Share
Post
Share
Email
Print

Save

While it’s wise to strive for simplicity in product design, the ultimate goals should be ease and clarity of use.

“Make everything as simple as possible, but not simpler.”—Albert Einstein

Your smart phone would be simpler if it didn’t have a camera. But it would also be a lot less useful. A paint can is a sublimely simple way to store paint. But it’s a dreadful way to interact with paint: It’s hard to open, hard to close, and guaranteed to make a mess every time you pour it.

Simplicity is an obvious virtue, but it is not the ultimate virtue. Sure, the fewer clicks, taps, steps, hurdles, fields, distractions, and doodads in a UI, the better. We UX designers have a whole bag of tricks for simplifying things—consolidating here, eliminating there, shrinking this, submerging that—and 19 times out of 20, the simpler approach is the better approach.

But, ahhh, that twentieth time. In our enthusiasm for making elements, widgets, and products simple, we need to avoid overshooting the target, making them too simple to serve their purpose well. For example:

  • An icon without any words attached to it is nice, simple, and clean. It avoids translation problems, but simultaneously runs a high risk of being incomprehensible in many languages.
  • The ubiquitous USB plug fits into a port only if you have the top on top. But since both plug and port are simple rectangles, most people can’t tell top from bottom. You have to examine both closely and compare them carefully to get the top on top. Most people don’t, so we routinely need two or more tries to get the damn thing plugged in. If the mating parts were just slightly more complex—say, shaped like a D or an obtuse isosceles triangle, or with a conspicuous dot always marking the top of both plug and port—we would struggle with USB plugs much less.
  • A mobile app that depends on users somehow knowing specialized gestures to navigate has the luxury of presenting a wonderfully simple interface, but a high percentage of users will give up on it before ever stumbling upon those secret handshakes.
  • There was an early mobile app that consisted simply of the complete text of the King James Bible—all 750,000+ words of it—with no pesky navigation or search functionality to clutter up the UI (uhhh, I mean, to enable you to find anything). You were left to just scroll and scroll and scroll and …
  • There is a service (which shall remain nameless) that syncs up your files on multiple devices. It’s designed to automatically and instantly delete a file everywhere if you delete it anywhere. Nice and simple: everything always in sync. And to keep things really simple, there is no warning, no “Are you sure?” and no undo. But 20% of its users view the service as a means of backing up their files. They are in for a nasty surprise when they discover later that their “backup” copy in the cloud has vanished just as soon as any instance of it anywhere else gets deleted, even if that deletion was an accident.
  • Many country selector dropdowns consist of a simple list of the world’s 190+ countries in alphabetical order. But such a simple widget will inconvenience every user except those in countries at the top of the alpha list. And chances are most of your users are not in Afghanistan, Albania, or Algeria.

So, yeah, making something too simple can be as problematic as making it too complex, just as making a room too cold can be as uncomfortable as making it too hot.

Scratching the Itch

Simplicity is a one-to-one match between an itch and a scratch. Fine-turning the scratch to the itch usually does mean subtracting, but not always. Sometimes it means a small addition, such as asking users whether they want that file deleted everywhere. To hit the appropriate level of simplicity, we need clarity about exactly what itch we’re trying to scratch.

The goal is not simplicity for its own sake. Simplicity is only a means to an end. The goal is ease. We can admire simplicity as a characteristic, but ease is what we want users to experience.

The goal is not simplicity for its own sake. Simplicity is only a means to an end. The goal is ease.

“Keep it simple” is a great rule of thumb but a poor reflex ideology, because of all the times it shames us into putting simplicity ahead of ease. Naturally, we want both, and they do tend to go together. But we sometimes have to lessen one to achieve the other. When we do, ease should win. As long as the result is to make the thing easier to use and to satisfy users’ actual needs, mission accomplished.

When Brevity Attacks

A prime way we simplify is to reduce verbiage. And sure, all things being equal, the fewer words or elements it takes to communicate something, the better. But all things are not always equal. Like making a room too cold, we sometimes overdo brevity, creating more problems than we solve. Better to use a little more verbiage to communicate clearly than to puzzle users with something concise but cryptic. Consider:

More consice vs. More clear table

Concise action button verbiage is a particularly sacred cow. You can’t get much more concise than the standard “OK” and “Cancel.” The word “OK” itself is pristinely simple, but that simplicity comes at a price: additional effort and occasional grief. To know what you are consenting to in a dialog box, for example, you have to go to the trouble of reading the rest of the dialog. Users often don’t, so they sometimes suffer by clicking “OK” with regards to things they did not intend to. To spare them a bit of effort and grief, a self-explanatory button is more helpful than a concise button. That tends to mean a tad more verbiage.

Here’s an example of how our well-meaning insistence on bare-minimum button wording can sometimes do more harm than good:

Leave Meeting button

Making the buttons self-explanatory (though less concise) can actually streamline the whole dialogue:

Leave Meeting button

Is this not simpler than the original?

Bottom line: Simplicity is good. Ease is better. Brevity is good. Clarity is better. What are some of your favorite examples of clarity and ease in design? Share your examples in the comments below.

 

Image of single cell organisms courtesy Shutterstock.

post authorJohn Boykin

John Boykin
John Boykin answers to user experience designer, information architect, interaction designer, information designer, and UX researcher. He’s been doing all of the above for over 10 years. Clients include Walmart, Macy’s and Bloomingdale’s, Blue Shield, Bank of America, Visa, Symantec, NBC, HP, Janus, Prosper, and Mitsubishi Motors. His site, wayfind.com, will tell you more than you want to know.

Tweet
Share
Post
Share
Email
Print

Related Articles

Struggling with PowerPoint’s design limitations? This step-by-step guide shows you how to build systematic design solutions, from mastering slide layouts to using sticker sheets for patterns. Learn to create polished, professional presentations with smart workarounds and helpful tips.

Article by Jim Gulsen
A Step-by-Step Guide to Creating a “Design System” in PowerPoint
  • The article gives a step-by-step guide to building systematic patterns in PowerPoint. It talks about the program’s limitations and gives essential tips like mastering slide layouts and customizing text settings.
  • It suggests using PowerPoint’s automated features carefully and advocating for manual workarounds to elevate quality.
  • The piece introduces creating sticker sheets for reusable design components and highlights strategies for successful workflows.
Share:A Step-by-Step Guide to Creating a “Design System” in PowerPoint
5 min read

Publishing in HCI and design research can feel overwhelming, especially for newcomers. This guide breaks down the process — from choosing the right venue to writing, submitting, and handling revisions. Whether you’re aiming for conferences or journals, learn key strategies to navigate academic publishing with confidence.

Article by Malak Sadek
A Guide to Publishing Human-Computer Interaction (HCI) and Design Research Papers
  • The article provides a guide to publishing in Human-Computer Interaction (HCI) and design research, sharing insights from the author’s PhD experience.
  • It explains the significance of publishing in academia and industry, offering an overview of peer-reviewed journals and conferences.
  • It breaks down the two main types of papers — review and empirical — detailing their structures and acceptance criteria.
  • The piece emphasizes strategic research planning, collaboration, and selecting the right venue for submission.
  • The piece also outlines practical steps for writing, revising, and handling rejections, encouraging persistence and learning from reviewer feedback to improve publication success.
Share:A Guide to Publishing Human-Computer Interaction (HCI) and Design Research Papers
8 min read

Accessibility isn’t just about compliance — it’s about inclusion. A deaf developer shares what UX designers need to know to create better experiences.

Article by Tamara Sredojevic
Designing for Deaf Users
  • The article talks about a deaf developer who shares insights on digital barriers, assistive tech, and inclusive design.
  • It presents a candid conversation on UX challenges, assistive technology, and advocating for better accessibility.
  • The piece dives into the challenges and solutions for creating truly accessible experiences.
Share:Designing for Deaf Users
11 min read

Join the UX Magazine community!

Stay informed with exclusive content on the intersection of UX, AI agents, and agentic automation—essential reading for future-focused professionals.

Hello!

You're officially a member of the UX Magazine Community.
We're excited to have you with us!

Thank you!

To begin viewing member content, please verify your email.

Tell us about you. Enroll in the course.

    This website uses cookies to ensure you get the best experience on our website. Check our privacy policy and