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