# Positioning Workshop

Run a positioning workshop that surfaces target customer, unmet need, category...

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill positioning-workshop -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill positioning-workshop -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill positioning-workshop -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill positioning-workshop -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Run a positioning workshop that surfaces target customer, unmet need, category, benefits, and differentiation. Use when your product messaging feels fuzzy, generic, or misaligned.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

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

## Input

**Works best with:** The product (or feature) whose positioning feels fuzzy.
**Also useful:** Current messaging, who you think the customer is, competitors, and where positioning breaks down today (sales calls, website, launch).

Anything supplied with the invocation itself, text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line, counts as answers already given. Use it and skip whatever it covers; don't re-ask.

**Arriving empty-handed? That works too.** The workshop opens by asking about your target customer and proceeds one question at a time.

**Example invocation:** `Run a positioning workshop for our API monitoring tool, we keep getting compared to Datadog and losing.`

## Key Concepts

### The Positioning Workshop Flow
An interactive discovery process that:
1. Gathers product context (marketing materials, competitor intel)
2. Identifies target customer segment through questioning
3. Uncovers underserved needs via Jobs-to-be-Done lens
4. Defines product category and benefits
5. Establishes competitive differentiation
6. Outputs a complete positioning statement (uses `positioning-statement.md`)

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/positioning-workshop/SKILL.md