There is a version of “talk to your users” that ends with a folder of recordings and zero clarity. That version is the one most founders are running. The advice to interview your users is everywhere. The script is nowhere. So a solo founder books three calls, asks the questions they think a researcher would ask, hears five different versions of “I love it, keep going,” and walks away more confused than before they started.
This article is the user interview template that fixes that. Fourteen behavior-anchored questions across four phases, recruiting copy that pulls a 30 to 45% reply rate from active users, a scoring rubric, good-versus-bad answer examples, and a copy-paste version you can drop into a Google Doc or Notion page in under five minutes. If you have launched and you have users, you can run your first interview today and have a different read on your product by Friday.
TL;DR. A user interview template for post-launch founders is a fixed sequence of behavior-anchored questions designed to surface what people did, not what they predict they will do. The template below covers 14 questions across four phases (context, last-time use, pain mapping, willingness-to-pay), a one-paragraph recruiting message, a three-bucket scoring rubric, and example answers so you know a strong one when you hear it. Run it on five users in your first two weeks post-launch.
▸ GRAB THE TEMPLATE Skip the article, run the calls. The full 14-question template ships as a printable PDF worksheet (9 pages, answer fields, scorecard, decision tree) and a Notion-ready markdown file you can duplicate into your workspace in under two minutes. |
What Is a User Interview Template?
A user interview template is a structured sequence of open-ended, behavior-anchored questions a founder uses on a 25 to 30 minute call with a current or former user, ordered the same way every time so cross-call comparison stays clean. The template focuses on what the user has done in the past, in specific moments, with specific tools. It avoids predictions, hypotheticals, and feature votes.
Predictions from users are guesses. Past behavior is data. The template treats the second as gold and the first as noise.
This is the methodology gap at the center of the PMF-at-50-users idea. The advice says have three conversations. It rarely says what to ask in them.
Why Do Most User Interviews Produce Nothing?
Most user interviews produce nothing because the founder asks “would you use this?” and the user, being polite, says yes. The Jobs-to-be-Done research community, led by Bob Moesta’s work at the Re-Wired Group, spent two decades documenting this pattern across more than a thousand buying-decision interviews and arrived at one rule. Hypothetical questions about future behavior produce results closer to a coin flip than to a forecast. Past-tense questions tied to a specific moment perform far better.
The other failure mode is worse than guesswork. It is selective listening. The founder hears the kind compliment, writes it down, and quietly buries the story about the user closing the tab three minutes in. The interview happened. The data was there. The founder filtered it.
Both failures share one cause. There was no template, so there was no protocol. With no protocol, the conversation drifts toward whatever each user wants to talk about. With a protocol, the user goes where the founder needs them to go.
Your fog about what users want is not a competence problem. It is a methodology problem. The fix is mechanical.
What Six Rules Must Every Question in a User Interview Template Pass?
Every question in this user interview template passes six rules before it gets used in a call.
Rule | What It Means | What It Filters Out |
Past-tense | Asks about a moment that has already happened | “Would you use this?” |
Behavior-anchored | Asks what they did, not what they think | “What do you think of the design?” |
Specific moment | Pins to one occasion, not a pattern | “How often do you use it?” |
Open-ended | Cannot be answered yes or no | “Did you find it useful?” |
Story before reasoning | Asks for the sequence of events before the explanation | “Why did you sign up?” asked first |
Compliment-resistant | Cannot be answered with politeness alone | “Do you like it?” |
What Are the 14 Questions in the Template?
These 14 questions are the script. Run them in this order. Do not improvise the order on calls one through five. After five interviews you will have a base of comparison data, and you can start to adapt with judgment behind you.
Phase 1: Context (3 questions)
Walk me through what you were doing in the hour before you signed up. Where were you, what were you trying to get done?
What had you tried before us that wasn’t working for you?
The moment you decided to give us a shot, what did you tell yourself you wanted out of it?
Phase 2: The Last Time They Used Your Product (5 questions)
When was the last time you opened the product? Walk me through that day, hour by hour if you can remember it.
What were you trying to get done in that specific session?
What did you do first inside the product? What happened next?
At what point did you stop using it? What was happening right before you stopped?
What did you do immediately after you closed the tab?
Phase 3: Pain Mapping (4 questions)
If we shut down tomorrow and you got a refund, what would you do instead?
What is the closest thing to us you have used? How does ours compare in your week?
Tell me about the most frustrating moment you have had with the product. What was happening in your day right before that moment?
When you've tried to solve this problem before, what's the one thing that's been hardest to get right?
Phase 4: Willingness to Pay (2 questions)
Pretend you told a friend about us last week. What did you say to convince them to try it?
If we doubled our price tomorrow, what would you do?
That is the script. Fourteen questions, four phases, 25 to 30 minutes if you keep moving.
Want a copy-paste version? Open a blank Google Doc or Notion page, paste the 14 questions above into a numbered list, add three rows at the bottom for your A/B/C scoring rubric, and save it as your master user interview template. PopHatch users get the same template pre-loaded inside the PopHatch workspace with the rubric attached and a notes column tied to call transcripts.
How Do You Recruit Users for an Interview?
You recruit by sending a one-paragraph email or DM to your most active users, your most recently churned users, and your most recently signed-up users. Three pools, equal weight. Send within 30 minutes of finishing the previous call so you don’t lose context between conversations.
The message that works:
Subject: 20 minutes? Founder of [product] here.
Hey [first name],
I’m the founder. I’m trying to figure out what is and isn’t working for the people who signed up in the last month. You’re one of them.
Could I take 20 to 25 minutes of your time on a video call this week? I am not selling you anything, I am not running a survey, and I will keep your name off any notes. I just want to hear about your day, your week, and where this product fits or doesn’t.
If yes, here’s my calendar: [link].
If no, totally fine. A two-line reply telling me what made you stop logging in would be the second-best thing.
Thanks for trying us out either way.
[Your first name]
Three things this message does. It tells them you are the founder. It asks for a small commitment with a fallback even smaller. It gives them an out that still gets you a data point. Active users reply at 30 to 45%. Churned users at 15 to 20%, which is plenty for the patterns you need.
How Do You Interpret What Users Say in an Interview?
Score each interview against three buckets within an hour of finishing the call, before the next one starts. Memory of vocal tone and pause length decays in 90 minutes. Score before it does.
Bucket | What It Captures | How to Weight It |
A. Behavioral | What they did. Timestamps, tool names, sequence. | 100% weight. Decisions live here. |
B. Reasoning | Why they say they did it. | 50% weight. Treat as a hypothesis. |
C. Prediction | What they claim they will do. Capture for reference. | 0% weight. Score, do not decide on it. |
If three users tell you “I’d use this every day,” and the dashboard shows two of them have not opened the app in two weeks, the prediction is false and the absence is the answer. Score the absence.
The cross-call pattern you are looking for is repetition in Bucket A. The same pre-signup moment described by three users in slightly different words is a customer segment. The same first-session friction described by four users is a product gap. The same workaround described by two users is a feature waiting to be promoted.
This is the same disciplined isolation work that runs through how to find product-market fit and how serious operators think about niche market examples. You are sorting noise from pattern, one specific moment at a time.
What Does a Good User Interview Answer Look Like?
A good answer is anchored in time, place, and prior tool. A weak answer is general, polite, and self-flattering. Three examples from the 14-question template, side by side.
Question | Weak Answer (score it low) | Strong Answer (score it high) |
When was the last time you opened the product? Walk me through that day. | “I use it pretty often, maybe a few times a week.” Generic, no anchor, no behavior. Probe again. | “Tuesday around 11pm. I was on the couch, I had Notion open already, my CSV import had failed, so I switched to your tool to clean it up.” Specific time, place, prior tool, trigger. |
If we shut down tomorrow and you got a refund, what would you do instead? | “I would probably find a similar tool. There are a lot of options out there.” No name, no path, no urgency. They are not depending on the product. | “I would go back to the spreadsheet I was using before. I have not found anything that does the cohort filter the way you do, so I would just live with the manual export again.” Names the alternative, names the gap. |
If we doubled our price tomorrow, what would you do? | “I would probably keep paying. It is worth it.” Polite, no thought given, almost certainly false. Score zero. | “I would stay through the end of the quarter and start looking. At $38 I am comparing you to Mixpanel, which we already have. At $19 I do not bother comparing.” Reveals competitive frame and price ceiling. |
If the user gives you the weak answer, probe one layer deeper before moving on. “Can you put a date on the last time? Tuesday afternoon, Wednesday morning?” “What were you doing in the 10 minutes before you opened it?” Anchors come back in the second pass roughly half the time.
Why Past Behavior Beats Predictions
A short note from the music industry, because the parallel matters. From where I sat at Warner Music Group, the listener surveys we ran in the 2010s asked fans what they wanted next. They told us. The next year, their streaming behavior contradicted the survey on almost every meaningful axis. The thing that predicted what listeners would do was what they had already done in the prior 30 days.
Founders rediscover this pattern with every cohort of new users. The interview template above is one way to stop rediscovering it.
There is a counterpoint worth sitting with. Some product decisions are forward-looking and have no behavioral history to anchor on. A new pricing tier, a new persona, a new geography. For those, you supplement interviews with a small structured experiment. The interview tells you the question. The experiment tells you the answer.
What Do You Do After Five Interviews?
After five interviews, you have enough to pick one of four decisions. Each one keys off a pattern across calls, not the strength of any single conversation.
If the same pre-signup moment shows up in three or more calls, your customer segment is sharper than your marketing currently reflects. Rewrite your homepage hero around that moment within seven days, update the onboarding copy to match, and audit your acquisition channel for more of that segment.
If the same first-session friction shows up in three or more calls, your activation flow is the priority. Block one week, defer the rest of the roadmap, and ship the fix. Re-recruit five new users post-fix and run the template again to compare friction timing before and after.
If the same workaround shows up in two or more calls, you are looking at a feature with paid willingness already proven. Build the simplest version this month and ship it first to the users who described the workaround.
If no pattern shows up across five calls, you do not have a product problem yet. You have a segment problem. Audit the channel the users came from. If everyone came from one source, the channel is doing the segmenting for you. Re-recruit from a different acquisition source and run the same 14 questions again. The PMF-at-50-users guide goes deeper on what segment quality looks like before you try to measure fit.
▸ TAKE IT WITH YOU The whole user interview template, packaged. Nine-page printable PDF with answer fields, recruiting email, scorecard, and decision tree. Plus a Notion-ready version you can duplicate per call. No email gate. |
Where the User Interview Template Stops Being Enough
Five interviews give you a decision. Twenty interviews give you a different problem. Once you start running the user interview template every two weeks, the work shifts from collecting answers to recognizing patterns across calls. You start seeing the same pre-signup moment in slightly different words across three users from different acquisition channels. You stop trusting your memory of which users said what. Your scoring rubric, which fit on a sticky note in week two, is now a 60-row spreadsheet you don’t have time to maintain.
That is the moment most solo founders quietly stop interviewing. Not because the work stopped paying off. Because the work started outpacing the spreadsheet.
This is the gap PopHatch is built into. PopHatch keeps the user interview template as a living document, scores each call against the same rubric automatically, surfaces the segment-level pattern by call number five, and links it back to the dashboard metric the pattern is supposed to move. The template stays the same. The pattern recognition stops being your second job.
Free 14-day trial. Founding Member pricing is locked at $19/month for the first 12 months.
Run the template, paste the transcripts, and let PopHatch pull the segment pattern out for you. pophatch.com