positioning-workshop

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Purpose

目标

Guide product managers through discovering and articulating product positioning by asking adaptive questions about target customers, unmet needs, product category, benefits, and competitive differentiation. Use this to align stakeholders on strategic positioning before writing PRDs, launch plans, or marketing materials—ensuring you've made deliberate choices about who you serve, what need you address, and how you differ from alternatives.

This is not a brainstorming session—it's a structured discovery process that outputs a Geoffrey Moore positioning statement backed by evidence and strategic choices.

通过提出关于目标客户、未满足需求、产品品类、核心价值及竞争差异化的自适应问题，引导产品经理完成产品定位的发掘与明确工作。可在撰写PRD、发布计划或营销物料前使用本方法，确保所有利益相关方在战略定位上达成一致——明确服务对象、解决的需求以及与竞品的差异。

这并非头脑风暴会议，而是一个结构化的发掘流程，最终产出基于实证与战略选择的Geoffrey Moore式定位声明。

Key Concepts

核心概念

The Positioning Workshop Flow

定位工作坊流程

An interactive discovery process that:

Gathers product context (marketing materials, competitor intel)
Identifies target customer segment through questioning
Uncovers underserved needs via Jobs-to-be-Done lens
Defines product category and benefits
Establishes competitive differentiation
Outputs a complete positioning statement (uses
```
positioning-statement.md
```
)

这是一个交互式发掘流程，包含以下步骤：

收集产品背景信息（营销物料、竞品情报）
通过提问明确目标客户群体
以Jobs-to-be-Done视角发掘未被满足的需求
定义产品品类与核心价值
确立竞争差异化
输出完整的定位声明（使用
```
positioning-statement.md
```
格式）

Why This Works

本方法的优势

Structured discovery: Prevents "positioning by committee" (too vague)
Evidence-based: Uses real marketing materials, customer feedback, competitive intel
Adaptive: Questions adjust based on B2B vs. B2C, new product vs. repositioning, etc.
Actionable output: Generates a Geoffrey Moore positioning statement ready for stakeholder review

结构化发掘： 避免“委员会式定位”（定位过于模糊）
基于实证： 运用真实的营销物料、客户反馈、竞品情报
自适应调整： 根据B2B/B2C、新产品/重新定位等场景调整问题
可落地输出： 生成可供利益相关方评审的Geoffrey Moore式定位声明

Anti-Patterns (What This Is NOT)

反模式（本方法不适用的场景）

Not a tagline generator: Positioning ≠ marketing copy
Not feature-first: Starts with customer problems, not product capabilities
Not consensus-driven: Forces hard choices (can't be "for everyone")

不是标语生成器： 定位≠营销文案
不以功能为导向： 从客户问题出发，而非产品功能
不追求共识妥协： 要求做出明确选择（无法做到“服务所有人”）

When to Use This

适用场景

Defining positioning for a new product
Repositioning an existing product (pivot, market shift)
Aligning stakeholders on product strategy
Preparing for launch or major release
Before writing positioning-dependent artifacts (PRD, press release, sales deck)

为新产品定义定位
为现有产品重新定位（转型、市场变化）
对齐利益相关方的产品战略
为产品发布或重大版本更新做准备
撰写依赖定位的文档前（PRD、新闻稿、销售演示文稿）

When NOT to Use This

不适用场景

Before customer research (positioning requires validated insights)
For internal tools with captive users (no market positioning needed)
When positioning is already clear and validated

客户研究开展前（定位需要经过验证的洞察）
针对内部工具（无市场定位需求）
定位已清晰且经过验证的情况

Facilitation Source of Truth

引导工作的参考标准

Use

workshop-facilitation

as the default interaction protocol for this skill.

It defines:

session heads-up + entry mode (Guided, Context dump, Best guess)
one-question turns with plain-language prompts
progress labels (for example, Context Qx/8 and Scoring Qx/5)
interruption handling and pause/resume behavior
numbered recommendations at decision points
quick-select numbered response options for regular questions (include
```
Other (specify)
```
when useful)

This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.

默认使用

workshop-facilitation

作为本技能的交互协议。

该协议定义了：

会议预告与参与模式（引导式、背景信息导入式、初步猜想式）
单轮提问机制，搭配通俗易懂的提示语
进度标识（例如：背景问题Qx/8、评分问题Qx/5）
中断处理与暂停/恢复规则
决策节点的编号式建议
常规问题的快速选择编号选项（必要时包含“其他（请说明）”）

本文档定义了特定领域的评估内容。若出现冲突，以本文档的领域逻辑为准。

Application

应用方法

This interactive skill asks up to 5 adaptive questions, offering 3-4 enumerated context-aware options at each step.

Interaction pattern: Pair with

skills/workshop-facilitation/SKILL.md

when you want a one-step-at-a-time flow with numbered recommendations at decision points and quick-select options for regular questions. If the user asks for a single-shot output, skip the multi-turn facilitation.

本交互式技能会提出最多5个自适应问题，每个步骤提供3-4个贴合场景的选项。

交互模式：若需要分步推进、在决策节点提供编号建议并为常规问题设置快速选择选项，可与

skills/workshop-facilitation/SKILL.md

搭配使用。若用户要求一次性输出结果，则跳过多轮引导流程。

Step 0: Gather Context (Before Questions)

步骤0：收集背景信息（提问前）

Agent suggests:

Before we begin, let's gather product context to ground our positioning work:

For Your Own Product:

Current website copy (homepage, product pages, value prop)
Existing positioning statements or messaging docs
Customer testimonials or case studies
Sales objections or competitive win/loss analysis
Product descriptions or feature lists

For Repositioning an Existing Product:

Current positioning (what are you saying today?)
Customer feedback or support tickets (what problems do they report?)
Competitive intel (how do competitors position themselves?)

If You Don't Have a Product Yet (or Want to Benchmark):

Find 2-3 competitor or analog products
Copy their website homepage, positioning statements, or value props
We'll use these as reference points

You can paste this content directly, or we can proceed with a brief description.

Agent建议：

在开始前，我们先收集产品背景信息，为定位工作奠定基础：

针对自有产品：

当前网站文案（首页、产品页、价值主张）
现有定位声明或沟通文档
客户 testimonial 或案例研究
销售异议或竞品胜负分析
产品描述或功能列表

针对现有产品重新定位：

当前定位（你当前对外传递的定位是什么？）
客户反馈或支持工单（他们反馈了哪些问题？）
竞品情报（竞品如何定位自身？）

若尚未拥有产品（或想要对标分析）：

找到2-3个竞品或同类产品
复制它们的网站首页、定位声明或价值主张
我们将这些作为参考依据

你可以直接粘贴相关内容，或简要描述信息。

Question 1: Target Customer Segment

问题1：目标客户群体

Agent asks: "Based on the context provided, who is the primary customer segment you're serving?"

Offer 4 enumerated options (adapted based on product context):

B2B: SMB decision-makers — E.g., "Small business owners (10-50 employees) managing operations" (like Gusto, QuickBooks)
B2B: Enterprise buyers — E.g., "IT/Product leaders at companies with 500+ employees" (like Salesforce, Workday)
B2C: Mass market consumers — E.g., "Gen Z users (18-25) seeking budgeting tools" (like Mint, Venmo)
B2C: Niche enthusiasts — E.g., "Fitness enthusiasts tracking macros and workouts" (like MyFitnessPal, Strava)

Or describe your own target customer segment (be specific: demographics, role, company size, behaviors).

Adaptation tip: If marketing materials mention "enterprises," "SMBs," "consumers," or specific personas, suggest those.

User response: [Selection or custom]

Agent提问： “根据提供的背景信息，你服务的核心客户群体是什么？”

提供4个编号选项（根据产品背景调整）：

B2B：中小企业决策者 —— 例如：“管理运营的小企业主（员工规模10-50人）”（类似Gusto、QuickBooks的客户）
B2B：企业级采购者 —— 例如：“员工规模500+企业的IT/产品负责人”（类似Salesforce、Workday的客户）
B2C：大众消费者 —— 例如：“寻求预算工具的Z世代用户（18-25岁）”（类似Mint、Venmo的客户）
B2C：小众爱好者 —— 例如：“追踪宏量营养素与运动的健身爱好者”（类似MyFitnessPal、Strava的客户）

或者描述你自己的目标客户群体（需具体：人口统计特征、角色、公司规模、行为习惯）。

适配提示： 若营销物料中提及“企业”“中小企业”“消费者”或特定用户画像，优先推荐对应选项。

用户回复： [选择或自定义内容]

Question 2: Underserved Need (Jobs-to-be-Done)

问题2：未被满足的需求（Jobs-to-be-Done视角）

Agent asks: "What underserved need or pain point does your target customer experience that your product addresses?"

Offer 4 enumerated options (adapted based on Question 1):

Example (if Q1 = B2B SMB decision-makers):

Time-consuming manual work — E.g., "Spend 10+ hours/week on tasks that should be automated" (invoice processing, payroll, reporting)
Lack of visibility or control — E.g., "Can't see real-time status of projects, causing missed deadlines" (project tracking, dashboards)
Compliance or risk burden — E.g., "Fear of tax penalties or legal issues due to manual errors" (accounting, HR compliance)
Costly inefficiency — E.g., "Losing revenue due to slow processes or customer friction" (sales ops, customer onboarding)

Or describe the specific pain point/unmet need based on customer research, support tickets, or competitive gaps.

Adaptation tip: Use language from customer testimonials or case studies in the provided materials.

User response: [Selection or custom]

Agent提问： “你的目标客户面临哪些未被满足的需求或痛点，而你的产品可以解决这些问题？”

提供4个编号选项（根据问题1的答案调整）：

示例（若问题1答案为B2B中小企业决策者）：

耗时的手工工作 —— 例如：“每周花费10+小时在本可自动化的任务上”（发票处理、薪资核算、报表生成）
缺乏可见性与管控能力 —— 例如：“无法查看项目实时状态，导致错过截止日期”（项目追踪、仪表盘）
合规或风险负担 —— 例如：“因手工操作失误担心面临税务处罚或法律问题”（会计、HR合规）
高成本低效 —— 例如：“因流程缓慢或客户体验不佳导致收入损失”（销售运营、客户入职）

或者基于客户研究、支持工单或竞品差距描述具体的痛点/未满足需求。

适配提示： 使用提供材料中客户 testimonial 或案例研究的表述方式。

用户回复： [选择或自定义内容]

Question 3: Product Category

问题3：产品品类

Agent asks: "What product category does your solution fit into? (This anchors how buyers evaluate you.)"

Offer 4 enumerated options (adapted based on Q1 + Q2):

Example (if Q1 = B2B SMB, Q2 = Time-consuming manual work):

Workflow automation platform — E.g., "Automates repetitive tasks across apps" (like Zapier, Integromat)
Business management software — E.g., "All-in-one platform for operations (invoicing, payroll, CRM)" (like HubSpot, Zoho)
Vertical SaaS — E.g., "Purpose-built for a specific industry (e.g., HVAC, legal, dental)" (like Jobber, Clio)
AI-powered assistant — E.g., "AI tool that automates workflows via natural language" (like Notion AI, Jasper)

Or define your own category. Note: Creating a new category is risky—pick an existing one unless you have strong rationale.

Adaptation tip: If competitors are in a clear category, default to that unless you're deliberately creating a new one.

User response: [Selection or custom]

Agent提问： “你的解决方案属于哪个产品品类？（这决定了买家如何评估你的产品）”

提供4个编号选项（根据问题1+问题2的答案调整）：

示例（若问题1为B2B中小企业，问题2为耗时的手工工作）：

工作流自动化平台 —— 例如：“跨应用自动化重复任务”（类似Zapier、Integromat）
企业管理软件 —— 例如：“一站式运营平台（发票、薪资、CRM）”（类似HubSpot、Zoho）
垂直领域SaaS —— 例如：“为特定行业量身打造（如暖通、法律、牙科）”（类似Jobber、Clio）
AI驱动助手 —— 例如：“通过自然语言自动化工作流的AI工具”（类似Notion AI、Jasper）

或者自定义品类。注意：创建新品类存在风险——除非有充分理由，否则选择现有品类。

适配提示： 若竞品属于明确的品类，默认选择该品类，除非你有意创建新品类。

用户回复： [选择或自定义内容]

Question 4: Key Benefit (Outcome, Not Features)

问题4：核心价值（成果，而非功能）

Agent asks: "What's the primary benefit or outcome your product delivers? (Focus on what the customer gets, not what the product has.)"

Offer 3 enumerated options (adapted based on Q2 need):

Example (if Q2 = Time-consuming manual work):

Time savings — E.g., "Reduces manual work from 10 hours/week to 1 hour" (measurable efficiency)
Error reduction — E.g., "Eliminates 95% of manual data entry errors" (accuracy/risk mitigation)
Cost savings — E.g., "Saves $500/month in labor costs by automating invoicing" (direct ROI)

Or describe the specific, measurable outcome your product delivers.

Quality check: Avoid features ("has AI," "includes dashboards"). Focus on outcomes ("makes decisions 3x faster," "prevents compliance violations").

User response: [Selection or custom]

Agent提问： “你的产品能为客户带来的核心价值或成果是什么？（聚焦客户获得的收益，而非产品具备的功能）”

提供3个编号选项（根据问题2的需求调整）：

示例（若问题2为耗时的手工工作）：

节省时间 —— 例如：“将手工工作从每周10小时减少到1小时”（可衡量的效率提升）
减少错误 —— 例如：“消除95%的手工数据录入错误”（准确性/风险降低）
节省成本 —— 例如：“通过自动化发票处理每月节省500美元人力成本”（直接投资回报）

或者描述产品带来的具体、可衡量的成果。

质量检查： 避免提及功能（“具备AI”“包含仪表盘”）。聚焦成果（“决策速度提升3倍”“避免合规违规”）。

用户回复： [选择或自定义内容]

Question 5: Competitive Differentiation

问题5：竞争差异化

Agent asks: "What's your primary competitor or competitive alternative, and how do you differ?"

Offer 4 enumerated options (adapted based on Q3 category):

Example (if Q3 = Workflow automation platform):

Incumbent SaaS leader — E.g., "Unlike Zapier (which requires technical setup), we offer no-code visual workflows accessible to non-technical users"
Spreadsheets/manual processes — E.g., "Unlike Excel (which requires manual updates), we provide real-time automated sync across tools"
Vertical competitor — E.g., "Unlike generic automation tools, we're pre-built for [industry] with templates and compliance features"
Enterprise-only solutions — E.g., "Unlike enterprise tools (complex, expensive), we're designed for SMBs with simple pricing and 10-minute setup"

Or describe your primary competitive alternative and your unique differentiation (focus on outcomes, not features).

Adaptation tip: Use competitive intel from provided materials (win/loss analysis, sales objections).

User response: [Selection or custom]

Agent提问： “你的主要竞品或替代方案是什么，你与它们的差异在哪里？”

提供4个编号选项（根据问题3的品类调整）：

示例（若问题3为工作流自动化平台）：

成熟SaaS领导者 —— 例如：“与Zapier（需要技术配置）不同，我们为非技术用户提供无需代码的可视化工作流”
电子表格/手工流程 —— 例如：“与Excel（需要手动更新）不同，我们提供跨工具的实时自动同步”
垂直领域竞品 —— 例如：“与通用自动化工具不同，我们为[行业]预建了模板与合规功能”
仅服务企业的解决方案 —— 例如：“与企业级工具（复杂、昂贵）不同，我们专为中小企业设计，定价简单，10分钟即可完成设置”

或者描述你的主要替代方案与独特差异（聚焦成果，而非功能）。

适配提示： 使用提供材料中的竞品情报（胜负分析、销售异议）。

用户回复： [选择或自定义内容]

Output: Generate Positioning Statement

输出：生成定位声明

After collecting responses, the agent generates a positioning statement using the

positioning-statement.md

format:

markdown

undefined

收集所有回复后，Agent将使用

positioning-statement.md

格式生成定位声明：

markdown

undefined

Positioning Statement

Based on your responses, here's your positioning statement:

Value Proposition

For [Target customer from Q1]

that need [Underserved need from Q2]
[Product name]
is a [Product category from Q3]
that [Key benefit from Q4]

For [Target customer from Q1]

that need [Underserved need from Q2]
[Product name]
is a [Product category from Q3]
that [Key benefit from Q4]

Differentiation Statement

Unlike [Primary competitor from Q5]
[Product name]
provides [Unique differentiation from Q5]

Unlike [Primary competitor from Q5]
[Product name]
provides [Unique differentiation from Q5]

Positioning Summary (One-Sentence Version)

[Product name] is a [category] for [target] that [benefit], unlike [competitor] which [limitation].

Example: "Acme Workflows is a no-code automation platform for small business owners that reduces manual work from 10 hours/week to 1 hour, unlike Zapier which requires technical setup and coding knowledge."

[Product name] is a [category] for [target] that [benefit], unlike [competitor] which [limitation].

Next Steps

Stress-test this positioning:
- Read it aloud to 5 target customers. Do they recognize themselves?
- Share with stakeholders (product, marketing, sales). Does it align?
- Check if differentiation is defensible (can competitors copy this in 6 months?).
Refine based on feedback:
- If target feels too broad → Narrow further (e.g., "SMB owners" → "SMB owners in service industries")
- If need isn't resonating → Validate with more customer research
- If category confuses → Pick a clearer category or commit to category creation
Apply to artifacts:
- Update website homepage and product pages
- Revise sales deck and pitch materials
- Use in PRD, press release, or roadmap planning (reference
```
press-release.md
```
  ,
```
positioning-statement.md
```
  )

Would you like to refine any part of this positioning, or shall we document it as final?

---

Stress-test this positioning:
- Read it aloud to 5 target customers. Do they recognize themselves?
- Share with stakeholders (product, marketing, sales). Does it align?
- Check if differentiation is defensible (can competitors copy this in 6 months?).
Refine based on feedback:
- If target feels too broad → Narrow further (e.g., "SMB owners" → "SMB owners in service industries")
- If need isn't resonating → Validate with more customer research
- If category confuses → Pick a clearer category or commit to category creation
Apply to artifacts:
- Update website homepage and product pages
- Revise sales deck and pitch materials
- Use in PRD, press release, or roadmap planning (reference
```
press-release.md
```
  ,
```
positioning-statement.md
```
  )

Would you like to refine any part of this positioning, or shall we document it as final?

---

Examples

示例

Example 1: Good Positioning Workshop (B2B SaaS Automation)

示例1：优质定位工作坊（B2B SaaS自动化）

Step 0 - Context Provided: User shares current website copy:

"Acme Workflows helps small businesses automate repetitive tasks. Connect your apps and save time."

Question 1 Response: "B2B: SMB decision-makers — Small business owners (10-50 employees) managing operations"

Question 2 Response: "Time-consuming manual work — Spend 10+ hours/week on invoice processing, data entry, reporting"

Question 3 Response: "Workflow automation platform — Automates repetitive tasks across apps"

Question 4 Response: "Time savings — Reduces manual work from 10 hours/week to 1 hour"

Question 5 Response: "Incumbent SaaS leader — Unlike Zapier (which requires technical setup), we offer no-code visual workflows accessible to non-technical users"

Generated Positioning Statement:

markdown

undefined

步骤0 - 提供的背景信息： 用户分享当前网站文案：

"Acme Workflows helps small businesses automate repetitive tasks. Connect your apps and save time."

问题1回复： "B2B: SMB decision-makers — Small business owners (10-50 employees) managing operations"

问题2回复： "Time-consuming manual work — Spend 10+ hours/week on invoice processing, data entry, reporting"

问题3回复： "Workflow automation platform — Automates repetitive tasks across apps"

问题4回复： "Time savings — Reduces manual work from 10 hours/week to 1 hour"

问题5回复： "Incumbent SaaS leader — Unlike Zapier (which requires technical setup), we offer no-code visual workflows accessible to non-technical users"

生成的定位声明：

markdown

undefined

Value Proposition

For small business owners (10-50 employees) managing daily operations

that need to eliminate 10+ hours/week spent on manual tasks like invoice processing, data entry, and reporting
Acme Workflows
is a no-code workflow automation platform
that reduces manual work from 10 hours/week to 1 hour by automating repetitive tasks across apps

For small business owners (10-50 employees) managing daily operations

that need to eliminate 10+ hours/week spent on manual tasks like invoice processing, data entry, and reporting
Acme Workflows
is a no-code workflow automation platform
that reduces manual work from 10 hours/week to 1 hour by automating repetitive tasks across apps

Differentiation Statement

Unlike Zapier, which requires technical setup and coding knowledge
Acme Workflows
provides visual, no-code workflows that non-technical business owners can set up in 10 minutes

Unlike Zapier, which requires technical setup and coding knowledge
Acme Workflows
provides visual, no-code workflows that non-technical business owners can set up in 10 minutes

Positioning Summary

Acme Workflows is a no-code automation platform for small business owners that reduces manual work from 10 hours/week to 1 hour, unlike Zapier which requires technical setup and coding knowledge.


**Why this works:**
- Target is specific (SMB owners, 10-50 employees, operations focus)
- Need is measurable (10+ hours/week on manual tasks)
- Category is clear (workflow automation)
- Benefit is outcome-focused (10 hours → 1 hour)
- Differentiation is defensible (no-code vs. technical setup)

---

Acme Workflows is a no-code automation platform for small business owners that reduces manual work from 10 hours/week to 1 hour, unlike Zapier which requires technical setup and coding knowledge.


**成功原因：**
- 目标客户具体（中小企业主，10-50名员工，聚焦运营）
- 需求可衡量（每周10+小时手工任务）
- 品类清晰（工作流自动化）
- 价值聚焦成果（10小时→1小时）
- 差异化具备防御性（无需代码 vs 技术配置）

---

Example 2: Bad Positioning Workshop (Vague)

示例2：劣质定位工作坊（模糊）

Question 1 Response: "Businesses" Question 2 Response: "Need better tools" Question 3 Response: "Software" Question 4 Response: "Productivity" Question 5 Response: "We're better than competitors"

Generated Positioning Statement:

markdown

**For** businesses
- **that need** better tools
- ProductX
- **is a** software
- **that** improves productivity

**Unlike** competitors
- ProductX
- **provides** better features

Why this fails:

Target is too broad ("businesses" = everyone)
Need is vague ("better tools" = meaningless)
Category is not specific ("software" says nothing)
Benefit is unmeasurable ("productivity" = how much?)
Differentiation is empty ("better features" = unverifiable)

How to fix: Go back and answer with specificity. Use customer research, not guesses.

问题1回复： "Businesses" 问题2回复： "Need better tools" 问题3回复： "Software" 问题4回复： "Productivity" 问题5回复： "We're better than competitors"

生成的定位声明：

markdown

**For** businesses
- **that need** better tools
- ProductX
- **is a** software
- **that** improves productivity

**Unlike** competitors
- ProductX
- **provides** better features

失败原因：

目标客户过于宽泛（“企业”=所有人）
需求模糊（“更好的工具”=无意义）
品类不具体（“软件”未传递任何信息）
价值无法衡量（“生产力”=提升了多少？）
差异化空洞（“更好的功能”=无法验证）

改进方法： 返回重新回答，确保内容具体。使用客户研究结果，而非主观猜测。

Common Pitfalls

常见陷阱

Pitfall 1: "For Everyone"

陷阱1：“服务所有人”

Symptom: Target is "all businesses" or "anyone who wants to be productive"

Consequence: Positioning becomes invisible—no one feels it's for them.

Fix: Narrow ruthlessly. Pick the first customer segment. You can expand later.

症状： 目标客户为“所有企业”或“任何想要提升生产力的人”

后果： 定位变得无辨识度——没有人觉得这是“为我量身打造”的。

解决方法： 果断缩小范围。先选择第一个客户群体，后续可再拓展。

Pitfall 2: Need is a Feature Request

陷阱2：需求是功能请求

Symptom: "Need better dashboards" or "Need AI-powered analytics"

Consequence: You've jumped to solution, not problem.

Fix: Ask "Why do they need that?" Keep asking until you hit the root need.

症状： “需要更好的仪表盘”或“需要AI驱动的分析”

后果： 直接跳到了解决方案，而非聚焦问题本身。

解决方法： 追问“他们为什么需要这个？”直到找到根源需求。

Pitfall 3: Category Confusion

陷阱3：品类混淆

Symptom: "We're a next-generation platform for digital transformation"

Consequence: Buyers don't know how to evaluate you.

Fix: Pick a category buyers understand. If creating a new one, budget for category education.

症状： “我们是下一代数字化转型平台”

后果： 买家不知道如何评估你的产品。

解决方法： 选择买家熟悉的品类。若要创建新品类，需预留品类教育的预算。

Pitfall 4: Differentiation is a Feature

陷阱4：差异化是功能

Symptom: "Unlike competitors, we have AI"

Consequence: Features are copiable. Not durable differentiation.

Fix: Focus on outcomes: "Unlike competitors, we reduce setup time from 2 hours to 10 minutes."

症状： “与竞品不同，我们拥有AI”

后果： 功能容易被复制，无法形成长期差异化。

解决方法： 聚焦成果：“与竞品不同，我们将设置时间从2小时缩短到10分钟。”

Pitfall 5: No Customer Validation

陷阱5：未经过客户验证

Symptom: Positioning created in a vacuum, never tested with customers

Consequence: It sounds good internally but doesn't resonate externally.

Fix: Read positioning statement to 5 target customers. If they don't say "Yes, that's me," revise.

症状： 定位在内部凭空产生，从未与客户测试

后果： 在内部听起来不错，但无法引起外部客户共鸣。

解决方法： 向5个目标客户朗读定位声明。如果他们没有说“对，这就是我”，则需要修改。

References

参考资料

Related Skills

External Frameworks

外部框架

Geoffrey Moore, Crossing the Chasm (1991) — Origin of positioning statement format
April Dunford, Obviously Awesome (2019) — Modern positioning methodology

Geoffrey Moore, Crossing the Chasm (1991) —— 定位声明格式的起源
April Dunford, Obviously Awesome (2019) —— 现代定位方法论

Dean's Work

Dean的工作

Positioning Statement Prompt Template

Skill type: Interactive Suggested filename:

positioning-workshop.md

Suggested placement:

/skills/interactive/

Dependencies: Uses

positioning-statement.md

, references

proto-persona.md

jobs-to-be-done.md

problem-statement.md

Positioning Statement Prompt Template

Skill type: Interactive Suggested filename:

positioning-workshop.md

Suggested placement:

/skills/interactive/

Dependencies: Uses

positioning-statement.md

, references

proto-persona.md

jobs-to-be-done.md

problem-statement.md

positioning-workshop

Original

Translation

Purpose

目标

Key Concepts

核心概念

The Positioning Workshop Flow

定位工作坊流程

Why This Works

本方法的优势

Anti-Patterns (What This Is NOT)

反模式（本方法不适用的场景）

When to Use This

适用场景

When NOT to Use This

不适用场景

Facilitation Source of Truth

引导工作的参考标准

Application

应用方法

Step 0: Gather Context (Before Questions)

步骤0：收集背景信息（提问前）

Question 1: Target Customer Segment

问题1：目标客户群体

Question 2: Underserved Need (Jobs-to-be-Done)

问题2：未被满足的需求（Jobs-to-be-Done视角）

Question 3: Product Category

问题3：产品品类

Question 4: Key Benefit (Outcome, Not Features)

问题4：核心价值（成果，而非功能）

Question 5: Competitive Differentiation

问题5：竞争差异化

Output: Generate Positioning Statement

输出：生成定位声明

Positioning Statement

Positioning Statement

Value Proposition

Value Proposition

Differentiation Statement

Differentiation Statement

Positioning Summary (One-Sentence Version)

Positioning Summary (One-Sentence Version)

Next Steps

Next Steps

Examples

示例

Example 1: Good Positioning Workshop (B2B SaaS Automation)

示例1：优质定位工作坊（B2B SaaS自动化）

Value Proposition

Value Proposition

Differentiation Statement

Differentiation Statement

Positioning Summary

Positioning Summary

Example 2: Bad Positioning Workshop (Vague)

示例2：劣质定位工作坊（模糊）

Common Pitfalls

常见陷阱

Pitfall 1: "For Everyone"

陷阱1：“服务所有人”

Pitfall 2: Need is a Feature Request

陷阱2：需求是功能请求

Pitfall 3: Category Confusion

陷阱3：品类混淆

Pitfall 4: Differentiation is a Feature

陷阱4：差异化是功能

Pitfall 5: No Customer Validation

陷阱5：未经过客户验证

References

参考资料

Related Skills

相关技能

External Frameworks

外部框架

Dean's Work

Dean的工作