Update nexus: fix conflicts and sync local changes
This commit is contained in:
Shen Wei
@@ -1,74 +1,74 @@
|
||||
---
|
||||
title: "POC Scoping"
|
||||
type: concept
|
||||
tags: [sales, pre-sales, proof-of-concept, evaluation]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
POC Scoping 是严格限定的概念验证（Proof of Concept）范围设计方法论——将 POC 从"免费试用"转变为有二元结果（成功/失败）的结构化评估，标准在开始前就已明确定义，避免范围蔓延和评估疲劳。
|
||||
|
||||
## Core Principles
|
||||
|
||||
### Start With the Problem Statement
|
||||
> "This POC will prove that [product] can [specific capability] in [buyer's environment] within [timeframe], measured by [success criteria]."
|
||||
|
||||
如果无法写出这句话，POC 就未完成范围定义。
|
||||
|
||||
### Define Success Criteria in Writing Before Starting
|
||||
- 模糊的成功标准 → 模糊的结果 → "我们需要更多时间评估" → 失败
|
||||
- 明确定义：通过标准是什么？未通过标准是什么？
|
||||
|
||||
### Scope Aggressively
|
||||
- POC 最大风险是范围蔓延
|
||||
- 一个聚焦的 POC 证明一个关键结论 > 宽泛的 POC 什么都没证明
|
||||
- 当买家要求增加测试项时："Absolutely — in phase two. Let's nail the core use case first."
|
||||
|
||||
### Hard Timeline
|
||||
- 标准：2-3 周
|
||||
- 更长的 POC 不会产生更好的决策，只会产生评估疲劳和竞争对手反击
|
||||
|
||||
### Build in Checkpoints
|
||||
- 中期检查点确认进度，及早发现偏差
|
||||
- 不要等到最终汇报才发现自己与买家标准不一致
|
||||
|
||||
## POC Scoping Template
|
||||
```markdown
|
||||
# Proof of Concept: [Account Name]
|
||||
|
||||
## Problem Statement
|
||||
[一句话：POC 将证明什么]
|
||||
|
||||
## Success Criteria
|
||||
| Criterion | Target | Measurement Method |
|
||||
|-----------|--------|-------------------|
|
||||
| [能力] | [量化目标] | [测量方法] |
|
||||
| [集成需求] | [通过/失败] | [测试场景] |
|
||||
| [性能基准] | [阈值] | [负载测试] |
|
||||
|
||||
## Scope — In / Out
|
||||
- **In scope**: [具体功能、集成、工作流]
|
||||
- **Out of scope**: [明确不测试的内容及原因]
|
||||
|
||||
## Timeline
|
||||
- Day 1-2: 环境配置
|
||||
- Day 3-7: 核心用例实施
|
||||
- Day 8: 中期检查点
|
||||
- Day 9-12: 完善和边界测试
|
||||
- Day 13-14: 最终汇报和决策会议
|
||||
|
||||
## Decision Gate
|
||||
[最终汇报后，买家基于成功标准做出 GO / NO-GO 决策]
|
||||
```
|
||||
|
||||
## Success Metrics
|
||||
- POC 转化率：80%+ 的 POC 进入商业谈判
|
||||
- 时间到技术决策：中位数 18 天
|
||||
|
||||
## Connections
|
||||
- [[DemoEngineering]] — Demo Engineering 是 POC 执行的前置铺垫
|
||||
- [[SalesEngineer]] — POC Scoping 是 Sales Engineer 的核心能力之一
|
||||
- [[FIA-Framework]] — 竞争定位在 POC 阶段尤为关键
|
||||
|
||||
## Contradictions
|
||||
- 与免费试用的混淆：传统"试用"思维认为越长越好，但 POC Scoping 主张 2-3 周是最佳窗口
|
||||
---
|
||||
title: "POC Scoping"
|
||||
type: concept
|
||||
tags: [sales, pre-sales, proof-of-concept, evaluation]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
POC Scoping 是严格限定的概念验证（Proof of Concept）范围设计方法论——将 POC 从"免费试用"转变为有二元结果（成功/失败）的结构化评估，标准在开始前就已明确定义，避免范围蔓延和评估疲劳。
|
||||
|
||||
## Core Principles
|
||||
|
||||
### Start With the Problem Statement
|
||||
> "This POC will prove that [product] can [specific capability] in [buyer's environment] within [timeframe], measured by [success criteria]."
|
||||
|
||||
如果无法写出这句话，POC 就未完成范围定义。
|
||||
|
||||
### Define Success Criteria in Writing Before Starting
|
||||
- 模糊的成功标准 → 模糊的结果 → "我们需要更多时间评估" → 失败
|
||||
- 明确定义：通过标准是什么？未通过标准是什么？
|
||||
|
||||
### Scope Aggressively
|
||||
- POC 最大风险是范围蔓延
|
||||
- 一个聚焦的 POC 证明一个关键结论 > 宽泛的 POC 什么都没证明
|
||||
- 当买家要求增加测试项时："Absolutely — in phase two. Let's nail the core use case first."
|
||||
|
||||
### Hard Timeline
|
||||
- 标准：2-3 周
|
||||
- 更长的 POC 不会产生更好的决策，只会产生评估疲劳和竞争对手反击
|
||||
|
||||
### Build in Checkpoints
|
||||
- 中期检查点确认进度，及早发现偏差
|
||||
- 不要等到最终汇报才发现自己与买家标准不一致
|
||||
|
||||
## POC Scoping Template
|
||||
```markdown
|
||||
# Proof of Concept: [Account Name]
|
||||
|
||||
## Problem Statement
|
||||
[一句话：POC 将证明什么]
|
||||
|
||||
## Success Criteria
|
||||
| Criterion | Target | Measurement Method |
|
||||
|-----------|--------|-------------------|
|
||||
| [能力] | [量化目标] | [测量方法] |
|
||||
| [集成需求] | [通过/失败] | [测试场景] |
|
||||
| [性能基准] | [阈值] | [负载测试] |
|
||||
|
||||
## Scope — In / Out
|
||||
- **In scope**: [具体功能、集成、工作流]
|
||||
- **Out of scope**: [明确不测试的内容及原因]
|
||||
|
||||
## Timeline
|
||||
- Day 1-2: 环境配置
|
||||
- Day 3-7: 核心用例实施
|
||||
- Day 8: 中期检查点
|
||||
- Day 9-12: 完善和边界测试
|
||||
- Day 13-14: 最终汇报和决策会议
|
||||
|
||||
## Decision Gate
|
||||
[最终汇报后，买家基于成功标准做出 GO / NO-GO 决策]
|
||||
```
|
||||
|
||||
## Success Metrics
|
||||
- POC 转化率：80%+ 的 POC 进入商业谈判
|
||||
- 时间到技术决策：中位数 18 天
|
||||
|
||||
## Connections
|
||||
- [[DemoEngineering]] — Demo Engineering 是 POC 执行的前置铺垫
|
||||
- [[SalesEngineer]] — POC Scoping 是 Sales Engineer 的核心能力之一
|
||||
- [[FIA-Framework]] — 竞争定位在 POC 阶段尤为关键
|
||||
|
||||
## Contradictions
|
||||
- 与免费试用的混淆：传统"试用"思维认为越长越好，但 POC Scoping 主张 2-3 周是最佳窗口
|
||||
|
||||
Reference in New Issue
Block a user