Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Paying Better Attention to the Problem with Indi Young
Summary
In tech culture, everyone is hell-bent on coming up with answers and solutions. We all assume we know what the person’s problem is; rarely does tech culture start at the very beginning, understanding the variety of approaches real people have to their real purposes and different moods and contexts. Instead, we build an idea into experiments to see if it solves the imagined “problem.” Sound familiar? We can’t go on solving things based on our own thin understanding of how others perceive the problem. We can’t go on assuming everyone is in the same mood and context. There is no one-size-fits-all solution. Indeed, we have done a lot of accidental harm in the world with the assumption that the tools we design are “neutral.” We need to get better at paying attention. We need to slow down and gather a richer, more nutritious understanding of the people we are trying to support. And we need to point a beam of light into possible future outcomes. Let’s put equal emphasis on the problem. Spending equal time in the problem space generates rich understanding. Understanding the depths, perspectives, horizons and histories of the way people achieve their purposes opens up loads more opportunities. We can begin making solutions that eschew “engagement” to truly support different people in different ways. The problem space deserves more attention and a slow cycle all of its own.
Key Insights
-
•
Most organizations overemphasize solutions and ignore deep understanding of users’ purposes in the problem space.
-
•
Big data correlations often lead to misleading conclusions if context and underlying reasoning aren’t explored.
-
•
Demographic breakdowns like age or gender rarely capture the true diversity of user thinking and motivations.
-
•
Thinking Styles are a more meaningful way to segment users based on their purposes and mental approaches.
-
•
Listening sessions provide rich qualitative data necessary to build cognitive empathy and uncover deep user insights.
-
•
Cognitive empathy is a skill that requires going beyond surface observations to understand people’s inner voices.
-
•
Technology disciplines are immature compared to fields like architecture or museum design that prioritize varied user purposes.
-
•
Most tech companies operate without proper ethical research oversight (e.g., institutional review boards).
-
•
Jobs to Be Done is useful for strategy but inadequate alone without rich qualitative problem space research.
-
•
Rich problem space research results remain valuable and relevant for years, unlike short-term solution testing data.
Notable Quotes
"We live in a solution culture that glorifies people who create solutions but not those who create knowledge."
"Correlation is not causation, and a lot of people in technology don’t understand that."
"Research theater is when results are designed just to create a reaction, not real understanding."
"Purpose is a super important word—understanding what a person is trying to get done, not just their behavior."
"You can’t meaningfully segment users by demographics alone if you want to support their real purposes."
"Cognitive empathy only forms with depth; you can’t build it at the surface level."
"Empathy is not sensitivity or an emotion—it is a skill that you have."
"Most technology research is not research at all but at best focus group testing, and often lacks ethics."
"We have this piece of glass and there’s a person on the other side, but we don’t understand their purpose."
"You have to build all the puzzle pieces with clear summaries before the patterns come together in mental models."
Or choose a question:
More Videos
"Empathy in jazz means the band is in it together—when someone plays a wrong chord, the rest adapt and turn it into an opportunity."
Jim KalbachJazz Improvisation as a Model for Team Collaboration
November 6, 2017
"Writing a book is awful in terms of time, sweat, and time away from your loved ones, but it’s an amazing gift to dig deep into something you care about."
Louis RosenfeldCoffee with Lou: Should You Write a (UX) Book?
March 7, 2024
"Propose new IC roles like a design problem: identify the need, gather research, and try it as an experiment with retrospectives."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles
February 22, 2024
"I think we as UX researchers are uniquely positioned to forge bonds with data teams because of our storytelling and cross-functional work."
Marieke McCloskeyUser Science: Product Analytics & User Research
March 11, 2021
"DeepFakes can look too realistic and might introduce new privacy risks if donor faces come from real people."
Llewyn Paine[Demo] Deploying AI doppelgangers to de-identify user research recordings
June 5, 2024
"You don’t want to overdesign just to make something more data interpretable because that can lead you down a dark path."
Joshua NobleCasual Inference
October 6, 2023
"We’re selectively skeptical—skeptical about some things but not others based on what we want to believe."
Sara LogelYour Colleagues are Your Users Too
March 29, 2023
"We are obligated to treat each other with kindness and respect; this is a safe and inclusive space."
Bria Alexander Louis RosenfeldWelcome
January 8, 2024
"I’ve nearly bought products in my sleep because I memorized the key presses from consistent checkout flows."
Sam ProulxOnline Shopping: Designing an Accessible Experience
June 7, 2023
