An
×
Our initial research design included identifying a target population, generating quantitative and qualitative survey and interview questions, and recruiting participants using networking techniques that mirrored the career exploration process. We worked in an uncharted space, which made it difficult to implement a strict research design. We struggled with how to approach top-level executives and using the norms of the business world. As we worked, a research framework developed organically.
We repeatedly ran into the question of when to stop collecting data and start synthesizing, fearing that we had not collected enough data for clear patterns to emerge. Also of concern was how to refine the scope of our questions so that we could generate meaningful data and provide relevant answers to our research questions. Our research and interviews indicated that ethnographic methods are used by applied anthropologists on collaborative teams including engineers and MBAs.
Furthermore, we came across the term “thick data,” which is used to describe the contextualized data that ethnographic inquiry provides. This is opposed to the concept of “big data,” which focuses on collecting data points about users. The idea is that thick data will help companies better understand the meaning of the data points they collect in order to generate appropriate responses.
We found that our process of research and synthesis was iterative and closely resembled the design thinking model, indicating overlap between the fields of design and social research. Anthropologists concerned with the future of ethnographic methods should ask what is included in the sweet spot between anthropology and design, what is left out, and whether the values supported by the shared methods are congruent with the goals of cultural anthropology today.
I continued aspects of this research inquiry at UCLA, which resulted in an honors thesis exploring human-centered software development culture.
Thesis Abstract
As the role of digital products expands in the consciousness of 21st century publics, business organizations are increasingly adopting a human-centered design approach to computer software development in an effort to innovate and reach a broader consumer base. Although there are many variations to incorporating human-centered design, they all share a singular philosophy of situating the human user at the center of the design process (Schneider, Arble, Olson, & Wolff, 1980). User psychological and physical needs and expectations are used as a primary focus of design as opposed to expecting the user to adapt to a design focusing on business, logistical, technological or other non-human factors (Greenhouse 2010). These emerging approaches to software design require an internal shift in thinking and adoption of new business practices. Such a transition between traditional software development processes (e.g. waterfall model) and emerging human-centered design methods (e.g. User-Centered Design and Agile) parallel the idea of a shift from modern to postmodern software development culture (Robinson et al. 1998). Through ethnographic research, this paper provides an on-the-ground description of how individuals of a design team at a traditional American company interact as they internalize this significant shift in thinking and practice. The ethnography takes place during a timely period when a hybridity of modern and postmodern software design and development culture can be observed. This period allows researchers to analyze how particular design activities and software development practices are defined through postmodernist culture.