UX Collective

We believe designers are thinkers as much as they are makers. https://linktr.ee/uxc

Follow publication

It’s not your design content that’s getting rejected: it’s your delivery

Use the “Doubtful Stakeholder” exercise to test whether your explanations make sense

Kai Wong
UX Collective
Published in
5 min readNov 19, 2024

A woman with a doubtful expression on her face
Photo by Pavel Danilyuk: https://www.pexels.com/photo/a-woman-with-a-doubtful-facial-expression-8637925/

Getting harshly rejected by doubtful stakeholders taught me the importance of translating your work.

I’ve heard it all, from being told, “I talked to the wrong users who didn’t know anything,” to getting polite nods and being told, “Just work on what I tell you, and we’ll tackle that next release.”

While it hurt in the moment, it also taught me a framework for double-checking if what you’re telling your audience makes sense to them.

If you’ve ever had your findings rejected, the problem isn’t always the content you’ve found. The problem is often how you deliver the news.

UX often has a translation problem

UX often runs into communication issues because it deals with qualitative data.

Most people in your organization work with quantitative data. Whether it’s Executives looking at KPIs and Metrics, Sales teams reaching quarterly goals, or Data Scientists doing statistical analysis, many of them have a number-oriented mindset.

On the other hand, UX is one of the few departments that looks at qualitative data and tries to base its recommendations on it. The problem is that bridging the gap between qualitative and quantitative isn’t always easy.

If you were to say something like “3/5 users found task 4 frustrating”, here are all the questions that someone must answer:

  • What does “frustrating” mean? Frustration is an emotion, meaning it’s not easily quantified, and no one knows its impact.
  • What does 3/5 users mean? That’s a small number of users that you talked to. It’s too small for any statistical analysis (i.e., we can’t say 60% of all users)
  • What does task 4 mean? Did you explain to your audience how you broke testing up into specific tasks and what task 4 was about?

This is where a lot of uncertainty comes from, and the first question in particular is what causes your team not to take action. Other people, from the Sales team to Customer…

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Written by Kai Wong

7xTop writer in UX Design. UX, Data Viz, and Data. Author of Data-Informed UX Design: https://tinyurl.com/2p83hkav. Substack: https://dataanddesign.substack.com

Responses (6)

Write a response

Ehhhh. Sometimes! I still face rejected design and UX ideas that are deeply based in business goals, deeply provable and supported. Mostly, these come from the least involved parties, and/or ego-driven execs who want to see their nebulous vanity projects executed and never venture inside the shoes of their users.

--

Kai, I think this is great insight. Another lens through which we might apply our story-telling as designers is business value. By connecting our research both to your questions of "so what?" and "show me the proof" as well as our business' primary values, we'll position ourselves to win over more allies.

--

It’s a large-scale effort that might collapse anytime if that person leaves.

I remember being removed from a web design committee very quickly when I emphasised the importance of information architecture to know how to organise and plan for a new website to replace the old one.

--