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
"Companies are no longer dependent on where people are located to work."
Lavy Kumar Kat Temple Shan Sebastian Tara Jensen Jenn ChouFuture of Work
June 9, 2021
"We used virtual sketching where users could move components into spaces representing their actual workflows on the platform."
Andreas Huebner Amy Takata Craig BrookesWhat Is It Like To Be Part of The UX Team at Compass?
March 11, 2021
"Cluster analysis is very useful if you want to avoid a one-size-fits-all approach to product or service design."
Ricardo MartinsUnlocking the power of advanced quantitative methods
March 12, 2025
"We changed the culture by changing the language, introducing common terms like hypotheses and experiments."
Monty HammontreeThe Future of UX Research
December 3, 2020
"We didn’t explain the philosophy behind the design ops activities, so others didn’t understand why some activities couldn’t be done outside design."
Benjamin RealShowing the Value of DesignOps by Not Having a DesignOps Team
October 21, 2020
"Some people have been doing research ops a lot longer than the term has existed."
Kate TowseyAsk Me Anything (AMA) with Kate Towsey
April 2, 2025
"When you look at data without training, confirmation bias makes you just find what you already believe."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"Accessible foundations are built by involving voices of people with disabilities from ideation to prototyping to launch."
Sam ProulxOnline Shopping: Designing an Accessible Experience
March 28, 2023
"Screen magnification users are a great place to start because your prototypes and tools will mostly just work with minimal adaptation."
Sam ProulxPrototype Reviews, People With Disabilities, and You
October 1, 2021
Latest Books All books
Dig deeper with the Rosenbot
How can research and operations teams collaboratively evaluate new UXR tools for usability and operational fit?
What are the financial barriers preventing birth centers from operating sustainably in rural areas?
How can power imbalances be acknowledged and shared with community members in design processes?