The question this lesson answers is simple: how do interview notes become a useful memo when the data are messy, personal, and hard to sort at first?
I keep returning to this because database commentary can fail in the same way. It can name a source, praise a feature, and still miss the part that matters most. The gap is often in the middle, where raw notes become meaning. That is where a memo starts to do real work.
A preparatory memo is not a polished argument. It is a working note that helps me think with the data instead of around it. In grounded theory, this kind of memo is a place to capture what seems to be happening, what keeps repeating, and what may be connected. It is also where I begin the constant comparative method, which means I compare each piece of data with the others to see what stays the same and what changes.
The point is not to force a neat theme too early. The point is to slow down and ask what the data are already showing. If an interview segment keeps returning to shame, exclusion, or a sense of being out of place, I do not flatten those feelings into one vague category. I ask what kind of shame it is, when it appears, and what seems to trigger it.
That habit matters in academic database commentary because databases often get described in broad, shallow ways. A source is called useful, large, or reputable, and the comment stops there. But commentary that is worth trusting has to say what kind of material is inside, what kind of search behavior it encourages, and what kind of user may feel lost in it.
One small example makes this clearer. Imagine an interview note that says a student avoided speaking up because they feared being exposed as not belonging. I would not memo that as “lack of confidence” and move on. I would compare it with other notes and ask whether the issue is fear of judgment, class difference, or a sense of being watched. Those are related, but they are not the same.
That same discipline helps with source commentary. A database can look generous from the outside and still hide hard limits inside. Full text may be uneven. Metadata may be thin. Subject labels may pull users in one direction and away from another. If I do not memo those differences, I end up with a description that sounds informed but teaches very little.
A good memo gives shape to the data before I try to explain them. I start by writing the scene in plain words. Then I mark the repeated idea. Then I name the property, which is a feature that can vary, like fear of exclusion, sense of belonging, or institutional gatekeeping. After that, I ask how the properties relate. Does one lead to another? Does one intensify under pressure? Does one appear only in certain settings?
This is where simple diagrams help. A circle for the core feeling. Arrows for pressure points. Boxes for conditions that seem to surround the event. The goal is not design. It is clarity. A quick sketch can show that several interview comments point to one pattern, even before I know how to write about it.
I find this especially useful when the data are autobiographical in a quiet way. People often speak as if they are talking about one event, when they are also revealing a long pattern. A memo lets me hold both levels at once. It keeps the immediate detail and the larger structure in view.
That same method can keep database commentary honest. I do not need to pretend a source is simple. I need to trace what kind of access it offers, what kind of search it rewards, and where its record is weak or incomplete. When I write that way, I am not selling a source. I am describing how it behaves.
The lesson here is practical. A preparatory memo turns scattered interview data into a working set of ideas. It helps me see repetition, difference, and relation. It also keeps me from mistaking a first impression for an analysis.
What I can do now, with more confidence, is move from a single note to a pattern. I can compare one interview moment with the next, name the properties that matter, and sketch how they fit together. That is the point at which the data begin to speak in a fuller way.
That is the kind of plain result I want The Source List to keep in view: one digital source worth knowing, one search tip, and one honest limitation.