Nail the 80/20 of usability with this checklist.

Simple Usability Checklist for Startups — Part 1 of 2

Article Summary: A concise, actionable list to avoid common usability mistakes. Use this to check against your app or product to help build an easy to use app and ensure the highest chance of success.

On air sign

#1: Ensure system status is visible

Design should keep users informed of what’s going on within a reasonable time frame . Users then learn from previous actions and can determine next steps. Predictable interactions create trust.

  1. [ ] Clearly show the system status
    ❌ Don’t: Keep user in the dark as to whats happening
    ✅ Do: “Your’e offline. We’ll save your changes locally until you reconnect”
  2. [ ] Ensure the system informs the user of the outcome when actions are taken by user.
    ✅ Do: “Success, your action worked” or “That option is not possible offline”
  3. [ ] Feedback is presented quickly and concisely

“The single biggest problem in communication is the illusion that it has taken place.”
— George Bernard Shaw, British playwright and Nobel Prize recipient

#2: Match system to real world

Use words, phrases and concepts familiar to your users, rather than internal / developer jargon.
▶️ Learn more: 2 Min Video Match between the System & Real World

  1. [ ] Use real world terminology, not jargon eg “Car” vs. “automobile”
    ❌ Don’t: “Database string updated”
    ✅ Do: “Changes Saved”
  2. [ ] Ensure Users can understand words used without a dictionary
  3. [ ] Opt for button copy with verbs eg ‘View Document’
    ❌ Don’t: ‘Click here’
    ⚠️ Caution: ‘Learn More’ is sort of ok but no help to screen readers
    ✅ Do: ‘View Document’, ‘Send File’, ‘View Case Study’ tell user exactly what to expect.
    ️️️️
Clearly marked exits give users confidence

#3: User control and freedom

Mistakes happen. Always have an emergency exit to leave the unwanted action without having to endure a difficult process. Ability to back out or undo cations gives user a sense of freedom, reducing stress and frustration.

  1. [ ] Support Undo, & ideally Redo
    ❌ Don’t: ‘This cannot be undone’ is lazy programming.
    ✅ Do: Fun fact: redo is undo’s undo.
  2. [ ] Ensure user can exit the current interaction
    ✅ Do: ‘Cancel’, ‘Back’, ‘Never Mind’ are all good escape hatches
  3. [ ] Exits are obviously marked & easily found
    ✅ Do: Use common UI patterns like the 🅧 in the top corner of a window
An example of what not to do: Inconsistent UI.

#4: Consistency

People spend most of their time not using your site / app. Reduce cognitive load by maintaining consistent language and interactions.

  1. [ ] Interactive elements with the same name, perform the same action
    ⚠️ Caution: Casually changing between terms that eg Log in /Sign In / Log On
    ✅ Do: There is much debate around using Log In vs Sign in.
    Pick one and stick to it.
  2. [ ] Consistent visual design throughout the app + marketing + all communications
  3. [ ] Consistent language throughout the app + marketing + all communications

#5: Prevent errors

Useful error messages are great. Preventing errors in the first place is even better

  1. [ ] Prevent high-cost errors first, then little frustrations
  2. [ ] Enlist warnings for large or destructive actions — undo + a warning is best
    ✅ Do: Ensure destructive buttons clearly marked
  3. [ ] Provide helpful constraints
    ✅ Do: Perhaps shoppers don’t want to order 500kg of bananas
  4. [ ] Provide helpful defaults
    ✅ Do: pre-populate fields with most common entries eg ‘Yes, allow notifications for important alerts’
  5. [ ] Prevent mistakes by removing memory burdens,
    ❌ Don’t: don’t make user remember between screens
    ✅ Do: show relevant information from previous pages in a flow

Part 2 coming soon.

--

--

--

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

The Quintessential Role Of Conflict In Innovation Projects

How did change in the design & colours of our Marketing Poster get us more Signups?

Getting started in design with Figma.

Empathy by design

Not all demand is created equal: Failure demand and the service design opportunity

Making the Complex Clear: The History and Origins of Information Architecture

Empathy At Scale

LoKi an anti-DV anti-Trafficking application.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Luke Simshauser

Luke Simshauser

More from Medium

Add This to Your Onboarding Process: Personality Playbooks

The Daily PPILL #12 — Watering Hole

Avoid “Zero Results” On Your Career Site

How to start the design proposal for your client.

Apartment renovation Copenhagen — Danila Lampis arkitekt