Discussion guides and qualitative research questions
Translate the business question into a practical discussion guide with objectives, topics, questions and probes.

Build a guide around the decision, not a list of questions
A useful discussion guide connects the business question to a conversation respondents can understand. It gives the moderator a clear direction while leaving space for unexpected but relevant experience. The aim is not to script every answer, but to make sure the discussion explores what the team genuinely needs to learn.
1. Define the business question
Begin with the decision the research will inform. What is the team trying to resolve, and how would a better understanding of consumers help? This provides a reference point for deciding which topics belong in the guide.
2. Set the research objectives
Translate that decision into the things the study needs to understand. Clear objectives help separate essential questions from interesting background topics, so the conversation has a purpose beyond collecting opinions.
3. Organise topics into a conversation
Use the objectives to identify the areas to explore. The guide should help respondents describe relevant experiences and give the moderator a practical structure for following the discussion.
4. Develop questions and probes
Frame questions in language respondents can answer from their own experience. Follow-up prompts should invite explanation and detail without suggesting the answer the team wants to hear.
An illustrative example
If the business question is “Why are interested consumers not buying?”, the guide might explore expectations, concerns, missing information and the point at which the decision stalls. Rather than assuming a single barrier, the conversation gives respondents room to explain their own reasons.
This is an illustration of guide development, not a client case study or a claim about research results. Share your business question and any existing objectives or draft questions to discuss how the guide could be developed.
Have a question about your project?
Send your name, email and what you want to understand. A complete brief is not required.