Home
cd ../playbooks
Product ManagementIntermediate

Positioning Workshop

Run a structured 5-question discovery (target → need → category → benefit → differentiation) that outputs a Geoffrey Moore positioning statement — not a brainstorm, a forcing function for hard choices.

90 minutes
By communitySource
#positioning#workshop#strategy#messaging#differentiation#geoffrey-moore

Your last positioning workshop ended with a tagline and a vibe — "empower modern teams to do more." Six months later, marketing, sales, and product each describe the product differently and the deck sounds like every competitor's. A positioning workshop isn't a brainstorm — it's a structured discovery that asks the same five questions and forces real answers, including "unlike whom" and "how do we prove it."

Who it's for: PMs running positioning sessions, founders aligning stakeholders, marketing leads sharpening messaging, sales enablement defining competitive narrative

Example

"Run a positioning workshop for our B2B automation tool" → Target: SMB owners (10-50 emp) / Need: 10+ hours/week manual work / Category: workflow automation / Benefit: 10hr→1hr / Differentiation: Unlike Zapier (technical setup) we provide visual no-code workflows

CLAUDE.md Template

New here? 3-minute setup guide → | Already set up? Copy the template below.

# Positioning Workshop

Run a structured 5-question discovery process that outputs a Geoffrey Moore positioning statement backed by evidence and strategic choices. Not a brainstorm — a forcing function for hard decisions about target, need, category, benefit, and differentiation.

Pairs with `positioning-statement` (output format), `proto-persona`, `jobs-to-be-done`, and `problem-statement`.

## Why This Works

- **Structured discovery** prevents positioning by committee
- **Evidence-based** — uses real marketing copy, customer feedback, competitive intel
- **Adaptive** — questions adjust based on B2B vs. B2C, new vs. repositioning
- **Actionable output** — Geoffrey Moore statement ready for stakeholder review

**Anti-patterns:** Not a tagline generator. Not feature-first. Not consensus-driven (forces hard choices).

## When to Use

**Use:** New product, repositioning (pivot/market shift), aligning stakeholders, before launch, before positioning-dependent artifacts (PRD, press release, sales deck).
**Don't use:** Before customer research, internal tools with captive users, when positioning is already validated.

## Application

### Step 0: Gather Context

**For your product:** website copy, existing messaging docs, customer testimonials, sales objections, competitive win/loss.
**For repositioning:** current positioning, customer feedback, competitor messaging.
**No product yet:** 2-3 competitor/analog products as benchmarks.

### Question 1: Target Customer Segment

"Who is the primary customer segment you serve?"

1. **B2B SMB decision-makers** — small business owners (10-50 employees)
2. **B2B Enterprise buyers** — IT/Product leaders at 500+ employee firms
3. **B2C mass market** — e.g., Gen Z budgeting, millennial fitness
4. **B2C niche enthusiasts** — fitness trackers, hobbyists
5. **Other** — describe (demographics, role, size, behaviors)

### Question 2: Underserved Need (JTBD)

"What underserved need or pain does the target experience that you address?"

Example options for SMB:
1. Time-consuming manual work (10+ hours/week on automatable tasks)
2. Lack of visibility/control (real-time status missing)
3. Compliance or risk burden (tax, HR, legal exposure)
4. Costly inefficiency (revenue loss from slow processes)
5. Other — describe based on customer research

**Adaptation:** mirror language from testimonials and case studies.

### Question 3: Product Category

"What category does your solution fit? (Anchors how buyers evaluate.)"

Example for SMB + manual work:
1. Workflow automation platform (Zapier, Integromat)
2. Business management software (HubSpot, Zoho)
3. Vertical SaaS (Jobber, Clio)
4. AI-powered assistant (Notion AI, Jasper)
5. Other — define your own (warning: category creation is expensive)

### Question 4: Key Benefit (Outcome, Not Features)

"What outcome does your product deliver?"

Example for manual-work need:
1. Time savings — 10 hours/week → 1 hour
2. Error reduction — 95% fewer manual entry errors
3. Cost savings — $500/month in labor savings
4. Other — measurable outcome only

**Quality check:** Reject features ("has AI"). Accept outcomes ("makes decisions 3x faster").

### Question 5: Competitive Differentiation

"Primary competitor or alternative, and how do you differ?"

Example for workflow automation:
1. Incumbent SaaS leader (Zapier requires technical setup)
2. Spreadsheets/manual (Excel requires manual updates)
3. Vertical competitor (generic tools lack industry templates)
4. Enterprise-only (complex/expensive vs. SMB-friendly)
5. Other — name the real alternative + outcome differentiation

### Output: Generate Positioning Statement

```markdown
## Value Proposition
**For** [target from Q1]
- **that need** [need from Q2]
- [product]
- **is a** [category from Q3]
- **that** [benefit from Q4]

## Differentiation Statement
- **Unlike** [competitor from Q5]
- [product]
- **provides** [unique differentiation from Q5]

## Positioning Summary (One-Sentence)
[Product] is a [category] for [target] that [benefit], unlike [competitor] which [limitation].
```

### Next Steps

1. **Stress-test** — read aloud to 5 customers; share with stakeholders; check defensibility (6-month copy test)
2. **Refine** — narrow target, validate need, clarify category
3. **Apply** — homepage, sales deck, PRD, press release

## Common Pitfalls

1. **"For everyone"** → narrow ruthlessly; pick first segment
2. **Need is a feature request** → ask "why do they need that?" until root need
3. **Category confusion** → pick a category buyers know
4. **Differentiation is a feature** → focus on outcome differentiation
5. **No customer validation** → read to 5 customers; revise if confused

## References

- `positioning-statement` — output format
- `proto-persona` — defines "For [target]"
- `jobs-to-be-done` — informs "that need"
- `problem-statement` — supports positioning
- `press-release` — applies positioning
- Geoffrey Moore, *Crossing the Chasm* (1991)
- April Dunford, *Obviously Awesome* (2019)
README.md

What This Does

Walks through 5 adaptive questions (target → need → category → benefit → differentiation) and outputs a Geoffrey Moore positioning statement plus a one-sentence summary. Each question offers 3-4 enumerated options grounded in your context (B2B/B2C, SMB/enterprise, new/repositioning).

Pairs with positioning-statement (output format), proto-persona, jobs-to-be-done, and problem-statement. Feeds into press-release and PRD messaging.


Quick Start

mkdir -p ~/Documents/PositioningWorkshop
mv ~/Downloads/CLAUDE.md ~/Documents/PositioningWorkshop/
cd ~/Documents/PositioningWorkshop
claude

Provide product context (website copy, marketing materials, competitor messaging). Claude facilitates the 5-question flow and outputs a complete positioning statement.


The Flow

Phase Question Output
0 Gather context (website, testimonials, competitive intel) Grounding material
1 Who's your target customer? Specific segment
2 What underserved need? JTBD-style pain
3 What category? Buyer mental file
4 What benefit/outcome? Measurable result
5 Who's the competitor? Real alternative + differentiation
Output Geoffrey Moore statement For/that need/is a/that + Unlike/provides

Tips & Best Practices

  • Use real artifacts. Paste your website copy, sales objections, competitor pages — don't workshop in a vacuum.
  • Resist consensus. Positioning forces hard choices; "let's serve both segments" is the failure mode.
  • Outcome-only benefits. "Has AI" is a feature; "makes decisions 3x faster" is positioning.
  • Name the real competitor. Excel/spreadsheets/email threads are often the actual alternative — not the competitor you wish you fought.
  • Read aloud to customers. If they don't say "yes that's me," go back to Q1 or Q2.

Common Pitfalls

  • "For everyone" or "for businesses" — invisible to all
  • Solution-first answers ("we need better dashboards" instead of root need)
  • Category creation without budget for category education
  • Feature-list differentiation ("unlike competitors, we have AI")
  • Solo PM workshop with no customer validation

$Related Playbooks

Product Management

PRD Development

Build a structured PRD that connects problem, users, solution, and success criteria across 8 phases — from scattered Slack threads to engineering-ready document for major initiatives.

2-3 days
Intermediate
Product Management

Press Release (Amazon Working Backwards)

Write a customer-perspective press release before building — Amazon's Working Backwards forcing function for clarity. If you can't write a compelling PR, the idea may be weak.

60 minutes
Intermediate
Product Management

Prioritization Framework Advisor

Pick the right prioritization framework (RICE, ICE, Value/Effort, Kano, Buy-a-Feature) based on product stage, team context, decision needs, and data availability — avoid framework whiplash.

30 minutes
Intermediate
Product Management

Problem Framing Canvas (MITRE)

Run MITRE's three-phase canvas — Look Inward (your biases), Look Outward (who's affected and who's left out), Reframe (problem + How Might We) — to solve the right problem before solutions.

60-90 minutes
Intermediate
Product Management

Problem Statement (User-Centered)

Write an empathy-driven problem statement (I am / Trying to / But / Because / Which makes me feel) that frames product work around user outcomes — not feature requests or business symptoms.

30 minutes
Beginner
Product Management

Product Analysis

Multi-path parallel product analysis with cross-model test-time compute — spawn parallel agents to explore your product from multiple angles, then synthesize an actionable optimization plan.

20 minutes
Advanced
Product Management

Product Sense Interview Answer

Six-part spine (clarify → rationale → goal → segmentation → pain → solution) for PM product-sense interviews — sound thoughtful out loud instead of over-scripted on paper.

20-30 minutes per practice answer
Advanced
Product Management

Product Strategy Session

End-to-end product strategy workflow orchestrating positioning, problem framing, discovery, prioritization, and roadmap across 6 phases over 2-4 weeks — with explicit decision points.

2-4 weeks
Advanced
Product Management

Proto-Persona

Create a lightweight, hypothesis-driven persona in hours from existing research, market signals, and team knowledge — a working customer profile before deeper validation.

60 minutes
Beginner
Product Management

Product Metrics Reviewer

Product metrics review with trend analysis, anomaly detection, and scorecard generation

10 minutes
Intermediate
Product Management

Product Spec Writer

Write feature specifications and PRDs from problem statements with user stories and acceptance criteria

10 minutes
Intermediate
Product Management

Skill Authoring Workflow

Turn raw PM content into a compliant, publish-ready Claude skill via 6 phases (preflight → generate → tighten → validate → integrate → package) using repo-native scripts.

60-90 minutes per skill
Intermediate

Browse all Product Management playbooks →