Usability Is the Last Thing You Should Be Testing


Usability Is the Last Thing You Should Be Testing

by Jeff Humble


Dear Reader,

Here's a common scenario you might find yourself in:

Somebody in leadership has been pushing for an idea for a long time, and your team finally gets a chance to tackle it. You want to do this by the books, so you design three versions and run a usability test with five users.

You catch some problems early and start feeling pretty confident in your approach. The executives love the design, so everyone is happy.

The idea is finally built, but customers completely ignore it.

It never gains traction, but nobody knows why. Eventually, the leader realizes the idea is a dud and blames the team's execution for the result.

🤦🏽‍♀️ What happened here?

You skipped the desirability test.

Usability should have been the last thing you tested.

4 Checks to "Validation"

Rather than validating an idea, you want to put an idea through 4 different validation checks. Here are they are in the most common order:

  1. Viability, a.k.a. "Should we build this?" - Generally not a design area, validated by business stakeholders
  2. Feasibility, a.k.a. "Can we build this?" - Generally not a design area, validated by tech stakeholders
  3. Desirability, a.k.a. "Will people want this?" - Potential for design, validated by users
  4. Usability, a.k.a. "Will people understand this?" - Owned by design, validated by users

Generally, you will go in that order, meaning usability is the final check and not as crucial as desirability. That might come as a shock to you if you're not aware of the whole process.

Desirability and usability are challenging because they are risks related to people, and people change. What was desirable five years ago may not necessarily be desirable today.

That's why testing is a full-time job. There are always risks related to desirability and usability. Very few designers can test for both.

Testing for desirability is a blind spot for many teams, and it's a good growth role for a senior designer.

Learn more in our four-week course on designing product experiments...only 2 essential seats left!

What methods do you have for testing desirability?

“wErE a FaMiLy HeRe. BrInG yOuR wHoLe SeLf To WoRk.” 🤦🏼‍♂️ -@tomfall

Source, shared in the Guild


COURSE: Defining UX Strategy
Learn to design a winning strategy that aligns design with business.
Next cohort: Feb. 16-Mar. 30, 2026
Join the Waitlist
Early bird pricing launches Jan. 9th!


COURSE: Facilitating Workshops

Learn to turn meetings into momentum and clear decisions.
Next cohort: March 23–April 30, 2026
Buy a Seat
Only 6 Regular seats left!


Until next week, y'all! ✌️

Jeff Humble
UX Strategist & Co-Founder
The Fountain Institute

The Fountain Institute

The Fountain Institute is an independent online school that teaches advanced UX & product skills.

Read more from The Fountain Institute

Title of Newsletter in Titlecase By Hannah Baker Dear Reader, Before we jump into new ideas for the year ahead, we wanted to pause for a moment. If your inbox was anything like ours last year, there’s a good chance you missed a few newsletters. So instead of sending another new idea right away, we put together a curated catch-up, a handful of pieces from 2025 that capture the questions we kept returning to. If you only read a few things from us last year, these are a good place to start. 🧠...

What Can't AI Do in Design in 2026 By Hannah Baker Dear Reader, If you work in design, your feeds are probably saying the same two things on repeat: Here’s everything AI can do for you, and Here’s why you should be terrified. Most of that conversation focuses on tools and job titles: “Will designers be replaced?” “Which roles are safe?” It makes for good headlines, but it’s not how the work actually changes in real life. A few months ago, walking to my studio listening to a Planet Money...

Does the Double Diamond make sense for AI-enabled teams? by Jeff Humble Dear Reader, For twenty years, the Double Diamond has been our north star. Discover, Define, Develop, Deliver. It's elegant. It's teachable. It's in every junior's UX case study. And it made sense…when it was created. All that upfront research made economic sense when coding was the most expensive part of the process. Better to get it right before handoff because it's expensive for engineering to make changes later. But...