Egor Urvanov

How to run and analyze interviews about AI useA 30-minute script, an analysis prompt and an Airtable table

A 30-minute call script, rules for staying on topic, a short company-wide questionnaire, interview analysis with ChatGPT or an agent using a ready prompt, and a said-versus-measured check against the report data.

· 16 min · · Research

Interview design based on recommendations from @Kseniya_Vasil. People, groups and numbers for the interviews come from the ChatGPT Enterprise usage report. It also holds the business task: what the company decides, who decides, and by which signs.

Here the analysis takes four steps: the conversation text goes to ChatGPT with the same prompt every time, the answer is copied into the person’s row, the table is grouped by difficulty, and repeats are checked with a company-wide questionnaire. What people say is compared with the report data. Below: the call script, the table and the analysis prompt.

Voice
Call30 mintl;dv · GranolaNotesTranscriptInto Notes
Text
QuestionsIn chatFollow-up1 messageChat logCopied to Notes
AirtableEverything in one table16 records
NameNotesFormatFrequency, self-reportedPer reportStatusHana SatoHost [00:00]: Think back to the last…voiceweeklyweeklyDonePavel Novak[27.09 10:15] Host: Describe the last…textregularlydoesn't use≠DoneNadia RahimiHost [00:00]voiceoccasionallyoccasionallyDone

Choosing a format

Criterion Voice Text
Depth of answers
Follow-up in the moment
How many people you can reach
Respondent's time30 min10 min
Risk of going off topic

Dots are a score from 1 to 5. For risk, more dots is worse.

Mix: the respondent picks the format
InvitationBy direct messageUp for a call?30 minutes
yesvoice call with a note-taking assistant
notext same questions, one at a time, in chat
Takeaway
In this exampleVoice scores 5 of 5 on depth, text scores 5 of 5 on reach. Each person picks the format.
In generalWhen people choose the format themselves, fewer decline. The formats differ in depth: a call gives a detailed story with follow-ups, a chat gives short answers. So chat answers help find cases and topics, but they are not treated as equal to calls. Voice is the main format; chat is for those who cannot take a call. A company-wide questionnaire is a separate tool, written after the interviews.
Next stepOffer both formats in one sentence in the invitation: "Shall we do a 30-minute call, or would you rather answer the questions in chat?"

Preparing for the meeting

  • Mention the note-taking assistantIn the invitation and at the start of the call: the assistant takes notes and a transcript that only the team sees, and answers go into the report without names. With Granola, no audio is kept
  • tl;dv or Granolatl;dv is connected to the calendar and joins the Google Meet or Zoom meeting on its own. Granola works without a bot, using your computer audio, and keeps only the transcript and notes
  • Airtable row created in advanceName, group and numbers from the table of all people, status "In progress", before the first message
  • Guide open on a second screenSeven script blocks and a 30-minute timer
  • One host, no note-takingtl;dv or Granola does the transcript, ChatGPT does the analysis
Takeaway
Next stepBefore the meeting, check that tl;dv sees the meeting in the calendar or Granola is running on your computer, and create the Airtable row, so the call is left with nothing but questions.

A 30-minute script

2
3
8
5
4
5
3

Minutes per block

  1. 1
    Intro
    "I'm looking at how people in the company actually get their work tasks done. This isn't an evaluation of you. Both successful and unsuccessful cases are equally useful to me. A note-taking assistant is with me: only we see the transcript, and answers go into the report without names. May I turn it on?"
  2. 2
    Role and context
    "What do you spend most of your week on?"
    Which tasks repeat · where you look for information and draft things
  3. 3
    The last work task
    "Think of the last work task that took you noticeable time. What did you need to get?"
    What means you had · what you chose and why · how you got to the result
  4. 4
    Result and effort
    "What did you end up with, and how much effort did it take?"
    What you used as is · what you finished yourself · what constraints there were: data, access, security
  5. 5
    A successful case
    "Think of a time a similar task went well. What was different then?"
    Tool · data · preparation
  6. 6
    Quitting and switching
    "Have you ever stopped using a tool or switched to another? How did that go?"
    Which tool · what you switched to · why. If this never happened, skip it
  7. 7
    Wrap-up
    "What didn't I ask that matters for understanding your work?"
    Thank them · say the answers go into the shared analysis without names
If the person doesn't mention AIDon't ask why they don't use it. Ask how they did the task and which options they considered. Ask about AI only if the person named it as a possible option themselves
Takeaway
In this exampleThe last task, result and effort take 13 of 30 minutes; the successful case and quitting or switching take another 9.
In generalThe conversation is built around the work, not the tool. That shows where AI helps, where the person chose another way, and where no new tool is needed. The successful case shows what already works; quitting and switching show why tools get replaced.
Next stepSet a timer: by minute 5, move on to the last work task. If not, cut the context down to one question. Pick the task topic for the person: their tasks show up in Project themes.

Staying on topic

Parking lotOff-topic points go into a separate field; come back to them in the last 2 minutes
One question at a timeNo "and also…" in the same sentence
Back to the caseGeneral opinion → "Can you recall a specific time?"
Don't defend the toolAnswer criticism only with "What happened next?"
5-second pauseStay quiet after an answer: people often add the key point themselves
Don't suggest solutionsNo ideas of your own, no names of other products
Situation → what to say
SituationHost's line
Asks for a new feature"When did you last need it? What did you do then?"
Drifts into complaints about processes"I'll put that in the parking lot. Back to the report task: what happened after?"
Answers with "usually" and "always""And how did it go the last time?"
Asks for the host's opinion"I'll share at the end. Right now what matters is how it works for you"
Block time is up"That's important, let's note it. I'll move to the next question"
Takeaway
In this exampleFive common situations, each with a line that brings the conversation back to the episode.
In generalBehind a feature request there is a specific case, and that case is what you need. The request itself is useful later as a hint about where to look for the problem.
Next stepKeep the phrase table next to the guide and write every feature request verbatim into a separate table field for off-topic items.

Logging in Airtable

The table keeps everyone in the sample, their conversations and the report data in one place. Decision: whom else to invite so each group has enough interviews, whom to send a follow-up, and which gaps between self-reported and measured use to discuss with the person.

tl;dv · GranolaTranscriptAirtableNotes field in the person's row

Voice: the tl;dv or Granola transcript is copied into the Notes field. Text: the chat log is copied into the same field with the date and time of each message.

One table: one row per person
AName≡Notes◉Format◉Group◉Status◉Frequency · self-reported◉Frequency · per reportƒ≠#Tokens · 3 mo#$ / 3 mo▦Activity
1Hana SatoHost [00:00]: Think back to the last time you…voicecodeDoneweeklyweekly=21.9M43825.09
2Luis MorenoHost [00:00]: Thanks for making the time…voicecodeDoneregularlyweekly≠12.7M39624.09
3Mira Castellano[26.09 18:40] Host: What result were you expecting…textagentPartialregularlyregularly=3.9M9726.09
4Jonas KellerHost [00:00]: What do you spend most of your…voiceresearchDoneweeklyweekly=1.1M1926.09
5Ben OrtizCodex onlyAwaiting replyCodex only3.2M6422.09
6Pavel Novak[27.09 10:15] Host: Describe the last task…textinactiveDoneregularlydoesn't use≠00—
7Sara QuinninactiveDeclineddoesn't use00—
8Nadia RahimiHost [00:00]: What did you do in ChatGPT yesterday…voiceother toolsDoneoccasionallyoccasionally=0.3M620.09
9Elif DemirprojectsIn progressweekly1.8M4127.09
16 records · 9 shown

ChatGPT fills in the orange field from the conversation in Notes. "Per report", "Tokens", "$" and "Activity" come from the ChatGPT Enterprise usage report. The "≠" field is a formula that compares the two frequencies.

Reading the table: what each column gives you
ColumnSourceWhat it affects
Name · Group"Eight groups" samplewhich way of getting tasks done the person represents
Notestl;dv, Granola or chat logsource for every field; any conclusion is checked against a quote
Formathostanswer depth: a chat has less detail than a call
Statushostnext action: remind, follow up, or replace the person
Frequency · self-reportedChatGPT takes it from the conversationhow often the person says they use AI
Frequency · per reportreport · adoption depthhow often they use it according to console data
≠Airtable formula: compares the two frequenciesno match: a question to clarify in the interview, since the report only sees the corporate tool for 3 months
Tokens · 3 moreport · top by spendamount of work in the corporate tool over 3 months, for sampling, not for weighting the answer
$ · 3 moreport · leaderboardspend over 3 months, for sampling, not for weighting the answer
Activityreport · users exportdate of the last action: long ago means a candidate for the "Tried and quit" group
How to read the sample rows
RowSignalWhat to do
Hana Satofrequencies match · $438 on code · Donethe highest spend on code: a conversation about her last task shows whether the current tool is enough
Luis Moreno≠ says "regularly", actually weeklyclarify: which tasks he counts as AI work
Pavel Novak≠ "regularly" with zero tokensclarify: which tools he uses and for which tasks
Mira CastellanoPartialsend one follow-up: where in the task they had to finish by hand
Ben OrtizAwaiting reply · Codex only · $64send a reminder: without him the "Codex only" group stays empty
Sara QuinnDeclinedreplace by the replacement rule: the next candidate of the "Inactive" group
Elif DemirIn progress · 7 active projectsschedule a call; fill in self-reported frequency after the conversation
Self-reported vs data: what to clarify in the interview
Measured in the interview
Pair in the report
If they differ, clarify
How often they use it
which tools the person uses and for which tasks
Main task
which tasks the person counts as AI work
How many tasks it covers
which projects are alive and for which tasks
What else they use
what these tools are and for which tasks; record them as a way of working
How much time it saves
no pair
self-reported only

Data limits: the report only sees the corporate tool and only for 3 months. Personal accounts and other tools do not show up in it, so a mismatch is a question to clarify, not a conclusion.

Statuses of 16 invitees
Done · 9
2
2
2
1
DonePartialAwaiting replyIn progressDeclined
Takeaway
In this example9 of 16 invitees gave an interview: the "Done" share is 56%. Pavel Novak's self-reported frequency doesn't match the report.
In generalOne row per person keeps the report data, format, raw conversation and status together. The statuses show whether you have enough people: the "Done" share among invitees tells you how many to invite so each group gets the needed number of interviews. A gap between self-reported and measured use is a question to clarify: the report only sees the corporate tool for 3 months.
Next stepUpdate the status right after each conversation. Keep the needed number of interviews in each group: with a 56% "Done" share, invite four people for two interviews per group. Send one follow-up to everyone marked Partial.

Text: wording

In a chat or a questionnaire it is hard to ask again, so a poorly worded question ruins the answer with no chance to fix it. Five common mistakes:

leading
How convenient is the tool for you?
Describe the last work task that took you noticeable time.
provocative
Why don't you use the tool if the company pays for it?
How did you do your last task of this kind? Which options did you consider?
feature request
What features are you missing?
At what point in your last task did you have to finish the work by hand?
hypothetical
Would you use it more if it had an agent?
What did you do the last time the result didn't work for you?
double-barreled
What do you do in the tool and how often?
What was the last task you did with AI?
Takeaway
In this exampleAll five fixed questions ask about a past episode.
In generalQuestions about convenience, features and the future collect opinions. A purchase decision rests on what people have already done, so a good question asks about a specific past case.
Next stepReread the chat and questionnaire questions and rewrite every question containing "convenient", "would you like" or "which features" into a question about the last work task.

Fill the table with Claude Code

The whole table can be handed to an agent: Claude Code or any other MCP-capable agent connects to Airtable and creates rows, pulls report data and analyzes conversations on its own.

Claude CodeOr any agent with MCP supportAirtable MCPReads and writes the tableAirtableAll fields and statuses
  • Create rowsFrom the list of people selected for interviews: name, group, status
  • Pull in report dataTokens, $, activity, frequency per report
  • Analyze NotesWith the same prompt as in ChatGPT: fields, difficulties, self-reported frequency, quotes
  • Update statuses"Partial" (incomplete answer) if the analysis contains "no data"
Takeaway
In this exampleThe agent creates rows, pulls in the report, analyzes Notes and updates statuses: four steps with no manual entry.
In generalThrough MCP the agent works with the table directly, leaving the researcher the conversations and checking conclusions against quotes. One analysis prompt for the agent and for ChatGPT keeps rows comparable.
Next stepConnect Airtable MCP to Claude Code and start with one command: "Create rows for the people on the list with status In progress".

Questionnaire

The questionnaire is written after the interviews, once you know which tasks and difficulties occur. It goes to the whole company to learn how widespread they are. Questions are short, and the answer options come from the interview analysis.

  1. 1
    Which of these tasks do you do at work?choice: tasks from the interviews · other, open fieldtasks
  2. 2
    How often do you do these tasks?choice: every day · every week · less often · I don'ttask frequency
  3. 3
    Which tools do you use for them?choice: ChatGPT · Claude · Cursor · another AI tool · I don't use AItools
  4. 4
    Which difficulties do you run into in these tasks?choice: difficulties from the interviews · I don't run into any · other, open fielddifficulties
  5. 5
    How often does this difficulty get in the way?choice: in almost every task · sometimes · rarelydifficulty frequency
  6. 6
    How much does it matter for the result?choice: gets in the way a lot · gets in the way · barely mattersimpact
  7. 7
    How do you work around this difficulty now?open field · I don'tworkarounds
  8. 8
    What else matters that the questions missed?open fieldanything missed
Takeaway
In this exampleEight short questions: six multiple-choice with options from the interviews and two open fields.
In generalThe interviews show which tasks and difficulties exist; the questionnaire shows how many people face them and how much they get in the way. The options "I don't run into any", "I don't use AI" and the open field catch what the interviews missed.
Next stepCollect the answer options from the interview analysis and send the questionnaire to the whole company. Count what share of people face each difficulty, how often, and how much it gets in the way. These shares feed the decision procedure in the report.

Interview analysis: the analysis prompt and a check against report data

  1. 1
    Give the Notes text to ChatGPT
    With the same prompt for every interview
  2. 2
    Move ChatGPT's answer into the person's row
    Task, context, chosen way, result, effort, constraints, difficulties, self-reported frequency
  3. 3
    Group the table by difficulty
    People with the same difficulty end up next to each other: you see how many there are and from which groups
  4. 4
    Check with the questionnaire
    Repeats become answer options in the company-wide questionnaire; the team breakdown is compared with Uniformity

Prompt for interview analysis

Below is a conversation with an employee about their work tasks.
Return strictly by field, only what the person said themselves:
1. Task: the last specific work task
2. Context: for whom and why, what means they had
3. Chosen tool or way, and why
4. Result
5. Effort: time and manual rework
6. Constraints: data, access, security
7. Difficulties: categories from the list {categories from the report's sign table} or "no difficulties"; if none fits, a new category in your own words
8. Self-reported frequency: weekly / regularly / occasionally / doesn't use / unknown
9. 1–2 verbatim quotes
If something is not in the conversation, write "no data" and don't make it up.

{text from Notes}
1 person
case
repeats across several
check with the questionnaire
questionnaire confirmed
into the decision procedure
Takeaway
In this exampleA difficulty for one person is a case; a repeat across several is a reason to check with the questionnaire.
In generalThe analysis keeps the whole task, not just the difficulty: without the context, the chosen way and the effort you cannot tell whether a new tool is needed. A repeat in interviews shows what to check, not how many people face it: only the questionnaire shows that. One prompt for all conversations keeps fields comparable, and "no data" stops ChatGPT from making things up.
Next stepOnce several analyses have piled up, group the table by difficulty and move repeats into the answer options of the questionnaire. Record "no difficulties" as a result. Take categories from the report's sign table and add new ones if none fits. The pilot decision follows the procedure in the report.
Common questions

How to analyze an interview with ChatGPT

The conversation text from the Notes field goes to ChatGPT with the same prompt for every interview. The answer is copied into the person’s row: task, context, method, result, costs, constraints, difficulties, frequency as stated. Then the table is grouped by difficulty.

Can an agent do the interview analysis

Yes. Claude Code or another agent with MCP support connects to Airtable, creates rows, pulls report data and analyzes Notes with the same prompt. The researcher keeps the conversations and checks conclusions against quotes.

How to compare what people say with the data

The table has two fields: frequency as stated and frequency by the report, with a mismatch flag next to them. Mismatches are discussed with the person rather than silently corrected.

How to analyze calls and text replies together

The text conversation is copied into the same Notes field with the time of each message. Text answers help find cases and themes, but they are not treated as equal to calls.

Further reading

Interview design based on recommendations from @Kseniya_Vasil. All names, teams and numbers in the examples are fictional.
  • AI
  • custdev
  • interviews
© 2026 Egor Urvanov