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.
The most popular design thinking strategy is BS
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
"Reducing cognitive load means some decisions should just be made for the team to free mental bandwidth."
Candace MyersStandardizing Design at Scale
September 9, 2022
"Ethnio allowed us to track participants' total compensation and set annual caps, reducing fraud risk and improving compliance."
Sarah Sgarlato Pierini Kevin NewtonFrom Passion to Execution: A Story of Evolving Research Maturity at LinkedIn
September 9, 2022
"We often point fingers at the person making the most money from the mess that designers put through the system."
Cennydd Bowles Dan Rosenberg Lisa WelchmanDay 1 Panel
June 4, 2024
"The team brought structure and clarity by mapping requirements into user journeys and stories."
Rob Mitzel Sébastien MaloThe Tale of Two Companies: Building a Successful UX Practice in a Century-Old Enterprise
January 8, 2024
"Start small by delivering the minimum amount of useful information, like a UX glossary or a single community of practice."
Maria TaylorKnowledge is Power: Managing the Lifeblood of the Design Org
October 3, 2023
"Using AI tools, you can diverge widely and then converge much faster."
Joe Meersman Pooria SohiUse AI to Drive Outcomes that Go Beyond the Design Sprint
September 25, 2024
"You have to empower your employees before you can pass on care to your customers."
Sara Asche Anderson Jamie KaspszakNot Your Ordinary Re-Brand: Design's Path to Driving Customer Obsession at Best Buy
January 8, 2024
"When I see users saying, oh my goodness, I didn’t know it did that, that’s a clear sign of too much complexity."
David Cronin Uday Gajendar Peter Morville Kendra ShimmellDiscussion
May 13, 2015
"Google’s HEART framework is great because different teams—engineering, product, and design—can all use it."
Kristin Skinner Kamdyn MooreGroup Activity: A Deep Dive Into Value and Outcomes
October 23, 2019
