Customer Interviews That Actually Change the Roadmap

Interviews often feel productive in the moment and then disappear into a folder. If the roadmap does not change, project plans stay the same, or no action follows, the interview did not help. My goal with interviews is simple: capture real behavior, reduce uncertainty, and turn what I heard into a decision I can stand behind a week later.

This is the playbook I use on consulting projects. It is light enough for a one-person team and structured enough for stakeholders who expect receipts. I prioritize high-impact customers whose individual feedback should carry real weight—for example, the decision maker behind one of your six-figure contracts.

What interviews are actually for

Behaviors, not opinions. What did they do last time, what did they try first, what did they do next.
Constraints. Time, money, policy, approvals, tools they must use.
Language. The exact words customers use to describe their problems. Those words will show up in copy, prompts, and UX. If your work leans JTBD, skim a practical primer first: Jobs to be Done interview basics.

If you only remember one thing: an interview is not a survey. You are not collecting votes. You are collecting stories and constraints that shape the product.

Before you schedule a single call

Write the decision you need to make. One sentence, present tense.
Example: “We will build a self-serve import flow before building team approvals.”
List 3–5 assumptions. These are the beliefs that must be true for that decision to be smart. If it helps to visualize, map them with an opportunity solution tree.
Define success evidence. What would you hear or see that supports or refutes each assumption?
Pick segments. Current users, lost deals, never-used prospects. Aim for variety.
Create a simple screener and incentive. 3–4 quick questions, a reasonable gift card or account credit.

Who to talk to (and how to recruit)

Customers in motion. People who recently tried to do the thing you care about.
Non-fans. Lost leads and churned users are gold. They cost more to recruit, but they will save months.
Light incentive. Enough to respect their time, not enough to buy flattery.
Short window. Book within a 10-day window so the stories are comparable.

If you will interview on a rolling basis, set up a small program for continuous user interviews.

The script that works (30 minutes)

Timebox the interview and stick to it. Ask open questions, then be quiet. Capture artifacts. Watch this video from Sprint about the Five-Act Interview for a live example.

00:00–02:00 Warm-up

“What is your role and what does ‘done’ look like in your week?”

02:00–12:00 The last time story

“Walk me through the last time you tried to ___.”
“What did you try first? Why?”
“What almost stopped you?”
“Can you show me any artifact from that process?” (screenshot, doc, email)

12:00–22:00 Constraints and workarounds

“What tools or policies shape how you do this?”
“When it breaks, what do you do?”
“How do you know it worked?”

22:00–28:00 Weigh the options

“If we changed one thing about this process, what would move the needle first?”
“What would you give up to get that?”

28:00–30:00 Close

“Anything I should have asked?”
“Can I follow up to show a mock and check if I understood?”

Bad vs better (quick rewrites)

Bad: “Would you use a dashboard for this?”
Better: “Show me the last place you looked to check progress.”
Bad: “Do you like our idea for approvals?”
Better: “Tell me about the last time you needed someone’s approval. How did you get it?”
Bad: “How much would you pay?”
Better: “What did this cost last time, including people’s time?”

For question tone, refresh on how to avoid leading questions.

You don’t get what you don’t ask for

Ask for artifacts. People remember poorly. Screenshots, spreadsheets, checklists, emails, tickets, calendar invites are facts.
Ask for numbers. “How long did it take, who touched it, what did it cost, how often does it happen.”
Confirm frequency. “When was the last time” and “how often in the past month” beat “how often in general.”

Turn notes into decisions in one hour

Do not drown in transcripts. Summarize like a product person.

Step 1: Make a highlight reel (15 minutes)
Skim your notes and copy only the moments that changed your mind. Keep exact quotes.

Step 2: Cluster by assumption (15 minutes)
Create three buckets: supports, contradicts, unclear. Drop highlights into buckets under each assumption.

Step 3: Write the one-page decision (30 minutes)
Use the template below and share it with stakeholders.

Decision (one sentence):
We will ____________________________________________.

Assumptions (list 3–5):
1) _________________________________________________
2) _________________________________________________
3) _________________________________________________

What we heard (highlights):
- [Supports A]  "__________"
- [Contradicts B] "__________"
- [Unclear C] "__________"

Call:
We will / will not change the roadmap.

Impact:
- Scope change (add/remove)
- Timeline change (faster/slower)
- Risk notes (what could burn us)

Next validation:
- What we will prototype or measure next
- By when, and how we will know it worked

If you work with RICE or EOS, attach the one-pager to the epic or quarterly objective. It adds to your audit trail when someone asks “why.”

Common anti-patterns and quick fixes

Interviewing to confirm your idea.
- Fix: ask about the last time, not your solution.
Collecting opinions, not behavior.
- Fix: ask for artifacts and numbers.
Talking too much.
- Fix: ask the question and count to five in your head. Teachers call this Wait Time
Treating quotes like votes.
- Fix: cluster by assumption and decide.
Letting insights rot.
- Fix: always produce a one-page decision within 24 hours.

Copy-Paste Resources

Customer interview screener (short)

1) In the last 30 days, have you tried to __________?
   - Yes / No
2) Which best describes you?
   - Evaluating tools / Using a tool / Built an internal workaround
3) Company size:
   - 1–10 / 11–50 / 51–200 / 200+
4) OK with a 30-minute video call? (Gift card included)
   - Yes / No

30-minute script (concise version)

0–2  : Role and "done"
2–12 : Last-time story (first step, obstacles, artifacts)
12–22: Constraints, workarounds, success signal
22–28: One change that moves the needle
28–30: Close + permission to follow up

One-page decision (markdown)

# Decision
We will __________.

## Assumptions
- A:
- B:
- C:

## Highlights
- Supports A: "____"
- Contradicts B: "____"
- Unclear C: "____"

## Call
We will / will not change the roadmap.

## Impact
- Scope:
- Timeline:
- Risks:

## Next validation
- Prototype/metric:
- Owner and date:

Want a pilot set up for your team? Book a 30-minute Customer Interview Sprint

Devin Vinson