Position Lock (PRISM Framework)
Engineer a positioning architecture that is structurally defensible and cascades consistently from brand level down to feature level.
When to Use
- New product positioning
- Repositioning after market shift
- Messaging overhaul
- Pre-launch messaging lock
- Category creation strategy
What You'll Need
Critical inputs (ask if not provided):
- Product/company to position
- Target audience (primary persona)
- Top 2-3 competitors
Nice-to-have:
- Battle Scanner output (competitive positioning)
- Whitespace Finder output (opportunities to position around)
- Journey Architect output (persona needs at each stage)
Process
Step 1: Build the 4-Layer Positioning Stack
Layer 1: Category Design
Decide your category strategy:
| Strategy |
When to Use |
Risk Level |
| Create new category |
You are truly different, market is ready |
High effort, highest leverage |
| Redefine existing category |
Existing category is stale, you have a fresh angle |
Medium effort |
| Compete within category |
Category is well-understood, you have clear advantages |
Lowest effort |
Layer 2: Strategic Narrative
The "big idea" connecting your product to a larger market shift:
- NOT a feature story -- a worldview story
- Format: "The world is changing from [old way] to [new way]. [Product] is built for the new world."
- Must feel inevitable and bigger than your product
Layer 3: Value Proposition Matrix
| Value Type |
Question It Answers |
Example |
| Functional |
What does it DO? |
"Automates X, reducing time by 80%" |
| Emotional |
How does it make them FEEL? |
"Confidence that nothing falls through cracks" |
| Social |
How does it make them LOOK? |
"Seen as innovative by leadership" |
| Economic |
What does it SAVE/EARN? |
"Saves $50K/year per team" |
Layer 4: Proof Architecture
Map evidence to every value claim:
- Metrics and data points
- Customer case studies
- Third-party validation (analyst quotes, awards)
- Product demonstrations
Step 2: PRISM Scoring
Score your positioning (1-10):
| Dimension |
Question |
Scoring Guide |
| Proposition clarity |
Can someone explain it in one sentence? |
1=confusing, 5=clear, 10=instantly obvious |
| Resonance |
Does it connect to a felt pain? |
1=abstract, 5=relevant, 10=visceral "that's me" |
| Isolation |
Could a competitor credibly claim the same? |
1=generic, 5=somewhat unique, 10=only we can say this |
| Substance |
Is every claim backed by evidence? |
1=vapor, 5=some proof, 10=bulletproof evidence |
| Memorability |
Is the language distinctive and sticky? |
1=forgettable, 5=decent, 10=quotable |
PRISM Score = average of all 5. Launch-readiness threshold: 7.0+
Step 3: Message Cascade Architecture
Build the L0-L5 hierarchy where every level ladders up:
| Level |
What It Is |
Example |
| L0 |
Category declaration |
"The AI-native project management platform" |
| L1 |
Brand tagline |
"Ship faster, stress less" |
| L2 |
Strategic narrative |
"Teams are drowning in tools. We built one that thinks." |
| L3 |
Persona-specific value props (3-5) |
"For PMs: Cut planning time by 60%" |
| L4 |
Use-case messaging (per scenario) |
"For sprint planning: AI suggests story points" |
| L5 |
Feature-level proof points |
"Auto-prioritization uses 12 signals to rank your backlog" |
Rule: Every lower level must ladder up. If L4 messaging contradicts L2, something is broken.
Step 4: Message Testing Plan
For each L1-L3 message variant:
- Hypothesis: "We believe [message A] will resonate more than [message B] because [reason]"
- Test method: A/B landing page, ad copy test, sales conversation test
- Success metric: Click-through rate, response rate, deal progression
- Sample size and timeline
Output
Save to outputs/positioning-[product]-[YYYY-MM-DD].md
Deliverables:
- Positioning Architecture: Full 4-layer stack with PRISM scores
- Message Cascade: Complete L0-L5 hierarchy
- Brand Voice Guidelines: Tone, vocabulary, and language rules
- Message Testing Plan: Prioritized variants with hypotheses
Chain Connections
- Next skill: Run
demand-engine to design demand gen campaigns using this messaging
- Also feeds:
enablement-forge (positioning is the backbone of all sales materials), launch-command (positioning must be locked before launch), product-announcement (messaging powers the announcement)
- Enhanced by: Run after
battle-scanner (competitive gaps inform positioning) and whitespace-finder (opportunities define what to position around)
1---2name: position-lock3description: Brand positioning and messaging architecture engine that creates a defensible market position with cascading message hierarchy from tagline to feature copy. Use when: positioning, messaging, brand positioning, value proposition, messaging framework, how do we position, what is our message.4---56# Position Lock (PRISM Framework)78Engineer a positioning architecture that is structurally defensible and cascades consistently from brand level down to feature level.910## When to Use11- New product positioning12- Repositioning after market shift13- Messaging overhaul14- Pre-launch messaging lock15- Category creation strategy1617## What You'll Need18**Critical inputs (ask if not provided):**19- Product/company to position20- Target audience (primary persona)21- Top 2-3 competitors2223**Nice-to-have:**24- Battle Scanner output (competitive positioning)25- Whitespace Finder output (opportunities to position around)26- Journey Architect output (persona needs at each stage)2728## Process2930### Step 1: Build the 4-Layer Positioning Stack3132**Layer 1: Category Design**33Decide your category strategy:34| Strategy | When to Use | Risk Level |35|----------|------------|------------|36| Create new category | You are truly different, market is ready | High effort, highest leverage |37| Redefine existing category | Existing category is stale, you have a fresh angle | Medium effort |38| Compete within category | Category is well-understood, you have clear advantages | Lowest effort |3940**Layer 2: Strategic Narrative**41The "big idea" connecting your product to a larger market shift:42- NOT a feature story -- a worldview story43- Format: "The world is changing from [old way] to [new way]. [Product] is built for the new world."44- Must feel inevitable and bigger than your product4546**Layer 3: Value Proposition Matrix**47| Value Type | Question It Answers | Example |48|-----------|-------------------|---------|49| Functional | What does it DO? | "Automates X, reducing time by 80%" |50| Emotional | How does it make them FEEL? | "Confidence that nothing falls through cracks" |51| Social | How does it make them LOOK? | "Seen as innovative by leadership" |52| Economic | What does it SAVE/EARN? | "Saves $50K/year per team" |5354**Layer 4: Proof Architecture**55Map evidence to every value claim:56- Metrics and data points57- Customer case studies58- Third-party validation (analyst quotes, awards)59- Product demonstrations6061### Step 2: PRISM Scoring62Score your positioning (1-10):6364| Dimension | Question | Scoring Guide |65|-----------|---------|---------------|66| **P**roposition clarity | Can someone explain it in one sentence? | 1=confusing, 5=clear, 10=instantly obvious |67| **R**esonance | Does it connect to a felt pain? | 1=abstract, 5=relevant, 10=visceral "that's me" |68| **I**solation | Could a competitor credibly claim the same? | 1=generic, 5=somewhat unique, 10=only we can say this |69| **S**ubstance | Is every claim backed by evidence? | 1=vapor, 5=some proof, 10=bulletproof evidence |70| **M**emorability | Is the language distinctive and sticky? | 1=forgettable, 5=decent, 10=quotable |7172**PRISM Score** = average of all 5. Launch-readiness threshold: 7.0+7374### Step 3: Message Cascade Architecture75Build the L0-L5 hierarchy where every level ladders up:7677| Level | What It Is | Example |78|-------|-----------|---------|79| L0 | Category declaration | "The AI-native project management platform" |80| L1 | Brand tagline | "Ship faster, stress less" |81| L2 | Strategic narrative | "Teams are drowning in tools. We built one that thinks." |82| L3 | Persona-specific value props (3-5) | "For PMs: Cut planning time by 60%" |83| L4 | Use-case messaging (per scenario) | "For sprint planning: AI suggests story points" |84| L5 | Feature-level proof points | "Auto-prioritization uses 12 signals to rank your backlog" |8586**Rule**: Every lower level must ladder up. If L4 messaging contradicts L2, something is broken.8788### Step 4: Message Testing Plan89For each L1-L3 message variant:90- Hypothesis: "We believe [message A] will resonate more than [message B] because [reason]"91- Test method: A/B landing page, ad copy test, sales conversation test92- Success metric: Click-through rate, response rate, deal progression93- Sample size and timeline9495## Output96Save to `outputs/positioning-[product]-[YYYY-MM-DD].md`9798### Deliverables:991. **Positioning Architecture**: Full 4-layer stack with PRISM scores1002. **Message Cascade**: Complete L0-L5 hierarchy1013. **Brand Voice Guidelines**: Tone, vocabulary, and language rules1024. **Message Testing Plan**: Prioritized variants with hypotheses103104## Chain Connections105- **Next skill**: Run `demand-engine` to design demand gen campaigns using this messaging106- **Also feeds**: `enablement-forge` (positioning is the backbone of all sales materials), `launch-command` (positioning must be locked before launch), `product-announcement` (messaging powers the announcement)107- **Enhanced by**: Run after `battle-scanner` (competitive gaps inform positioning) and `whitespace-finder` (opportunities define what to position around)
varunk130