Knowledgebase

Understanding the Cost of Complexity Print

  • uiuxdesign, guide, howto, solution, zillionkinghost, hosting, support
  • 0

Why less is usually better.

WHAT EVERY ADDITION COSTS

Attention A decision for the user Space Something to maintain Something that can break

WHY THAT MATTERS

Interfaces accumulate. Nothing is ever removed.

WHAT ACCUMULATION PRODUCES

Options nobody uses, obscuring the ones people need.

WHAT TO ASK BEFORE ADDING ANYTHING

What proportion of users need this? What happens if it is not there? Can it be automatic instead?

THAT LAST QUESTION

Frequently the best answer. A setting nobody should have to choose should be chosen for them.

WHAT TO DO ABOUT RARELY USED FEATURES

Move them, rather than removing capability.

Common actions prominent, rare actions available.

WHAT TO RESIST

Adding an option because one customer requested it Adding a feature because a competitor has one

WHAT TO REVIEW PERIODICALLY

What is actually used.

WHAT TO REMOVE

What is not.

WHAT THAT REQUIRES

Evidence, and the willingness to act on it.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot