Make coding for qualitative data section easier to understand

At the moment the analyzing your data episode starts with a section "Start by labeling the qualitative data".

At the STRUDEL contributor workshop I gave some feedback that this section is quite hard to know how to do if you're not experienced in qualitative research. @jlcohoon and I had a really fantastic discussion about whether the answer is "yes, it is hard" or whether we can make it simpler.

We realised that I was expecting there to be a step where the interview transcript and notes were turned into a list of "complete thoughts" that were THEN labelled as part of the coding process. This doesn't map to how many UX researchers actually conduct their qualitative analyses though!

One idea (I think Mary had it!) was to use the skit from the first part of the talk to show how the transcript and researcher notes can be used to capture "complete thoughts" and label them.

Another idea is to include in the lesson that its ok to not code everything, but rather read your notes and pull out a few themes that seem actionable. The point here is what makes the analysis *rapid* usability testing!

The last note to capture here is @jlcohoon's comment of "I just want them to know not to rely on their memory, to actually use the notes and transcripts" - which I think is very easy to understand and an important point! Probably a good opener to this episode?

Begin with the analyzing your data episode and its “Start by labeling the qualitative data” section; review the workshop feedback and the competing ideas in this issue. Done means the lesson gives inexperienced learners a clear way to use notes and transcripts for rapid analysis, while making the intended coding or theme-selection process understandable.

Written by the indexing model from the issue text.