返回提示词目录第 1391 页

规划产品路线图投入比例

依据产品阶段与团队现状划分路线图工作投入,明确各类事项占比、质量护栏、调整触发条件和复盘方式。

完整提示词

<context>
You set an explicit split of a team's capacity between types of work: new capabilities, improvements to what exists, technical debt and platform health, and bugs and support. Without an agreed split, feature work wins every planning meeting, debt piles up until delivery slows, and then a dramatic "stabilisation quarter" stops everything. With a split, debt and quality work stop needing a fresh argument each time. The right mix depends on stage: an early product leans heavily to new capability, a mature product with many customers needs more for quality and debt, and a product being wound down mostly needs maintenance. Many teams also find their real split is far from what they believe, because unplanned work hides in "features".
{{#goals}}
Goals: {{goals}}
{{/goals}}
</context>

<task>
Situation:

<situation>
{{situation}}
</situation>

{{#current_split}}
Current split:

<current_split>
{{current_split}}
</current_split>
{{/current_split}}

1. Define the work types in plain words so items can be classified consistently, with an example of each from the user's situation. Say where grey cases go (for example a performance fix customers ask for).
2. Describe where time goes now from the user's data. If no data is given, say the first step is to classify the last one or two quarters of finished work, and explain how.
3. Recommend a target mix as percentages with a range, fitted to the product stage and pains. State the reasoning in terms of the situation, not generic ratios.
4. Set guardrails: a floor for debt and quality work that is not traded away for features, a cap on unplanned work before it triggers a conversation, and who can approve going outside the range.
5. Say how the mix should shift as the situation changes, for example after a major launch, when incidents rise, or when the product matures.
6. Set up tracking: how each item is tagged, how often the actual split is reviewed against the target, and what happens when they diverge.
</task>

<constraints>
- Present any percentages as a starting point with a range, not an industry law. Do not cite benchmarks or studies unless the user provided them.
- Use the user's numbers when given and show how you derived the current split.
- Do not recommend stopping all feature work unless the situation clearly calls for it, and if so give exit criteria.
- Keep the policy short enough for a team to remember.
{{> output/uncertainty}}
</constraints>

<output_format>
## Where time goes now
Table: work type | definition | example | current share (or "unknown").

## Recommended mix
Table: work type | target share | range.

## Why this mix
Short paragraph tied to the situation.

## Guardrails
Bullets.

## How the mix shifts
Bullets: trigger and new mix.

## Tracking
Bullets: tagging, review rhythm, response to drift.
</output_format>

可替换内容

  • {{#goals}}
  • {{goals}}
  • {{/goals}}
  • {{situation}}
  • {{#current_split}}
  • {{current_split}}
  • {{/current_split}}
  • {{> output/uncertainty}}

分类与标签

商业营销、产品路线图、团队产能、资源分配、技术债务

前往 AI 图片创作