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.

Or install from your terminal:
npx ccplaybooks add positioning-workshop
# 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

Get new playbooks like this one

One email a week with new Claude Code workflows. Free, like everything here.

No spam. Unsubscribe anytime.

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 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

Recommendation Canvas (AI Product)

10-component canvas for evaluating AI product proposals — business + customer outcomes, hypothesis with tiny experiments, PESTEL risks, value justification, SMART metrics, and next steps.

90-120 minutes
Advanced
Product Management

Roadmap Planning

Build an outcome-driven roadmap across 5 phases (gather inputs → define epics → prioritize → sequence → communicate) with hypotheses, RICE scores, and stakeholder alignment.

1-2 weeks
Intermediate
Product Management

SaaS Economics & Efficiency Metrics

PM-focused reference for unit economics (CAC, LTV, payback, contribution margin) + capital efficiency (burn, runway, OpEx) + ratios (Rule of 40, magic number) — with cash-trap pitfalls.

30-60 minutes
Advanced
Product Management

SaaS Revenue & Growth Metrics

PM reference for revenue + retention metrics — MRR/ARR, ARPU/ARPA, ACV, churn (logo + revenue), NRR, expansion, quick ratio — with cohort analysis and 10 most common pitfalls.

30-60 minutes
Intermediate
Product Management

User Story Mapping Workshop

Facilitated 5-question Jeff Patton story mapping workshop — backbone activities, prioritized tasks, walking-skeleton MVP, and 3 release slices for end-to-end incremental delivery.

90-120 minutes
Intermediate

Browse all Product Management playbooks →