Qualitative Analysis

The Qualitative Analysis Trap (or, Coding Until Blue in the Face)

There is a trap that is easy to fall into when conducting a thematic-style analysis of qualitative data. The trap revolves around coding and, specifically, the idea that after a general familiarization with the in-depth interview or focus group discussion content the researcher pores over the data scrupulously looking for anything deemed worthy of a code. If you think this process is daunting for the seasoned analyst who has categorized and themed many qualitative data sets, consider the newly initiated graduate student who is learning the process for the first time.

Recent dialog on social media suggests that graduate students, in particular, are susceptible to falling into the qualitative analysis trap, i.e., the belief that a well done analysis hinges on developing lots of codes and coding, coding, coding until…well, until the analyst is blue in the face. This is evident by overheard comments such as “I thought I finished coding but every day I am finding new content to code” and “My head is buzzing with all the possible directions for themes.”

Coding of course misses the point. The point of qualitative analysis is not to deconstruct the interview or discussion data into bits and pieces, i.e., codes, but rather to define the research question from participants’ perspectives Read Full Text

Qualitative Data Processing: Minding the Knowledge Gaps

The following is a modified excerpt from Applied Qualitative Research Design: A Total Quality Framework Approach (Roller & Lavrakas, 2015, pp. 34-37).

Once all the data for a qualitative study have been created and gathered, they are rarely ready to be analyzed without further analytic work of some nature being done. At this stage the researcher is working with preliminary data from a collective datasetKnowledge gap that most often must be processed in any number of ways before “sense making” can begin.

For example, it may happen that after the data collection stage has been completed in a qualitative research study, the researcher finds that some of the information that was to be gathered from one or more participants is missing. In a focus group study, for instance, the moderator may have forgotten to ask participants in one group discussion to address a particular construct of importance—such as, the feeling of isolation among newly diagnosed cancer patients. Or, in a content analysis, a coder may have failed to code an attribute in an element of the content that should have been coded.

In these cases, and following from a Total Quality Framework (TQF) perspective, the researcher has the responsibility to actively decide whether or not to go back and fill in the gap in the data when that is possible. Regardless of what decision the researcher makes about these potential problems that are discovered during the data processing stage, the researcher working from the TQF perspective should keep these issues in mind when the analyses and interpretations of the findings are conducted and when the findings and recommendations are disseminated.

It should also be noted that the researcher has the opportunity to mind these gaps during the data collection process itself by continually monitoring interviews or group discussions. As discussed in this Research Design Review article, the researcher should continually review the quality of completions by addressing such questions as Did every interview cover every question or issue important to the research? and Did all interviewees provide clear, unambiguous answers to key questions or issues? In doing so, the researcher has mitigated the potential problem of knowledge gaps in the final data.

 

 

Image captured from: https://modernpumpingtoday.com/bridging-the-knowledge-gap-part-1-of-2/

The Important Role of “Buckets” in Qualitative Data Analysis

An earlier article in Research Design Review“Finding Connections & Making Sense of Qualitative Data” – discusses the idea that a quality approach to a qualitative research design incorporates a carefully considered plan for analyzing, and making sense of, the data in order to produce outcomes that are ultimately useful to the users of the research. Specifically, this article touches on the six recommended steps in the analysis process.* These steps might be thought of as a variation of the classic Braun & Clarke (2006) thematic analysis scheme in that the researcher begins by selecting a unit of analysis (and thus becoming familiar with the data) which is then followed by a coding process.

Unique to the six-step process outlined in the earlier RDR article is the step that comes after coding. Rather than immediately digging into the codes searching for themes, it is recommended that the researcher look through the codes to identify categories. These categories basically represent buckets of codes that are deemed to share a certain underlying construct or meaning. In the end, the researcher is left with any number of buckets filled with a few or many codes from which the researcher can identify patterns or themes in the data overall. Importantly, any of the codes within a category or bucket can (and probably will) be used to define more than one theme.

As an example, consider an in-depth interview study with financial managers of a large non-profit organization concerning their key considerations when selecting financial service providers. After the completion of 35 interviews, the researcher absorbs the content, selects the unit of analysis (the entire interview), and develops 75-100 descriptive codes. In the next phase of the process the researcher combs through the codes looking for participants’ thoughts/comments that convey similar broad meaning related to the research question(s). In doing so, Read Full Text