Case Analysis Meeting

Description

A short, form-guided meeting in which the researcher closest to a case and one or more colleagues summarise its current state, explanations, rival interpretations and next steps.

In multi-case work the meaning of each case gets lost in the flow of fieldwork, write-ups and coding. A case analysis meeting brings the field-worker most familiar with a case together with a critical friend or co-researchers. A recorder takes notes under fixed headings on a form: main themes, impressions and summary statements; explanations, speculations and hypotheses; alternative interpretations, minority reports and disagreements; next steps for data collection; and implications for revising the coding scheme. The most involved researcher opens on the main themes, others ask clarifying questions, and the recorder files points under the right heading and summarises back from time to time. The tone is friendly scepticism: no generalisation goes unillustrated, and rival hypotheses are kept alive. Notes are copied to everyone and can themselves be coded. The book advises keeping meetings to about an hour and a half and not letting case data pile up before holding one. For UX teams this is a disciplined version of the synthesis huddle, with an explicit slot for alternative explanations and for changes to the codebook.

Attributes

Loss type
Vestigial
Effort
Hours

Steps

  1. Prepare a one-page form with headings: main themes; explanations and hypotheses; alternative interpretations and disagreements; next steps for data collection; implications for coding.
  2. Schedule the meeting soon after a batch of sessions for a given case (a customer, segment or site), with the researcher who ran them, a colleague and a recorder.
  3. Start with the lead researcher's main themes; others ask for evidence and examples.
  4. Record points under the relevant heading as the talk moves, and prompt the group to reach the later headings if it stalls.
  5. Explicitly capture rival explanations and what data would separate them.
  6. Circulate the notes, plan follow-up questions and revise codes before the next round of fieldwork.

Sources

  • Miles, M. & Huberman, A. M., Qualitative Data Analysis: An Expanded Sourcebook, 2nd ed. (1994)

Also known as

  • Case analysis meeting form
  • Structured case debrief

Categories

  • User Research
  • Qualitative Analysis & Synthesis