Auto-sync: 2026-04-20 09:58
This commit is contained in:
24
wiki/concepts/Technical-Discovery.md
Normal file
24
wiki/concepts/Technical-Discovery.md
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: "Technical Discovery"
|
||||
type: concept
|
||||
tags: [sales, pre-sales, methodology]
|
||||
---
|
||||
|
||||
## Definition
|
||||
结构化需求分析过程,揭示买方架构、集成需求、安全约束和真正的技术决策标准,而非仅依赖公开的 RFP 文档。
|
||||
|
||||
## Core Elements
|
||||
- 架构需求分析
|
||||
- 集成点识别
|
||||
- 安全约束确认
|
||||
- 技术决策标准挖掘
|
||||
- 真实需求 vs 表面需求区分
|
||||
|
||||
## Relationship to Sales Engineer
|
||||
技术发现是售前工程师的核心能力之一,在 POC 和演示之前必须完成。发现的质量直接决定后续所有技术活动的方向正确性。
|
||||
|
||||
## Connections
|
||||
- [[Sales Engineer]] — 执行技术发现的主体
|
||||
- [[Demo Engineering]] — 技术发现的输出用于设计演示
|
||||
- [[POC-Scoping]] — 技术发现的结果定义 POC 范围
|
||||
- [[Solution Architecture]] — 技术发现是解决方案架构的前置输入
|
||||
Reference in New Issue
Block a user