In Vivo Coding

Description

Code data with participants' own telling terms, then unpack and test each term rather than taking it at face value.

In vivo codes use the participants' own words as code labels, preserving their meanings in the coding itself. Charmaz identifies three useful kinds: general terms that everyone 'knows' but that condense significant meaning; a participant's innovative term that captures an experience; and insider shorthand of a particular group. The rigour lies in treating each term as problematic: asking what category it suggests, what implicit meanings it carries, and how people act on it, and comparing usage across participants. In vivo codes do not stand alone; they must be integrated into analytic categories. They also act as a check on the researcher's labels, showing whether the analyst has grasped what matters to participants. Classic examples include replacing researcher labels with the group's own terms after asking what members called themselves.

Attributes

Loss type
Siloed
Effort
Days

Steps

  1. While coding, attend to participants' language and mark terms that seem telling.
  2. Record each term verbatim as a code, with its speaker and context.
  3. In later sessions, ask participants what the term means and how they use it.
  4. Compare instances of the term across participants and situations.
  5. Ask what analytic category the term points to and what actions it is linked with.
  6. Integrate the term into developing categories and use it to check your own code labels.

Sources

  • Constructing Grounded Theory (Charmaz, 2006)

Also known as

  • In vivo codes
  • Participant-term codes

Categories

  • User Research
  • Qualitative Analysis & Synthesis