The Problem Interview Method: 15 Questions That Reveal Buying Intent

What Is a Problem Interview?

A problem interview is a structured customer-discovery conversation used to understand whether a specific group of people experiences a problem that is frequent, costly, frustrating, or strategically important enough to justify action. The emphasis is on past events, current behaviour, existing alternatives, and buying conditions rather than reactions to a proposed product.

A good problem interview helps you understand:

• how often the problem occurs;
• what triggers it;
• who is affected;
• what happens when it remains unresolved;
• how the customer manages it today;
• what the workaround costs in money or time;
• whether money is already being spent;
• who owns the problem internally;
• who can approve a purchase; and
• what could prevent a change.

This makes the method useful well before a business invests heavily in product development, hiring, pricing, or marketing.

It can also be valuable when an established company is considering a new service line. The same principle applies: test the strength of the problem before assuming the market wants your preferred solution.

The most useful customer interview is not the one that produces the most enthusiasm. It is the one that reduces the most uncertainty about what customers actually do. — Consulting Journal editorial observation

Why Is “Would You Pay for This?” Usually a Weak Question?

Asking whether someone would pay for a hypothetical solution measures an intention without requiring a real decision. There is no budget approval, competing priority, implementation risk, procurement requirement, switching cost, or payment involved. A more reliable interview examines previous behaviour and current economic consequences before discussing willingness to pay.

Suppose you are considering software that automates monthly management reporting.

You could ask:

“Would you pay AED 300 a month for automated reports?”

A respondent may say yes because the idea sounds convenient.

A more useful sequence would be:

• When did you prepare your last management report?
• How long did it take?
• Who was involved?
• Which parts required manual work?
• What happens when reporting is delayed?
• What software or external support do you currently use?
• Have you tried to improve the process before?
• Who would approve a change to the current system?

The second approach reveals operating reality.

You may discover that the respondent likes automation but only prepares reports twice a year. Alternatively, you may learn that three employees spend several days every month preparing them and management has already considered replacing the process.

Those are very different commercial situations.

What Signals Suggest a Problem May Be Worth Paying to Solve?

The strongest problems usually leave behavioural and economic evidence. Look for repeated incidents, meaningful consequences, improvised workarounds, existing spending, clear ownership, and active attempts to improve the situation. One signal alone is rarely decisive, but several appearing consistently across interviews can indicate a problem deserves deeper commercial testing.

1. The problem keeps happening

Recurring problems are usually easier to build repeatable businesses around than isolated frustrations.

Listen for specific frequency:

• every week;
• at each month-end;
• whenever a new client is onboarded;
• during every audit;
• each time a supplier changes pricing; or
• whenever management requests a particular report.

Frequency matters because small inefficiencies can become expensive when repeated.

2. The consequences are meaningful

A problem becomes more commercially relevant when leaving it unresolved has a noticeable cost.

Consequences could include:

• lost staff hours;
• slower invoicing;
• delayed decisions;
• customer complaints;
• revenue leakage;
• operational rework;
• management escalation;
• missed sales opportunities; or
• increased dependence on manual processes.

The interviewer should understand not only that the problem is irritating, but what the irritation causes.

3. The customer already has a workaround

Workarounds are useful evidence because they show effort.

A company may have built a spreadsheet, assigned an employee, hired a freelancer, purchased several tools, created a manual checklist, or developed an internal process simply to manage the issue.

An imperfect solution is still a solution. It is often your real competitor.

4. Money or staff time is already being spent

Existing expenditure is one of the clearest signs that a problem has economic weight.

The spending does not have to be on a direct competitor. It may appear as:

• software subscriptions;
• consultancy fees;
• outsourced support;
• additional employees;
• overtime;
• administrative labour; or
• lost productive hours.

The relevant question is whether the business is already paying, directly or indirectly, to live with the problem.

5. Someone is accountable for the outcome

In B2B markets, the person experiencing the problem may not be the person authorised to fix it.

You therefore need to identify:

• the user;
• the operational owner;
• the budget holder;
• the final approver; and
• anyone who can delay or block adoption.

A strong problem with no clear owner can still be difficult to commercialise.

Which Problem Interview Questions Reveal Real Buying Intent?

Good problem interview questions ask for concrete events and decisions. They should uncover what happened, what the customer did, what the problem cost, what alternatives were tried, how purchases are approved, and what might trigger action. The interviewer does not need to ask every question; follow the evidence that matters most.

Questions about the most recent incident

1. When did this problem happen most recently?
2. What was happening immediately before it occurred?
3. What did you do first to deal with it?

These questions move the customer away from generalisations and towards a specific event.

Questions about current workarounds

1. How do you manage this problem today?
2. Which part of the current process creates the most difficulty?
3. What other approaches have you tried?

A workaround can reveal far more than a complaint. It tells you how much effort the customer is already willing to invest.

Questions about cost and consequences

1. How much time does this usually take?
2. What happens if the issue is not resolved quickly?
3. Which other people or teams are affected?

These questions help translate pain into operational or financial impact.

Questions about spending and budget

1. Do you currently pay for any software, service, employee time, or external support related to this problem?
2. What does the current approach roughly cost the business?
3. Where would the budget for solving this type of issue normally come from?

Avoid pressuring the interviewee into producing artificial precision. A reasonable range or description may be more useful than a guessed figure.

Questions about the buying process

1. Who would normally decide whether to change the current approach?
2. What happened the last time the business purchased something similar?
3. What would most likely prevent a solution from being approved?

The answers may reveal procurement reviews, security requirements, integrations, switching concerns, budget timing, leadership approval, or simple lack of urgency.

What Does Strong Customer Evidence Sound Like?

Strong evidence contains details about recent behaviour, repeated consequences, actual spending, attempted solutions, internal ownership, or a real next step. Weak evidence tends to be general, hypothetical, and complimentary. The objective is not to make every interview sound positive. It is to learn whether customer behaviour supports the business assumption you are testing.

A weak response might sound like:

“Invoicing can be frustrating. An automated platform would probably help.”

The customer has expressed an opinion, but you still know very little.

A stronger response could reveal that the company spends every Monday reconciling invoices, pays for two separate applications, still uses spreadsheets, recently reviewed alternatives, and rejected one because it did not integrate with existing accounting software.

That response gives you evidence of frequency, cost, existing spending, previous search activity, and a specific adoption barrier.

It still does not guarantee a sale.

It does, however, give you something far more useful than enthusiasm.

Example 1: A Dubai-based professional services firm says its client onboarding is “too manual.” Further questioning shows that an administrator spends several hours on each new client, documents arrive through different channels, and the company recently added another employee partly to manage the workload. The problem now has observable operational cost.

Example 2: A UAE startup founder says cash-flow forecasting is a major concern. During the interview, however, the founder cannot remember the last forecast prepared, has never tried a tool or adviser, and takes no action when cash projections change. The concern may be real, but current behaviour suggests limited urgency.

How Should You Run a Problem Interview?

A practical problem interview should test one important assumption at a time. Begin with the customer's context, ask for a recent example, explore the behaviour surrounding that event, and record observable facts separately from your interpretation. Avoid turning the session into a product demonstration before you understand the problem independently.

A simple process is:

1. Write the assumption clearly. For example: “Small accounting firms lose substantial staff time chasing clients for documents.”
2. Understand the interviewee's role. Establish what they are responsible for and how closely they experience the problem.
3. Ask about the most recent incident. Specific events produce better evidence than general opinions.
4. Follow interesting evidence. If the customer mentions a spreadsheet, outsourced service, additional employee, or failed software purchase, investigate it.
5. Separate facts from interpretation. “The customer dislikes reporting” is interpretation. “Two employees spend every Thursday preparing reports” is evidence.
6. End with the buying environment. Understand budgets, approvals, competing priorities, and barriers.

How Can You Compare Several Problem Interviews?

Compare interviews using the same evidence categories rather than relying on which conversation felt most encouraging. Review frequency, severity, current action, spending, urgency, decision ownership, and commitment. The purpose is not to create a mathematically perfect score. It is to make patterns visible across a group of potential customers.

After each interview, classify the evidence as weak, moderate, or strong for:

• Frequency: Is the problem rare, occasional, or recurring?
• Severity: Is it inconvenient or economically meaningful?
• Current action: Is the customer doing nothing or actively working around it?
• Existing spending: Is money or substantial staff time already involved?
• Urgency: Is action hypothetical or tied to a current priority?
• Decision process: Are the buyer and approvers identifiable?
• Commitment: Did the customer merely compliment the idea, or agree to a concrete next step?

A pattern across interviews matters more than one unusually enthusiastic respondent.

What Common Mistakes Create False Validation?

False validation usually comes from leading the customer towards the answer the interviewer hopes to hear. Pitching too early, accepting vague responses, treating complaints as demand, and confusing compliments with commitment can make a weak opportunity appear stronger than it is. Discovery should test assumptions, not protect them.

Common mistakes include:

• explaining the product before understanding the customer's normal behaviour;
• asking leading questions such as “Wouldn't automation make this easier?”;
• relying on hypothetical willingness-to-pay questions;
• accepting words such as “often” or “usually” without asking for a recent example;
• treating frustration as proof that a customer will change;
• ignoring current alternatives;
• failing to identify the actual budget holder;
• overlooking implementation and switching barriers; and
• counting praise as a buying signal.

A useful interview may sometimes weaken your original idea. That is still valuable research.

Discovering that customers do not care enough to act can save months of development, hiring, and marketing spend.

What Should You Prepare Before Customer Interviews?

Preparation helps keep the conversation focused without turning it into a rigid questionnaire.

Use this checklist:

• Write one or two assumptions you want to test.
• Define the customer segment you are interviewing.
• Prepare a short opening that does not pitch the solution.
• Select the most relevant questions from the interview list.
• Create space to capture exact examples and factual observations.
• Record current tools, workarounds, and alternatives mentioned.
• Note any figures relating to time, spending, or frequency.
• Identify users, influencers, budget owners, and approvers.
• Record purchasing barriers or implementation concerns.
• Capture any concrete next action offered by the interviewee.
• Review interviews together to identify repeated patterns.
• Keep assumptions separate from confirmed evidence.

How Should Founders Use What They Learn?

The purpose of the Problem Interview Method is not to collect enough positive comments to justify an idea. It is to improve the quality of the next business decision.

After several interviews, ask:

• Is the same problem appearing repeatedly?
• Are customers already taking action?
• Does the problem carry a measurable cost?
• Are existing solutions clearly inadequate?
• Can we identify who owns the budget?
• Is there a realistic trigger for purchase?
• Are the same objections appearing across interviews?

If the evidence is weak, refine the customer segment, reconsider the problem, or investigate a different use case.

If the evidence is strong, the next stage may be solution testing, pricing research, prototype evaluation, or a paid pilot.

The most useful outcome is not necessarily confirmation. It is greater certainty about what the market is actually doing.