# Applications: Applying SUCCESs Across Contexts

The SUCCESs framework is not theoretical — it is a practical toolkit that can be applied to any communication context. This reference provides step-by-step guidance for applying all six principles to landing pages, product demos, onboarding flows, presentations, email campaigns, internal communications, and documentation. Each section includes templates, checklists, and before/after examples.

## Applying SUCCESs to Landing Pages

A landing page has one job: convert a visitor into a lead or customer. Each SUCCESs principle strengthens a different part of that conversion process.

### Element-by-Element Breakdown

| Principle | Landing Page Element | Implementation |
|-----------|---------------------|----------------|
| **Simple** | Headline + subheadline | One value proposition. No compound sentences. No "and." |
| **Unexpected** | Above-the-fold hook | A counterintuitive claim or surprising statistic |
| **Concrete** | Benefits section | Specific outcomes with numbers, not abstract promises |
| **Credible** | Social proof section | Named customers, specific metrics, Sinatra Test logos |
| **Emotional** | Pain/aspiration section | One customer's story or a vivid problem description |
| **Stories** | Case study or testimonial | A complete character-problem-solution-outcome narrative |

### Landing Page Template

```
[HEADLINE: Simple — one core value proposition in under 10 words]
[SUBHEADLINE: Unexpected — counterintuitive claim or surprising angle]

[HERO SECTION]
- Concrete outcome #1 (specific number)
- Concrete outcome #2 (specific number)
- Concrete outcome #3 (specific number)
[CTA BUTTON]

[SOCIAL PROOF: Credible]
- Logo bar with named companies
- "Join [specific number] teams including [impressive name]"

[PAIN SECTION: Emotional]
- "You know the feeling when [specific, relatable pain]..."
- Individual focus: one person's experience

[STORY SECTION: Stories]
- Customer transformation narrative (character → problem → solution → outcome)
- Direct quote with name, title, and company

[CREDIBILITY SECTION: Credible]
- Specific metric: "[X] customers processed [Y] in the last month"
- Testable credential: "Try free for 14 days, no credit card"

[FINAL CTA]
```

### Before/After: Landing Page Headline

**Before:**
> "The All-in-One Platform for Modern Teams"
> "Streamline your workflow with AI-powered automation and seamless integrations."

**After:**
> "Ship 3x Faster Without Hiring"
> "Your competitor just launched in 2 weeks. Yours has been stuck for 2 months. Here is why."

## Applying SUCCESs to Product Demos

Product demos fail when they become feature tours. A sticky demo tells a story, creates curiosity, and delivers emotional impact.

### The Sticky Demo Framework

| Phase | Principle | What to Do |
|-------|-----------|-----------|
| **Opening (30 seconds)** | Unexpected + Emotional | Start with the customer's pain, not your product. State something surprising. |
| **Setup (1-2 minutes)** | Simple + Concrete | "Today I will show you ONE thing: how [specific outcome] happens in [specific time]" |
| **Demonstration (3-5 minutes)** | Concrete + Credible | Use real data, real names, real workflows. Time the action. |
| **Aha Moment (30 seconds)** | Unexpected | The moment where the old way vs. new way becomes viscerally clear |
| **Proof (1 minute)** | Credible + Stories | "Here is what [named customer] said after seeing this for the first time" |
| **Close (30 seconds)** | Emotional + Simple | Return to the pain. Show how it is now resolved. One CTA. |

### Demo Script Template

```
"Before I show you anything, let me ask you a question.
[UNEXPECTED: A question that reveals a pain they did not realize they had]

Here is what [REAL CUSTOMER NAME] was dealing with:
[EMOTIONAL: 2-sentence description of their specific problem]

Watch what happens when I [CONCRETE: specific action].
[DEMONSTRATE: real data, timed, specific]

See that? [SIMPLE: one sentence explaining what just happened]
That used to take [CREDIBLE: specific old time]. Now it takes [specific new time].

[CUSTOMER NAME] told us: '[STORY: direct quote about the impact].'

Want to try it with your own data? [CTA]"
```

### Before/After: Demo Opening

**Before:**
> "Hi, thanks for joining. Today I am going to give you a tour of our platform. Let me start with the dashboard..."

**After:**
> "Before I show you anything, I want you to think about the last time you needed a report for a meeting and could not find the right numbers in time. That happened to the VP of Sales at Notion last quarter. It cost them a $2M deal. Let me show you why that will never happen to you."

## Applying SUCCESs to Onboarding Flows

Onboarding is where most products lose users. A sticky onboarding flow guides users to their first "aha moment" as fast as possible while building belief and motivation.

### Screen-by-Screen Framework

| Screen | Principle | Content |
|--------|-----------|---------|
| **Welcome** | Unexpected + Emotional | Not "Welcome to [Product]." Instead: "In the next 3 minutes, you will see [specific surprising outcome]." |
| **Quick Win (Step 1)** | Simple + Concrete | One action. Show the result immediately. Use real data if possible. |
| **Progress** | Credible | "You are already ahead of 70% of new users who skip this step." |
| **Core Value (Step 2-3)** | Concrete + Unexpected | Deliver the "aha moment" — the thing that makes them say "Oh, THAT is what this does." |
| **Social Proof** | Credible + Stories | "[Name] at [Company] got to this point and never looked back. Here is what they built." |
| **Celebration** | Emotional | Celebrate the first success. Make them feel accomplished. |
| **Next Step** | Simple | One clear next action. Not a menu of 10 options. |

### Before/After: Onboarding Welcome Screen

**Before:**
> "Welcome to DataSync! Let us get you set up. Here are the 7 steps to get started."

**After:**
> "In 90 seconds, you will see all your customer data in one place for the first time. Ready? Let us start with one click: connect your CRM."

## Applying SUCCESs to Presentations and Pitches

Presentations fail when they are information dumps. A sticky presentation is structured as a journey with one core message, supported by surprise, proof, emotion, and story.

### The Sticky Presentation Structure

| Section | Duration | Principle | Content |
|---------|----------|-----------|---------|
| **Hook** | 30 seconds | Unexpected | Open with a surprising fact, a bold claim, or a mystery |
| **Problem** | 2-3 minutes | Emotional + Concrete | Make the audience feel the problem. Use one person's story. |
| **Core Insight** | 1 minute | Simple | State your one key message. This is your Commander's Intent. |
| **Evidence** | 5-7 minutes | Credible + Concrete | Prove your claim with specific data, demonstrations, and examples |
| **Story** | 2-3 minutes | Stories | A complete narrative that embodies your core message |
| **Implications** | 2 minutes | Unexpected + Emotional | "Here is what this means for you, specifically" |
| **CTA** | 30 seconds | Simple | One clear ask. Not three options. One. |

### Presentation Checklist

- [ ] The first slide has no logo, no agenda, no "About Us" — just the hook
- [ ] There is ONE core message (say it in 10 words or fewer)
- [ ] At least one moment will make the audience say "I did not know that"
- [ ] Every statistic is human-scale and compared to something familiar
- [ ] At least one real person's story is told with name, context, and outcome
- [ ] The audience knows exactly what to do next when it ends
- [ ] There are fewer than 20 slides for a 30-minute presentation
- [ ] No slide has more than 15 words on it

### Before/After: Presentation Opening Slide

**Before:**
> Slide 1: Company logo, "Q3 Strategic Review," date, presenter name, agenda

**After:**
> Slide 1: "47% of our customers almost left last quarter. Here is why they stayed."

## Applying SUCCESs to Email Campaigns

Email is the most competitive attention environment. Your message competes with 100+ other emails in a single inbox. SUCCESs principles help you win the open and the click.

### Email Framework

| Email Element | Principle | Implementation |
|--------------|-----------|----------------|
| **Subject line** | Unexpected + Simple | Pattern-breaking curiosity gap in under 8 words |
| **First sentence** | Concrete + Emotional | A specific, vivid pain or aspiration they can picture |
| **Body** | Stories + Credible | One story or proof point — not a catalog of features |
| **CTA** | Simple | One action. Not "Learn more, sign up, or reply." Just one. |

### Email Templates

**The Curiosity Gap Email:**
```
Subject: The mistake your team is making every Monday

[Name], last Monday your team probably spent 2 hours in a meeting
that could have been a 5-minute async update.

I know this because 84% of teams we surveyed do the same thing.

[Customer name] at [Company] eliminated Monday meetings entirely.
Their team shipped 30% more that quarter.

Here is the 2-minute change they made: [LINK]
```

**The Story Email:**
```
Subject: How [Name] saved 12 hours a week

Quick story:

[Name] runs ops at [Company]. Every Friday, she spent 3 hours
compiling a report nobody read.

One day she asked: "What if the report wrote itself?"

She found [Product]. Setup took 15 minutes. The next Friday,
the report was in her inbox at 8am. She went to a yoga class instead.

Want your Fridays back? [CTA]
```

**The Surprising Stat Email:**
```
Subject: You are losing $4,200/month (here is the math)

[Name], your team has 12 people. Each one spends ~30 minutes/day
on [specific manual task].

That is 130 hours/month. At your team's average hourly cost,
that is $4,200 going to a task a machine can do.

Here is the math: [LINK]
And here is the fix: [CTA]
```

## Applying SUCCESs to Internal Communications

Internal communications are where the Curse of Knowledge does the most damage. Everyone assumes shared context. Nobody questions the jargon. Ideas die in the noise of Slack and email.

### Making Internal Messages Stick

| Principle | Internal Application | Example |
|-----------|---------------------|---------|
| **Simple** | One message per communication. No "3 things" emails. | "This quarter's priority: reduce churn. Everything else supports that." |
| **Unexpected** | Lead with the surprising data point | "We lost more customers last month than in the previous 6 months combined." |
| **Concrete** | Use real examples from the team's experience | "Remember the Acme Corp escalation last Tuesday? That is the exact problem we are solving." |
| **Credible** | Share the data behind the decision | "Here are the 47 customer interviews that led to this conclusion." |
| **Emotional** | Make the impact personal | "If we do not fix this, the support team will keep working weekends." |
| **Stories** | Tell the story of a real customer or team member | "Let me tell you what happened when our newest engineer tried to deploy for the first time." |

### Before/After: Company All-Hands Announcement

**Before:**
> "We are excited to announce a strategic realignment of our go-to-market motion. Effective next quarter, we will be transitioning to a product-led growth model with enhanced self-serve capabilities and optimized conversion funnels."

**After:**
> "Starting next quarter, customers can buy our product without ever talking to a salesperson. Why? Because 60% of our signups already try to buy online and give up. We are losing $200K/month to a 'Contact Sales' button. Here is what changes."

## Applying SUCCESs to Documentation and Help Content

Documentation is the most undervalued communication channel. Great documentation reduces support tickets, improves onboarding, and builds trust. But most documentation is cursed by knowledge.

### The Sticky Documentation Framework

| Principle | Documentation Application |
|-----------|--------------------------|
| **Simple** | One concept per page. Clear hierarchy. Lead with the answer, not the context. |
| **Unexpected** | Call out common mistakes upfront. "Most users try X first. Here is why Y works better." |
| **Concrete** | Every instruction includes a screenshot or code example. Never say "configure as needed." |
| **Credible** | Include "Why" sections explaining the reasoning. Link to source documentation. |
| **Emotional** | Acknowledge the user's frustration. "We know this is confusing. Here is the simplest path." |
| **Stories** | Include use case examples. "Here is how a marketing team uses this feature to..." |

### Before/After: Help Article

**Before:**
> **Setting Up Integrations**
> Navigate to the Settings panel and select the Integrations tab. Configure your desired integrations by providing the necessary credentials and selecting the appropriate sync options.

**After:**
> **Connect Slack in 60 Seconds**
> Want your team to get notified in Slack when a deal closes? Here is how:
> 1. Click Settings (gear icon, top right)
> 2. Click Integrations
> 3. Find Slack and click Connect
> 4. Choose your channel (most teams pick #sales-wins)
> 5. Done. Your next closed deal will trigger a celebration message.
>
> Common mistake: Choosing #general instead of a specific channel. Your team will tune it out within a week.

## Master Checklist: SUCCESs Audit for Any Context

Before publishing any communication, verify each principle:

- [ ] **Simple:** ONE core message, understandable by a 12-year-old, most important info first
- [ ] **Unexpected:** Opens with a pattern-break, creates a curiosity gap, surprise serves the core message
- [ ] **Concrete:** Abstractions replaced with examples, numbers are human-scale, audience can picture it
- [ ] **Credible:** Proof point included, testimonials use real names, claims are verifiable or testable
- [ ] **Emotional:** Connects to a feeling, features an individual's experience, answers "What is in it for me?"
- [ ] **Stories:** Includes a narrative with character + problem + resolution, illustrates the core message

## Quick Reference: One-Line SUCCESs Reminders

| Principle | One-Line Reminder |
|-----------|-------------------|
| **Simple** | "If they remember one thing, what must it be?" |
| **Unexpected** | "What will make them look up from their phone?" |
| **Concrete** | "Can they picture it happening?" |
| **Credible** | "Why should they believe me?" |
| **Emotional** | "What will they feel?" |
| **Stories** | "Whose story illustrates this?" |

# Case Studies: Sticky Ideas Analyzed Through the SUCCESs Framework

The best way to understand the SUCCESs framework is to see it in action. This reference analyzes real-world sticky ideas — messages, campaigns, stories, and legends that have endured for years or decades. Each case study breaks down which principles made the idea stick and what lessons you can extract for your own communication.

## Case Study 1: JFK's Moonshot Speech (1961)

### The Idea

"I believe that this nation should commit itself to achieving the goal, before this decade is out, of landing a man on the moon and returning him safely to the earth."

### Why It Stuck

This single sentence mobilized an entire nation, directed billions of dollars in spending, and aligned hundreds of thousands of engineers, scientists, and administrators toward one goal. Fifty years later, "moonshot" is a synonym for ambitious goals.

### SUCCESs Analysis

| Principle | Present? | How It Was Used |
|-----------|----------|----------------|
| **Simple** | Yes | One goal. Not "advance our space capabilities" — land a man on the moon. Commander's Intent at its purest. |
| **Unexpected** | Yes | In 1961, the U.S. was behind the Soviet Union in space. Committing to the moon was audaciously counterintuitive. |
| **Concrete** | Yes | "Landing a man on the moon and returning him safely." Not "space exploration leadership." You can picture a person standing on the moon. |
| **Credible** | Yes | The President of the United States, speaking before Congress, staking his presidency on the claim. |
| **Emotional** | Yes | National pride, Cold War urgency, the spirit of exploration. "We choose to go to the moon not because it is easy, but because it is hard." |
| **Stories** | Partial | The speech itself was not a story, but it launched a decade of stories — every mission, every astronaut, every triumph and failure became part of the narrative. |

### Lessons

- A concrete deadline ("before this decade is out") makes an abstract goal tangible
- The best Commander's Intent generates thousands of decisions without further guidance
- Audacious goals can be simple if they are concrete enough to picture

## Case Study 2: Subway's Jared Diet Story

### The Idea

Jared Fogle, a college student weighing 425 pounds, lost 245 pounds by eating Subway sandwiches twice a day for a year.

### Why It Stuck

Subway's advertising agency initially rejected the story. Too simple, too weird, too risky. But a local franchise owner championed it, and the campaign ran for over a decade, contributing to Subway becoming the largest restaurant chain in the world by number of locations.

### SUCCESs Analysis

| Principle | Present? | How It Was Used |
|-----------|----------|----------------|
| **Simple** | Yes | The core message is effortless: eat Subway, lose weight. No calorie counting, no complex diet plans. |
| **Unexpected** | Yes | Fast food that helps you lose weight? That is a direct violation of expectations about fast food. |
| **Concrete** | Yes | 425 pounds to 180 pounds. Pants with a 60-inch waist held up as a prop. Two specific sandwiches (6-inch turkey, 12-inch veggie). |
| **Credible** | Yes | Anti-authority credibility. Jared was not a doctor or a nutritionist — he was a regular guy who did it himself. His old pants were the testable credential. |
| **Emotional** | Yes | Jared's transformation was deeply personal. Anyone who has struggled with weight could identify with him. |
| **Stories** | Yes | This IS a story. Character (Jared, a struggling college student), problem (extreme obesity), journey (ate Subway for a year), outcome (lost 245 pounds, got his life back). |

### Lessons

- Anti-authorities (regular people) are more persuasive than experts for personal transformation stories
- Concrete proof props (the old pants) are more memorable than any statistic
- Stories that seem too simple or too good often are the stickiest — if they are true
- The Sinatra Test: if Subway could help someone lose 245 pounds, it can probably help you eat healthier

## Case Study 3: "Don't Mess with Texas" Anti-Littering Campaign

### The Idea

A public anti-littering campaign that reframed littering as a violation of Texas identity rather than a civic duty.

### Why It Stuck

Previous anti-littering campaigns in Texas used guilt and environmental messaging. They failed completely with the target demographic: young men aged 18-35 who drove pickup trucks and did not respond to guilt. "Don't Mess with Texas" reduced littering by 72% in the first year.

### SUCCESs Analysis

| Principle | Present? | How It Was Used |
|-----------|----------|----------------|
| **Simple** | Yes | Four words. One message. Do not litter — because you are Texan. |
| **Unexpected** | Yes | An anti-littering campaign that never mentions the environment, guilt, or civic responsibility. Instead, it appeals to state pride. |
| **Concrete** | Yes | "Mess with" is vivid and physical. You can picture someone throwing trash on the ground — and picture a Texan being angry about it. |
| **Credible** | Yes | Endorsed by Texas celebrities (Dallas Cowboys players, Willie Nelson, Stevie Ray Vaughan). But the real credibility was identity-based: Texans trust other Texans. |
| **Emotional** | Yes | Pure identity appeal. Not "you should not litter" but "Texans do not litter." It tapped into fierce state pride. |
| **Stories** | Partial | The campaign featured Texas icons in TV spots, each telling a mini-story about Texas pride. |

### Lessons

- Identity-based messaging ("what would someone like me do?") is more powerful than rational argument
- Understanding your audience's identity is more important than understanding their logic
- The best campaigns do not tell people what to do — they tell people who they are
- Simple, memorable language becomes a cultural artifact: "Don't Mess with Texas" is now on license plates, t-shirts, and bumper stickers decades later

## Case Study 4: The Nordstrom Tire Refund Legend

### The Idea

A customer walked into a Nordstrom store and asked to return a set of tires. Nordstrom does not sell tires. The employee gave the customer a full refund anyway.

### Why It Stuck

This story has been told and retold inside and outside Nordstrom for decades. It may or may not be literally true, but it perfectly encapsulates Nordstrom's commitment to customer service. It is a generative story — it tells every Nordstrom employee how to behave in ambiguous situations.

### SUCCESs Analysis

| Principle | Present? | How It Was Used |
|-----------|----------|----------------|
| **Simple** | Yes | The core message is crystal clear: at Nordstrom, the customer is always right. Always. No exceptions. |
| **Unexpected** | Yes | Refunding tires at a store that does not sell tires is absurd. That absurdity is what makes it memorable. |
| **Concrete** | Yes | Tires. Not "a product." Not "an item." Tires. You can see them, smell the rubber, picture the confused employee and the determined customer. |
| **Credible** | Partial | The story's credibility comes from its specificity and from Nordstrom's real reputation for service. But the literal truth is debated. |
| **Emotional** | Yes | It inspires both admiration (what a company!) and aspiration (I want to work/shop there). |
| **Stories** | Yes | This is a pure story. Character (employee + customer), problem (unreasonable request), resolution (do it anyway), outcome (legendary service reputation). |

### Lessons

- Stories do not need to be literally true to be organizationally true — they encode values
- The more extreme the example, the stronger the behavioral guidance it provides
- One concrete story is worth a thousand pages of company values documents
- Generative stories teach people what to do in situations they have never encountered

## Case Study 5: The Kidney Heist Urban Legend

### The Idea

A man wakes up in a bathtub full of ice in a hotel room. A note tells him to call 911 immediately. He discovers that one of his kidneys has been surgically removed.

### Why It Stuck

This story has circulated in various forms since the 1990s across dozens of countries. It has never been verified as true. Yet it persists because it is perfectly engineered — not by design, but by the evolutionary pressure of retelling. Versions that are stickier survive; versions that are not die out.

### SUCCESs Analysis

| Principle | Present? | How It Was Used |
|-----------|----------|----------------|
| **Simple** | Yes | Core message: be careful with strangers, especially when traveling. One idea, instantly graspable. |
| **Unexpected** | Yes | Waking up in a bathtub full of ice with a kidney missing is a shocking violation of expectations about what happens when you go to a hotel. |
| **Concrete** | Yes | Bathtub. Ice. A note. A phone. A scar. Every element is viscerally tangible. |
| **Credible** | Partial | The story is credible because of its vivid details (which details imply truth) and because it is told as a friend-of-a-friend account. |
| **Emotional** | Yes | Fear, vulnerability, violation. It hits primal safety concerns. |
| **Stories** | Yes | Pure narrative: a character, a setup, a catastrophic event, a grim discovery. |

### Lessons

- Ideas that use all six principles tend to survive across time and cultures — even without intentional design
- Urban legends are naturally selected for stickiness: the versions that spread best are the versions that survive
- Concrete sensory details (the ice, the bathtub, the note) are what make the story retellable
- Emotional ideas spread faster than rational ones — fear is one of the most powerful drivers

## Case Study 6: "Names, Names, Names" — Local Newspaper Motto

### The Idea

Horace Greeley, a local newspaper editor, told his reporters that the secret to a successful local paper was "names, names, names" — publish as many local names as possible.

### Why It Stuck

This three-word motto guided decades of editorial decisions. When reporters wondered whether to cover a story, what angle to take, or what photo to run, the answer was always: prioritize local names. It was the Commander's Intent for an entire organization.

### SUCCESs Analysis

| Principle | Present? | How It Was Used |
|-----------|----------|----------------|
| **Simple** | Yes | Three words. One principle. Infinitely generative. |
| **Unexpected** | Partial | For journalists trained to chase "big" stories, the idea that names matter more than events was counterintuitive. |
| **Concrete** | Yes | "Names" is concrete. Not "community engagement" or "local relevance." Names. You can count them. |
| **Credible** | Yes | Came from a successful editor with a proven track record. The paper's popularity was the proof. |
| **Emotional** | Partial | People love seeing their names in print. The motto tapped into that universal human desire for recognition. |
| **Stories** | No | This is not a story — it is a generative principle. But it generated thousands of stories. |

### Lessons

- A generative metaphor (one that guides behavior in novel situations) is the most powerful form of simplicity
- The best Commander's Intent fits in three words
- Concrete instructions ("names") beat abstract goals ("community relevance") every time
- If your team needs a manual to interpret your strategy, your strategy is not simple enough

## Case Study 7: Apple's "1,000 Songs in Your Pocket"

### The Idea

When Apple launched the iPod in 2001, Steve Jobs described it as "1,000 songs in your pocket."

### Why It Stuck

Competing MP3 players advertised storage capacity in megabytes and gigabytes. Nobody knew what "5 GB of storage" meant in practical terms. Jobs translated the technical specification into a concrete, personal outcome. It became one of the most memorable product taglines in history.

### SUCCESs Analysis

| Principle | Present? | How It Was Used |
|-----------|----------|----------------|
| **Simple** | Yes | Six words. One idea. No technical jargon. |
| **Unexpected** | Yes | In 2001, carrying 1,000 songs was genuinely surprising. Music collections lived on shelves and in CD binders, not in pockets. |
| **Concrete** | Yes | "1,000 songs" — you can picture your music library. "In your pocket" — you can feel it. Two concrete images in six words. |
| **Credible** | Yes | It was Steve Jobs on stage with the physical product. You could hold it. |
| **Emotional** | Yes | Freedom, joy, personal identity. Your music — all of it — with you everywhere. Music is deeply emotional to most people. |
| **Stories** | Partial | Not a narrative, but it implies a story: imagine walking down the street with your entire music collection. |

### Lessons

- Translating technical specs into human outcomes is one of the most powerful applications of concreteness
- "5 GB" means nothing. "1,000 songs" means everything. Same fact, different stickiness.
- The best product descriptions tell you what the product does for you, not what it is
- Physical metaphors ("in your pocket") ground abstract benefits in the body
- Competitors who advertise specs lose to competitors who advertise outcomes

## Cross-Cutting Patterns

Analyzing these cases together reveals patterns that apply to any sticky idea:

### Pattern 1: Concreteness Is Non-Negotiable

Every single case study uses concrete language. This is not a coincidence. Abstraction is the most common reason ideas fail to stick. Tires, bathtubs, the moon, 1,000 songs — these are images that lodge in memory.

### Pattern 2: Emotional Resonance Drives Sharing

Ideas spread when they make people feel something. Fear (kidney heist), pride (Don't Mess with Texas), inspiration (JFK), aspiration (Jared), delight (iPod). The feeling does not need to be positive — it needs to be strong.

### Pattern 3: Simple Does Not Mean Short

JFK's moonshot sentence is long. But it has one idea. Simplicity is about the number of core ideas, not the number of words.

### Pattern 4: Stories Are the Ultimate Vehicle

Five of the seven case studies are primarily stories. Stories combine all other principles naturally: they require characters (concrete), events (unexpected), outcomes (credible), and emotions (emotional). If you can only use one principle, use stories.

### Pattern 5: Stickiness Is Testable

You can predict stickiness by auditing against the SUCCESs framework. Ideas that score high on multiple principles tend to spread and endure. Ideas that rely on only one principle tend to fade.

## How to Reverse-Engineer Stickiness

When you encounter a message, campaign, or idea that sticks with you, run this analysis:

### Step 1: Identify the Core Message

What is the single idea being communicated? Write it in one sentence.

### Step 2: Run the SUCCESs Audit

| Principle | Is It Present? | How Is It Implemented? |
|-----------|---------------|----------------------|
| Simple | | |
| Unexpected | | |
| Concrete | | |
| Credible | | |
| Emotional | | |
| Stories | | |

### Step 3: Find the Dominant Principle

Which principle does the heaviest lifting? That is the idea's "stickiness engine."

### Step 4: Identify Transferable Techniques

What specific technique can you borrow for your own communication?

| Case Study | Transferable Technique |
|-----------|----------------------|
| JFK Moonshot | Set a concrete, time-bound goal that generates decisions |
| Subway Jared | Use an anti-authority with a dramatic personal transformation |
| Don't Mess with Texas | Frame behavior as identity, not obligation |
| Nordstrom Tires | Tell an extreme example that teaches the principle |
| Kidney Heist | Use vivid sensory details to make any scenario feel real |
| Names Names Names | Create a generative metaphor that guides behavior |
| 1,000 Songs | Translate technical specs into human, emotional outcomes |

### Step 5: Apply to Your Context

Take the technique and apply it directly:

- **Your moonshot:** "We will [specific, concrete outcome] by [date]"
- **Your Jared:** "Meet [real person] who [dramatic transformation using your product]"
- **Your identity frame:** "[Your audience identity] does not [undesirable behavior]"
- **Your Nordstrom story:** "One time, we [extreme example of your core value]"
- **Your vivid details:** "On [specific day], at [specific place], [specific thing happened]"
- **Your motto:** "[Three words] that guide every decision"
- **Your pocket:** "[Number] [things your audience cares about] in [where they want it]"

## Stickiness Scoring Exercise

Take your current most important message and score it:

| Principle | Score (0-10) | Evidence |
|-----------|-------------|---------|
| Simple | | |
| Unexpected | | |
| Concrete | | |
| Credible | | |
| Emotional | | |
| Stories | | |
| **Total** | **/60** | |

- **45-60:** Extremely sticky. This message will endure.
- **30-44:** Strong. A few improvements could make it exceptional.
- **15-29:** Average. Significant rework needed on weak principles.
- **Below 15:** Will not stick. Fundamental reimagining required.

Now look at your lowest-scoring principle. That is where the biggest improvement opportunity lies. Raise your weakest principle by even 3 points and the entire message gets stronger.

# Concrete: Making Ideas Tangible and Memorable

Abstraction is the enemy of memory. The more abstract your language, the fewer hooks your audience has to hold onto. Concrete ideas stick because they engage the senses, create mental images, and connect to real experience. This reference is a deep dive into making any idea — no matter how complex or intangible — concrete enough to remember and act on.

## The Velcro Theory of Memory

Think of memory as Velcro. One side has thousands of tiny hooks. The other side has thousands of tiny loops. The more hooks and loops that connect, the stronger the bond.

Abstract ideas are smooth — they have very few hooks. Concrete ideas are covered in hooks: sensory details, specific images, tangible objects, real people, particular moments.

| Abstract (Smooth) | Concrete (Velcro) | Why It Sticks |
|-------------------|-------------------|---------------|
| "Vehicle" | "A red 1967 Mustang convertible" | You can see it, hear the engine, feel the wind |
| "Improve customer satisfaction" | "Every customer gets a handwritten thank-you note within 24 hours" | You can picture someone writing the note |
| "Increase efficiency" | "Cut the report from 47 clicks to 3" | You can count the clicks |
| "Better communication" | "Every team member posts a 2-sentence daily update by 9am" | You can do it or not do it — it is binary |
| "Drive growth" | "Add 200 paying customers every month" | You can track it on a chart |

### Why This Matters for Communication

When you say "vehicle," every person in the room pictures a different thing. One sees a truck, another a sedan, another a motorcycle. When you say "red 1967 Mustang convertible," everyone sees the same thing. Concrete language creates shared understanding. Abstract language creates the illusion of shared understanding.

## Abstract vs. Concrete: Transformation Techniques

### Technique 1: Replace Categories with Examples

Every time you use a category word, ask: "Can I replace this with a specific example?"

| Category (Abstract) | Specific Example (Concrete) |
|---------------------|----------------------------|
| "Businesses of all sizes" | "A 3-person design studio and a 500-person logistics company" |
| "Various industries" | "Hospital ERs, fast-food chains, and law firms" |
| "Multiple use cases" | "Tracking sales calls, onboarding new hires, and debugging outages" |
| "Key stakeholders" | "The VP of Engineering, the head of recruiting, and the CFO" |
| "Significant improvement" | "Went from 4 missed deadlines per quarter to zero" |

### Technique 2: Translate Features into Sensory Outcomes

Features are abstract capabilities. Sensory outcomes are what the user sees, hears, or feels when the feature works.

| Feature (Abstract) | Sensory Outcome (Concrete) |
|--------------------|---------------------------|
| "Real-time collaboration" | "You see your teammate's cursor moving across the document as they type" |
| "Automated reporting" | "Every Monday at 8am, a PDF lands in your inbox with last week's numbers" |
| "Intelligent search" | "Type 'that email from Sarah about the budget' and it finds the exact thread" |
| "Seamless integration" | "Click 'Connect Salesforce' and your pipeline appears in 30 seconds" |
| "Advanced analytics" | "A red dot appears next to any customer who is likely to churn this month" |

### Technique 3: Convert Percentages to Real Numbers

Percentages feel abstract. Real numbers tied to real things feel concrete.

| Percentage (Abstract) | Real Number (Concrete) |
|----------------------|----------------------|
| "Save 30% of your time" | "Get back 12 hours every week — that is a whole day and a half" |
| "Reduce errors by 85%" | "Go from 17 bugs per release to 2 or 3" |
| "40% faster deployment" | "Deploy in 6 minutes instead of 10 — before your coffee gets cold" |
| "95% uptime" | "Down for 18 days a year — that is almost 3 full work weeks" |
| "99.9% uptime" | "Down for 8 hours a year — roughly one workday" |

### Technique 4: Add Time, Place, and Person

Abstractions float in a void. Concrete ideas are anchored to a specific time, place, and person.

**Abstract:**
> "Our platform improves team productivity."

**Concrete (with time, place, and person):**
> "Last Tuesday at 2pm, the engineering team at Acme Corp used our platform to resolve a production incident in 11 minutes. The same type of incident used to take them 3 hours."

## Sensory Language: Engaging the Five Senses

The brain processes sensory information differently from abstract information. Sensory details activate the same brain regions as actual experience. When you read about the smell of fresh bread, your olfactory cortex activates.

### Applying Sensory Language to Product Messaging

| Sense | Abstract Version | Sensory Version |
|-------|-----------------|-----------------|
| **Sight** | "Beautiful dashboard" | "A clean white screen with three colored bars — green means you are on track" |
| **Sound** | "Get notified instantly" | "Your phone buzzes the moment a deal closes" |
| **Touch** | "Easy to use" | "Drag a card from one column to the next — that is it" |
| **Taste/Smell** | "Fresh ingredients" | "Tomatoes picked this morning, basil that still smells like the garden" |
| **Motion** | "Fast loading" | "Pages snap into place — no spinning wheels, no waiting" |

### The Sensory Language Audit

Go through your current messaging and highlight every abstract word. Then, for each one, ask: "Can the audience see it, hear it, touch it, or feel it?" If not, rewrite.

**Common abstract words that need sensory replacements:**

| Abstract Word | Ask Yourself | Possible Replacement |
|--------------|-------------|---------------------|
| "Efficient" | What does efficient look like? | "Finishes in 3 clicks" |
| "Powerful" | What does power look like here? | "Processes 1 million rows in under a second" |
| "Innovative" | What is the innovation? Show it. | "The first tool that lets you edit video by editing text" |
| "Seamless" | What would seams look like? | "No login screens, no copy-pasting, no switching tabs" |
| "Robust" | What survives that others don't? | "Handles Black Friday traffic without a single error" |

## Specific Numbers vs. Vague Claims

Vague claims feel like marketing. Specific numbers feel like truth.

### The Specificity Principle

The more specific a number, the more believable it is — even if the audience does not verify it. "We have helped 2,347 companies" is more believable than "We have helped thousands of companies," even though both could be equally true or false.

| Vague Claim | Specific Claim | Why It Works |
|------------|---------------|-------------|
| "Thousands of customers" | "2,347 customers across 41 countries" | Specificity implies careful tracking |
| "Saves you hours" | "Saves 11.4 hours per week on average" | Decimal point implies measurement |
| "Fast support" | "Average response time: 47 seconds" | Odd number implies real data |
| "Lots of integrations" | "Connects to 143 tools including Slack, Salesforce, and HubSpot" | Number + examples = concrete |
| "Trusted by leading companies" | "Used by 7 of the Fortune 10" | Precise fraction implies verifiable |

### When to Use Round Numbers vs. Precise Numbers

- **Round numbers** for vision and scale: "We want to help 1 million small businesses"
- **Precise numbers** for credibility and proof: "We have helped 14,832 small businesses so far"
- **Never use round numbers** when claiming results: "Saves about 50%" feels like a guess. "Saves 47%" feels like a measurement.

## Demonstrations and Before/After Comparisons

### The Power of Demonstration

A demonstration is worth a thousand bullet points. When someone can see the product working with real data on a real problem, abstraction evaporates.

**Rules for effective demonstrations:**

1. **Use real data** — never "Lorem ipsum" or fake company names
2. **Solve a real problem** — not a contrived example
3. **Show the pain first** — demonstrate the old way before the new way
4. **Time it** — "Watch: this takes 8 seconds" is more concrete than "It's fast"
5. **Let the audience drive** — interactive demos beat scripted walkthroughs

### Before/After Comparison Template

| Dimension | Before (Without Product) | After (With Product) |
|-----------|-------------------------|---------------------|
| **Time spent** | [Specific hours/minutes] | [Specific hours/minutes] |
| **Steps required** | [Specific number of steps] | [Specific number of steps] |
| **Error rate** | [Specific frequency] | [Specific frequency] |
| **People involved** | [Specific roles/count] | [Specific roles/count] |
| **Tools used** | [List specific tools] | [Just your tool] |
| **Emotional state** | [Concrete frustration] | [Concrete relief] |

### Example Before/After

| Dimension | Before | After |
|-----------|--------|-------|
| **Time** | 4 hours every Friday afternoon | 10 minutes on Monday morning |
| **Steps** | Export from 3 tools, paste into Excel, format, email | Click "Generate" and it sends itself |
| **Errors** | Wrong numbers at least once a month | Automated = zero manual errors |
| **People** | Analyst + manager + reviewer | Nobody (it's automated) |
| **Tools** | Salesforce, Google Analytics, Excel, Gmail | Just our dashboard |
| **Feeling** | "Friday afternoons are the worst" | "I forgot reports were even a thing" |

## Application Across Contexts

### Product Messaging

| Abstract Product Message | Concrete Product Message |
|-------------------------|------------------------|
| "Streamline your workflow" | "Cut 23 steps down to 5. Here is what goes away: [list]" |
| "Enterprise-ready security" | "Your data is encrypted, stored in Frankfurt, and we passed a SOC 2 audit last month" |
| "Actionable insights" | "Every morning you see a list of the 3 customers most likely to upgrade this week" |

### Presentations

| Abstract Slide | Concrete Slide |
|---------------|----------------|
| "We saw significant growth in Q3" | "Q3: 847 new customers, $2.1M in new ARR, 3 enterprise logos" |
| "Our users love the product" | "[Screenshot of actual user message]: 'This tool literally saved my job'" |
| "We are expanding into new markets" | "We signed our first customer in Tokyo last Tuesday. Here is their story." |

### Documentation and Help Content

| Abstract Documentation | Concrete Documentation |
|-----------------------|-----------------------|
| "Configure your settings as needed" | "Click Settings > Notifications > toggle 'Email alerts' to ON" |
| "Integrate with your existing tools" | "Step 1: Open Slack. Step 2: Type /connect. Step 3: Paste your API key." |
| "Customize the dashboard" | "Drag the Revenue widget to the top-left corner. It snaps into place." |

## Exercises: Make Any Abstract Idea Concrete

### Exercise 1: The Camera Test

Read your message and ask: "Could a camera record this?" If a filmmaker cannot point a camera at it and capture it, the language is too abstract.

- "Improve team alignment" — A camera cannot film "alignment." Rewrite.
- "Every Monday at 9am, the team spends 15 minutes reviewing the same dashboard together" — A camera can film this.

### Exercise 2: The Specificity Ladder

Take an abstract statement and make it more specific in five steps:

1. "We help companies" (most abstract)
2. "We help mid-size SaaS companies"
3. "We help mid-size SaaS companies reduce churn"
4. "We help mid-size SaaS companies reduce churn by identifying at-risk accounts"
5. "We send you a Slack alert when a customer has not logged in for 7 days, with a suggested re-engagement email ready to send" (most concrete)

### Exercise 3: The "Show Me" Challenge

For every claim you make, imagine the audience saying "Show me." Can you?

| Claim | "Show Me" Response |
|-------|--------------------|
| "We are fast" | Live demo: task completes in 3 seconds |
| "Customers love us" | Screenshot of a real review with the customer's name |
| "We save you money" | Calculator: enter your numbers, see the savings |
| "Easy to learn" | Video: new user going from signup to first result in 90 seconds |

### Exercise 4: The Translation Table

Create a two-column table for your product. Left column: every abstract word you use. Right column: the concrete replacement.

Build this into your team's writing process. Keep a running "translation table" that converts your internal jargon into concrete, customer-facing language.

## Industry-Specific Concreteness

| Industry | Abstract Norm | Concrete Alternative |
|----------|--------------|---------------------|
| **SaaS** | "Boost productivity" | "Your team ships 2 more features per sprint" |
| **Healthcare** | "Improve patient outcomes" | "Patients leave the hospital 1.3 days sooner" |
| **Finance** | "Optimize portfolio performance" | "Your retirement fund earned $14,200 more last year than the market average" |
| **Education** | "Enhance learning outcomes" | "Students scored 23 points higher on the state math test" |
| **E-commerce** | "Increase conversions" | "47 more people bought something today than yesterday" |
| **Real estate** | "Premium location" | "8-minute walk to the subway, 3 blocks from the park" |
| **Consulting** | "Drive strategic transformation" | "We helped them close their books in 3 days instead of 21" |
| **Manufacturing** | "Optimize supply chain" | "Parts arrive 2 days earlier, and you hold 30% less inventory" |

## Concreteness Checklist

Before publishing any message:

- [ ] Every abstract noun has been replaced with a specific, tangible example
- [ ] Numbers are specific, not rounded (unless intentionally used for vision)
- [ ] The audience can form a mental image of the claim
- [ ] At least one concrete before/after comparison is included
- [ ] Sensory language engages at least one sense (sight, sound, touch)
- [ ] Examples use real names, real places, or real scenarios — not placeholders
- [ ] The Camera Test passes: a filmmaker could capture the scene
- [ ] Category words have been replaced with specific instances
- [ ] Statistics are human-scale and relatable
- [ ] Every "Show me" challenge can be met with evidence

# Credible: Making People Believe Your Idea

An idea can be simple, surprising, concrete, and emotional — but if people do not believe it, none of that matters. Credibility is what turns an interesting claim into a convincing one. There are two types of credibility: external (borrowed from authorities) and internal (built into the message itself). The most powerful sticky ideas use both.

## External Credibility

External credibility comes from outside your message. It is borrowed from people, institutions, or achievements that your audience already trusts.

### Authorities

An authority is someone with recognized expertise or status. When an authority endorses your idea, their credibility transfers to you.

| Authority Type | Example | Best For |
|---------------|---------|----------|
| **Domain expert** | "Recommended by Dr. Sarah Chen, Stanford oncologist" | Technical or scientific claims |
| **Celebrity** | "Used by Serena Williams" | Consumer products, lifestyle brands |
| **Institution** | "Published in the New England Journal of Medicine" | Academic or research claims |
| **Industry leader** | "Featured in TechCrunch, Forbes, and Wired" | Startup credibility |
| **Award or certification** | "Winner of the 2024 Red Dot Design Award" | Quality and design claims |

**Limitations of authority credibility:**
- Audiences are increasingly skeptical of celebrity endorsements
- The authority must be relevant to your claim (a dentist endorsing a car feels wrong)
- Authority alone is not enough — it must be paired with substance

### Anti-Authorities

An anti-authority is the opposite of a traditional expert. It is a real person whose personal experience makes them credible. Anti-authorities are often more persuasive than authorities because they are relatable.

**Why anti-authorities work:**
- They have lived experience, not theoretical knowledge
- The audience identifies with them ("This person is like me")
- Their credibility cannot be bought or faked

| Anti-Authority | Claim | Why It Works |
|---------------|-------|-------------|
| A cancer survivor | "This treatment saved my life" | Personal stakes, authentic experience |
| A former smoker | "I quit after 20 years using this method" | Relatable struggle, proof of transformation |
| A small business owner | "I was drowning in spreadsheets until I found this tool" | Shared pain, practical credibility |
| A burned-out developer | "I was working 80-hour weeks. This tool gave me my weekends back" | Emotional resonance through shared experience |

**The power of the anti-authority:** Pam Laffin, a 29-year-old smoker with emphysema, was far more persuasive in anti-smoking campaigns than any surgeon general. She was not an expert — she was a cautionary example. Her credibility came from lived consequence.

### Credentials

Credentials are verifiable facts about your track record, qualifications, or achievements.

| Credential Type | Example |
|----------------|---------|
| **Track record** | "12 years in business, 0 data breaches" |
| **Certifications** | "SOC 2 Type II compliant, HIPAA certified" |
| **Numbers** | "Processed $4.2 billion in transactions last year" |
| **Client list** | "Trusted by NASA, Stripe, and the NHS" |
| **Experience** | "Founded by ex-Google and ex-Apple engineers" |

## Internal Credibility

Internal credibility is built into the message itself. It does not rely on external sources — it makes the audience believe through the structure and specificity of the claim. Internal credibility is often more powerful than external credibility because it feels earned rather than borrowed.

### Vivid Details

Specific, vivid details make claims feel true. When someone says "On a Tuesday afternoon in the conference room on the 4th floor," it feels like a real memory, not a fabrication. Liars speak in generalities. Truth-tellers speak in specifics.

| Vague (Less Credible) | Vivid (More Credible) |
|-----------------------|----------------------|
| "A company improved their metrics" | "Acme Corp's support team in Phoenix reduced ticket resolution time from 4.2 hours to 47 minutes" |
| "We helped a client grow" | "We helped BrightPath go from $400K ARR to $2.1M ARR in 11 months" |
| "Our users are happy" | "Last Thursday, a user named Marcus sent us a screenshot of his team celebrating — they had closed their first deal in 3 minutes flat using our tool" |

### Statistics

Statistics can be powerful — but only if presented correctly. Most statistics fail because they are too abstract, too large, or too disconnected from human experience.

**The problem with raw statistics:**
- "37 grams of saturated fat" means nothing to most people
- "$3.5 trillion healthcare market" is too large to comprehend
- "47% improvement" is abstract without a baseline

### Making Statistics Human-Scale and Sticky

The key to sticky statistics is making them relatable. Translate numbers into things people can see, feel, or compare to their own experience.

| Raw Statistic | Human-Scale Version | Technique Used |
|--------------|--------------------|-|
| "37 grams of saturated fat" | "More saturated fat than a bacon-and-eggs breakfast, a Big Mac with fries, and a steak dinner — combined" | **Comparison to known quantities** |
| "10 TB of storage" | "Every book ever written in every language, stored 100 times over" | **Familiar reference point** |
| "2.5 million data points per second" | "Imagine every person in Chicago sending you a message at the same time. We handle that, every second." | **Population analogy** |
| "$1.2M in savings" | "That is 8 new full-time hires, or a new office, or 3 years of your marketing budget" | **Alternative uses** |
| "99.99% uptime" | "Less than 53 minutes of downtime per year — you probably lose more time making coffee" | **Time translation** |

**Rules for sticky statistics:**

1. Always compare to something the audience already understands
2. Use the smallest meaningful number (not millions when thousands work)
3. Make the comparison visceral, not just mathematical
4. One powerful statistic beats ten mediocre ones

### The Sinatra Test

"If I can make it there, I can make it anywhere." The Sinatra Test is a single example so impressive that it handles all objections. It is proof by intimidation — one reference that makes further questions unnecessary.

**How the Sinatra Test works:**
If you catered a White House dinner, you can cater anything. If you handled security for the Olympics, you can handle security for anyone. The one example is so extreme that every lesser challenge is implicitly covered.

| Domain | Sinatra Test Example | What It Proves |
|--------|---------------------|---------------|
| **Security** | "We protect the Pentagon's networks" | Security for any organization |
| **Scalability** | "We handled Super Bowl Sunday traffic for CBS" | Scalability for any event |
| **Reliability** | "NASA uses us for mission-critical systems" | Reliability for any use case |
| **Design** | "Apple chose us for their retail experience" | Design quality for anyone |
| **Speed** | "We process trades for high-frequency trading firms in 3 microseconds" | Speed for any application |
| **Trust** | "We manage $2 trillion in retirement assets" | Fiduciary trust for anyone |

**Finding your Sinatra Test:**
1. Who is the most demanding, prestigious, or extreme customer you serve?
2. What is the hardest thing your product has ever handled?
3. What is the one example that would make a skeptic say "OK, I believe you"?

### Testable Credentials

A testable credential invites the audience to verify the claim themselves. It says "Don't take my word for it — see for yourself."

| Testable Credential | Why It Works |
|--------------------|-|
| "Try it free for 14 days" | Zero risk to verify the claim |
| "Run our tool on your own data and compare the results" | Personal verification |
| "Here is a live dashboard showing our uptime right now" | Real-time proof |
| "Call any of these 50 customers and ask them" | Third-party verification |
| "Google our name + 'review' and read what comes up" | Transparent confidence |

**Why testable credentials are so powerful:**
- They demonstrate confidence in the product
- They transfer the burden of proof to the audience
- They feel fair and honest — you are not hiding anything
- Even if most people never test it, the invitation itself builds trust

## Building Credibility for New Products and Startups

New companies face a credibility gap. They have no track record, no famous customers, no brand recognition. Here are strategies for building credibility from scratch:

### Strategy 1: Founder Credibility

| Element | Example |
|---------|---------|
| **Relevant experience** | "Built by a team that spent 10 years inside the problem at [BigCo]" |
| **Skin in the game** | "We left $300K/year jobs to build this because we could not stand the status quo" |
| **Domain expertise** | "Our CTO wrote the open-source library that 40% of the industry already uses" |

### Strategy 2: Early Customer Proof

| Element | Example |
|---------|---------|
| **Specific results** | "Our first 10 customers saw an average 3.2x ROI in 60 days" |
| **Named customers** | "Acme Corp, BrightPath, and Zenith all signed in our first month" |
| **Before/after** | "Before us: 4 hours. After us: 12 minutes. Ask them." |

### Strategy 3: Transparent Honesty

| Element | Example |
|---------|---------|
| **Acknowledge limitations** | "We are early. We have 47 customers. Here is what they say." |
| **Show the journey** | "Here is our public roadmap. Here is what we shipped last month." |
| **Admit what you are not** | "We are not for enterprise yet. We are the best tool for teams under 50." |

### Strategy 4: The "Try It" Approach

| Element | Example |
|---------|---------|
| **Free trial** | "Start in 2 minutes. No credit card required." |
| **Sandbox** | "Play with a demo account loaded with sample data" |
| **Money-back guarantee** | "If you do not see results in 30 days, full refund, no questions" |
| **Proof of work** | "Here is our product analyzing YOUR website, right now, for free" |

## Before/After Credibility Improvements

### Landing Page Headline

**Before:**
> "The best project management tool for modern teams."

**After:**
> "The project management tool that helped Stripe ship 3x faster. Try it free."

### Sales Email

**Before:**
> "We offer a cutting-edge solution that has been shown to improve results significantly."

**After:**
> "Last quarter, 3 companies in your space switched from [Competitor] to us. All three reduced their close time from 14 days to 5. Here is a case study from one of them."

### Product Page Testimonial

**Before:**
> "'Great product!' — Happy Customer"

**After:**
> "'We were spending 6 hours a week on reporting. Now it is automated. I literally got a promotion because of the time I saved.' — Maria Torres, Head of Ops at Acme Corp"

### Pricing Page

**Before:**
> "Join thousands of happy customers."

**After:**
> "Join 4,782 teams. Here are the last 10 companies that signed up: [live feed]. Average time to first value: 4 minutes."

## Credibility Checklist

Before publishing any claim, verify:

- [ ] At least one form of external credibility is present (authority, anti-authority, or credential)
- [ ] At least one form of internal credibility is present (vivid details, statistics, Sinatra Test, or testable credential)
- [ ] Statistics are human-scale and compared to something the audience understands
- [ ] Specific numbers are used instead of vague quantities ("2,347" not "thousands")
- [ ] Testimonials include the person's full name, title, and company
- [ ] Claims are verifiable — the audience could check them if they wanted to
- [ ] There is a Sinatra Test candidate: one example so strong it covers all objections
- [ ] A testable credential is offered: "See for yourself" in some form
- [ ] Credibility sources are relevant to the specific claim being made
- [ ] Honest limitations are acknowledged (increases trust in the claims you do make)

## Credibility Pitfalls to Avoid

| Pitfall | Why It Backfires | Fix |
|---------|-----------------|-----|
| **Unverifiable claims** | "Best in class" means nothing | Replace with specific, provable metrics |
| **Irrelevant authority** | Celebrity endorsing enterprise software | Use domain-relevant authorities |
| **Stale proof** | "Award winner 2018" | Use recent examples and continuously refresh |
| **Anonymous testimonials** | "A Fortune 500 company" | Name them, or do not mention them |
| **Over-claiming** | "We are 10x better than everything" | Specific, modest claims are more believable |
| **Round numbers** | "Saved millions of dollars" | "Saved $2.4M in the first 9 months" |
| **Missing context** | "97% customer satisfaction" | "97% satisfaction across 1,200 quarterly surveys" |

# The Curse of Knowledge: The Silent Killer of Communication

The Curse of Knowledge is the single most important concept in "Made to Stick." It is not one of the six SUCCESs principles — it is the villain that all six principles are designed to defeat. Once you know something, you cannot imagine not knowing it. This gap between what you know and what your audience knows is where communication goes to die.

## What the Curse of Knowledge Is

The Curse of Knowledge is a cognitive bias: when you possess knowledge, you unconsciously assume others possess it too. You skip steps, use shorthand, rely on jargon, and abstract away details — because to you, those details are obvious. To your audience, they are invisible.

**The core problem:** Experts communicate like experts, to an audience of non-experts. The more you know about a subject, the harder it is to communicate it clearly to someone who does not.

### Why It Is So Dangerous

The Curse of Knowledge is uniquely dangerous because it is invisible to the person afflicted by it. You do not know you are skipping context. You do not realize your jargon is opaque. You genuinely believe you are being clear — because from inside your head, you are.

| What You Think You Said | What Your Audience Heard |
|------------------------|-------------------------|
| "We use a microservices architecture with event-driven communication" | "We use... technical stuff" |
| "The ROI on this initiative is clear" | "They want me to spend money" |
| "Leverage our API to integrate seamlessly" | "There is some technical work involved, I think?" |
| "We optimize the customer journey" | "They do something with customers" |
| "Our ML pipeline processes data in real time" | "They have AI, I guess" |

## The Tapping Experiment

In 1990, Elizabeth Newton conducted a simple experiment at Stanford that became the most famous demonstration of the Curse of Knowledge.

### The Setup

- **Tappers:** Asked to tap the rhythm of a well-known song (like "Happy Birthday") on a table
- **Listeners:** Asked to identify the song from the tapping alone
- **Before listening:** Tappers predicted that listeners would identify the song 50% of the time
- **Actual result:** Listeners identified the song only 2.5% of the time

### Why the Gap Is So Large

When tappers tapped, they heard the full song in their heads — melody, lyrics, instruments. They could not believe the listeners could not hear it too. But listeners heard only a series of disconnected taps. Rhythmic Morse code with no melody.

### What This Means for Communication

Every time you present a product, write a landing page, or pitch an investor, you are a tapper. You hear the full symphony of your product's value. Your audience hears disconnected taps. The Curse of Knowledge makes it nearly impossible for you to hear what they hear.

| You (The Tapper) | Your Audience (The Listener) |
|-------------------|----------------------------|
| See the complete product vision | See a list of features |
| Understand how everything connects | See disconnected pieces |
| Know the backstory and context | Start with zero context |
| Feel the emotional weight of the problem | Have not felt the problem yet |
| Think in domain-specific language | Think in everyday language |

## How the Curse Manifests

The Curse of Knowledge shows up in specific, recognizable patterns. Learning to spot these patterns is the first step to overcoming them.

### Pattern 1: Jargon and Acronyms

Using specialized vocabulary that feels natural to you but is foreign to your audience.

| Cursed Version | Clear Version |
|---------------|--------------|
| "Our SaaS platform leverages NLP for CRM optimization" | "Our software reads your customer emails and tells you who needs attention" |
| "We reduce CAC through LTV-optimized retention loops" | "We help you keep customers longer so you spend less finding new ones" |
| "Deploy containerized microservices via our CI/CD pipeline" | "Push a button and your code goes live in 60 seconds" |
| "HIPAA-compliant PHI management with role-based ACLs" | "Patient records stay private — only authorized staff can see them" |

### Pattern 2: Skipped Context

Jumping to conclusions without providing the steps that got you there.

**Cursed version:**
> "Obviously, the key challenge is alignment between product and go-to-market."

**What the audience needs to hear first:**
> "Right now, your product team builds features based on what they think customers need. Your sales team promises features based on what they think closes deals. These two lists rarely overlap. That misalignment is costing you deals and wasting engineering time."

### Pattern 3: Over-Abstraction

Using high-level concepts when specific, concrete examples would be clearer.

| Over-Abstracted | Concrete |
|----------------|----------|
| "We enable digital transformation" | "We moved their paper forms to a mobile app — 10,000 fewer pieces of paper per month" |
| "We drive operational excellence" | "Their warehouse team finds items in 30 seconds instead of 10 minutes" |
| "We facilitate collaboration" | "Designers and engineers comment on the same file instead of emailing screenshots back and forth" |

### Pattern 4: The Assumed "Why"

Assuming your audience already cares about the problem you solve.

**Cursed version:**
> "Introducing our new monitoring dashboard!"

**What the audience is thinking:**
> "Why do I need a monitoring dashboard? What happens without one?"

**Uncursed version:**
> "Last month, your site went down for 47 minutes before anyone noticed. Our dashboard would have caught it in 12 seconds."

### Pattern 5: Feature Blindness

Listing features instead of explaining outcomes, because features are how you think about the product internally.

| Feature (How You Think) | Outcome (How They Think) |
|------------------------|-------------------------|
| "Real-time sync" | "Your changes show up on your coworker's screen instantly" |
| "256-bit AES encryption" | "Your data is locked with the same security banks use" |
| "Automated workflow engine" | "The boring stuff happens by itself" |
| "Custom role-based permissions" | "The intern can see reports but cannot delete anything" |

## Diagnosing the Curse in Your Own Communication

### The Five Warning Signs

Use this checklist to audit any piece of communication:

1. **The Jargon Count:** Count every word or phrase that requires industry knowledge. More than 2 per paragraph? You are cursed.

2. **The Context Check:** Read your message and ask, "Would this make sense to someone hearing about this for the first time?" If not, you have skipped context.

3. **The "So What?" Test:** After every claim, ask "So what? Why should I care?" If the answer is not obvious to an outsider, you have assumed the "why."

4. **The Abstraction Audit:** Highlight every abstract noun (efficiency, optimization, transformation, alignment). Each one is a potential curse symptom.

5. **The Mom Test:** Could your mother (or any non-expert) understand this? If you hesitate, the answer is no.

### Self-Diagnosis Exercise

Take your most recent piece of external communication (email, landing page, presentation). Read it as if you had never heard of your company or product. Mark every place where:

- [ ] You used a word your audience might not know
- [ ] You assumed background knowledge
- [ ] You used an abstraction instead of a concrete example
- [ ] You stated a feature without explaining why it matters
- [ ] You jumped to a conclusion without showing your reasoning

Count the marks. That is your Curse of Knowledge score. Aim for zero.

## Remedies

### Remedy 1: Outsider Testing

The most reliable cure is to show your communication to people who are NOT inside your bubble.

**Who to test with:**
- New employees (first 30 days — they still remember what confusion feels like)
- Customers who recently evaluated your product (they remember the learning curve)
- Friends and family who work in different industries
- Interns or junior team members

**What to test:**
- "Read this and tell me what you think it means"
- "After reading this, what would you do next?"
- "Is there anything confusing or unclear?"
- "What questions do you have?"

**The rule:** If even one person is confused, the message is cursed. The problem is never the audience. It is always the message.

### Remedy 2: Concrete Language

Replace every abstraction with a specific, tangible example. If you cannot picture it, neither can your audience.

| Abstract (Cursed) | Concrete (Clear) |
|-------------------|-----------------|
| "Streamlined operations" | "Orders ship in 2 hours instead of 2 days" |
| "Enhanced visibility" | "See exactly which step your order is on, right now" |
| "Improved efficiency" | "The report that took 4 hours now takes 10 minutes" |
| "Optimized performance" | "Pages load in 0.8 seconds instead of 3.2 seconds" |

### Remedy 3: Stories

Stories are the most powerful curse-breaker because they force concreteness and context. You cannot tell a story in abstractions. "A customer had a problem and our product solved it" is not a story. "Sarah, a 35-year-old veterinarian in Austin, was spending her evenings doing paperwork instead of being with her family" is the beginning of a story.

### Remedy 4: Analogies

Analogies bridge the gap between what you know and what your audience knows by anchoring the new idea in something familiar.

| New Concept | Analogy | Why It Works |
|-------------|---------|-------------|
| Container orchestration | "Like an air traffic controller for your servers" | Everyone understands air traffic control |
| API | "Like a waiter taking your order to the kitchen" | Restaurants are universal |
| Machine learning | "Like a new employee who gets better the more examples you show them" | Everyone has onboarded someone |
| Microservices | "Instead of one big machine, you have many small specialists" | Specialists are a known concept |

### Remedy 5: The "What I Mean Is..." Technique

When you catch yourself using jargon or abstraction, pause and say "What I mean is..." The explanation that follows is almost always clearer than the original.

**Original:** "We need to achieve alignment across our go-to-market motion."
**"What I mean is..."** "We need sales, marketing, and product to agree on who we are selling to and what we are saying."

## The Curse in Different Contexts

### Product Teams

Product managers are deeply cursed. They live inside the product every day, understand every feature, and have context for every decision. When they write requirements, release notes, or product pages, they unconsciously skip the context that makes things understandable.

**Common symptoms:**
- Release notes that list feature names without explaining value
- Product pages organized by feature category instead of customer problem
- Onboarding flows that assume familiarity with the product concept
- Documentation that skips "why" and jumps to "how"

**Fix:** Have someone who has never used the product attempt to complete onboarding using only your written materials. Watch where they get stuck.

### Marketing

Marketers inherit the curse from the product team and add their own layer. They develop their own shorthand ("lead nurturing," "funnel optimization," "brand positioning") that means nothing to customers.

**Common symptoms:**
- Landing pages filled with industry buzzwords
- Value propositions that could describe any company
- Campaign messaging that sounds impressive but communicates nothing specific
- Social media content that performs well internally but poorly externally

**Fix:** Run every piece of external copy through the "Mom Test." If your mother cannot explain what you sell after reading your homepage, rewrite it.

### Sales

Sales teams develop their own jargon through repetition. They pitch so often that they forget which parts of the pitch require context.

**Common symptoms:**
- Demos that start with a product tour instead of the customer's problem
- Pitches that assume the prospect understands the problem as deeply as the salesperson
- Follow-up emails full of product terminology the prospect has never used
- Proposals that lead with features instead of outcomes

**Fix:** Record a sales call. Play it back and mark every moment where a prospect says "What do you mean by...?" or looks confused. Those are curse moments.

### Documentation

Technical writers are often the most deeply cursed. They know the product so well that they write documentation for themselves, not for the user.

**Common symptoms:**
- Setup guides that skip "obvious" steps (which are only obvious to people who already know the product)
- Error messages that use internal error codes instead of plain language
- Help articles that answer "how" but never "why" or "when"
- FAQs that address the questions the company wants to answer, not the questions users actually ask

**Fix:** Track your top support tickets. If users keep asking questions that your documentation "already answers," the documentation is cursed.

## Exercises: Identify and Overcome Your Own Curse

### Exercise 1: The Jargon Jar

For one week, every time someone in your team uses a jargon word in customer-facing communication, they put a dollar in the jargon jar. At the end of the week, count the money. Buy the team lunch with the proceeds. The point is not punishment — it is awareness.

### Exercise 2: The Blank Slate Review

Give your homepage, pitch deck, or key email to five people who have never heard of your product. Ask them three questions:
1. What does this company do?
2. Who is it for?
3. Why would someone use it?

If fewer than 4 out of 5 answer correctly, you are cursed.

### Exercise 3: The Reverse Explainer

Ask a new customer to explain your product to someone else. Record what they say. Their explanation — in their words, with their framing — is probably better than yours. It is certainly more understandable to other non-experts.

### Exercise 4: The Abstraction Detector

Take any document and highlight every abstract noun. For each one, write a concrete alternative underneath. Compare the two versions. The concrete version is almost always better.

### Exercise 5: The 10-Year-Old Test

Explain your product to a 10-year-old (or pretend to). If you cannot do it, you have not found the core idea. Keep simplifying until a child would nod and say, "Oh, so it is like..."

## Building Curse-Awareness into Team Processes

### Hiring

Include non-expert communication in interview processes. Ask candidates to explain a complex concept from their previous role to someone outside the field. Evaluate clarity, not just accuracy.

### Onboarding

Require new employees to document their confusion during the first two weeks. What was unclear? What jargon did they encounter? This fresh perspective is gold for improving external communication.

### Review Processes

Add a "Curse of Knowledge check" to every review process:

| Process | Curse Check |
|---------|------------|
| **Content review** | "Would a first-time visitor understand this?" |
| **Product review** | "Would a new user know what to do here?" |
| **Presentation review** | "Would someone outside our industry follow this?" |
| **Email review** | "Would the recipient know what we are asking and why?" |

### Regular Audits

Every quarter, select 5 pieces of customer-facing communication and run them through the full diagnostic: count jargon words, check for skipped context, test with outsiders, replace abstractions with concrete examples, and verify that every "why" is explicit. Track your Curse of Knowledge score over time. It should decrease as awareness grows.

### The Buddy System

Pair a domain expert with a non-expert for every major communication project. The expert provides the substance. The non-expert provides the clarity. Neither can do the other's job. Both are essential.

# Emotional: Making People Care

People act on feelings, not facts. Research consistently shows that emotional processing drives decisions, and rational analysis follows to justify them. The Emotional principle is about making your audience feel something — not manipulating them, but connecting your idea to things they already care about. An idea that makes people feel is an idea that moves people to act.

## The Mother Teresa Principle

"If I look at the mass, I will never act. If I look at the one, I will." — Mother Teresa

This is not just a poetic sentiment. It is backed by research. In a landmark study, researchers gave participants one of two charity appeals:

**Version A (Statistics):**
> "Food shortages in Malawi are affecting more than 3 million children. In Zambia, severe rainfall deficits have resulted in a 42% drop in corn production, leaving an estimated 3 million people facing hunger."

**Version B (Individual):**
> "Rokia is a 7-year-old girl from Mali, Africa. She is desperately poor and faces a threat of severe hunger or even starvation. Her life will be changed for the better as a result of your financial gift."

Participants who read Rokia's story donated more than twice as much as those who read the statistics.

### Why Individuals Beat Statistics

| Statistics | Individual Story |
|-----------|-----------------|
| Trigger analytical thinking | Trigger empathy and feeling |
| Feel abstract and distant | Feel personal and immediate |
| Overwhelm ("I can't solve 3 million") | Feel actionable ("I can help Rokia") |
| Activate the rational mind | Activate the emotional mind |
| Create "psychic numbing" — larger numbers = less feeling | Create identification — one face = deep feeling |

### Applying the Mother Teresa Principle

| Instead Of | Use |
|-----------|-----|
| "10,000 businesses use our product" | "Meet David, who runs a 12-person accounting firm in Portland. Last month, he nearly lost his biggest client." |
| "We process millions of transactions" | "When Rosa's payment failed at checkout, our system caught it in 0.3 seconds and re-routed it. She never knew anything happened." |
| "Our customers save an average of 15 hours per week" | "Sarah used to leave the office at 8pm every night. Now she picks up her daughter from school at 3." |

## Self-Interest: WIIFM

"What's In It For Me?" is the most powerful question in communication. Every audience member — consciously or not — is asking it. Your job is to answer it explicitly.

### The WIIFM Ladder

Features tell. Benefits sell. But personal benefits are what truly move people. Most messaging stops at the product benefit level when it should go deeper.

| Level | Example (Project Management Tool) | Emotional Pull |
|-------|-----------------------------------|---------------|
| **Feature** | "Gantt chart view with dependencies" | None |
| **Product benefit** | "See your entire project timeline at a glance" | Mild interest |
| **Personal benefit** | "Stop getting blindsided by missed deadlines" | Relief |
| **Emotional outcome** | "Walk into your status meeting feeling prepared and confident" | Strong motivation |
| **Identity outcome** | "Be the manager who always delivers on time" | Deep motivation |

### Mapping Features to Emotional Outcomes

| Feature | Product Benefit | Personal Benefit | Emotional Outcome |
|---------|----------------|-----------------|-------------------|
| Automated alerts | Know about issues early | Stop firefighting | Sleep through the night |
| Single dashboard | All data in one place | No more tab-switching | Feel in control |
| Team templates | Standardized processes | Less onboarding time | Look like a capable leader |
| Mobile app | Access anywhere | Work from your kid's soccer game | Be present for your family |
| Custom reports | Any metric, any time | Answer the CEO's question instantly | Feel confident in front of leadership |

## Identity Appeal: "What Would Someone Like Me Do?"

People make many decisions based on identity rather than calculation. Instead of asking "What is the cost-benefit analysis?" they ask "What would a person like me do in this situation?"

### The Three Questions of Identity-Based Decision Making

1. **Who am I?** (What group do I belong to?)
2. **What kind of situation is this?** (How do I categorize this decision?)
3. **What would someone like me do in this situation?** (What does my identity prescribe?)

### The "Don't Mess with Texas" Case

The Texas anti-littering campaign is a masterclass in identity appeal. Previous campaigns used guilt ("Please don't litter") and statistics ("Littering costs Texas $X million"). Neither worked on the target demographic: young men aged 18-35.

The solution: Appeal to their identity as Texans. "Don't Mess with Texas" reframed littering as un-Texan behavior. It worked because it answered the identity question: "What would a proud Texan do? Not litter."

### Applying Identity to Product Messaging

| Target Identity | Message Frame | Example |
|----------------|--------------|---------|
| "I'm an innovator" | "For teams that move first" | "Join the companies that adopted AI before their competitors" |
| "I'm a responsible leader" | "For leaders who protect their teams" | "The security tool that means you never have to explain a breach" |
| "I'm data-driven" | "For people who demand evidence" | "Every recommendation comes with the data behind it" |
| "I'm a maker" | "Built by builders, for builders" | "We wrote our first version in a weekend. You'll have yours running in an hour." |
| "I'm a caring professional" | "For people who put customers first" | "The support tool for teams that believe every ticket is a person" |
| "I'm scrappy and resourceful" | "For teams doing more with less" | "Enterprise power at a startup price — no sales calls required" |

## Maslow's Hierarchy Applied to Messaging

Abraham Maslow's hierarchy of needs provides a framework for understanding which emotional level to target. People must satisfy lower needs before they care about higher ones.

| Maslow Level | Need | Messaging Approach | Example |
|-------------|------|-------------------|---------|
| **Physiological** | Survival, basic needs | Appeal to fundamental necessities | "Keep the lights on" (infrastructure reliability) |
| **Safety** | Security, stability | Appeal to risk reduction | "Never lose your data again" |
| **Belonging** | Community, connection | Appeal to group membership | "Join 5,000 teams who have already made the switch" |
| **Esteem** | Recognition, achievement | Appeal to professional reputation | "Be known as the person who transformed your team's workflow" |
| **Self-actualization** | Growth, purpose | Appeal to potential and meaning | "Build the product that changes your industry" |

### Matching Maslow to Your Audience's Current State

| Audience State | Maslow Level | Message Focus |
|---------------|-------------|---------------|
| Startup about to run out of money | Safety | "Reduce your burn rate by $30K/month" |
| Mid-career professional feeling stagnant | Esteem | "Lead the initiative that gets you promoted" |
| Team overwhelmed with technical debt | Safety → Belonging | "Get your weekends back. Your team will thank you." |
| Executive seeking legacy | Self-actualization | "Build the company that outlasts you" |
| New employee wanting to prove themselves | Esteem | "Impress your new team in your first week" |

## The Semantic Stretch Problem

The "semantic stretch" happens when you over-abstract an emotional appeal until it loses all power. It is the opposite of concreteness — and it kills emotional resonance.

### How Semantic Stretch Works

1. Start with a concrete, emotional idea: "Support soldiers recovering from combat injuries"
2. Stretch it: "Support our veterans"
3. Stretch more: "Support our troops"
4. Stretch more: "Support national defense"
5. Stretch too far: "Promote freedom and security"

Each step up the abstraction ladder loses emotional power. "Promote freedom and security" makes no one feel anything. "Support soldiers recovering from combat injuries" makes people feel a specific empathy.

### Semantic Stretch in Product Messaging

| Over-Abstracted (Stretched) | Emotionally Concrete |
|---------------------------|---------------------|
| "Empower your organization" | "Help your team ship the feature they have been stuck on for 3 months" |
| "Transform the customer experience" | "Make sure no customer ever waits on hold for more than 30 seconds" |
| "Drive digital transformation" | "Move that one manual process that drives your team crazy into a 3-click workflow" |
| "Enable growth" | "Help your best salesperson close 4 more deals this quarter" |
| "Optimize business outcomes" | "Stop losing $12,000 every month to invoicing errors" |

## Emotional Appeal by Audience Type

### B2B Audiences

B2B buyers are often assumed to be purely rational. They are not. They fear making bad decisions, want to look competent to their peers, and worry about job security.

| Emotional Need | Message Approach | Example |
|---------------|-----------------|---------|
| **Fear of failure** | Risk mitigation | "No one ever got fired for choosing [Product]" |
| **Career advancement** | Personal impact | "The project that gets you noticed by the C-suite" |
| **Peer validation** | Social proof | "Your competitor already uses this" |
| **Time pressure** | Relief from overwhelm | "Automate the report that eats your Friday afternoons" |
| **Control** | Empowerment | "Finally, a tool where YOU set the rules, not IT" |

### B2C Audiences

B2C messaging can be more directly emotional, but must avoid manipulation.

| Emotional Need | Message Approach | Example |
|---------------|-----------------|---------|
| **Belonging** | Community | "Join 2 million people who start their morning with [Product]" |
| **Self-expression** | Identity | "Show the world who you really are" |
| **Convenience** | Relief | "Dinner, decided. In 30 seconds." |
| **Status** | Aspiration | "The watch worn by people who don't need to check the time" |
| **Joy** | Delight | "The moment you open the box, you will smile" |

### Nonprofit Audiences

Nonprofit messaging lives or dies on emotional appeal — but faces unique challenges around donor fatigue and the Mother Teresa effect.

| Emotional Need | Message Approach | Example |
|---------------|-----------------|---------|
| **Compassion** | Individual story | "This is Ana. She walks 3 miles for water every morning." |
| **Agency** | Clear impact | "Your $25 buys a water filter that lasts Ana's family 5 years." |
| **Community** | Collective identity | "Be one of the 10,000 people who made this possible." |
| **Urgency** | Deadline + consequence | "The rainy season starts in 6 weeks. Without a well, the village floods." |
| **Hope** | Transformation | "Last year, Ana started school for the first time. She wants to be a nurse." |

## Before/After: Adding Emotional Resonance

### Product Landing Page

**Before:**
> "Our platform integrates with 200+ tools and reduces workflow complexity through automated task management and real-time collaboration features."

**After:**
> "Remember the last time you stayed late because three tools would not talk to each other? That was the last time. We connect everything so you can go home on time."

### Sales Pitch Opening

**Before:**
> "Let me tell you about our solution's key differentiators in the competitive landscape."

**After:**
> "I talked to your support lead last week. She told me her team gets 400 tickets a day and they are drowning. I want to show you what 'not drowning' looks like."

### Internal Communication

**Before:**
> "We need to improve our NPS score by 15 points this quarter to meet strategic objectives."

**After:**
> "Last week, a customer named James wrote us a one-star review. He said, 'I wanted to love this product, but you made it impossible.' I want us to make it possible for James — and the 200 other customers who feel the same way."

## Exercises: Finding the Emotional Core

### Exercise 1: The "Why Do You Care?" Chain

Ask "Why do you care about this?" five times, going deeper each time:
1. "We want to increase conversion rates." — Why do you care?
2. "Because we need more revenue." — Why do you care?
3. "Because if we do not grow, we will have to lay people off." — Why do you care?
4. "Because these people trust us and depend on us." — Why do you care?
5. "Because I believe you should fight for the people who fight for you."

That last answer is the emotional core.

### Exercise 2: The Single Person Test

Take your message. Now imagine delivering it to one specific person — a real customer with a real name, face, and story. Does your message change? It should become more personal, more specific, more emotional.

### Exercise 3: The Identity Map

1. Write down 5 identities your target audience holds (professional, personal, aspirational)
2. For each identity, write what that identity demands in this situation
3. Frame your message as consistent with their strongest identity

### Exercise 4: The Emotional Audit

Read your message and mark every word that triggers a feeling. If you have fewer than 3 emotional triggers in a paragraph, rewrite. If you have more than 5, you risk manipulation — dial it back.

## Ethical Boundaries of Emotional Appeal

Emotional appeal is a tool, not a weapon. The line between persuasion and manipulation is intent and truthfulness.

| Persuasion (Ethical) | Manipulation (Unethical) |
|---------------------|------------------------|
| Highlighting real pain your product solves | Inventing or exaggerating pain |
| Sharing genuine customer stories | Fabricating testimonials |
| Creating urgency from real deadlines | Fake countdown timers and false scarcity |
| Appealing to identity aspirations | Shaming people for who they are |
| Using emotion to illuminate truth | Using emotion to hide truth |

### Guidelines for Ethical Emotional Appeal

- [ ] The emotion is grounded in truth — the pain, joy, or aspiration is real
- [ ] The audience would not feel deceived if they saw behind the curtain
- [ ] The emotional appeal leads to a decision that genuinely benefits the audience
- [ ] You would be comfortable if your messaging strategy were made public
- [ ] Individual stories are real or clearly labeled as composite examples
- [ ] Urgency is based on real deadlines, not manufactured pressure
- [ ] You appeal to identity aspirations, never to shame or fear of exclusion

# Simple: Finding the Core of Your Idea

Simplicity is the first and most critical principle in the SUCCESs framework. But simple does not mean dumbed down. It means finding the essential core of an idea and expressing it compactly enough that it is both easy to understand and profoundly useful. The art of simplicity is the art of ruthless prioritization. If you say three things, you say nothing.

## Commander's Intent

The U.S. Army teaches officers to write a "Commander's Intent" (CI) for every mission. It is a plain-language statement of the single most important outcome. If communications break down, if the plan falls apart, every soldier can still make good decisions because they know the CI.

### How Commander's Intent Works

1. A colonel plans a complex mission with dozens of moving parts
2. The plan rarely survives first contact with the enemy
3. But the CI does: "Secure the hilltop by dawn" or "Prevent enemy movement across the bridge"
4. Every decision made by every soldier is filtered through the CI

### Applying Commander's Intent to Your Work

| Context | Commander's Intent Example |
|---------|---------------------------|
| **Startup pitch** | "We make hiring decisions 10x faster" |
| **Product launch** | "Customers can go from signup to first value in under 5 minutes" |
| **Marketing campaign** | "Convince small business owners they are losing money every day they wait" |
| **Internal initiative** | "Reduce support ticket volume by 30% in Q2" |
| **Presentation** | "The audience should leave believing AI will replace their current workflow" |

### Exercise: Finding Your Commander's Intent

Ask yourself these questions in order:

1. If my audience remembers only ONE thing, what must it be?
2. If everything else in my plan fails, what single outcome matters most?
3. Can I say it in one sentence without jargon?
4. Would a new hire understand it on their first day?
5. Does it help people make decisions when I am not in the room?

## The Inverted Pyramid

Journalists have used the inverted pyramid for over a century. The most important information comes first. Every subsequent paragraph adds less critical detail. A reader who stops at any point has still received the core message.

### Structure

```
[CORE MESSAGE — the one thing]
   [Supporting detail #1 — most important context]
      [Supporting detail #2 — helpful but not essential]
         [Supporting detail #3 — nice to have]
            [Background — for the deeply interested]
```

### Why the Inverted Pyramid Works

- People scan, they do not read linearly
- Attention is frontloaded: you have 3-7 seconds
- Mobile screens show only the first 1-2 sentences
- Executives read the first line, not the last

### Before/After: Inverted Pyramid Applied

**Before (buried lead):**
> "After extensive research spanning 18 months across 4 countries, involving 2,300 participants and using a novel AI-based methodology, our team discovered that the average enterprise customer spends 40% of their workday on tasks that could be fully automated."

**After (inverted pyramid):**
> "Your team wastes 40% of their workday on tasks a machine could handle. We proved it across 2,300 employees in 4 countries over 18 months — and we built the tool that fixes it."

## Simplification Techniques

### Analogy

Analogies let you borrow someone else's schema. Instead of explaining your new idea from scratch, you connect it to something the audience already understands.

| New Concept | Analogy | Why It Works |
|-------------|---------|-------------|
| Slack (early days) | "IRC for your company, but friendly" | Technical audience understood IRC |
| Dropbox pitch | "iTunes for your files" | Everyone understood iTunes sync |
| Airbnb | "eBay for physical spaces" | eBay's model was well-known |
| Docker | "Shipping containers for software" | Physical metaphor made abstraction tangible |
| Stripe | "PayPal for developers" | Positioned in a known market with a twist |

**Rules for good analogies:**
- The source concept must be well-known to YOUR audience (not just you)
- The comparison should hold at the structural level, not just surface
- Acknowledge where the analogy breaks down before your audience does

### Generative Metaphor

A generative metaphor is more powerful than a regular analogy because it does not just explain — it generates behavior. It tells people what to do in novel situations.

**Example:** "Names, names, names" — This was the motto of a local newspaper editor. When reporters had to decide whether to cover a story, what angle to take, or what photo to run, the answer was always: prioritize local names. It was generative because it guided thousands of micro-decisions.

| Generative Metaphor | Organization | Decisions It Drives |
|---------------------|-------------|---------------------|
| "THE low-fare airline" | Southwest Airlines | Reject first-class seating, reject assigned seats, reject hub model |
| "Democracy dies in darkness" | Washington Post | Pursue investigative stories, resist access journalism |
| "Don't be evil" | Google (early) | Reject short-term revenue for user trust |
| "Move fast and break things" | Facebook (early) | Ship features before they are polished |

### Prioritization: The Forced Choice

Simplicity requires forced-ranking. If everything is important, nothing is.

**Exercise: The "If you could only..." test**

1. List all the things you want your message to communicate
2. Force yourself to choose ONE
3. Everything else becomes supporting evidence for that one thing

**Example for a project management SaaS:**
- Candidate messages: easy to use, powerful integrations, great reporting, saves time, team collaboration, affordable
- Forced choice: "Saves time"
- Everything else supports it: "Easy to use (saves learning time), great reporting (saves analysis time), integrations (saves switching time)"

## Schema Theory: Using What People Already Know

People do not learn from scratch. They attach new information to existing mental models (schemas). The more you can connect to what your audience already knows, the faster they understand.

### How to Use Schemas

| Strategy | Example |
|----------|---------|
| **Build on existing knowledge** | "It's a CRM, but for recruiting" — CRM is a known schema |
| **Start with the familiar** | "You know how Excel lets you sort data? Now imagine it sorted itself." |
| **Use universally understood concepts** | Time, money, family, health — everyone has schemas for these |
| **Tap into professional schemas** | For developers: "It's like git, but for database migrations" |

### When Schemas Backfire

Schemas can also mislead. If you say "It's the Uber of healthcare," people may import the wrong assumptions (gig workers, surge pricing, regulatory problems). Choose your schema anchor carefully.

## Simple vs. Simplistic

There is a critical difference between simple and simplistic. Simple ideas retain their depth. Simplistic ideas lose it.

| Simplistic (Avoid) | Simple (Aim For) |
|--------------------|-----------------|
| "We help businesses" | "We cut payroll processing from 3 days to 3 hours" |
| "Our product is better" | "Customers switch to us after their second outage with [Competitor]" |
| "We use AI" | "Our AI reads your contracts and flags the clauses that cost you money" |
| "Improve your life" | "Sleep 2 hours more every night" |
| "Innovation platform" | "Test 10 ideas a week instead of 1 a month" |

**The test for simple vs. simplistic:**
- Does it help someone make a decision? (Simple)
- Could it apply to any company in the world? (Simplistic)
- Does it generate specific behavior? (Simple)
- Is it an empty platitude? (Simplistic)

## Before/After Examples

### Product Messaging

**Before:**
> "Our AI-driven, cloud-native platform leverages advanced machine learning algorithms and proprietary NLP models to deliver enterprise-grade content optimization solutions across multiple channels and touchpoints."

**After:**
> "Write an email. Our AI makes it twice as good in 10 seconds."

### Presentation Opening

**Before:**
> "Today I want to walk you through our Q3 strategic roadmap, covering the five key initiatives across product, engineering, marketing, and customer success, including timelines, dependencies, and resource allocation."

**After:**
> "We have one goal this quarter: cut churn in half. Everything I am about to show you exists to achieve that."

### Email Subject Lines

| Before | After |
|--------|-------|
| "Re: Follow-up on our conversation regarding potential partnership opportunities" | "One question about our partnership" |
| "Q3 Performance Review and Strategic Planning Update" | "We grew 40%. Here is how we do it again." |
| "Invitation to participate in beta testing of new feature" | "You are one of 50 people who get to try this first" |

### Healthcare Communication

**Before:**
> "Patients with hyperlipidemia should implement dietary modifications emphasizing reduced saturated fat intake and increased consumption of omega-3 fatty acids."

**After:**
> "Eat less fried food. Eat more fish. Your cholesterol will drop."

### Financial Services

**Before:**
> "Our diversified portfolio optimization strategy employs risk-adjusted return maximization across multiple asset classes."

**After:**
> "We grow your money while you sleep, and we have done it for 20 years straight."

## Exercises for Finding the Core Message

### Exercise 1: The Cocktail Party Test

Imagine you are at a loud cocktail party. Someone asks what your product does. You have one sentence before they get distracted. Write that sentence. Now cut it in half.

### Exercise 2: The Grandparent Test

Explain your product to a grandparent who does not use technology. If you cannot do it, you are relying on jargon and insider knowledge. Rewrite until a non-expert gets it.

### Exercise 3: The Headline Test

Write the newspaper headline for your product. You have 8 words maximum. What makes the front page?

### Exercise 4: The "So What?" Ladder

1. Start with your current message
2. Ask "So what?" — write the answer
3. Ask "So what?" again — write the answer
4. Keep going until you hit something emotionally resonant
5. That is your core message

**Example:**
- "We use AI to analyze sales calls" — So what?
- "Managers see which reps need coaching" — So what?
- "Reps close more deals" — So what?
- "Your team hits quota every quarter" — That is the core.

### Exercise 5: The Forced Tradeoff

List every message you want to communicate. Now imagine you can only afford a billboard (7 words). Which message survives? That is your core.

## Industry-Specific Simplification

| Industry | Typical Complexity | Simplified Core |
|----------|-------------------|----------------|
| **Cybersecurity** | "Zero-trust network architecture with SIEM integration" | "Hackers get in. We make sure they get nothing." |
| **EdTech** | "Adaptive learning platform with personalized curricula" | "Every student gets a private tutor, powered by AI" |
| **FinTech** | "Cross-border payment orchestration layer" | "Send money to 50 countries in 3 seconds" |
| **HealthTech** | "Clinical decision support system leveraging EHR data" | "Doctors get the right diagnosis, faster" |
| **HR Tech** | "Employee experience platform with engagement analytics" | "Know who is about to quit before they do" |
| **DevTools** | "CI/CD pipeline with infrastructure-as-code provisioning" | "Push code. It is live in 60 seconds." |
| **MarTech** | "Omnichannel customer data platform with predictive segmentation" | "Know what your customer wants before they do" |

## Testing Simplicity with Outsiders

The final test for simplicity is not your opinion — it is whether outsiders understand it.

### The 5-Person Test

1. Find 5 people who know nothing about your product
2. Show them your message for 10 seconds
3. Take the message away
4. Ask them to repeat what it said
5. If 4 out of 5 get the core right, you have achieved simplicity

### Red Flags That Your Message Is Not Simple Enough

- [ ] People ask "But what does it actually do?" after reading it
- [ ] You need a follow-up explanation
- [ ] Different people interpret it differently
- [ ] It sounds like it could describe any company in your category
- [ ] You use more than one comma in the core statement
- [ ] It requires industry knowledge to understand
- [ ] You are proud of how clever it sounds (clever is the enemy of clear)

### Simplicity Checklist

Before publishing any message, verify:

- [ ] There is ONE core message, not two or three
- [ ] A smart 12-year-old could understand it
- [ ] It uses concrete language, not abstractions
- [ ] It helps someone make a decision or take action
- [ ] It is compact — every word earns its place
- [ ] It uses analogy or schema to connect to existing knowledge
- [ ] It passes the 5-Person Test
- [ ] It is simple, not simplistic — it retains depth and meaning

# Stories: The Flight Simulator for the Brain

Stories are the oldest technology for transferring knowledge. They predate writing, libraries, and the internet. When we hear a story, our brains simulate the experience as if it were happening to us. Neural coupling research shows that a listener's brain activity mirrors the speaker's brain activity during a well-told story. This makes stories the most powerful vehicle for making ideas stick.


## Table of Contents
1. [Why Stories Work](#why-stories-work)
2. [Three Story Plots](#three-story-plots)
3. [Story Structure for Product Messaging](#story-structure-for-product-messaging)
4. [Spotting Stories in the Wild](#spotting-stories-in-the-wild)
5. [Story Collection Systems](#story-collection-systems)
6. [Story Templates for Different Contexts](#story-templates-for-different-contexts)
7. [Mental Simulation: Stories as Flight Simulators](#mental-simulation-stories-as-flight-simulators)
8. [Stories for Inspiration vs. Stories for Instruction](#stories-for-inspiration-vs-stories-for-instruction)
9. [Before/After: Transforming Facts into Stories](#beforeafter-transforming-facts-into-stories)
10. [Building an Organizational Story Library](#building-an-organizational-story-library)

---

## Why Stories Work

Stories achieve two things that no other communication format can match:

1. **Simulation:** Stories are mental flight simulators. They let people rehearse situations without real-world risk. A customer success story teaches prospects how to evaluate, buy, implement, and succeed — all without lifting a finger.

2. **Inspiration:** Stories move people to act. Not through logic ("you should do this") but through modeling ("look what happened when someone like you did this"). The listener thinks, "If they can do it, maybe I can too."

### Stories vs. Other Formats

| Format | Teaches | Inspires | Remembered | Resisted |
|--------|---------|----------|------------|----------|
| **Bullet points** | Somewhat | Rarely | Poorly | Often |
| **Statistics** | Facts only | Rarely | Poorly | Sometimes |
| **Arguments** | Logic | Sometimes | Moderately | Often |
| **Stories** | Behavior + context | Strongly | Extremely well | Rarely |

People do not argue with stories the way they argue with claims. A claim invites counterargument. A story invites identification.

## Three Story Plots

Research into folk tales, urban legends, and viral narratives reveals that sticky stories overwhelmingly follow one of three plots.

### 1. The Challenge Plot

**Structure:** A protagonist faces a daunting obstacle and overcomes it through perseverance, courage, or ingenuity.

**Emotional response:** Inspiration, courage, determination.

**When to use:** When you want your audience to take a difficult action, push through resistance, or believe that hard things are worth doing.

**Examples:**
- The startup that was rejected by 50 investors before finding one who believed
- The customer who was about to cancel their contract but gave the product one more try — and it changed everything
- The engineer who stayed up for three days straight to fix the bug before the launch

**Template:**
> "[Character] was facing [specific, daunting challenge]. Everyone told them [conventional wisdom]. Instead, they [unexpected action]. It was hard — [specific struggle]. But then [turning point]. Today, [concrete outcome]."

### 2. The Connection Plot

**Structure:** A relationship bridges a gap — between people, groups, cultures, or perspectives.

**Emotional response:** Warmth, empathy, belonging, trust.

**When to use:** When you want to build community, foster collaboration, or show that your product connects people.

**Examples:**
- The customer who used the product's collaboration feature to help a competitor (and both benefited)
- The remote team that felt disconnected until they found a tool that recreated the feeling of being in the same room
- The support agent who went above and beyond for a customer and turned a detractor into an advocate

**Template:**
> "[Person A] and [Person B] seemed to have nothing in common. [Person A] was [context]. [Person B] was [different context]. But when [connecting event], something unexpected happened: [outcome that bridged the gap]. Now, [ongoing result]."

### 3. The Creativity Plot

**Structure:** Someone discovers an innovative solution to a problem, often by looking at it from a completely new angle.

**Emotional response:** Excitement, curiosity, a desire to innovate.

**When to use:** When you want to demonstrate novel thinking, encourage experimentation, or show how a new approach changes everything.

**Examples:**
- The team that solved a billion-dollar problem by asking a question no one had asked before
- The customer who used the product in a way the developers never imagined
- The company that turned a limitation into their biggest competitive advantage

**Template:**
> "For years, everyone in [industry] assumed [common approach]. [Character] tried a different approach: [novel idea]. At first, people were skeptical. But [specific evidence of it working]. It turned out that [insight]. Now, [new reality]."

## Story Structure for Product Messaging

Every product story should follow this five-part arc. Each part serves a specific purpose.

### The Five-Part Product Story Arc

```
Character → Problem → Journey → Solution → Outcome
```

| Part | Purpose | What to Include | Length |
|------|---------|----------------|--------|
| **Character** | Create identification | Name, role, company size, relatable detail | 1-2 sentences |
| **Problem** | Create tension | Specific pain, failed attempts, stakes | 2-3 sentences |
| **Journey** | Build anticipation | What they tried, why it failed, moment of discovery | 2-4 sentences |
| **Solution** | Demonstrate value | How the product helped (specific, concrete) | 2-3 sentences |
| **Outcome** | Deliver payoff | Measurable results + emotional transformation | 2-3 sentences |

### Example: Complete Product Story

**Character:**
> "Maria runs a 15-person customer success team at a mid-size SaaS company. She cares deeply about her team and her customers."

**Problem:**
> "Last year, three of her best reps quit within two months. Exit interviews revealed the same thing: they were drowning in manual reporting. Every week, each rep spent 6 hours pulling data from four different tools, copying it into spreadsheets, and writing updates. Maria knew it was killing morale, but she had no budget for a new tool."

**Journey:**
> "She tried building a Google Sheets automation. It broke every other week. She asked engineering for help — they had a 6-month backlog. She even considered hiring a part-time data analyst, but the math did not work. Then her VP of Sales mentioned a tool his team had been piloting."

**Solution:**
> "Maria signed up for a free trial on a Tuesday afternoon. By Thursday, the tool was pulling data from all four sources automatically. Each rep got a personalized dashboard that updated in real time. The weekly report that took 6 hours now generated itself in 3 minutes."

**Outcome:**
> "Six months later, Maria's team had zero voluntary turnover. Rep satisfaction scores went from 3.2 to 4.7 out of 5. But the moment Maria remembers most is when one of her reps said, 'I finally have time to actually talk to my customers.' That is when she knew it worked."

## Spotting Stories in the Wild

The best product stories already exist — you just need to find them. They are hiding in places you probably do not check.

### Where to Find Stories

| Source | What to Look For | Example Story Seed |
|--------|-----------------|-------------------|
| **Support tickets** | Emotional language, grateful responses, unusual use cases | "Thank you SO MUCH. I was about to get fired because of this problem." |
| **Sales calls** | Objections overcome, aha moments, competitor comparisons | "The moment they saw the demo, the CFO leaned forward and said, 'Wait, show me that again.'" |
| **User interviews** | Before/after descriptions, workarounds, emotional reactions | "Before this, I was using 3 spreadsheets and a prayer." |
| **NPS comments** | Extreme scores (9-10 or 0-3) with written explanations | "I recommended this to my entire network. Not because you asked, but because I felt I owed it to them." |
| **Customer reviews** | Unsolicited praise or criticism with specific details | "I almost did not sign up because of the pricing page. So glad I did." |
| **Internal Slack** | Team celebrations, customer wins, problem resolutions | "Just got off the phone with a customer who said we saved their quarter." |
| **Social media** | Organic mentions, screenshots, threads | "Okay I need to talk about this tool because it changed my entire workflow." |

### Story Signals to Watch For

Listen for these phrases — they are the beginning of a story:

- "You will not believe what happened..."
- "I almost gave up, but then..."
- "The moment I realized..."
- "I was so frustrated that I..."
- "Nobody thought it was possible, but..."
- "Here is what I did not expect..."

## Story Collection Systems

Stories are perishable. If you do not capture them, they disappear. Build a system.

### The Story Bank

Create a shared document or database where anyone in the organization can submit stories.

**Fields for each story:**

| Field | Description |
|-------|-------------|
| **Date captured** | When the story was discovered |
| **Source** | Support ticket, sales call, interview, etc. |
| **Character** | Who is the protagonist? (name, role, company) |
| **Problem** | What challenge were they facing? |
| **Journey** | What did they try before finding us? |
| **Solution** | How did our product help specifically? |
| **Outcome** | What measurable and emotional results did they achieve? |
| **Plot type** | Challenge, Connection, or Creativity |
| **Quote** | One verbatim quote from the customer |
| **Permission** | Can we use this publicly? (Y/N) |
| **Tags** | Industry, use case, feature, persona |

### Making Story Collection a Habit

| Role | Story Collection Action | Frequency |
|------|------------------------|-----------|
| **Support team** | Flag tickets with emotional language or unusual outcomes | Daily |
| **Sales team** | Record the "aha moment" from every demo or call | After each call |
| **Customer success** | Capture before/after moments during check-ins | Monthly |
| **Product team** | Note unexpected use cases from analytics or feedback | Weekly |
| **Marketing** | Monitor social mentions and review sites for organic stories | Weekly |

## Story Templates for Different Contexts

### Case Study Template (800-1200 words)

```
1. Headline: [Outcome] — How [Company] [achieved result]
2. Summary: 2-3 sentence overview
3. The Challenge: What problem did they face? (3-4 paragraphs)
4. The Solution: How did they implement our product? (2-3 paragraphs)
5. The Results: Specific metrics + emotional impact (2-3 paragraphs)
6. Key Quote: One powerful customer quote
7. Call to Action: Invite the reader to try it themselves
```

### Demo Story Script (3-5 minutes)

```
"Let me show you what [real customer] experienced.
They were dealing with [specific problem].
Watch what happens when [demonstrate feature].
See that? [Point out the transformation].
[Customer name] told us this saved them [specific outcome].
Now let me show you how this would work with YOUR data..."
```

### Presentation Story (2-3 minutes)

```
"I want to tell you about [Name].
[One sentence about who they are — relatable detail].
[Name] had a problem: [specific, vivid description].
They tried [what they tried first]. It did not work because [reason].
Then [turning point — discovery of your product/idea].
The result? [Concrete, measurable outcome].
But here is what [Name] said that stuck with me: '[emotional quote]'.
That is what this is about."
```

### Email Story (3-4 sentences)

```
"Quick story: [Name] at [Company] was [specific problem].
After switching to [Product], [specific result in a number].
Their words: '[short quote]'.
[CTA: Want similar results?]"
```

## Mental Simulation: Stories as Flight Simulators

Stories do not just inform — they train. When an audience hears a well-constructed story, they mentally rehearse the decisions, actions, and outcomes. This is why:

- Medical students learn from case studies, not just textbooks
- Pilots train in simulators before they fly
- Firefighters share stories around the firehouse

### How to Maximize the Simulation Effect

1. **Include decision points:** Show where the character had to choose, so the listener rehearses choosing
2. **Include obstacles:** Show what went wrong, so the listener rehearses problem-solving
3. **Include sensory details:** The more vivid the story, the more realistic the simulation
4. **Include the "how":** Do not skip the implementation steps — those are what the listener needs to rehearse

## Stories for Inspiration vs. Stories for Instruction

| Inspiration Stories | Instruction Stories |
|--------------------|--------------------|
| Focus on the outcome and the emotion | Focus on the process and the steps |
| "They achieved the impossible" | "Here is exactly how they did it" |
| Best for: keynotes, campaigns, brand | Best for: onboarding, documentation, training |
| Plot: Challenge or Connection | Plot: Creativity or Challenge (with detail) |
| Emotional payoff: "I want that too" | Practical payoff: "Now I know how to do it" |

Use inspiration stories to motivate. Use instruction stories to enable.

## Before/After: Transforming Facts into Stories

### Product Feature Announcement

**Before (Facts):**
> "New feature: automated invoice reconciliation. Matches invoices to purchase orders using AI. Reduces manual work. Available now."

**After (Story):**
> "Last month, we watched Priya from CloudSync spend 3 hours every Friday matching invoices to purchase orders by hand. Forty-seven invoices, each compared line-by-line to a spreadsheet. So we built something. Today, Priya clicks one button and the AI matches all 47 invoices in under a minute. Last Friday, Priya left the office at 2pm. Automated invoice reconciliation is available now."

### Quarterly Business Review

**Before (Facts):**
> "Q3 results: 15% revenue growth, 200 new customers, NPS increased from 42 to 51."

**After (Story):**
> "At the start of Q3, we had a problem. Our biggest customer told us they were evaluating competitors. Their exact words: 'We love your product, but your onboarding is killing us.' So we rebuilt onboarding from scratch. That customer not only stayed — they upgraded. And they were not the only ones. 200 new customers joined this quarter. Revenue grew 15%. NPS jumped from 42 to 51. But the number I care about most is this: zero customers left because of onboarding."

## Building an Organizational Story Library

A story library is a curated, searchable collection of stories organized for easy retrieval in any context.

### Story Library Structure

| Category | Subcategory | Example Stories to Collect |
|----------|-------------|---------------------------|
| **Origin** | Founding, mission, pivots | Why we started, the first customer, the pivot that saved us |
| **Customer** | By persona, industry, use case | One story per persona per industry if possible |
| **Product** | By feature, by problem solved | How each major feature changed a specific customer's life |
| **Team** | Culture, values in action | Moments when the team lived the company values |
| **Failure** | Lessons learned, comebacks | Mistakes we made and what we learned |
| **Vision** | Where we are going, why it matters | Stories that illustrate the future we are building |

### Maintaining the Library

- **Review quarterly:** Remove outdated stories, add fresh ones
- **Tag everything:** Industry, persona, feature, plot type, emotional tone
- **Rate for impact:** Which stories get the strongest audience reactions?
- **Get permission:** Always confirm that customers are comfortable being named
- **Keep it accessible:** Every customer-facing team member should be able to find the right story in under 2 minutes

### Story Quality Checklist

Before adding a story to your library:

- [ ] There is a named, relatable character (not "a company")
- [ ] The problem is specific and vivid (not "they had challenges")
- [ ] Failed attempts are included (builds tension and credibility)
- [ ] The solution involves your product naturally (not forced)
- [ ] The outcome includes both a number and an emotion
- [ ] At least one direct quote from the customer is included
- [ ] The story follows one of the three plots (Challenge, Connection, Creativity)
- [ ] It can be told in under 3 minutes for verbal contexts
- [ ] You have explicit permission to use it
- [ ] It is less than 6 months old (or timeless in nature)

# Unexpected: Breaking Patterns and Creating Curiosity

The Unexpected principle serves two distinct purposes: getting attention and holding it. Surprise breaks through the noise and grabs attention. Curiosity gaps sustain it long enough for your message to land. Without the unexpected, your message is wallpaper — present but invisible.

## The Two Tasks of Unexpectedness

| Task | Mechanism | Duration | Goal |
|------|-----------|----------|------|
| **Get attention** | Surprise | Instant (seconds) | Break the pattern, interrupt autopilot |
| **Hold attention** | Curiosity | Sustained (minutes to hours) | Keep them engaged until the payoff |

Both are necessary. Surprise without curiosity is a firecracker — loud but forgotten. Curiosity without surprise never gets the chance to work because no one is paying attention in the first place.

## Getting Attention: Pattern-Breaking Surprise

The human brain runs on patterns. We predict what comes next based on what came before. When a prediction fails, we pay attention. That is surprise.

### How Surprise Works

1. **Your audience has an expectation** (a mental pattern or schema)
2. **You violate that expectation** (something does not fit the pattern)
3. **The brain flags the violation** (surprise = involuntary attention)
4. **You resolve the surprise** by connecting it back to your core message

### The Critical Step Most People Miss

Surprise alone is not sticky. The surprise must serve the core message. A dancing monkey in your presentation gets attention but teaches nothing. The resolution of the surprise — the "aha" moment — is where stickiness happens.

### Surprise Mechanics: A Three-Step Process

**Step 1: Identify your core message**
What is the one thing you need the audience to understand or believe?

**Step 2: Find the counterintuitive aspect**
What is surprising, unexpected, or non-obvious about your core message? Where does common sense get it wrong?

**Step 3: Communicate the surprise**
Lead with the pattern violation. Then resolve it with your core message.

### Examples of the Three-Step Process

| Core Message | Counterintuitive Aspect | Surprise Communication |
|-------------|------------------------|----------------------|
| Movie popcorn is unhealthy | People think popcorn is a light snack | "Your bag of movie popcorn has more saturated fat than a bacon-and-eggs breakfast, a Big Mac with fries, AND a steak dinner — combined." |
| Our product saves time | People assume setup takes forever | "Most tools promise to save time after weeks of setup. Ours saves time during setup." |
| Customer support matters | Companies invest in acquisition, not retention | "You spend $50 to acquire a customer and $0 to keep them. We flip that math." |
| Simplicity wins | People equate features with value | "We removed 60% of our features. Revenue went up 40%." |

## Holding Attention: Curiosity Gaps

Curiosity is the intellectual need to close an open gap in knowledge. Psychologist George Loewenstein identified this as the "information gap" theory of curiosity: when we perceive a gap between what we know and what we want to know, we feel a strong urge to close it.

### The Gap Theory of Curiosity (George Loewenstein)

Loewenstein's research established four key principles:

1. **Curiosity arises from a gap in knowledge** — not from a complete absence of knowledge. You need to know something to realize what you do not know.
2. **The gap must feel closeable** — if the answer seems unknowable, curiosity dies. If it seems within reach, curiosity intensifies.
3. **Curiosity is aversive** — it is a form of intellectual discomfort. People are motivated to close the gap to relieve the discomfort.
4. **Curiosity increases as you get closer to the answer** — partial information fuels more curiosity, not less.

### Practical Implication

Before you can create a curiosity gap, you must first ensure your audience has enough context to realize something is missing. This is why good teachers provide context before asking a question, and why mystery novels give you clues before the reveal.

### Techniques for Creating Curiosity Gaps

#### 1. Questions

Ask a question your audience cannot immediately answer but desperately wants to.

| Weak Question (No Gap) | Strong Question (Creates Gap) |
|------------------------|------------------------------|
| "Want to save money?" | "What is the one expense you pay every month that you could eliminate today?" |
| "Is your team productive?" | "How many hours per week does your best engineer spend NOT coding?" |
| "Do you want more customers?" | "Why did 73% of your trial users quit on day 3?" |

#### 2. Predictions

Ask the audience to predict an outcome before revealing it. Their commitment to their prediction makes them hungry for the answer.

**Examples:**
- "Before I show you the results, guess what percentage of users completed onboarding. Write it down."
- "How long do you think it takes the average customer to see ROI with our product? Most people guess 3 months."
- "What do you think is the number one reason deals stall in your pipeline?"

#### 3. Mysteries

Present an unexplained phenomenon and delay the explanation.

**Examples:**
- "In 2019, a small SaaS company with 4 employees beat Salesforce in 3 enterprise deals. Here is how."
- "Nordstrom once gave a customer a full refund for a set of tires. Nordstrom does not sell tires. Why would they do that?"
- "One email subject line generated a 94% open rate. It had only two words."

#### 4. Challenges to Assumptions

State something your audience believes, then reveal it is wrong.

**Examples:**
- "You have been told content is king. It is not. Distribution is."
- "Everyone says you need product-market fit first. The most successful founders we studied did something else."
- "The best-performing landing page in our test had no hero image, no testimonials, and no CTA button above the fold."

## Before/After: Adding Unexpectedness

### Product Launch Announcement

**Before (Expected):**
> "We are excited to announce our new analytics dashboard with real-time insights, custom reports, and team collaboration features."

**After (Unexpected):**
> "Most analytics dashboards create more questions than answers. So we built one that only shows you the three numbers that matter for your business today."

### Conference Presentation Opening

**Before (Expected):**
> "Good morning. Today I will be talking about the future of AI in healthcare. I have 30 slides to share."

**After (Unexpected):**
> "Last year, an AI diagnosed a rare disease in 12 seconds. The patient had seen 7 doctors over 3 years. None of them caught it. Let me tell you that story."

### Sales Email

**Before (Expected):**
> "Hi [Name], I wanted to reach out to introduce our platform that helps companies improve their sales process."

**After (Unexpected):**
> "Hi [Name], your last three job postings all mention 'data-driven sales culture.' But I noticed your team is still using spreadsheets to forecast. There is a disconnect — and it is costing you about $200K a year."

### Pricing Page

**Before (Expected):**
> "Choose the plan that is right for you. Basic: $29/mo. Pro: $99/mo. Enterprise: Contact us."

**After (Unexpected):**
> "83% of our customers choose Pro. But 40% of them do not need it. Take our 2-minute quiz to find out which plan actually fits — we would rather you save money and stay for years."

### Onboarding Welcome Screen

**Before (Expected):**
> "Welcome to [Product]! Let us get you set up. Click 'Next' to begin."

**After (Unexpected):**
> "In the next 3 minutes, you are going to see something that took your team 3 hours last week happen automatically. Ready?"

## Surprise in Different Contexts

### Product Launches

| Technique | Example |
|-----------|---------|
| **Reveal a hidden cost** | "You are spending $4,000/month on a tool your team uses for 2 features. Here are those 2 features, free." |
| **Contradict best practices** | "We broke every rule of SaaS pricing. Here is why it works." |
| **Show an extreme outcome** | "One customer saved $2.4 million in their first year. They almost did not sign up." |

### Presentations and Pitches

| Technique | Example |
|-----------|---------|
| **Open with the end** | "By the end of this demo, you will have canceled a meeting on your calendar. Let me show you why." |
| **Start with failure** | "Our first version was terrible. Customers hated it. That is the most important thing I can tell you about our product today." |
| **Use a prop or demo** | "This USB stick contains every customer complaint from last quarter. Watch what happens when I plug it in." |

### Marketing Campaigns

| Technique | Example |
|-----------|---------|
| **Reframe the problem** | "You do not have a lead generation problem. You have a lead quality problem." |
| **Use specificity** | "This ad was written by AI in 4.7 seconds. Can you tell?" |
| **Reverse the pitch** | "5 reasons you should NOT buy our product" (filter for ideal customers) |

## Anti-Patterns: When Surprise Goes Wrong

### Gimmicky Surprise Without Substance

The surprise must connect to your core message. If it does not, you get attention but waste it.

| Gimmicky (Avoid) | Substantive (Aim For) |
|-------------------|----------------------|
| Clickbait headline with unrelated content | Headline that surprises AND delivers |
| Shock value for its own sake | Unexpected truth that changes perspective |
| "You won't believe what happened next" | "Here is why the obvious answer is wrong" |
| Random humor unrelated to the message | Humor that illuminates the core insight |

### Other Anti-Patterns

- **The bait-and-switch:** Promising one thing, delivering another. Destroys trust.
- **The false mystery:** Creating a curiosity gap with a disappointing payoff. Worse than no gap at all.
- **The overused surprise:** "Everything you know about X is wrong" only works if you actually deliver a genuine insight.
- **The unresolved surprise:** Getting attention but never connecting it back to your core message.

## Exercises for Finding the Unexpected Angle

### Exercise 1: The "Common Sense" Audit

1. Write down the five things everyone in your industry "knows to be true"
2. For each one, find evidence that it is wrong, incomplete, or misleading
3. The strongest counterpoint is your unexpected angle

### Exercise 2: The Prediction Game

1. Present your key statistic or finding to 10 people
2. But first, ask them to predict the answer
3. The statistics where predictions are furthest from reality are your most surprising points

### Exercise 3: The "What If" Flip

Take your core message and flip every assumption:
- "Our product is fast" becomes "What if speed is the wrong metric?"
- "We save you money" becomes "What if your biggest cost is not money but attention?"
- "We are the market leader" becomes "What if being the leader is the problem?"

### Exercise 4: The News Reporter Test

If a journalist were writing about your product, what angle would make it newsworthy? News is inherently about the unexpected. If you cannot find a news angle, you have not found the surprise yet.

### Exercise 5: The Outsider Perspective

Show your message to someone outside your industry. Ask them what surprises them about it. Often, what feels obvious to insiders is genuinely surprising to outsiders — and that surprise is the angle you should lead with.

## Curiosity Gap Checklist

Before finalizing any message, verify:

- [ ] There is a genuine surprise that connects to the core message
- [ ] The surprise violates a specific expectation (not just generic "wow")
- [ ] A curiosity gap is opened early and resolved with a satisfying payoff
- [ ] The audience has enough context to feel the gap (not too much, not too little)
- [ ] The unexpected element is not gimmicky — it deepens understanding
- [ ] The payoff delivers on the promise of the surprise
- [ ] You have tested it on at least one person who did not see it coming

## The Unexpectedness Spectrum

Not all surprise is equal. Use this spectrum to calibrate:

| Level | Type | Effect | Risk |
|-------|------|--------|------|
| 1 | **Mild twist** | "Huh, I did not know that" | Low impact but safe |
| 2 | **Reframe** | "I never thought about it that way" | High impact, moderate risk |
| 3 | **Counterintuitive** | "Wait, that goes against everything I believed" | Very high impact, requires strong evidence |
| 4 | **Paradigm shift** | "This changes everything" | Transformative but hard to achieve |

Aim for Level 2-3 in most product messaging. Level 1 is forgettable. Level 4 requires extraordinary proof.