FICTIONAL PRACTICE INTERVIEW
Project: Northstar meeting follow-up study
Interview ID: NS-07
Participant: "Maya" (fictional operations lead)
Interviewer: "Jon" (fictional researcher)
Length: approximately 12 minutes
Created by Vyxora Editorial for practice. No real person, company, or research participant is represented.

[00:00] Jon: Think about the last project meeting you attended. What did you do after the call?

[00:09] Maya: I opened the shared document and cleaned up my notes. I usually write almost everything while people are talking, so after the meeting I have a page of fragments. Then I compare it with the recording if we have one.

[00:26] Jon: What are you trying to find when you clean it up?

[00:30] Maya: First, anything I promised to do. Then decisions. The harder part is figuring out whether something was actually decided. Someone will say, "We should probably launch Thursday," and five minutes later the group is talking as if Thursday is fixed. I don't want to turn a suggestion into a commitment.

[00:55] Jon: How do you handle that now?

[00:58] Maya: I write "proposed" next to it. If I remember, I add the speaker's name. Then I send the notes in chat and ask people to correct them. Usually nobody replies unless something is wrong.

[01:20] Jon: Does that work well enough?

[01:23] Maya: For small meetings, yes. I said in the survey that follow-up takes ten minutes. That's true when it is our weekly check-in and everyone knows the project. For customer calls or planning sessions, it can take forty-five minutes because I replay sections.

[01:48] Jon: What makes those meetings harder?

[01:51] Maya: There are more changes inside the conversation. Last week, the product lead said the onboarding copy was approved. Near the end, legal asked for another review, so it was not really approved anymore. If I only copy the first statement, the notes are wrong. If I only copy the last statement, people cannot see why the task reopened.

[02:25] Jon: What would useful notes show in that case?

[02:29] Maya: The current state first: legal review is open. Under that, show that product approved the copy earlier and then legal reopened it. I want the history, but I do not want to read a transcript to find it.

[02:48] Jon: You mentioned replaying the recording. What are you checking?

[02:52] Maya: Exact wording when a decision is sensitive, and who said they would do something. Speaker labels are messy sometimes, so I listen to the audio before assigning an owner. If I cannot tell, I write "owner to confirm." I would rather leave a blank than confidently put the wrong name.

[03:20] Jon: What do you do with requests from customers?

[03:23] Maya: I used to copy every request into our backlog. That made a huge backlog full of solutions customers happened to name. Now I try to capture the problem underneath. A customer might ask for a weekly email, but what they need is a reliable way to know whether a blocker changed. The email is one possible solution.

[03:53] Jon: Can you give me a recent example?

[03:55] Maya: A client asked for a dashboard during an interview. Later she said she spends Monday morning asking three team leads for updates. The useful note was not "build a dashboard." It was "the project owner cannot see cross-team status without asking each lead." We still kept the dashboard request as evidence, but we did not treat it as the finding.

[04:28] Jon: How do you separate those two in your notes?

[04:31] Maya: Not consistently. Sometimes I have a heading called requests and another called pain points. Sometimes everything ends up under takeaways. That is one reason the notes are hard for someone else to use.

[04:50] Jon: What would you want a tool to do for you?

[04:53] Maya: Pull out the decisions, tasks, questions, and themes, but show me where each one came from. I need to click back to the words around it. A quote by itself can be misleading. I also need to change the output. The first pass will never understand all our internal context.

[05:25] Jon: Would you trust an automatic summary?

[05:28] Maya: As a draft. Not as the record. I would check decisions and names every time. For a casual internal sync, I might skim more lightly. For a customer promise or legal issue, I would go back to the recording and transcript.

[05:51] Jon: Earlier you said you write almost everything during a meeting. Does that affect the conversation?

[05:57] Maya: Yes. I miss follow-up questions because I am typing. But if I stop typing, I worry the details will disappear. Recording helps, except some customer calls cannot be recorded. In those calls I still need manual notes.

[06:24] Jon: So would recording solve the problem?

[06:27] Maya: No. It gives me a source to check. It does not decide what matters, and it does not fix a vague conversation. Also, permission matters. Our customer agreement allows recording only when everyone on the call agrees.

[06:50] Jon: How do you organize several interviews about the same topic?

[06:54] Maya: Poorly. Each interview has its own document. I make a separate synthesis page and copy findings over. Then I lose the link back to the interview. If someone challenges a finding, I have to search through six documents.

[07:21] Jon: What do you mean by a finding?

[07:24] Maya: A sentence that explains a pattern relevant to our question, with examples behind it. Although with one interview I would call it an observation, not a pattern. I learned that distinction after overstating a customer comment in a planning meeting.

[07:48] Jon: What happened?

[07:50] Maya: One customer said the setup checklist was confusing, and I wrote "customers cannot complete setup." Engineering treated it like a broad failure. Later interviews showed that experienced admins were fine; new admins did not understand one permission step. My note was too broad and dropped the condition that made the comment useful.

[08:25] Jon: How would you write it now?

[08:28] Maya: "One first-time admin could not tell which permission was required at step three; check whether other new admins have the same problem." Then I would link the quote and add it to the next interview guide.

[08:49] Jon: What tends to get lost when notes are shortened?

[08:52] Maya: Exceptions, uncertainty, and sequence. People like clean bullets, but the conversation is usually less clean. "Launch Thursday" is easy to remember. "Thursday is possible if legal approves the copy by Tuesday" is the useful version.

[09:18] Jon: Is there anything you would not want in shared notes?

[09:21] Maya: Personal details that do not affect the project. Customer interviews sometimes include names of coworkers or internal problems. We remove names unless they are necessary, and access to raw transcripts is narrower than access to the synthesis.

[09:48] Jon: If you could change one part of your current process, what would it be?

[09:52] Maya: I would keep every claim attached to its source passage while I edit. Right now, evidence gets separated from the note during copy and paste. Once that happens, people remember the polished sentence and forget how tentative the original answer was.

[10:19] Jon: What would tell you the process was working better?

[10:22] Maya: During the next meeting, someone could open the note, see the current decision and why it changed, then jump to the relevant passage if they disagree. For research, we could see which interviews support an observation and which ones contradict it.

[10:50] Jon: You said "which interviews support an observation." Would a count be useful?

[10:55] Maya: Sometimes, but I would be careful. Three short mentions are not automatically stronger than one detailed account. A count can help me find where to look; it cannot do the interpretation for me.

[11:17] Jon: What should I have asked that I did not?

[11:21] Maya: Ask who is responsible for reviewing the notes. Tools make drafts easy, but the team still needs a person who can say, "Yes, this is the decision we made," or "No, that was still a proposal."

[11:42] Jon: Who does that on your team?

[11:45] Maya: Usually me for operations meetings. For customer research, the researcher owns the analysis and the product lead reviews the implications. We have not written that down, though.

[12:03] Jon: Thanks. Is there anything you want to correct before we finish?

[12:07] Maya: The ten-minute follow-up answer. I do not want that quoted without the condition. Ten minutes is the easy weekly meeting. The complicated calls take much longer.

END OF FICTIONAL TRANSCRIPT

Practice note: This transcript deliberately includes a correction, a changed decision, a proposed solution that points to an underlying need, an exception, uncertainty about ownership, and an explicit limit on what one interview can support.