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
"What is your mission for this design Ops summit? When this conference ends, what do you want to feel?"
Louis Rosenfeld Bria AlexanderDay 1 Welcome
September 23, 2024
"A mature design system needs both UI kits and matching developer component libraries; we provide both out of the box."
George Abraham Stefan IvanovDesign Systems To-Go: Reimagining Developer Handoff, and Introducing App Builder (Part 2)
October 1, 2021
"Don't think constraints are real. Executives see them as excuses for not delivering."
Jess GrecoClaiming your power: Practical tools for amplifying your unique voice
March 13, 2025
"We have to meet them where they are. Designers need to learn the language of business. That’s a very, very important lesson."
Robert SchwartzWe're Here for the Humans
June 9, 2017
"Potential refers to not yet actualized possibilities that may or may not come to fruition."
Nicole AleongFuture Orientations to Everyday Life: Futures Anthropology as a Methodology
March 26, 2024
"A growth mindset in research means being ready to adapt protocols based on what actually works with participants."
Mila Kuznetsova Lucy DentonHow Lessons Learned from Our Youngest Users Can Help Us Evolve our Practices
March 9, 2022
"People will say, I’m not totally sure what they do, but I know we need it."
John Mortimer Milan Guenther Lucy Ellis Patrick QuattlebaumPanel Discussion
December 3, 2024
"Blockchain apps aren’t located in one country or jurisdiction, making legal enforcement of accessibility laws difficult."
Sam ProulxTo Boldly Go: The New Frontiers of Accessibility
November 18, 2022
"The prompt becomes part design spec, part requirement doc, and part programming language."
Josh Clark Veronika KindredSentient Scenes and Radically Adaptive Experiences
June 11, 2025
Latest Books All books
Dig deeper with the Rosenbot
In what ways can AI automate UX research tasks, and what limitations does it currently have?
How can researchers integrate multiple stakeholder perspectives into a coherent research narrative?
How do enterprises balance qualitative and quantitative tools while integrating AI into UX research workflows?