Auto-sync: 2026-04-21 04:02
This commit is contained in:
@@ -1,27 +1,31 @@
|
||||
---
|
||||
title: "Executive Summary"
|
||||
type: concept
|
||||
tags: [Proposal, Sales, Strategy]
|
||||
last_updated: 2026-04-20
|
||||
tags: [Proposal, Sales, Strategy, consulting, decision-making, c-suite]
|
||||
sources: []
|
||||
last_updated: 2026-04-21
|
||||
---
|
||||
|
||||
## Definition
|
||||
执行摘要是提案最关键的部分,许多评估者尤其是高级利益相关者只阅读此部分。它不是提案的总结,而是放在最前面的结束论证。
|
||||
执行摘要,一种针对 C-suite 决策者的结构化简报格式,要求在 325-475 字内传达复杂业务信息的核心要点。提案中的执行摘要是最关键的部分,许多评估者尤其是高级利益相关者只阅读此部分。
|
||||
|
||||
## Structure
|
||||
1. **Mirror the buyer's situation**(2-3 句,证明你倾听并理解了他们的处境)
|
||||
## Format Requirements
|
||||
- **长度**:325-475 words(≤ 500 max)
|
||||
- **量化**:每个关键发现必须包含 ≥ 1 个量化或比较数据点
|
||||
- **结构**:5 部分(SITUATION OVERVIEW / KEY FINDINGS / BUSINESS IMPACT / RECOMMENDATIONS / NEXT STEPS)
|
||||
- **可操作性**:建议必须包含 Owner + Timeline + Expected Result
|
||||
|
||||
## Format for C-suite Decision Making
|
||||
1. **Mirror the buyer's situation**(2-3 句)
|
||||
2. **Introduce the central tension**—不行动的成本或错失的机会
|
||||
3. **Present your thesis**—你的方法如何解决这个矛盾(制胜主题在此出现)
|
||||
4. **Offer proof**—一个或两个具体证据点(指标、类似案例、差异化因素)
|
||||
5. **Close with the transformed state**—他们可以期望的具体结果
|
||||
3. **Present your thesis**—你的方法如何解决这个矛盾
|
||||
4. **Offer proof**—具体证据点
|
||||
5. **Close with the transformed state**—具体结果
|
||||
|
||||
## Key Principles
|
||||
- 保持在一页以内
|
||||
- 每一句都必须有其存在的价值
|
||||
- 从买家的语言出发,不是从你的解决方案出发
|
||||
- 制胜主题必须在此部分出现
|
||||
## Frameworks Used
|
||||
- [[McKinsey SCQA Framework]]
|
||||
- [[BCG Pyramid Principle]]
|
||||
- [[Bain Action-Oriented Model]]
|
||||
|
||||
## Connections
|
||||
- [[Executive Summary]] ← critical_section_of ← [[Proposal Strategy]]
|
||||
- [[Executive Summary]] ← contains ← [[Win Theme]]
|
||||
- [[Executive Summary]] → leads_to → [[Three-Act Proposal Narrative]]
|
||||
## Related Entities
|
||||
- [[Executive Summary Generator]]
|
||||
Reference in New Issue
Block a user