Interviews

Eight transcripts, a codebook, and every quote checked.

The folder

  • Eight interviews with founders who changed direction early. Fictional, and pseudonymised: F01 to F08.
  • The interview guide: six questions.
  • Your own transcripts work the same way. Only if your data plan allows it: what it reads is sent (What it can touch, Thursday).

Is it really anonymous?

  1. Get it: the download prompt is in the handout, section 7. Then “Set up git here and commit everything.”
  2. “Read the transcripts. Is anything still identifying, even without the names? List it, with the file and line.”

Pseudonymising by hand misses things. Here, three things slipped through.

A codebook first

Read the interview guide and three transcripts. Propose a codebook: six to eight codes, each with a definition and an example. Don’t code anything yet.

Argue with it. Merge two codes, split one, add the one you care about. Then: “Save it as coding/codebook.md and commit.”

Code all eight

Code all eight transcripts with the codebook. Save every coded excerpt in coding/excerpts.csv: founder, line number, code, and the exact quote.

What are the three main themes? For each: which founders, and the two best quotes. Save it as themes.md.

Every quote, checked

Check every quote in themes.md and excerpts.csv against the transcripts, word for word, with a script. List any that don’t match exactly.

A script that compares text can’t be charmed by a confident paraphrase.

Then push

  • “Which founder doesn’t fit the themes? What does that do to theme 1?”
  • “Does anyone contradict themselves?”
  • “Did they plan the change, or does it only look planned afterwards?”
  • “What would a sceptical quantitative reviewer say about theme 2?”

Done early? “Make a table: founder by code, with counts. Which codes always come together?”

Who does what

The agentReads eight interviews in a minute. Proposes codes. Finds every instance. Checks every quote, mechanically.
YouDecide what a code means. Judge the themes. Own the interpretation, and the ethics.

Coding was the slow part. Now the slow part is thinking, which is the part you’re good at.

Next: References, on your paper folder.