NPS, UMUX-lite, SUS, CSat, CES…

These are just tools for producing a number that will send your team off optimizing the wrong things.

Best thing you can do is just ignore them.

(If there’s a follow-on ‘verbatim’ question, spend your time there. That could be useful.)
The problem with ‘satisfaction’ is it’s a meaningless term.

Are you satisfied with this conversation?

If you gave me a 7, how is that different than if you gave me a 6? Or a 3?

Everyone brings a different meaning of satisfaction to the survey. We don’t know their context.
When every respondent brings their own meaning and context to a question, you can’t aggregate the answers. You’re aggregating apples, oranges, watermelons, and bees. What’s the average of all that mean?

Satisfaction measures are literally garbage measures.
While we’re here, averaging is often a bad idea in UX quantitative research. It’s treats margins and outliers as noise and focuses on the center.

The result is we aim for average experiences, not truly exceptional experiences.

Nobody wants an average experience.
When working on quant data, we need to understand the stories that happen at the margins.

The folks with horrific experiences are seeing the worst of our designs.

Those with wonderful experiences are seeing our true potential.

Exceptional experiences happen at the margins.
Folks think the numbers have meaning. They don’t.

If you spend time (like I have) watching people actually answer the numeric question, you quickly realize the numbers don’t mean a thing.

When you don’t have access to users, rolling dice is just as accurate as these measures.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Jared Spool

Jared Spool Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @jmspool

25 Sep
It makes me smile when a product manager tells me they need a full time researcher before they can do any research.

I look them in the eyes and say “you’re a full time user researcher.”

All PMs are user researchers.
Maybe not a good one.
However, they can become a better one.
User research is what PMs do.

They identify what users and customers need. Why the product doesn’t do that yet. What needs to change to make the user’s life better.

It’s the most important part of their job.
The great user research a PM has, the better their product will be. We’ve got 40 years of product management history to prove this.

It’s too bad the PM literature ignores this fact that user research is critical to great PM work.

It would make their jobs so much easier.
Read 7 tweets
19 Sep
Current status Image
Frog on a log Image
Status Update: Image
Read 4 tweets
18 Aug
"Don't let the perfect be the enemy of the good."

In UX design, this thinking delivers more damage than benefit.

There's usually a LOT of distance between good and perfect.

Good leaves room for better, which, when provided by someone else, leaves our designs behind.
We can do more that just good.

We can meet needs and exceed expectations.

We can excel beyond just satisfactory. (Satisfaction surveys should be banned in UX design. They measure the wrong things.)
There's a lot we can do to go beyond just being "good" before we come anywhere near being "perfect."

We should strive to provide experiences that people want, need, and enjoy.

Don't let the good be the enemy of the better.
Read 4 tweets
15 Aug
Current status Image
Image
Image
Read 5 tweets
6 Jun
This is better than the Shopify scooter → car diagram.

However, it still leaves out the most important aspect of an MVP: That it’s an instrument for learning, not an actual product.

Eric Reis defined it as the least work necessary to learn the most about users needs.

1/
We should be creating simple MVPs to learn what people need.

That’s not how it’s used in many places. Instead, people see it as the least we can build to claim we shipped something.

2/
When we think in terms of learning, instead of shipping, we don’t need to give it to everyone. Just enough to learn something.

And we also need to make sure we have the instrumentation and process in place to actually learn.

Shipping something and moving on is not learning.
3/
Read 10 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Thank you for your support!

Follow Us on Twitter!

:(