Translation Comparison - define-problem-statement

A problem statement is a concise document that frames the problem you're solving, articulates the impact on users and the business, and defines clear success criteria. It serves as the foundation for all subsequent product work by ensuring alignment on what problem to solve before jumping to how to solve it.

问题陈述是一份简洁的文档，它明确了你要解决的问题，阐述其对用户和业务的影响，并定义清晰的成功标准。它是所有后续产品工作的基础，确保在着手解决问题的「方法」之前，先就需要解决的「问题」达成共识。

When to Use

使用场景

Starting a new initiative or project to establish shared understanding
Realigning a drifted project back to its original intent
Communicating up to leadership or stakeholders about priorities
Evaluating whether a proposed solution actually addresses the core problem
Onboarding new team members to provide context

启动新举措或项目，建立共同认知
将偏离方向的项目重新拉回原定目标
向领导层或利益相关方传达优先级
评估提议的解决方案是否真正解决核心问题
为新团队成员提供背景信息，帮助他们快速融入

Instructions

操作步骤

When asked to create a problem statement, follow these steps:

Identify the User Segment Ask who is experiencing this problem. Get specific about the user persona, role, or segment. Avoid vague descriptions like "users" . instead target "mobile shoppers completing checkout" or "enterprise admins managing 50+ users."
Understand the Pain Points Explore what friction, frustration, or unmet need the user experiences. Ask probing questions to understand the severity and frequency of the problem. Look for evidence from user research, support tickets, or behavioral data.
Establish Business Context Connect the user problem to business impact. How does this problem affect revenue, retention, growth, or strategic goals? Why should the organization invest in solving this now versus later?
Define Success Metrics Identify how you will measure success. What metrics will move if this problem is solved? Establish current baselines and target improvements. Be specific and time-bound.
Surface Constraints and Considerations Note any technical limitations, resource constraints, regulatory requirements, or dependencies that will shape the solution space.
Capture Open Questions Document what you don't know yet. What assumptions need validation? What additional research is needed?

当需要创建问题陈述时，请遵循以下步骤：

确定用户群体 询问谁正面临这个问题。明确具体的用户角色、画像或群体。避免使用「用户」这类模糊描述，转而定位「完成结账流程的移动购物者」或「管理50+用户的企业管理员」这类具体群体。
了解痛点 探究用户遇到的摩擦、困扰或未被满足的需求。通过追问来了解问题的严重程度和发生频率。从用户研究、支持工单或行为数据中寻找相关证据。
明确业务背景 将用户问题与业务影响关联起来。这个问题会如何影响收入、留存、增长或战略目标？为什么组织需要现在就投入资源解决这个问题，而不是稍后？
定义成功指标 确定如何衡量成功。解决这个问题后，哪些指标会发生变化？设定当前基准和目标改进值。确保指标具体且有时间限制。
梳理约束条件与考量因素 记录任何会影响解决方案范围的技术限制、资源约束、监管要求或依赖关系。
记录待解问题 记录目前未知的内容。哪些假设需要验证？还需要开展哪些额外研究？

Output Format

输出格式

Use the template in

references/TEMPLATE.md

to structure the output.

使用

references/TEMPLATE.md

中的模板来构建输出内容。

Quality Checklist

质量检查清单

Before finalizing, verify:

Problem is specific to a defined user segment (not "all users")
Impact is quantified with data or reasonable estimates
Success metrics have baselines and targets
Problem describes the "what" without prescribing the "how"
Business context explains why this matters now
Open questions are captured for follow-up

最终定稿前，请验证以下内容：

问题针对特定的用户群体（而非「所有用户」）
影响已通过数据或合理估算量化
成功指标有基准值和目标值
问题描述了「是什么」，而非预设「如何解决」
业务背景说明了为何现在需要解决这个问题
已记录待跟进的待解问题

See

references/EXAMPLE.md

for a completed example.

可查看

references/EXAMPLE.md

中的完整示例。

define-problem-statement

Original

Translation

Problem Statement

问题陈述