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
-
•
Technology culture glorifies solutions but undervalues knowledge creation through deep research.
-
•
Correlation from big data should never be mistaken for causation without deeper qualitative understanding.
-
•
Demographic segments like age and gender often fail to explain user behaviors; thinking styles based on purpose provide richer insights.
-
•
Problem space research focuses on understanding people's purposes, not just their interaction with a product or organization.
-
•
Mental model diagrams and thinking styles enable gap analysis and strategic opportunity identification.
-
•
Empathy in design is a skill, best developed through deep cognitive empathy rather than surface-level emotional contagion or simplistic feeling.
-
•
"Research theater" refers to superficial data analysis aimed at influencing stakeholders without real insight.
-
•
Mature disciplines like architecture and museum design pay better attention to human purposes compared to technology.
-
•
Listening sessions, unlike typical interviews, prioritize deeply understanding users’ inner thinking and guiding principles.
-
•
Integrating problem space research with methods like Jobs to Be Done enhances strategic decision making, though Jobs to Be Done alone is insufficient for design.
Notable Quotes
"We live in a solution culture where we glorify people who can come up with solutions but not the people creating knowledge."
"Correlation is not causation and many in technology don’t understand that big data correlations alone don’t prove causality."
"You can’t explain why women check their bags just by demographics; you need to understand their purposes and contexts."
"Research theater is results designed to create reactions rather than deep understanding."
"Technology often puts the organization’s logic on the outside and forces users to think like the organization, not themselves."
"Empathy is not an emotion or sensitivity; it is a skill you have to develop."
"Cognitive empathy means consciously understanding other people’s perspectives from their own inner voice."
"Most teams build empathy on imaginary personas instead of real, deeply researched thinking styles."
"We need to grab the reins and push back when stakeholders misunderstand what valid research is."
"Deep problem space research creates data that could last decades and support multiple future projects."
Or choose a question:
More Videos
"The 1500 are designers, we don't distinguish strictly between UX or visual or industrial—they all bring design to the org."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Sometimes the director is the most senior design person in the org and ends up playing the executive role without the title or support."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Governance isn’t about choking creativity, it’s about putting bounds and clarity that enable purposeful collaboration."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Transportation must evolve to be more sustainable and accessible for all."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"The squad model flopped for us after six months but created culture triads that stuck around."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Never be afraid to get into good trouble; start by asking why."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Delivering research in small, lean increments allowed us to iterate fast and reduce bias."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Our brains are terrible at operating only on one type of information, whether object-oriented or context-oriented."
Designing Systems at Scale
November 7, 2018
"Ethics evolve faster than law; just because something is legal doesn’t mean it’s ethical."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
