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
How Might We (HMW) is a commonly accepted design thinking practice for framing a problem in space exploration, usually within a codified "design sprint" framework. However, there are risks and limitations that can undermine its value. Join us for a candid, provocative discussion with Tricia Wang, who wrote a searing yet insightful piece recently in Fast Company that challenges the value of the HMW practice, while offering alternatives to help us transcend its issues.
Key Insights
-
•
The 'how might we' approach has been co-opted in many settings to enforce conformity and suppress alternative ideas, rather than encourage creative problem-solving.
-
•
Teams using 'how might we' must critically examine who the 'we' represents and whether those communities are truly included in decision-making.
-
•
Diversity and inclusion efforts often fail because companies seek to engage marginalized communities externally without changing their internal leadership and talent structures.
-
•
Building local research and design capacity in communities is more sustainable and ethical than relying on outside consultants who lack contextual understanding.
-
•
Designers need to foster trust and authentic interpersonal connections across organizational silos to drive meaningful change internally.
-
•
Conversations around values and purpose should be prioritized within teams to align efforts and expose misalignments that hinder productivity and retention.
-
•
Representation matters critically, especially in research teams, to avoid harm and misinterpretations when working with underrepresented groups.
-
•
Design teams benefit from diverse professional backgrounds like journalism and engineering, which enrich research and insight generation.
-
•
Emerging tech fields like Web3 present an opportunity to embed equitable design practices early, avoiding repeating past mistakes seen in Web2.
-
•
Feeling discomfort or skepticism towards standard design methodologies is a healthy sign prompting critical reflection and potential innovation.
Notable Quotes
"How might we has become like a church—untouchable and sanctimonious instead of a flexible tool."
"You have to ask who the 'we' is in the room, because often the communities you're designing for aren't represented or understood there."
"It's not about going out to communities but changing your team and leadership to genuinely reflect those communities."
"Companies parachuting in to 'study' marginalized groups often do more harm than good when they don't build local capacity."
"Building trust across functions means simple acts like scheduling lunch or coffee meetings with no agenda."
"Values conversation is less threatening when framed as wanting to understand why we're doing this project or why we're here."
"Designers are the most insecure function in many companies because their role—to represent people's needs—is both critical and ambiguous."
"Representation is key to avoiding harm and misinterpretation, especially when working with Indigenous and marginalized communities."
"Web3 offers a unique chance to get involved early before some of the ethical challenges of Web2 take root."
"Make a note when something about your design process doesn't feel right—discomfort is a guide to curiosity and improvement."
Or choose a question:
More Videos
"Stakeholder analysis and managing stakeholders is critical in hierarchical cultures to maintain trust."
Megan BlockerA Selectively Scrappy Approach to ResearchOps
November 8, 2018
"Our ability to articulate design’s value will pave the way for change or leave us stalled in the status quo."
Jon FukudaTheme 3 Intro
September 25, 2024
"Our AI tools help with speed and efficiency, and also help save money by reducing redundant research."
Andy Barraclough Betsy NelsonFrom Costly Complexity to Efficient Insights: Why UX Teams Are Switching To Voxpopme
September 23, 2024
"Everyone should know where everything is all the time — that’s the archivist’s motto for knowledge management."
Ben Davies Matt Duignan Andrew Michael Dr. Emily DiLeoExpert Panel: The Principles of Research Repository Design
March 11, 2022
"We seek to decentralize ourselves as designers and recenter ourselves as facilitators who draw on the expertise in the room."
Ashley Cortez Devika Menon Nidhi Singh Rathore Danita J. Reese Mari NakanoShifting Toward Community-Led Innovation in Local Government
December 8, 2021
"I wanted to make sure that we don’t lie with the data but give product teams raw ingredients so they can transform the products the right way."
Adel Du ToitGet Your CFO To Say: 'Our Strategic Goal is User Obsession'
June 10, 2022
"Having the researcher in the room throughout the product lifecycle is super helpful."
Anna AvrekhUser Research, Design, and Product - A Love Story
March 11, 2021
"It's cheaper to fix accessibility issues in the design phase than to wait until after coding or production."
Kate KalcevichIntegrating Accessibility in DesignOps
September 23, 2024
"Synthesis is a researcher’s superpower, not just analysis or breaking things down."
Robin Beers Nalini Kotamraju Andy WarrPanel: Excellence in Communicating Insights
March 26, 2024