Skip to content

deanpeters/Product-Manager-Skills / plugins/pm-define/skills/positioning-statement

positioning-statement

Verified

Create a Geoffrey Moore-style positioning statement. Use when clarifying who you serve, what problem you solve, your category, and why you're different from alternatives.

FileKindSize
SKILL.mdskill md10.1 KB
examples/sample-industrial.mdmarkdown4.1 KB
examples/sample.mdmarkdown1.8 KB
template.mdmarkdown664 B

examples/sample-industrial.md

View on GitHub
# Positioning Statement Examples — Industrial

Northfield Automation's NFA-500 platform, positioned against the alternatives a plant actually
considers. Written during the replacement play that phases out the NFA-200.

The industrial twist: your hardest competitor is usually **doing nothing.** A line that runs is a
line nobody wants to touch, so positioning has to beat inertia before it beats a rival.

---

## Example 1: Good Positioning Statement (NFA-500)

**Value Proposition:**
- **For** plant operations teams running legacy production lines they cannot afford to replace
- **that need** modern control and diagnostics without a capital-scale machine replacement
- NFA-500
- **is a** modular retrofit control platform
- **that** brings a decades-old line up to current control, safety, and diagnostic standards while
  the machine itself keeps running

**Differentiation Statement:**
- **Unlike** a full machine replacement, or a fixed-I/O controller that must be swapped whole when
  requirements change
- NFA-500
- **provides** modular I/O you expand in place, fault detail down to the slot, and firmware you
  update without a site visit

---

**Why this works:**
- **It names the real alternative.** "A full machine replacement" is what the CFO is comparing
  against, and it's an order of magnitude more expensive. Position against the actual decision on
  the table, not the nearest competitor's spec sheet.
- **"They cannot afford to replace" is the whole market.** Retrofit exists because replacement is
  unaffordable. Saying so out loud qualifies the buyer in one line.
- **"While the machine itself keeps running"** answers the objection before it's raised. In a plant,
  the fear is downtime during the fix.
- **The differentiation is checkable.** Modular I/O, slot-level fault detail, remote firmware —
  three claims a skeptical controls engineer can verify in a demo.

---

## Example 2: Bad Positioning Statement (same product)

**Value Proposition:**
- **For** industrial customers
- **that need** better automation
- NFA-500
- **is a** next-generation industrial control solution
- **that** leverages advanced technology to optimize operations and drive efficiency

**Differentiation Statement:**
- **Unlike** legacy solutions
- NFA-500
- **provides** superior performance, reliability, and value

---

**What breaks:**
- **"Industrial customers"** is not a segment. A refinery, a bakery, and a machine shop share
  nothing that matters here.
- **"Better automation"** — better than what, at what? The statement never identifies a job.
- **"Legacy solutions"** dodges the actual competitor. If the honest answer is "the controller
  they already have, which still works," say that — it's a harder and more useful problem.
- **"Superior performance, reliability, and value"** are three claims nobody can test, which means
  a controls engineer will discount all three.
- Swap in any competitor's name and the statement still reads fine. That's the tell.

---

## Example 3: Good Positioning Statement (a different segment, same product)

The same platform sold to a different buyer needs a different statement — not a different product.

**Value Proposition:**
- **For** machine builders and system integrators specifying controls for customer installations
- **that need** one control platform they can standardize on across varied customer sites
- NFA-500
- **is a** modular retrofit control platform
- **that** covers small and large I/O counts from a single product family, so one set of
  engineering, spares, and training serves every job

**Differentiation Statement:**
- **Unlike** stocking three controller families to cover the range of jobs they bid
- NFA-500
- **provides** one platform, one toolchain, and one spares inventory across the range

---

**Why the second statement exists:**
The integrator doesn't care about the 2am fault light — they care about carrying less inventory and
training fewer people. Same product, same capability, different **job**.

Writing one statement to cover both would produce something that says "flexible and efficient" and
persuades neither. Positioning is per-segment; when a statement starts hedging to cover two
audiences, that's the signal to split it.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall