Researchers can expect to perform analytic actions repeatedly; that this iteration is required is a common observation. Yet, how researchers engage in iteration to progress their theorizing is not articulated. Our analysis provides new insight into what it means to iterate in the service of driving analysis. We examine iteration through the lens of the analytic process of coding in specific research projects. Using a relational definition of coding, we identify the reported coding actions of several studies with rich descriptions of their analytical processes. By doing this, we show that it is useful to understand these coding actions in the context of coding moments that relate to how researchers use the coding actions as their project develops. The moments we identify are making codes, organizing to code, and putting patterns together. To show iteration, we trace the reported coding practices in exemplar articles. These tracings indicate that the reported process is not a fixed or consistent sequence. Rather, iterativity is organized by what is the next needed analytic input required to progress a given situated study.
Locke et al. (Mon,) studied this question.