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.
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
"Anonymous idea sharing helps prevent bias when some team members have more sway or intimidate others."
Billy CarlsonIdeation tips for Product Managers
December 6, 2022
"Accessibility doesn’t stop at the desktop just because you’ve made your desktop website accessible."
Sam ProulxMobile Accessibility: Why Moving Accessibility Beyond the Desktop is Critical in a Mobile-first World
November 17, 2022
"A typical enterprise customer has like five analysts who need a login, not millions of users."
Dan WillisEnterprise Storytelling Sessions
May 13, 2015
"An org chart is about formal reporting; a relationship map is about networking and collaboration across silos."
Michael PolivkaScaling Design through Relationship Maps
November 7, 2017
"The top LLM we tested got only 47% accuracy categorizing Reddit posts, which is sobering."
Karen McGrane Jeff EatonAI for Information Architects: Are the robots coming for our jobs?
November 21, 2024
"Ratios always start on the premise of spreading people too thin, which is not a great way to get success."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
"If you find someone not following values, start with a one-on-one to understand their point of view and realign together."
Kim Holt Emma Wylds Pearl Koppenhaver Maisee XiongA Salesforce Panel Discussion on Values-Driven DesignOps
September 8, 2022
"I thought I could single handedly bring design thinking to MailChimp. Turns out it took 1,000 people."
Jacqui Frey Alison RandSetting the Table for Dynamic Change
October 24, 2019
"Talking about UX ROI as reducing failure is like opening a new restaurant and saying please come because we won’t make you sick."
How to Identify and Increase your "Experience Quotient"
June 15, 2018
