Solution Brief

解决方案简报

A solution brief is a concise, one-page document that communicates the proposed solution to a problem. It serves as the bridge between problem understanding and detailed specification, providing enough context for stakeholders to align on the approach without getting lost in implementation details. The one-page constraint forces clarity and prioritization.

解决方案简报是一份简洁的单页文档，用于针对某个问题传达提议的解决方案。它是连接问题理解与详细规范的桥梁，为利益相关者提供足够背景信息以统一实施方法，同时避免陷入具体实现细节。单页的限制要求内容清晰且突出重点。

When to Use

使用场景

Pitching a solution approach to stakeholders for buy-in
Aligning cross-functional teams on what you're building and why
Documenting solution intent before detailed PRD writing
Comparing multiple solution options at a high level
Communicating product direction to leadership

向利益相关者推介解决方案以获得认可
让跨职能团队就开发内容及原因达成共识
在编写详细PRD前记录解决方案意图
从高层级对比多种解决方案选项
向领导层传达产品方向

Instructions

操作步骤

When asked to create a solution brief, follow these steps:

Recap the Problem Summarize the problem in 2-3 sentences maximum. Don't re-explain the full problem statement . reference it if needed. The reader should immediately understand what pain point this solution addresses.
Describe the Proposed Solution Explain what you're building in clear, non-technical language. Focus on the user experience and core value proposition. Avoid implementation details . this is about what, not how.
List Key Features Identify 3-5 essential features that comprise the solution. These should be the minimum set needed to solve the problem. Resist the urge to include nice-to-haves . the one-page constraint demands focus.
Define Success Metrics Connect the solution to measurable outcomes. How will you know if this works? Reference metrics from the problem statement and set targets.
Acknowledge Trade-offs Document what you're explicitly NOT doing and why. Good solution briefs are honest about scope limitations and alternatives that were considered but rejected.
Identify Risks and Mitigations Surface the biggest risks to success and your plan to address them. This builds stakeholder confidence and surfaces concerns early.
Outline Next Steps Provide 3-5 immediate actions to move the solution forward. Be specific about who does what.

当需要创建解决方案简报时，请遵循以下步骤：

回顾问题 用最多2-3句话总结问题。无需重新解释完整的问题陈述，必要时可引用。读者应能立即理解该解决方案解决的痛点。
描述提议的解决方案 用清晰的非技术语言解释将要开发的内容。聚焦用户体验与核心价值主张。避免涉及实现细节——这部分是关于“做什么”，而非“怎么做”。
列出关键功能 确定构成解决方案的3-5个核心功能。这些应是解决问题所需的最小集合。克制添加锦上添花功能的冲动——单页限制要求内容聚焦。
定义成功指标 将解决方案与可衡量的结果关联起来。如何判断方案是否有效？参考问题陈述中的指标并设定目标。
说明权衡取舍 记录明确不会做的事情及原因。优秀的解决方案简报会坦诚说明范围限制，以及那些被考虑但最终被否决的替代方案。
识别风险与缓解措施 指出影响成功的最大风险及应对计划。这能增强利益相关者的信心，并尽早发现潜在问题。
概述下一步行动 提供3-5项推动解决方案落地的即时行动。明确具体责任人及任务。

Output Format

输出格式

Use the template in

references/TEMPLATE.md

to structure the output.

使用

references/TEMPLATE.md

中的模板构建输出内容。

Quality Checklist

质量检查清单

Before finalizing, verify:

Brief fits on one page when printed (approximately 500-700 words)
Problem recap is concise (2-3 sentences maximum)
Solution description avoids technical jargon
Features are limited to 3-5 essential capabilities
Trade-offs are explicitly stated
Next steps are specific and actionable

定稿前，请验证：

打印后简报内容可容纳在单页内（约500-700字）
问题回顾简洁（最多2-3句话）
解决方案描述无技术术语
功能限制为3-5项核心能力
明确说明权衡取舍
下一步行动具体且可执行

Examples

示例

See

references/EXAMPLE.md

for a completed example.

可查看

references/EXAMPLE.md

获取完整示例。

develop-solution-brief

Original

Translation