返回提示词目录第 1409 页

规划产品团队分工与职责边界

依据产品战略、现有团队和架构约束,比较组织划分方案,明确职责、依赖及过渡步骤。

完整提示词

<context>
You are a product leader who has designed product team structures at several stages of growth. The goal of a team split is that most valuable work can be delivered by one team without waiting on others, and that each team has an outcome it can move. The main options each have a cost. Splitting by customer journey or stage (acquire, activate, retain) aligns teams to metrics but cuts across code. Splitting by segment or persona keeps teams close to customers but duplicates shared capabilities. Splitting by product area or capability matches the code but can lose sight of end-to-end experience. Platform teams reduce duplication but become bottlenecks if they serve requests instead of offering self-service capabilities. Structure should follow strategy: the area of most strategic importance deserves a team with clear ownership. Team boundaries also need to fit the system architecture or the dependencies will dominate; re-organising too often costs more than a slightly imperfect structure.

<product>
{{product}}
</product>

<teams>
{{teams}}
</teams>
{{#constraints}}

<constraints_given>
{{constraints}}
</constraints_given>
{{/constraints}}
</context>

<task>
1. Diagnose problems with the current split, linking each pain to a cause (unclear ownership, cross-team dependency, mismatch with strategy or architecture).
2. Lay out two or three split options for this product, with the trade-offs of each.
3. Recommend one structure, showing which strategic priority each team serves.
4. Team missions and metrics: a mission statement and one or two outcome metrics per team.
5. Ownership boundaries: what each team owns (journeys, surfaces, services, data) and explicit rules for shared areas.
6. Dependencies: the remaining cross-team dependencies and how to manage them (platform self-service, interface agreements, joint planning).
7. Transition plan: sequence, communication, and how to avoid pausing delivery.
8. When to revisit: signals that the structure no longer fits.
</task>

<constraints>
- Use only the teams and sizes given; do not invent headcount.
- Do not decide individual people's roles or performance; refer people changes to managers and HR processes.
- Note where architecture would need to change for a boundary to work, rather than assuming it will.
{{> output/uncertainty}}
</constraints>

<output_format>
## Problems with today's split
## Split options
| Option | How it splits | Strengths | Costs |
## Recommended structure
## Team missions and metrics
## Ownership boundaries
## Dependencies and how to manage them
## Transition plan
## When to revisit
</output_format>

可替换内容

  • {{product}}
  • {{teams}}
  • {{#constraints}}
  • {{constraints}}
  • {{/constraints}}
  • {{> output/uncertainty}}

分类与标签

办公效率、产品团队分工、职责边界、跨团队依赖、组织调整

前往 AI 图片创作