返回提示词目录第 1186 页

功能投票看板需求审查

分析投票来源、重复请求与时间偏差,重算需求权重,并给出看板治理规则和用户回复草稿。

完整提示词

<context>
You audit a public feature voting board (for a SaaS product, an app, a game or an open community) so the product team stops reading vote counts as a ranking. Votes measure how many board visitors clicked, which depends on who visits the board, how long a post has been up, whether it was shared on social media or in a customer's Slack, and how it was worded. Old posts accumulate votes; duplicates split them; a post titled as a solution ("add Gantt charts") collects votes from people with different problems.

The useful output is demand weighted by who is asking and why, a cleaner board, and honest replies to the oldest, most voted posts.
</context>

<task>
<board>
{{board_export}}
</board>

{{#customer_segments}}
<customer_segments>
{{customer_segments}}
</customer_segments>
{{/customer_segments}}

1. Who votes: count distinct voters if possible, the share of votes from the top 10% of voters, the plan or segment mix of voters against the customer mix, and the share of votes from non-customers or free users.
2. Vote quality: find duplicates and near-duplicates (merge candidates with combined votes), age effects (votes per month since posting rather than total), spikes suggesting a campaign or social share (many votes in a few days, new accounts), and vague or multi-request posts.
3. Weighted demand: for each of the top 15-20 posts, compute votes per month, distinct paying accounts, and if segments are given, a weight by segment (for example by revenue share or strategic segment). Show the formula used and how the ranking changes from raw votes.
4. Problems behind the requests: group posts by the underlying problem or job, not the requested feature, using the descriptions and comments. Note where several requests share one problem and could be solved together.
5. Board changes: merge rules, a post template asking for the problem and current workaround, status labels with honest meanings, a rule for closing stale posts, and when to show vote counts.
6. Replies: draft short replies for the three to five oldest high-vote posts with an honest status (planned, not planned, need to learn more), without dates you have not been given.
</task>

<constraints>
- Use only the data given. If voter identities are not in the export, say which analyses are limited and do the rest.
- Never promise delivery dates or commit to building anything in the drafted replies; mark any decision you need from the team as [decision].
- Do not treat a campaign spike as invalid demand; report it separately and explain what it does and does not show.
- If the export is empty or only lists titles without votes, ask for vote counts and dates and stop.
</constraints>

<output_format>
## Summary
Three to five bullets.

## Who is voting
Table: measure | value | note.

## Vote quality issues
Bullets grouped by duplicates, age effects, spikes, vague posts.

## Weighted demand
Table: post or merged group | raw votes | months open | votes per month | paying accounts | weighted score | raw rank | new rank. Formula stated above the table.

## Problems behind the requests
Table: underlying problem | posts | combined signal | note.

## Board changes
Numbered list.

## Replies to post
Each reply under the post title, under 80 words.

## Questions
Up to five.
</output_format>

可替换内容

  • {{board_export}}
  • {{#customer_segments}}
  • {{customer_segments}}
  • {{/customer_segments}}
  • [decision]

分类与标签

办公效率、用户反馈、功能投票、需求去重、看板治理、用户回复

前往 AI 图片创作