Community Program Participant Interview Guide: Capture Experience Without Leading

A community program participant interview guide should help people describe what happened in their own words. It should not steer them toward a success story, test their gratitude or make continued support feel conditional on a favorable answer.

The guide below supports program learning and accountable follow-up. Adapt it to the population, language, setting, safeguarding duties and evaluation plan. A responsible program owner remains accountable for consent, interpretation and action.

Define the learning purpose before recruiting

Write one clear purpose statement: what decision will these interviews inform, and what evidence is missing? Useful purposes include understanding barriers to access, testing whether delivery matches the intended model, identifying unintended effects or improving a specific stage of the participant journey.

Avoid a purpose so broad that every personal detail appears relevant. Collecting more information increases burden and privacy risk without necessarily improving the decision. Separate program learning from eligibility assessment, case management, complaints investigation and public storytelling. Each may need different staff, notices and safeguards.

Create a short evidence plan:

Use the community outreach report template when interviews are one input within a broader outreach record.

Protect choice, safety and accessibility

Participation must be voluntary in practice, not merely described that way. Explain who is conducting the interview, why, how information will be used, whether participation affects services, which questions are optional and how someone can stop. Do not ask a person’s direct service provider to recruit them when that relationship could create pressure without addressing the power imbalance.

Plan language support, accessible formats, transport, timing, support persons and a private setting. Decide what the interviewer should do if someone shares immediate danger, abuse, a serious service concern or another matter covered by an escalation duty. Explain relevant limits before the interview rather than after a disclosure.

Never promise anonymity if staff will retain names or recognizable stories. State accurately whether responses are confidential, de-identified, aggregated or attributed with separate permission. For sensitive contexts, qualified safeguarding, privacy or ethics review may be required.

Recruit a useful range of participants

Do not recruit only the easiest people to reach or those already known to be enthusiastic. Define relevant variation such as program stage, location, language, attendance pattern, access needs or completion status. Include people who disengaged when safely and ethically possible; their experience may reveal barriers hidden by completion data.

Document the recruitment route, inclusion criteria, exclusions, invitation wording and response pattern. Do not treat the interview group as statistically representative unless the design supports that claim. Qualitative interviews can reveal mechanisms, meanings and exceptions without estimating population prevalence.

Compensation should recognize time without becoming coercive. Set it consistently, explain it before participation and avoid linking it to the content or positivity of answers. Keep contact details separate from interview material where practical.

Prepare roles, evidence and boundaries

Assign one interviewer, one optional note taker and one accountable review owner. The interviewer manages rapport, pacing and neutral follow-up. The note taker captures key language, examples and nonverbal context that is appropriate to record. The review owner checks interpretations, risks and actions.

Prepare a participant information statement, consent record, topic guide, referral or escalation route, secure note location and correction process. If the interview may produce a casework request, explain whether it will be handled inside or outside the research record.

The research interview notes template can help separate observed statements, interviewer notes and later interpretation. Use participant codes rather than names in working analysis where identity is unnecessary.

Copy this participant interview guide

COMMUNITY PROGRAM PARTICIPANT INTERVIEW

Purpose:
Interviewer / note taker:
Participant code:
Date / format / accessibility support:
Consent confirmed for: participation / notes / recording / quotations

OPENING
1. Please tell me a little about how you came to use the program.
2. What did you expect before you started?

EXPERIENCE
3. Walk me through what happened from your first contact onward.
4. What parts were easiest or most useful? What made them so?
5. What parts were difficult, uncomfortable or less useful?

ACCESS AND INCLUSION
6. Was there anything that made taking part easier or harder?
7. Was the program appropriate for your language, circumstances and access needs?

CHANGE AND CONTEXT
8. What, if anything, is different for you since taking part?
9. What else may have contributed to that change?

IMPROVEMENT
10. If you could change one part of the program, what would it be and why?
11. What have I not asked that the program team should understand?

CLOSE
Questions from participant:
Follow-up requested and authorized:
Correction / withdrawal route repeated:

Treat the questions as a route map, not a script to complete at any cost. Skip questions that are irrelevant, already answered or likely to create avoidable harm.

Ask neutral questions and probes

Begin with concrete experience before asking for evaluation. “Walk me through your first visit” is easier to answer accurately than “Was onboarding effective?” Ask one question at a time and leave enough silence for reflection.

Useful neutral probes include “Can you give an example?”, “What happened next?”, “What made that easier or harder?” and “How did you interpret that?” Contrast these with leading probes such as “That was helpful, wasn’t it?” or “Would you agree staff were supportive?”

Do not convert uncertainty into agreement. If an answer is unclear, reflect it tentatively: “I heard that the timing worked, but the location did not. Is that accurate?” The user interview questions guide offers additional patterns for behavior-based questions and follow-ups.

Capture authorized evidence responsibly

Ask separately about participation, recording and use of quotations. A person may agree to the conversation but decline audio capture or public attribution. Provide a genuine notes-only option and confirm how a recording will be stored, accessed and deleted.

For an authorized participant conversation with informed, visible consent, Kuno can help create a reviewable draft transcript and notes. Staff must verify meaning, protect identities and decide what belongs in the program record. Explore Kuno

Follow the applicable policy and seek qualified advice where law, safeguarding or research governance requires it. The meeting recording consent form can inform a clear capture record, but it does not replace a context-specific consent process.

Analyze without erasing disagreement

Separate raw evidence, coding and conclusions. Preserve enough context to understand who experienced what, under which conditions, without exposing identity unnecessarily. Look for recurring patterns, strong exceptions, differences between groups and plausible alternative explanations.

Do not count mentions as if they were survey percentages. Frequency can matter, but severity, specificity and consequences also matter. One credible safeguarding concern requires action even if it appears once. One vivid positive story does not prove program-wide impact.

Invite a second reviewer to challenge themes and identify leading assumptions. Where appropriate, return a concise interpretation to participants or a representative group for correction. Record disagreements rather than forcing consensus.

Turn findings into owned follow-up

For each finding, state the supporting evidence, confidence, affected journey stage, proposed response, owner and review date. Distinguish a participant suggestion from an approved change. Explain why a recommendation was accepted, deferred or declined.

Share back what the team learned and what will happen next in an accessible form. Closing the loop respects participants’ contribution and tests whether staff interpreted it fairly. Use a decision log template for material choices and rationale.

Do not publish identifiable quotations under a general research consent. Obtain specific permission, show the final wording and context where feasible, and make refusal consequence-free.

Run a final quality and ethics check

Before analysis or distribution, confirm:

• The purpose and decision owner are explicit.
• Recruitment did not select only favorable voices.
• Participation, recording and quotation choices were separate.
• Accessibility and language needs were addressed.
• Questions were neutral, singular and experience-based.
• Notes distinguish participant words from interpretation.
• Sensitive details are minimized and access is controlled.
• Safeguarding and complaint routes were followed where triggered.
• Findings include exceptions, uncertainty and alternative explanations.
• Each accepted action has an owner and review date.
• Participants have a realistic correction or withdrawal route where promised.
• Reporting does not claim representativeness the design cannot support.

Make participant evidence easier to review without outsourcing judgment. Kuno supports consented capture and draft organization; accountable people decide what the conversation means and how the program should respond. See Kuno