Customer Research Questions That Improve Campaigns and Products

Customer research becomes weak when it asks people to predict the future: “Would you buy this?”, “Do you like the campaign?” or “Which feature do you want?” Participants may be polite, speculate or answer the version of themselves they hope to be.

Stronger research asks for a recent, specific story. It reconstructs what happened, which alternatives appeared, where the customer struggled, what evidence influenced the decision and what outcome followed.

The objective is not to collect quotes that support an internal idea. It is to reduce uncertainty before a marketing or product decision.

Start with the decision you need to make

Before writing questions, complete this sentence:

> After this research, we need to decide whether to [take an action] for [customer and context], based on evidence about [uncertainty].

Examples:

• Which problem should a Saudi B2B campaign lead with?
• Why do UAE e-commerce customers abandon after reaching delivery options?
• Which onboarding step prevents Arabic-speaking users from first value?
• What proof does an enterprise buying committee require before a consultation?

GOV.UK’s Service Manual recommends clear, actionable research objectives and selecting methods that match them. If a question cannot change a decision, remove it or explain why it is worth collecting.

Recruit behaviour, not convenience

Select participants based on the behaviour or journey under study:

• Recent buyers and successful users
• Qualified prospects who did not buy
• Customers who stalled or cancelled
• Users who needed support
• Buyers, approvers and end users in B2B
• People with relevant accessibility needs
• Priority Saudi and UAE segments, in the language actually used

Obtain informed consent for participation, observation and recording. Explain the purpose, data collected, use, storage, sharing and withdrawal process in language the participant understands. Check local legal and data-protection requirements with qualified advisers.

Open with one recent story

Product Talk recommends story-based interviews focused on past behaviour. Begin with a prompt such as:

• “Tell me about the last time you tried to solve this problem.”
• “Walk me through the day you decided to look for a provider.”
• “Tell me about your first attempt to complete this task.”
• “Take me back to the most recent purchase in this category.”

Then excavate the sequence:

• What happened first?
• What triggered you to act then?
• Who else was involved?
• What did you do next?
• What information did you look for?
• Where did you hesitate or stop?
• What did you choose, and what happened afterward?

Stay with one story long enough to understand context. A list of twenty unrelated questions often produces twenty shallow opinions.

Questions for positioning and demand

Use these to understand the market problem and message:

• What was happening when the issue became important?
• How did you describe the problem to a colleague or manager?
• What did continuing with the old way cost in time, revenue, risk or effort?
• Which outcome mattered most, and who defined success?
• Which alternatives did you consider, including doing nothing or using an internal process?
• What made one option feel relevant or irrelevant?
• Which claim was difficult to believe?
• What evidence gave you confidence?
• What words did you search or ask others?

Do not ask, “Is our brand innovative?” Ask what the customer noticed, remembered, compared and repeated to someone else.

The customer’s exact language can inform copy, but a vivid phrase from one interview is not automatically a market-wide insight. Look for patterns and verify them through search, CRM, campaign and sales evidence.

Questions for campaigns and content

• Where did you first encounter information about the problem or category?
• Which source did you trust, and why?
• What did you need to understand before taking the next step?
• Which page, advert, message or format helped?
• What felt generic, confusing or too promotional?
• What question remained unanswered?
• What nearly stopped you from submitting the form or booking?
• What did you expect to happen immediately afterward?
• Did the follow-up match the original promise?

Ask participants to explain the message in their own words. Misinterpretation is often more useful than a preference rating.

Questions for product and onboarding

• What were you trying to accomplish when you opened the product?
• What did you expect the first useful result to be?
• Show me how you completed the task last time.
• At which point did you feel uncertain?
• What did you think would happen after that action?
• What workaround, spreadsheet, message or external tool did you use?
• What made you return—or decide not to return?
• How do you know the job is complete?

Observation matters. People may forget steps they perform automatically. Ask them to demonstrate a real or safely reconstructed workflow, then separate what they did from why the team thinks they did it.

Research the GCC context without stereotypes

Sample deliberately across market, language, role, company type and journey. Do not assume every Saudi buyer wants Arabic or every UAE buyer wants English. Ask:

• Which language did you use at each stage, and why?
• Were any terms unclear or unnatural?
• Who needed an Arabic or English version to approve the decision?
• Which local payment, identity, procurement or support step mattered?
• Did response time or communication channel affect trust?
• Which market-specific proof was required?

Avoid leading and hypothetical questions

Replace:

• “Would faster delivery make you buy?” with “Tell me about the last delivery delay and what you did.”
• “Do you prefer Arabic?” with “Which language did you use at each step of your last purchase?”
• “Would you use this feature?” with “Show me how you solve this problem today.”
• “How much would you pay?” with “What did you pay for the current alternative, and how was that approved?”

Remain neutral. Do not correct participants, defend the product or teach an intended answer. Ask for real examples and let the conversation develop naturally.

Turn sessions into decisions

Debrief immediately. Capture observations separately from interpretations:

• Observation: what was said or done.
• Interpretation: what it may mean.
• Evidence strength: frequency, recency and context.
• Decision implication: which assumption or choice changes.
• Next test: what needs validation.

GOV.UK recommends analysing with observers to reduce individual bias and separating observed evidence from what the team thinks it means.

Create an opportunity map rather than a feature-vote tally. Cluster customer needs, obstacles and desired outcomes. Combine research with behavioural data, support, CRM, win/loss and campaign performance.

End each round with one of five actions: change the message, alter the offer, fix the journey, test a product assumption or gather more evidence. Document why.

Good customer research does not ask people to design the campaign or product for you. It gives your team reliable context to make a better decision.

DEMA helps GCC marketing and product teams connect customer research with bilingual campaigns, product journeys and revenue measurement. Request a free growth audit or book a free consultation to identify the customer questions your next growth decision depends on.