产品市场定位策略

作者原文

Find and own a defensible market position. Use when messaging sounds like competitors, conversion is weak despite awareness, repositioning a product, or testing positioning claims. Includes Crawl-Walk-Run rollout methodology and the word change that improved enterprise deal progression.

SkillPi 解读

能完成的任务

产品市场定位策略

适合谁

请按作者原文中的适用场景判断。

输入和输出

以作者完整文档为准；本站未运行验证产物。

软件、账号及付费要求

使用前按完整文档确认软件、账号、费用及权限；由宿主核对并授权实际文件读写和外部服务。文档引用域名（非运行白名单）：github.com, linkedin.com

限制与区别

原文中的功能、版本状态和效果描述属于作者陈述；中文为对应翻译。仅核对固定版本及静态附件证据，不保证运行效果、外部服务或兼容性。

实测状态

未测试

安全评级与访问范围

caution · 静态证据核验，不代表运行安全保证。

使用前按完整文档确认软件、账号、费用及权限；由宿主核对并授权实际文件读写和外部服务。文档引用域名（非运行白名单）：github.com, linkedin.com

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地；本站的核验不会授予任何运行权限。

原始 SKILL.md

---
name: gtm-positioning-strategy
description: Find and own a defensible market position. Use when messaging sounds like competitors, conversion is weak despite awareness, repositioning a product, or testing positioning claims. Includes Crawl-Walk-Run rollout methodology and the word change that improved enterprise deal progression.
license: MIT
metadata:
  author: Smit Patel (https://linkedin.com/in/smitkpatel)
  source: https://github.com/beingsmit/technical-product-gtm
---

# Positioning Strategy

Find and own a defensible market position. Turn generic messaging into clear differentiation — or at least test whether your differentiation actually resonates before committing to it.

## When to Use

**Triggers:**
- "Our messaging sounds exactly like competitors"
- "Brand awareness is strong but conversion is weak"
- "Sales team can't explain why we're different"
- "Buyers see us as interchangeable"
- "Should we reposition before we rebrand?"
- "How do we test positioning claims?"

**Context:**
- Competitive markets with similar offerings
- Messaging that isn't converting
- New product launches
- Repositioning existing products
- Sales team reports buyer confusion

---

## Core Frameworks

### 1. One Word Can Change Everything (The "Autonomous" Problem)

**The Pattern:**

Early enterprise conversations for an autonomous AI product. Positioned as "autonomous AI agent."

Developers: "Cool, but scary."
Managers: "Will this replace our team?"
Deal progression: Slow. Lots of "we'll think about it."

**The Change:**

One word: "autonomous" → "AI teammate"

Same product. Same capabilities. Different framing.

**Result:**

Developers: "This helps me."
Managers: "This makes my team more productive."
Deal progression: Measurably faster.

**Why This Matters:**

Positioning isn't what you do. It's what you **don't say**.

We could've said "replaces developers" (technically true for some tasks). Would've killed every enterprise deal.

**The Framework: Word Choice Shapes Buyer Psychology**

**Words that scare enterprises:**
- Autonomous (implies: no control, replacing humans)
- Replaces (threatens: job security)
- Fully automated (removes: human judgment)
- AI-first (means: unclear, buzzword)

**Words that convert:**
- Teammate (implies: collaboration, helping)
- Augments (helps: makes humans better)
- You stay in control (reassures: human oversight)
- Handles repetitive work (specific: saves time)

**How to Test Word Choice:**

Don't guess. Test.

**Test 1: Outbound Email A/B**
- Send 100 prospects Version A ("autonomous agent")
- Send 100 prospects Version B ("AI teammate")
- Measure: Reply rate, meeting booked rate
- Signal strength: High (real buyer intent)

**Test 2: Website Homepage A/B**
- Version A: Current positioning
- Version B: New word choice
- Measure: Click-through rate on key CTAs
- Duration: 1-2 weeks minimum
- Signal strength: Moderate (interest without commitment)

**Test 3: Sales Call Scripts**
- Half of AEs use positioning A
- Half use positioning B
- Measure: Demo-to-trial conversion
- Signal strength: High (real sales cycle)

**Common Mistake:**

Changing positioning based on internal consensus, not customer feedback. Your team isn't the buyer.

---

### 2. Test Before You Commit (Crawl-Walk-Run Positioning Rollout)

**The Pattern:**

Positioning changes create risk. Brand confusion. Sales misalignment. Customer churn (if existing customers don't recognize you).

**De-risk through phased rollout:**

**Crawl Phase (1-2 weeks): Validation**

Test messaging without committing product/org resources.

**Actions:**
- A/B test website headlines (new vs incumbent)
- Run two outbound email sequences (different positioning angles) to cold prospects
- Ask existing customers: "If we described ourselves as [new positioning], would you still recognize us?"

**Measurement:**
- Track CTR on web variants
- Track reply rates on outbound sequences
- Document qualitative feedback

**Go/No-Go:**
- At least one positioning variant outperforms incumbent by 20%+ on reply rate
- Existing customers don't say "wait, that's not what you do"
- Proceed if clear winner; if tied, run longer or test new angles

**Walk Phase (2-3 weeks): Alignment**

If testing validates, align product and sales to new positioning (but don't rebrand publicly yet).

**Actions:**
- Rewrite website copy (homepage, enterprise pages, CTAs)
- Create sales enablement: updated pitch deck, call scripts, email templates
- Update documentation to match new narrative
- Build use-case-specific examples

**Measurement:**
- Sales team feedback on messaging usability
- Website analytics on engagement (not conversion yet)
- Segment analysis (who's responding?)

**Go/No-Go:**
- Sales team says new messaging is easier to use
- CTR metrics improve vs incumbent
- No major customer confusion
- Proceed to Run

**Run Phase (2-3 weeks and ongoing): Scale**

Full commitment. This is the rebrand.

**Actions:**
- Launch dedicated landing pages per use case
- Outbound campaigns per positioning angle
- Update all customer-facing materials
- Train customer success team on new narrative
- Announce repositioning (if appropriate)

**Measurement:**
- Pipeline volume by positioning angle
- Win rate by positioning angle
- CAC efficiency by channel
- Customer retention (did we lose anyone?)

**Common Mistakes:**
- Skipping Crawl (jumping to full rebrand without validation)
- Running phases in parallel (creates confusion if messaging changes mid-rollout)
- Waiting for perfect product before repositioning (product should follow positioning, not precede it)
- Not measuring at each phase (can't determine if test "won")

---

### 3. Positioning Clarity Diagnosis

**The Pattern:**

If your messaging closely resembles competitors' messaging, you have a positioning problem, not a product problem.

**Positioning Failure Manifests As:**
- All competitors describe nearly identical value props
- Differentiation requires explaining complex technical details
- Buyers see offerings as interchangeable
- Marketing metrics (CTR, engagement) weak vs industry benchmarks
- Sales conversations get derailed by comparison questions

**How to Execute:**

**Step 1: Competitor Messaging Audit**
- Collect homepage headlines from 5-7 direct competitors
- Identify shared claims (these are commoditized)
- Map where competitors claim unique value

**Example:**

If everyone says "fastest," "most reliable," "easiest to use" — these are table stakes, not differentiation.

**Step 2: Assess Your Actual Strengths**
- What can you do that competitors can't, without massive R&D?
- What do your best customers choose you for? (Ask them)
- What structural advantages do you have? (Deployment model, data ownership, pricing, network effects, etc.)

**Step 3: Find Under-Served Position**
- Where do existing solutions fail users?
- What problem is everyone ignoring?
- What buyer segment is under-served?

**Step 4: Stake a Clear Claim**

Must be:
- Something you can own now (not future roadmap)
- Something competitors can't easily copy (structural advantage)
- Resonant with your best customer segments

**Common Mistakes:**
- Claiming you're "better" at what everyone does (unbelievable)
- Positioning on features competitors already have
- Multiple positions simultaneously (choose one)
- Waiting for perfect product before positioning shift

---

### 4. Market Positioning Architecture (Three Layers)

**Layer 1: Market Context**
- What problem is the market experiencing?
- Why is it experiencing this problem now?
- What happens if problem goes unsolved?

**Example:**
"Infrastructure teams manage increasingly complex deployments across hybrid environments. Organizations adopt microservices and distributed systems. This creates operational complexity that traditional monitoring tools can't handle."

**Layer 2: Positioning Statement (1-2 sentences)**
- **Who we serve**: What customer segment?
- **What problem we solve**: The specific pain
- **How we're different**: Why we matter vs alternatives
- **Proof**: Why should they believe us?

**Example:**
"We help platform teams ship faster through [core capability] that connects [workflow A], [workflow B], and [business outcome] in real-time."

**Layer 3: Narrative**

Expand positioning into story:
- Why the world is changing
- Why existing solutions don't work
- Why our approach is better
- What the future looks like with us

**How to Execute:**

Write all three layers before testing. Test Layer 2 (positioning statement) first with Crawl-Walk-Run methodology. If that validates, build out Layer 3.

---

### 5. Headline and Sub-headline Testing

**Principle:** Clear positioning requires testable structure: headline (what are you?) + sub-headline (for whom? why?).

**Main Headline Formats:**
- "The [adjective] [category] that [differentiator]"
- "[Product] for [specific use case]"
- "[Product] that [core benefit]"

**Examples:**
- "The customizable platform for [workflow]"
- "Infrastructure for autonomous teams"
- "The enterprise-grade alternative to [incumbent]"

**Red Flags:**
- Using competitor name (defensive, not confident)
- Too technical (buyer won't understand)
- Claiming multiple benefits (choose one)
- Vague ("the future of X" — unbelievable)

**Sub-headline Purpose:**

Clarifies who, why, how it's different from status quo.

**Examples:**
- "Deploy anywhere. Scale instantly. Your infrastructure, your rules."
- "For teams drowning in repetitive work. Automation that handles the 80%, humans handle the 20%."
- "Enterprise-grade. No lock-in. Works with your existing stack."

**How to Test:**

A/B test headline + sub-headline combinations:
- Variant A: Current messaging
- Variant B: New positioning angle
- Variant C: Different differentiation claim

Measure CTR, reply rates, conversion.

Pick winner based on data, not opinion.

---

### 6. Positioning Defensibility Assessment

**Principle:** A positioning is only valuable if competitors can't easily copy it.

**Defensibility Hierarchy:**

**1. Structural Advantage (Strongest)**
- Hard to copy: unique data ownership, deployment flexibility, pricing model, network effects
- Example: "Built for regulated industries with on-prem deployment" (can't copy without rebuilding architecture)

**2. Market Position (Strong if First)**
- Defensible if you own it first and scale
- Example: "First AI platform for [specific workflow]" (copycats look derivative)

**3. Product Feature (Weak)**
- Easy to copy: UX, specific capability
- Example: "Faster API calls" (competitor ships speed improvement in 6 weeks)

**How to Assess:**

For each positioning claim, ask:

1. Can competitor copy this with single product sprint? (Yes = not defensible)
2. Do we have structural advantage? (No = temporary positioning)
3. Is this credible given current product? (No = don't claim it yet)
4. Can we own this position before competitors react? (No = too slow)

**Common Mistake:**

Positioning on features competitors can easily match. This creates positioning treadmill — you're always defending, never owning.

---

## Decision Trees

### Should We Reposition?

```
Is brand awareness strong but conversion weak?
├─ Yes → Positioning problem, test new angles
└─ No → Continue...
    │
    Does our messaging sound like competitors?
    ├─ Yes → Positioning problem
    └─ No → Not a positioning issue
```

### Which Positioning Angle Should We Test?

```
Do we have structural advantage competitors can't copy?
├─ Yes → Position on structural advantage
└─ No → Continue...
    │
    Are we first in a category?
    ├─ Yes → Position on category ownership
    └─ No → Find under-served segment/use case
```

### Should We Move from Crawl to Walk Phase?

```
Did new positioning outperform incumbent by 20%+?
├─ Yes → Move to Walk (alignment phase)
└─ No → Continue...
    │
    Did we run test long enough (2+ weeks)?
    ├─ No → Run longer
    └─ Yes → Try different positioning angle or stay with incumbent
```

---

## Common Mistakes

**1. Claiming to be "better" at what everyone does**
   - Unbelievable. Find different angle.

**2. Positioning on easily-copied features**
   - Competitors will match. Need structural advantage.

**3. Waiting for perfect product before positioning shift**
   - Product work should follow positioning, not precede

**4. Testing too many positioning angles simultaneously**
   - Can't determine what's working. Test one at a time.

**5. Skipping validation phase**
   - Jumping to full rebrand without testing = risk

**6. One positioning for all buyer personas**
   - Different personas care about different things

**7. Generic positioning that doesn't differentiate**
   - "Best-in-class," "innovative" = meaningless

---

## Quick Reference

**Crawl-Walk-Run Testing:**
- Crawl (1-2 weeks): A/B test messaging, measure reply rates
- Walk (2-3 weeks): Align sales/product to winning angle
- Run (ongoing): Full repositioning, measure pipeline/conversion

**Word choice that converts:**
- ✅ Teammate, augments, you stay in control
- ❌ Autonomous, replaces, fully automated

**Positioning audit steps:**
1. Collect competitor messaging
2. Identify your actual strengths (ask customers)
3. Find under-served position
4. Stake clear, defensible claim

**Defensibility hierarchy:**
1. Structural advantage (unique data, deployment flexibility, pricing model)
2. Market position (category ownership)
3. Product feature (weakest, easily copied)

**Testing hierarchy (signal strength):**
1. Outbound reply rates (highest)
2. Sales call conversion (high)
3. Website CTR (moderate)

---

## Related Skills

- **ai-gtm**: AI-specific positioning (copilot vs agent vs teammate)
- **technical-product-pricing**: Price as a positioning signal
- **0-to-1-launch**: Positioning for new product launches

---

*Based on positioning work at AI agent and developer platforms, including navigating the framing spectrum from "autonomous" to "AI companion" and how category framing changes enterprise buyer perception. Also includes Crawl-Walk-Run rollout methodology from repositioning products without breaking existing customer recognition. Not theory — patterns from testing positioning before committing to rebrands.*

版权与许可声明

MIT License

Copyright GitHub, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.