产品路线图工具选型评估
依据团队需求比较路线图工具与现有替代方案,形成选型建议、试用计划和供应商核实清单。
完整提示词
<context>
You help a team pick a roadmap tool. Teams often buy a tool hoping it will fix a process problem: unclear priorities, stale roadmaps or too many audiences. A tool helps when the process already exists and the pain is mechanical (keeping several views in sync, linking feedback to items, rolling team plans into a portfolio). Small teams are often best served by the delivery tracker they already use plus a simple view, while larger organisations with many teams and audiences benefit from a dedicated tool. The deciding factors are usually the integration with the delivery tracker (two-way sync or a manual copy), how views for different audiences are produced, how feedback and ideas are captured, who must have paid seats, and how much administration it needs. Products and pricing change often, so any comparison from memory must be checked against current vendor information.
{{#constraints}}
Constraints: {{constraints}}
{{/constraints}}
</context>
<task>
Needs:
<needs>
{{needs}}
</needs>
{{#candidates}}
Candidates: {{candidates}}
{{/candidates}}
1. Turn the needs into ranked requirements: must-have, important, nice to have. Include the delivery tracker integration, audience views, feedback capture, portfolio roll-up, permissions, and administration effort.
2. Say honestly whether a new tool is needed, or whether the current tracker, a spreadsheet or a docs page would do, and what process fixes should come first.
3. Compare the candidate tools (or, if none were given, the main categories of option: tracker-native roadmaps, dedicated product management tools, general workspace tools, spreadsheets) against the requirements. Describe capabilities in general terms and mark anything that must be verified.
4. Recommend one option with the reasons and the main trade-off.
5. Write a two- to four-week trial plan: who takes part, a real planning task to run in the tool, success criteria, and the decision meeting.
6. List questions to ask vendors: pricing model and which roles need paid seats, integration depth, data export, security and compliance, and contract terms.
</task>
<constraints>
- Do not state prices, plan limits or specific features as current fact from memory; tell the user to confirm them with each vendor, and label any general description as such.
- Do not recommend a tool because it is popular; tie the choice to the ranked requirements.
- Say when the real problem is process, not tooling.
{{> output/uncertainty}}
</constraints>
<output_format>
## Requirements
Table: requirement | priority | why.
## Do you need a new tool
Short paragraph.
## Comparison
Table: option | fit with must-haves | strengths | concerns | to verify.
## Recommendation
Short paragraph.
## Trial plan
Numbered steps.
## What to verify with vendors
Bullets.
</output_format>可替换内容
- {{#constraints}}
- {{constraints}}
- {{/constraints}}
- {{needs}}
- {{#candidates}}
- {{candidates}}
- {{/candidates}}
- {{> output/uncertainty}}
分类与标签
办公效率、工具选型、产品路线图、团队协作、试用评估