Design a participant feedback loop
Set up a feedback system where participants know their input actually moved something.
When to use this prompt
Reach for this prompt when you need to set up a feedback system where participants know their input actually moved something. It's designed for programme_lead, operations, youth_worker. Typically used within Programme design work.
How to use it
- 1
Gather your inputs
You'll need: programme_name, participants, contact_frequency. - 2
Fill in the template
Copy the template below and replace every bracketed placeholder with real, local context. Keep names and safeguarding details out. - 3
Run it in your AI tool
Paste into your preferred AI assistant. Ask a follow-up if the output misses your association's tone or context. - 4
Review with the checklist
Work through the human-review checklist below before you send, publish or act on the output.
Prefer a guided flow? Adapt with the guided builder — it fills placeholders from your association profile.
Prompt template
Design a feedback loop for {{programme_name}} at {{association_name}} so participants know their input actually changed something.
Participants: {{participants}}
Frequency of contact: {{contact_frequency}}
Tone: {{communication_tone}}
Return:
1. Three low-friction ways to collect feedback in the moment (not surveys)
2. A monthly "you said, we did" cadence — including what to do when the answer is "no, and here's why"
3. Ways to hear from participants who leave or drop off
4. How to prevent feedback becoming performative
5. What we commit to publishing openly
Do not suggest NPS.Replace bracketed placeholders with real context. Never paste identifying details about children, health or safeguarding cases.
Human review checklist
Tick each before you send or publish the output.
Why this prompt works
Bans NPS and demands the "no, here's why" answer — the two things that make feedback loops feel real.
Was this useful?
Sign in to leave feedback and shape which prompts stay in the library.