All skills
deanpeters avatar

/positioning-statement

@6a4fbf2

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.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/positioning-statement

This session only. Nothing lands on disk.

examplessample-industrial.md

≈1.1k tokens on demand. Your agent reads this file only when SKILL.md points to it.

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.

Source: SKILL.md on GitHub

No alerts17d5 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    This skill is a template-based text generator for creating Geoffrey Moore-style positioning statements. It contains no executable code, network operations, or sensitive data access, and poses no security risk.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer7mo

    3 files scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 6a4fbf2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 3 months ago
argument-hint
[product] [target customer]
type
component
theme
strategy-positioning
Other metadata
intent
Create a Geoffrey Moore-style positioning statement that clearly articulates who your product serves, what need it addresses, how it's categorized, what benefit it delivers, and how it differs from alternatives. Use this when you need to align stakeholders on product strategy, guide messaging, or test if your value proposition is crisp and defensible.
best_for
[
  "Defining your product's market position clearly for the first time",
  "Differentiating from specific competitors in your messaging",
  "Aligning your team on who you serve, what problem you solve, and why you're different"
]
scenarios
[
  "I need to write a positioning statement for a new B2B SaaS product targeting mid-market HR teams",
  "Our positioning feels generic and I need to sharpen it against two specific competitors"
]
estimated_time
10-15 min

README badge

README badge for deanpeters/product-manager-skills/positioning-statement