---
name: osp-value-map
description: Create an Open Strategy Partners style product value map with tagline, positioning, personas, value cases, feature hierarchy, validation checks, and technical marketing proof.
---

# OSP Value Map

You build an OSP-style product value map: tagline, positioning, personas, value cases, and a feature-to-value hierarchy backed by proof.

## Workflow

1. Read product context, features, audience, proof, and technical docs.
2. Create a value map: tagline, position statements, personas, value cases, feature hierarchy, and validation checks.
3. Connect each feature to a persona need and value case.
4. Route to `osp-content-optimizer` for content pages, metadata, technical writing, and SEO.

## Output

Create `osp-value-map-[product].md` with:

- Tagline
- Market, technical, UX, and business position statements
- Personas and needs
- Value cases
- Feature hierarchy
- Proof needed
- Validation checklist

## Quality bar

No feature should exist without a value case. No value case should exist without a persona need.

## Attribution

Adapts the Open Strategy Partners Product Value Map methodology, licensed
CC BY-SA 4.0. ShareAlike requires this attribution to travel with the work —
keep it here and in THIRD_PARTY_NOTICES.md when redistributing.

## Hand off to

PMM OS is a chain, not a menu — don't dead-end at advice. Pass the work on:

- [`osp-technical-marketing`](../osp-technical-marketing/SKILL.md) — write the technical content
- [`osp-content-optimizer`](../osp-content-optimizer/SKILL.md) — optimize it
- [`pmm-artifact-factory`](../pmm-artifact-factory/SKILL.md) — produce the assets
- [`pmm-coach`](../pmm-coach/SKILL.md) — review before anything customer- or exec-facing.

## Depth

Apply the [PMM OS output-depth standard](../product-marketing-os/references/output-depth-standard.md): every section must be **specific** (named alternatives, segments, numbers — not "competitors"/"users"/"better"), **complete** (the real dimensions, not just the first), **reasoned** (the why and the trade-off), and **evidenced** (a proof or a named proof-gap). Depth is not length — do not pad, but never reduce a section to one generic line. Self-check each section before returning.

## Frameworks & deep references

Read and apply the deep frameworks below before you produce output — they carry the methodology, templates, and worked examples behind this skill (from the PMM OS framework library). Read the ones relevant to the request and *apply* them; don't paste them verbatim.

- [`positioning/04-differentiated-value-proof-points.md`](../product-marketing-os/references/library/positioning/references/core/04-differentiated-value-proof-points.md) — attribute → value → proof chain
- [`messaging/02-pain-claim-gain-messaging.md`](../product-marketing-os/references/library/messaging/references/core/02-pain-claim-gain-messaging.md) — pain-claim-gain per value