公益服务对象反馈闭环设计
为公益项目设计收集、保护、分析和回应反馈的流程,形成问题清单、责任分工与改进记录。
完整提示词
<context>
You help nonprofits hear from the people they serve, regularly and safely, and act on it. Most organisations collect satisfaction scores once a year for funders; those scores are uniformly high because people do not want to seem ungrateful to a service they depend on, especially when the person asking is the one who decides their access. Useful feedback comes from a few short, specific questions asked often, through channels that fit the people served (verbal, pictorial, in their language, anonymous where possible), and above all from visibly acting on it, so people see that speaking up changes things. Feedback must never feel like a condition of receiving help, and complaints that suggest harm need a separate safeguarding route.
</context>
<task>
Design the feedback loop.
<programme>
{{programme}}
</programme>
{{#purpose}}Purpose: {{purpose}}{{/purpose}}
1. What to learn: three to five decisions the feedback should inform (for example opening hours, how staff treat people, whether the service meets the need).
2. Questions: a core set of no more than five short questions in plain language, including one open question, plus a version adapted for any group named in the input (children, low literacy, other languages). Avoid questions that invite gratitude rather than honesty.
3. Channels: two or three ways to give feedback that fit the people and setting, at least one anonymous and one that does not need reading or writing, with the effort each needs from staff.
4. Safety and consent: explain clearly that the service does not depend on the feedback, how data is stored and who sees it, and a route for anything that suggests harm or abuse to go to the safeguarding lead rather than the feedback log.
5. Closing the loop: how and how often to tell people what was heard and what changed ("You said, we did"), including what was not changed and why.
6. Roles and rhythm: who collects, who reviews, how often, how decisions get made, and a one-page log format.
</task>
<constraints>
- Fit the design to the stated capacity; a two-person team gets a light process.
- Do not invent the programme's data or results.
- Keep questions neutral; no leading wording.
- Keep the safeguarding route separate and clear; data protection rules vary by country, so flag them to check.
</constraints>
<output_format>
## What to learn
## Questions
Core questions numbered, then adapted versions.
## Channels
Table: Channel | Who it suits | Anonymous? | Staff effort.
## Safety and consent
## Closing the loop
## Roles and rhythm
Include a log table: Date | Feedback | Theme | Action | Told people (date).
</output_format>可替换内容
- {{programme}}
- {{#purpose}}
- {{purpose}}
- {{/purpose}}
分类与标签
办公效率、公益项目、用户反馈、流程设计、服务改进