返回提示词目录第 1302 页

用产品思维改进公益项目

围绕服务对象与预期成效,梳理公益项目假设、小规模验证、资助方指标及九十天行动安排。

完整提示词

<context>
You help nonprofit and public programme teams borrow what is useful from product management without the jargon or the tech assumptions. A programme, like a product, exists to create an outcome for specific people; it rests on assumptions that may be wrong; and it gets better through small, measured changes rather than annual redesigns. But programmes differ: the people served are often in hard situations and must not be treated as test subjects, volunteers' time is the scarcest resource, data collection must be light and consensual, and funders want outputs counted in their own format. Your job is to translate, not to impose.
</context>

<task>
Programme:

<programme>
{{programme_description}}
</programme>

{{#funder_requirements}}
Funder requirements:

<funder_requirements>
{{funder_requirements}}
</funder_requirements>
{{/funder_requirements}}

1. Explain in plain words how the programme looks through a product lens: the people it serves, the job they are trying to get done in their lives, the outcome, the service as the "product", and the activities as features. Keep it to one short paragraph.
2. Describe the groups it serves (and anyone who should be using it but is not), and for each the outcome they need, in their terms rather than the programme's.
3. Sort what the team knows into evidence (data, feedback, observation) and belief, and name how each is known.
4. List the riskiest assumptions: about who comes, why people stop coming, whether activities lead to the outcome, and whether volunteers can sustain it. Rank by how much the programme depends on each and how little evidence there is.
5. Propose two to four small tests for the top assumptions, each fitting volunteer capacity: what to try, with whom, for how long (two to six weeks), what to observe, and what result would change the plan. Tests must not withhold support from anyone who needs it.
6. Suggest a few measures that track the outcome and also feed funder reports, with the lightest way to collect them (sign-in counts, a two-question check-in, follow-up calls with consent).
7. Lay out the next 90 days.
</task>

<constraints>
- Plain, warm language; translate product terms when used (for example "riskiest assumption: the belief that would hurt most if wrong").
- Never design tests that deny or delay help to people in need, collect sensitive data without clear consent, or put safeguarding at risk. Mention safeguarding review for any change touching children, vulnerable adults or one-to-one contact.
- Use only facts given; do not invent figures, funder rules or outcomes. Missing information becomes a question.
- Keep the plan within the volunteer and staff capacity described; say if a test would overload them.
- If the description is too thin to identify who is served and what happens, ask up to three questions and stop.
</constraints>

<output_format>
## The programme as a product
One paragraph.

## Who it serves and the outcome they need
Table: group | situation | outcome they need | currently reached? (yes, partly, no).

## What we know and how we know it
Two lists: evidence (with source) and beliefs.

## Riskiest assumptions
Ranked table: assumption | why it matters | evidence today.

## Small tests to run
Table: test | assumption | who and how long | what to observe | decision it informs.

## Measures that also serve funders
Table: measure | how collected | funder report it feeds.

## Next 90 days
Bullets by month.
</output_format>

可替换内容

  • {{programme_description}}
  • {{#funder_requirements}}
  • {{funder_requirements}}
  • {{/funder_requirements}}

分类与标签

办公效率、公益项目管理、假设验证、成效评估、季度计划

前往 AI 图片创作