Positioning Messaging Designer

Positioning & Messaging Designer

You are helping design positioning and messaging for a client. This is the bridge between knowing WHO to sell to (ICP) and knowing WHAT to say (copy). Most companies skip this step — they go from ICP straight to copy and wonder why everything needs rewriting.

The core insight: you don't invent messaging. You extract it from the contrast between the customer's current reality and what becomes possible. The Use Case Messaging Canvas and the Opposites method make this systematic.

---

When This Skill Activates

Situation 1: Copy Skip. Client has an ICP but went straight to writing copy. Messaging is inconsistent across channels — LinkedIn says one thing, the website says another, sales pitches a third. The symptom is constant rewriting.

Situation 2: Positioning is vague. Client can't articulate what makes them different in one sentence. "We're an AI-powered platform that helps companies..." — generic, category-stuffed, says nothing. No clear alternative, no contrast.

Situation 3: Post-ICP work. ICP building was just completed with icp-builder and the next step is translating those insights into a positioning framework and messaging architecture.

Before starting: Confirm the client has SPICED data. If they don't have customer interviews or at least deal analysis with pain language, the positioning will be fiction. Send them back to ICP work first.

---

The Chain

This is the sequence. Every step feeds the next:

ICP + SPICED → Positioning → Messaging Framework → Copy (every channel)

Skip a step and everything downstream breaks. This skill covers the middle two.

---

Part 1: Positioning — The 12 Elements

Positioning answers: "Why should I choose you over the alternative?" It's not a tagline. It's the structure that makes the solution visible in a crowded market.

Primary Elements (answer "Why choose you?")

Work through these six with the client. Every one should be grounded in SPICED data, not aspiration:

1. Category — What market do you play in?
2. Alternative — What do they compare you to? (Competitors, doing nothing, building in-house)
3. Differentiation — What makes you meaningfully different?
4. Capabilities — What can they DO with you that they can't elsewhere?
5. Benefits — What results do they get?
6. Features — What powers those capabilities?

Secondary Elements (add specificity)

1. Personas — Who specifically benefits most?
2. Use Case — What job are they hiring you for?
3. Overarching Problem — What big-picture struggle ties it together?
4. Sub-Problems (1, 2, 3) — Specific blockers (these come from SPICED Pain)

For the full element definitions with examples, read references/positioning-messaging-reference.md Section 1.

The Positioning Line

Once the 12 elements are mapped, write ONE repeatable positioning line. Six formulas to choose from:

| Formula | Structure | Best when... | |---------|-----------|-------------| | Problem/Outcome | "We help [who] reduce [pain] so they achieve [result]" | Main value is solving a costly pain | | Job-to-be-Done | "When you need to [job], use [us] instead of [old way]" | Job is clear, you're the obvious alternative | | Category + Competitor | "Unlike [alternative], we're [difference]" | Competing for budget against a specific rival | | Segment/Niche | "[Category] built for [niche], not generic [everyone]" | You own a specific niche | | Primary Value Vector | "The most [value] way for [who] to [result]" | Differentiator is speed, cost, or simplicity | | Strategic Archetype | "The [archetype] in [category] for [who] who need [job]" | Positioning as a platform, not a tool |

Pick ONE. Make it repeatable. Back it with proof. Keep it consistent across all channels.

For full formula details with examples, read references/positioning-messaging-reference.md Section 2.

---

Part 2: The Use Case Messaging Canvas

The canvas is the core deliverable. Two sides: Old Way (their current reality) and New Way (what becomes possible), connected by a Use Case and Persona.

How to Build It

Step 1: Fill the Left Side First (Their Reality)

This is THEIR world, not your narrative. Use their words from SPICED interviews:

• Overarching Problem — Big picture struggle, in their words
• 3 Specific Problems — Pain 1, 2, 3 from SPICED (exact customer language)
• Limitation of Current Way — What's broken about how they do it now (anti-feature)
• Current Way — What they actually do today (anti-capability)

If it doesn't come from SPICED data, it's not positioning — it's fiction.

Step 2: Fill the Center (Job & Persona)

• Use Case — The specific job or outcome being done
• Persona — Who specifically benefits (name, title, context)

Step 3: Flip Each Row to the Right (The Opposites Method)

Every New Way element is the OPPOSITE of an Old Way element:

• Problem → Benefit (directly solves the pain)
• Anti-feature → Product Feature (what was broken → what's now possible)
• Anti-capability → Capability (what they did manually → what the system does)
• Overarching Problem → Desired Outcome (the aspirational end state)

The Opposites write the messaging. You don't invent it — you extract it from the contrast.

For the full canvas template and detailed instructions, read references/positioning-messaging-reference.md Sections 3-4.

Pain language enrichment: Reference your own collection of raw customer pain language. The left side of the canvas should sound like real customer quotes — specific, emotional, concrete.

---

Part 3: From Framework to Copy

The messaging framework is not a document you write once and file. It's the operating system for everything the client says. Three tools working together:

| Tool | Purpose | Feeds into | |------|---------|-----------| | SPICED | WHAT to say (substance) | Use Case Canvas | | Use Case Canvas | WHERE to put it (structure) | Copy outlines | | Opposites | HOW to say it (contrast) | Every headline, email, post |

The canvas produces messaging that flows directly into LinkedIn posts (Old Way vs New Way is high-engagement), website copy, sales decks, email sequences, and proposal templates.

---

Delivery Formats

Within a 90-Day Programme (full build): Run the weekly GTM sequence — Tuesday ICP, Wednesday Positioning, Thursday Messaging. Iterate over 2-3 weeks. Canvas becomes the living source of truth.

Standalone Positioning Workshop (half-day): Pre-gather SPICED data. Work through 12 elements and one positioning line in the morning. Build the canvas in the afternoon. Client leaves with a complete messaging framework.

As follow-on to ICP work: Natural handoff from icp-builder. SPICED data from the ICP process feeds directly into the left side of the canvas.

For the weekly GTM sequence (Tuesday/Wednesday/Thursday workflow), read references/positioning-messaging-reference.md Section 6.

---

Norton Framework Additions (Source: Kyle Norton Revenue Leadership Podcast, E62, Feb 2026)

Radical Clarity in Noisy Markets (Donnelly, E62)

The 30-Second Clarity Test: "If you can't understand who we are in 30 seconds, we have hashtag failed." Use this as a validation gate before finalising any positioning work.

How to apply:

1. Read the positioning line to someone unfamiliar with the company
2. After 30 seconds, ask them to repeat back what the company does and for whom
3. If they can't → the positioning needs more iteration
4. If they can → test with 5 more people to confirm

Time-to-aha as diagnostic metric:

• Crescendo's previous state: 20 minutes for customers to get the aha moment
• Target: much faster (ideally within 30 seconds of reading/hearing the positioning)
• Track this during sales calls — how long before the prospect "gets it"?

Iterative Refinement Process (Donnelly, E62)

Positioning is not a one-shot exercise. Crescendo went through five pitch decks in six months.

Validation velocity:

• Test messaging with BDRs doing 400 calls/day = real-world message validation at speed
• Run past existing customers (Crescendo learned their pricing was too complex from customer feedback)
• Outside consultants (mixed results — internal iteration often more effective)
• Real-time positioning workshops with the sales team

Implication for Use Case Canvas: After completing the Opposites method and Canvas, don't treat it as finished. Build a 30-day validation sprint:

1. Week 1: BDR testing (volume calls using new messaging)
2. Week 2: AE testing (discovery calls using new framing)
3. Week 3: Customer validation (existing customers react to new positioning)
4. Week 4: Iterate and lock — or start another cycle

Three-Priority Clarity (Donnelly, E62)

An organisational messaging clarity test: can everyone in the org repeat the three things they're doing this quarter?

If they can't: The messaging is too complex, there are too many priorities, or communication is broken.

Use in positioning work: After finalising positioning, test whether the sales team can articulate the top 3 value propositions without notes. If not, simplify further.

Gartner context: B2B buyers spend two-thirds of any buying journey "gathering, processing, and de-conflicting information." Your positioning either reduces that work or adds to it.

---

Common Mistakes to Flag

When working with clients, watch for these patterns:

1. Writing positioning before SPICED — Guessing instead of listening. Send them back to customer interviews.
2. Filling the right side before the left — Their narrative overwrites customer reality. Always start with the Old Way.
3. Using "nice" words instead of customer words — Messaging won't resonate. Use the exact language from interviews.
4. Forgetting the Opposites — New Way doesn't clearly contrast with Old Way. Every right-side element should be a direct flip.
5. Creating a document instead of a system — The canvas should be a living reference that everyone uses, not a slide deck that collects dust.

---

Reference Files

| File | When to read | What's inside | |------|-------------|---------------| | references/positioning-messaging-reference.md | Always — the full methodology | 12 positioning elements, 6 positioning formulas, Use Case Canvas structure, Opposites method, weekly GTM sequence, blank canvas template |

Related Skills

• icp-builder — The step BEFORE this skill: builds, validates, and expands the ICP that feeds positioning
• sales-methodology — Discovery calls produce SPICED data that feeds the canvas
• marketing-operations — Uses messaging framework outputs for campaign execution

Cross-References

• icp-builder — Input: the ICP and SPICED data that feeds positioning
• gtm-planning — Positioning line feeds into GTM collateral and territory messaging

> Built by Neon Triforce

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: NEON-Rutger
• Source: NEON-Rutger/B2B-revops-skills
• License: MIT
• Homepage: https://www.neontriforce.com

Install and usage instructions live in the source repository linked above.