Customer Discovery Interviews: Questions That Avoid Polite Yeses

A Dubai founder asks a retailer whether it would use a tool to resolve supplier delivery discrepancies. The manager says it sounds useful. In a second conversation, a receiving supervisor describes the last short shipment, the photographs she took and the three people who had to agree before finance could release the invoice. The second conversation gives the founder something to investigate. It shows where the work takes place, who bears the cost and where a new tool would have to fit.

A discovery interview should help the team decide what to learn or test next. Begin with a recent event and ask the person to reconstruct it. Look for actions, records and consequences. Save the proposed product for the end of the discussion or a separate meeting so the account of current work does not follow the founder’s description of the solution.

Prepare one assumption to test

Write a short assumption before the call. A founder might believe that receiving supervisors at UAE retailers with several branches spend enough time resolving short deliveries for an operations director to fund a change. Break that into questions about frequency, effort and authority. A supervisor can explain the work, while a buyer or finance manager may be better placed to explain the budget and procurement process.

Recruit people who have handled the job recently and people who can explain an alternative. Include accounts that were enthusiastic and ones that have little reason to favour the idea. Note how each person was recruited. Three colleagues at one company may offer valuable perspectives on a single process. Count them as three interviews and one buying organisation when reporting account-level findings.

Tell participants what the session is for, how long it will take and how you intend to use the information. Give them room to decline a topic or stop. If the team wants to record the conversation, check the applicable requirements and obtain appropriate permission before recording. When notes contain personal data, have the responsible team review the applicable regime and process. The UAE federal personal data protection law includes controls on purpose, necessity, security and retention. UAE federal personal data protection law, Article 5

Ask about the last time it happened

Follow the sequence before asking for a summary. If the interviewee says it usually takes a long time, ask what time the last case started, what happened during the wait and when it closed. Distinguish ten minutes of hands-on work from two days waiting for another party. An improvement that reduces staff time may leave the waiting period in place.

Ask what worked well. The current process may give the receiving team a direct line to a supplier or produce a record finance trusts. A founder who hears only the frustrating part could build something that disrupts the rest. Find out what the buyer would need to preserve and what happened the last time it tried to change the process.

Follow the handoff to the person who pays

In the retailer example, the receiver may submit the claim, the buyer may negotiate with the supplier and finance may decide whether the invoice can be paid. Ask each role to describe the same kind of case from its perspective. Record where the accounts agree and where they differ. The person who feels the inconvenience may have a different reason for acting from the person who controls the budget.

Ask about a purchase the organisation actually made. How did it identify the supplier? Who reviewed the terms and implementation? What evidence did the buyer need before signing? If the participant has never been involved in a similar purchase, ask who can explain it. Keep that answer as an unanswered question in the research record until the team has spoken to someone who knows.

Test priority with a trade-off. Ask what would have to move down the list for this problem to get attention. A manager may want a better process and still defer it while opening a branch or changing a core system. Find out what event would create a reason to act and whether it is scheduled or speculative. Capture the date or decision it depends on so the founder can reassess later.

Keep compliments separate from actions

A participant who says a product sounds useful may be responding generously to a founder’s effort. Ask what they would need to see next and whether there is an action they are comfortable taking. A recipient may share a blank form, introduce a budget owner or agree to review a mock-up at a specified time. Record the action when it occurs and keep it distinct from any purchase commitment.

Suppose a hypothetical team interviews 12 people at nine UAE retailers. Seven people describe a recent discrepancy, four provide or point to a shareable blank template and two make an introduction to a budget owner. The figures describe different types of evidence. Two introductions are a reason to check how a purchase might happen. They do not establish two orders. Before reporting the number of affected retailers, reconcile which interviewees came from the same accounts.

Treat a clear refusal as useful evidence. If an interviewee says the proposed tool would add an extra step, ask which step and who would have to do it. If a budget owner says they cannot purchase this year, distinguish a timing problem from a structural requirement such as an existing contract or mandatory integration. The founder can then decide whether the same constraint is likely to apply to the rest of the segment.

Run the conversation without coaching the answer

Use the same core questions across interviews and follow the details when a participant mentions a particular job. Ask one question at a time. If an answer is unclear, repeat what you understood and give the person a chance to correct it. Keep the interviewee’s words separate from the team’s interpretation in the notes.

Avoid offering a reason in the question. Instead of asking whether invoices are delayed because evidence arrives late, ask what happened between delivery and invoice approval. If the interview moves to the product, note the point where you introduced it. A later comment about a proposed screen is feedback on the concept. A description of how the person handled yesterday’s shipment is evidence about current practice.

If several languages are used, ask participants which language works best for the discussion and keep important terms in context. A word for approval might mean a supervisor’s check at one firm and a formal buyer sign-off at another. Ask who has authority to proceed and which record proves it. Make the notes specific enough that another teammate can understand the difference without guessing at the translation.

Turn notes into a testable decision

Use a short record for each conversation. Include participant role, buying organisation, recruitment channel, recent example, stated consequence, evidence available and next action. Mark the source of each observation. A person describing their own work gives different evidence from someone summarising what another department does. Confirm the latter with the department if it could change the decision.

After several interviews, group observations by workflow and buyer. Look for a repeated sequence and cases that contradict it. If independent retailers use the same kind of evidence but chains send every claim through a central portal, the two groups may need different products or different integration paths. Revisit the segment definition before counting both as one market.

Set a decision rule for the next round. The team could proceed to a mock-up if several independent accounts describe the same unresolved step and a person with buying authority confirms it matters. If the accounts agree on the pain but disagree on who controls the process, interview the missing role. If the process works well for the intended buyers, revisit the assumption and record why the team changed direction.

Have a second team member review a few anonymised notes. Ask them to identify which claims are supported and which depend on inference. If the reviewers reach different conclusions, trace the gap back to the notes and decide what to ask next. This check is particularly useful when the same founder recruited participants, led the conversation and has already invested time in the product.

Keep a log of contacts who decline or do not reply. It helps the team see whether the sample is dominated by people with spare time, a warm relationship or unusually strong interest in the issue. When an account declines, keep the fact separate from its reason unless the person volunteered one. Then recruit for a missing type of account, such as a branch with a central receiving team. This can change the conclusions more than another conversation with someone in the same network.

Check whether an action still matters after a few days. A scheduled review that the buyer attends with the right colleague is stronger evidence than an invitation sent by the founder. Record the result even when the meeting falls through. The team can then distinguish an unreliable introduction route from a product question it still needs to test.

Use UAE startup settings to find the missing perspective

in5 Tech in Dubai describes a programme application that includes a business plan presentation and a pitch for shortlisted applicants. If a team is preparing to apply, it can use the interview record to explain the problem, buyer and next test in concrete terms. The programme’s selection process is separate from a customer’s purchase decision. in5 Tech application process

An in5 Dubai reel shows a speaker beside in5 branding. A workspace or founder event can be useful for finding people who know the sector. Decide which perspective is missing before asking for an introduction. If interviews have covered receivers and managers, seek someone who actually reviews the supplier claim or approves a new tool.

Finish each conversation by confirming what you heard and agreeing any next step. If the participant offers an introduction, record whether it was made. If they offer to show a workflow, agree which example can be shared safely. If there is no next step, keep the evidence already gathered and move on. A good discovery round leaves the team with a clearer account of the buyer’s work and a specific question the next test can answer.