Positioning Statement (Geoffrey Moore)

# Positioning Statement (Geoffrey Moore)

Create a Geoffrey Moore-style positioning statement articulating who your product serves, what need it addresses, how it's categorized, what benefit it delivers, and how it differs from alternatives. Align stakeholders on strategy, guide messaging, test if value prop is crisp and defensible.

Not a tagline or elevator pitch — a strategic clarity tool that forces hard choices about target, need, and differentiation.

## The Framework

From *Crossing the Chasm* (Geoffrey Moore). Two parts:

### Value Proposition

- **For** [target customer]
- **that need** [underserved need]
- [product name]
- **is a** [product category]
- **that** [benefit statement]

### Differentiation Statement

- **Unlike** [primary competitor or competitive alternative]
- [product name]
- **provides** [unique differentiation]

## Why This Works

- **Forces specificity** — can't say "for everyone" or "unlike all competitors"
- **Exposes assumptions** — if you can't fill "unlike X," differentiation may not be defensible
- **Focuses on outcomes, not features** — "reduces churn 40%" > "has analytics"
- **Category anchors perception** — "is a CRM" vs. "is a workflow tool" changes buyer evaluation

## Anti-Patterns

- Not a tagline ("Nike: Just Do It" ≠ positioning)
- Not a feature list (no "AI, automation, integrations")
- Not generic ("for businesses that need efficiency" = theater)
- Not aspirational fluff ("revolutionizes productivity")

## When to Use

**Use:** New product or major pivot, aligning founders/exec/PM/marketing, testing differentiation, before PRDs/launch plans/sales collateral.
**Don't use:** Internal tools with captive users, still in problem validation, substitute for customer research.

## Application

### Step 1: Gather Context

- **Target customer segment** — Demographics, behaviors, role (not "SMBs" or "developers")
- **Underserved need** — Pains, gains, JTBD (see `jobs-to-be-done`)
- **Product category** — How buyers mentally file your solution
- **Competitive landscape** — Direct competitors AND substitute behaviors ("Excel" is often the real competitor)

**Missing context?** Don't guess — use discovery interviews, market research, or customer interviews.

### Step 2: Draft Value Proposition

```markdown
## Value Proposition

**For** [specific target customer/persona]
- **that need** [underserved need — pains, gains, JTBD]
- [product name]
- **is a** [product category]
- **that** [benefit — outcomes, not features]
```

**Quality checks:**
- **Target specificity:** Could you describe this person to a recruiter?
- **Need clarity:** Does it resonate emotionally, or is it generic?
- **Category fit:** Does category help or box you in?
- **Outcome focus:** Saying what user *gets*, not what product *has*?

### Step 3: Draft Differentiation Statement

```markdown
## Differentiation Statement

- **Unlike** [primary competitor or alternative]
- [product name]
- **provides** [unique differentiation — outcomes]
```

**Quality checks:**
- **Competitor honesty:** Real alternative buyers consider? (Not who you wish.)
- **Substance:** Could a competitor copy in 6 months? If yes, not durable.
- **Outcome framing:** What users *achieve* differently, not what you *do* differently?

### Step 4: Stress-Test

1. **Would a customer recognize themselves?** Read aloud — specific or generic?
2. **Is the need defensible?** Point to research/interviews/data?
3. **Does category help or hurt?** Anchors against right competitors or boxes in?
4. **Is differentiation believable?** Prove with demo, case study, data?
5. **Does it guide decisions?** "Should we build feature X?" — does positioning answer?

If any "no" or "sort of," revise.

### Step 5: Socialize and Iterate

- Share with founders, execs, product, marketing, sales
- Test with customers (read aloud — do they nod or look confused?)
- Refine ruthlessly — never done on first draft

## Examples

```markdown
**For** software development teams
- **that need** to reduce email overload and improve real-time collaboration
- Slack
- **is a** team messaging platform
- **that** centralizes communication and makes conversations searchable

**Unlike** email and other chat tools
- Slack
- **provides** persistent, searchable, organized conversations integrated with the tools teams already use
```

## Common Pitfalls

1. **"For everyone"** — "For businesses that want to grow" → no one feels it's for them; pick first segment
2. **Feature creep** — "Provides AI, automation, analytics, integrations" → lead with outcome; features are HOW, not WHY
3. **Imaginary competitor** — "Unlike outdated legacy systems" → straw man; name actual competitor (often Excel)
4. **Unprovable differentiation** — "Revolutionary AI" → make falsifiable: "10x faster queries than Snowflake on <1TB datasets"
5. **Category confusion** — "Next-gen platform for digital transformation" → buyers don't know how to evaluate; pick understood category

## References

- `problem-statement` — Defines problem positioning addresses
- `jobs-to-be-done` — Informs "that need" statement
- `proto-persona` — Defines "For [target]" segment
- `press-release` — Positioning informs messaging
- Geoffrey Moore, *Crossing the Chasm* (1991)
- April Dunford, *Obviously Awesome* (2019) — modern positioning playbook
- Al Ries & Jack Trout, *Positioning: The Battle for Your Mind* (1981)