Authors:
Indi Young, Kunyi Mangalam
"First we need to understand the problem." You hear this phrase more often these days in the applied realm of software development. Because of design thinking and lean UX, there is more awareness of the value of understanding the problem space. However, outside of design teams, no matter if you're in tech, commercial, industrial, or government, there is stiff resistance to taking time to understand the problem [1]. This is due to many factors, one of which is speed-to-solution and efficiency-of-production, and another of which is unfamiliarity with how qualitative data represents a population. The power and value that…
You must be a member of SIGCHI, a subscriber to ACM's Digital Library, or an interactions subscriber to read the full text of this article.
GET ACCESS
Join ACM SIGCHIIn addition to all of the professional benefits of being a SIGCHI member, members get full access to interactions online content and receive the print version of the magazine bimonthly.
Subscribe to the ACM Digital Library
Get access to all interactions content online and the entire archive of ACM publications dating back to 1954. (Please check with your institution to see if it already has a subscription.)
Subscribe to interactions
Get full access to interactions online content and receive the print version of the magazine bimonthly.
