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
"I’ve been using screen readers for 30 years and accessibility has always been a passion of mine."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"Most of our designers are contractors; they have limited voice because they’re bound by contracts."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"I tried to do everything all by myself at first and it didn’t catch on because no one else knew I was doing it."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Your career is a design project. It’s the only one you own, so own it like you would a product."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"A lot of our work still happens in spreadsheets, because they’re flexible and dynamic."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Would you feel confident leaving your project success to the flip of a coin based on the fact that almost half of all change fails?"
Amy EvansHow to Create Change
September 25, 2024
"We’re powering a 300 plus organization of designers, researchers, program managers, and strategists."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"It’s impossible to be angry with a warm cup of tea in your hand."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"What if the atomic unit of research wasn’t the reports, but it was the insight within those reports?"
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
