Dear Reader,
Today’s newsletter comes from the audience. Here are 3 challenges from my newsletter survey. Can you find the theme?
“The organisation I work for prioritises design based on business need and not customer need.”
“Ideating what's best for the user and then trying to explain it to client”
“My design challenges are to justify not only to do the user research but also to need the time to analyze the results and present them in a meaningful way.”
Today, let's get back to the UX basics: promoting the user perspective within the business.
They’re the ones that are experiencing our designs, and they’re the ones that pay the bills.
Business conversations about users happen in metrics, numbers, and analytics by default. Is the user perspective in these numbers?
It's all user data, but it's hard to empathize with the human condition in a graph about button conversions.
Analytics isn't counter to human-centered design, but analytics are on a business-centric view by default. But what is easy to track isn't always valuable.
Behind every count, there is a real human behavior or demographic, but these numbers are generally organized around a button or a quarterly goal.
The segmentation is generally based on what the business cares about.
For example:
To make the business care about the user, you must organize the data around the customer. That's an extra step, but it's an important one.
Here are the top 3 ways to talk about the user with more than numbers.
The French economist Pierre Guillaume Frédéric Le Play first employed a case study in 1829 to explain statistics about family budgeting in an easy-to-digest format.
They were quickly adopted as teaching tools. Today, the case study is most commonly used to explain a corporate solution to a customer problem.
Designers can use the case study to tell a story about a single user in detail when the numbers don't give enough context.
Most UX portfolios employ this technique to tell the story of a project.
UX case studies can be organized around a user's daily journey, the designer's process, or internal stages such as marketing funnels.
Common storytelling formats:
Get more inspiration for case studies in this video by Ellen Lupton.
The UX persona is everywhere these days.
Alan Cooper gave birth to UX personas in 1983 to make products more focused. In those days, products were designed and built by developers. Cooper's book The Inmates Are Running the Asylum inspired user-centered software design with a focus...rather than the one-size-fits-all approach.
Learn more about "real personas" in this interview video with Alan Cooper
Personas are typically filled with marketing information. Demographics like age, income, and location in UX personas often step into the domain of marketing research.
The quality of personas varies wildly, thanks partly to personas becoming a "required UX portfolio artifact." A quick Google search reveals fluffy, made-up personas and templates that have nothing to do with real user research.
What if you want to show things like personality and style? Demographics don't give us the full picture:
The archetype in UX is focused on user behavior, which contrasts the demographics of personas.
UX Archetypes come from the social sciences and literature. Carl Jung pioneered the idea of archetypes long before designers, but his definition of them feels like it's straight out of a Medium article:
You probably already know non-UX archetype frameworks like the OCEAN Big 5 of Openness, Conscientiousness, Extroversion, Agreeableness, and Neuroticism or the 16 personality types of the Myers-Briggs.
Here's an example from UX:
Archetypes provide a bit more "why" into the user data. These are often used with personas, and the two have been merging in the past five years.
Watch a quick video example of a common archetype
In practice, you might use a combination of all 3 formats to get the job done.
When presenting user insights in the form of a case study/persona/archetype, keep these things in mind:
Case studies, personas, and archetypes are powerful formats for communicating the "why" behind user data.
But they should always be based on real research data.
To learn how to gather UX data, check out this free 7-day mini-course on UX Research.
It's 7 lessons for designers that want to get better at research.
Get the FREE course |
Some recent feedback:
“Fabulous mini course, a great refresher, foundation setter or even an intro!”
Until next week!
Jeff Humble
Designer & Co-Founder
The Fountain Institute
P.S. We just announced the August meetup. Grab a spot for Taking the Wheel of Your Design Career with Damian Martone, and stick around after the talk for our new networking groups!
The Fountain Institute is an independent online school that teaches advanced UX & product skills.
Are you stuck in reactive mode? by Jeff Humble Dear Reader, Some designers spend their whole careers reacting to other people's moves. As a design manager, I remember being in this position. I had to brace myself every Monday morning for some radical change in company direction. We never knew what the new agenda would be, but we knew that it would throw our work into chaos. Sometimes, all it took was for the founder to read a single article to change the company agenda. When a competitor...
Why Your Portfolio Isn’t Working (and How to Fix It) By Hannah Baker Dear Reader, Let’s talk about a harsh truth: Your UX portfolio might be the least important thing in your job search. Yep, I said it. You spent hours making sure it showcases your best work. You structured your case studies just right. You ensured your problem statements, research insights, and solutions flowed together. And yet… hiring managers are ghosting you like a bad Hinge date. Well, the problem isn’t your...
Chasing Competitors Instead of User Needs by Jeff Humble Dear Reader, Have you ever had a CEO who was overly obsessed with beating the competition? I know I have. You may not have realized exactly how this can be toxic. So, I'd like to help you out with two case studies. Here is a tale of two companies and how they handled the competition. The first took a company-first approach while the second took a user-first approach. It goes like this... Company-First: The Rise & Fall of Google+ Google+...