made-to-stick

Imported from wondelai/skills (made-to-stick/SKILL.md) via skills.sh. Install upstream with npx skills add wondelai/skills --skill made-to-stick. Copyright stays with the author (MIT).

Made to Stick Framework

A framework for crafting ideas and messages that are understood, remembered, and drive lasting action. Based on decades of research into why some ideas survive and others die.

Core Principle

The Curse of Knowledge is the single greatest barrier to effective communication. Once we know something, we can't imagine not knowing it—which makes us bad at explaining our ideas to others. Sticky ideas aren't born, they're made: the SUCCESs framework provides six principles that make any idea more memorable and impactful.

Scoring

Goal: 10/10. Score any messaging (copy, presentations, campaigns, onboarding) by running the Quick Diagnostic: rate each of the six traits 1-10, then map the 6-60 total to a band (50-60 = 9-10, extremely sticky; 35-49 = 7-8, strong; 20-34 = 4-6, forgettable; below 20 = ≤3, won't stick). Always state the current score, which traits scored lowest, and the specific fix from the diagnostic's Fix column.

The SUCCESs Framework

Simple · Unexpected · Concrete · Credible · Emotional · Stories

Not a checklist—a toolkit. Not every sticky idea uses all six, but the stickiest ideas tend to use most of them—don't force all six onto a message that only needs two.

1. Simple

Core concept: Find the core of the idea and share it compactly. Simple ≠ dumbed down—it means ruthless prioritization: "if you say three things, you say nothing."

The Commander's Intent: if everything else goes wrong, what ONE thing must we accomplish? For messaging: if people remember ONE thing about your product, what should it be? The inverted pyramid: lead with the most important thing; readers who stop anywhere still got the core.

Techniques for simplicity:

Application to product messaging:

The test: Can you explain it to a smart 12-year-old? Warning: don't simplify into emptiness—"we make the world better" is simple but meaningless.

See references/simple.md when you can't reduce a message to one core idea—it has the Commander's Intent exercise, the inverted-pyramid pattern, and five "find the core" drills.

2. Unexpected

Core concept: Get attention by breaking patterns (surprise); hold attention by creating curiosity gaps (interest). The surprise must connect to the core message—identify the counterintuitive implication and communicate that.

Example surprises:

Creating curiosity gaps — open a gap in knowledge, create the desire to fill it:

Anti-pattern: Gimmicky surprise without substance.

See references/unexpected.md when a message reads as predictable—it has techniques for finding the counterintuitive angle and engineering curiosity gaps.

3. Concrete

Core concept: Use sensory language and specific details instead of abstract concepts. Abstraction kills memorability; the more concrete and specific the idea, the stickier it becomes.

Abstract vs. Concrete:

The Velcro theory of memory: concrete ideas have more "hooks"—"bicycle" is easier to remember than "vehicle" because you can picture it.

Techniques for concreteness:

Application: features → outcomes; percentages → real numbers ("saves 40%" → "saves 16 hours/month"); categories → specific examples ("restaurants" → "pizza shops in Brooklyn"); demos > feature lists.

See references/concrete.md when a message stays abstract—it has sensory-language drills and the abstract-to-concrete conversion process.

4. Credible

Core concept: Help people believe your idea using external credibility (authorities, credentials) and internal credibility (vivid details, human-scale statistics, testable claims)—internal is more powerful.

External credibility:

Internal credibility:

The Sinatra Test: one reference so impressive it handles all objections—"We secured the White House" (security), "We handle Super Bowl traffic" (scalability), "Used by Apple, Google, and Microsoft" (quality).

Making statistics stick: put them in a context people understand—not "37 grams of saturated fat" but "more saturated fat than a Big Mac, fries, and milkshake combined."

See references/credible.md when a claim sounds unbelievable—it has authority types, the Sinatra Test, and methods for making statistics human-scale.

5. Emotional

Core concept: Make people feel something—people act on emotion, not analysis. Statistics numb; stories about individuals inspire action. Mother Teresa principle: "If I look at the mass, I will never act. If I look at the one, I will."

Emotional appeals:

The identity approach: people decide based on identity, not calculation—frame your product as consistent with who they want to be:

Avoid the "semantic stretch": don't over-abstract the emotion—"Support the troops" beats "Support our national defense infrastructure."

See references/emotional.md when a message is all logic and no feeling—it has the individual-focus, identity, and self-interest appeal frameworks.

6. Stories

Core concept: Stories are flight simulators for the brain: they simulate experience, inspire action, stay memorable through narrative structure, and bypass resistance (people don't argue with stories).

Three story plots that work:

Story structure for product messaging: character (relatable customer) → problem (emotional) → journey (what they tried, concrete) → solution (how your product helped, specific) → outcome (measurable + emotional).

Example:

"Sarah ran a 10-person design agency. Her team spent 4 hours every Friday compiling client reports from 5 different tools. She'd tried hiring an intern, building spreadsheets, even a custom tool. Nothing worked. Then she found [Product]. Now reports generate in 10 minutes. Last Friday, her team left at 3pm for the first time in years."

Spotting stories in the wild: support tickets (problems + resolutions), sales calls (objections + breakthroughs), user interviews (before/after moments), internal Slack (team wins).

See references/stories.md when you need to build a narrative—it has the three story plots, the product-story structure, and methods for collecting real stories.

The Curse of Knowledge

How it manifests: jargon your audience doesn't know; skipping context that seems "obvious"; assuming your audience sees what you see; over-abstracting because you know the specifics.

Solutions: test messaging with outsiders (not your team); use concrete language, not abstractions; tell stories, not bullet points; ask "would my mom understand this?"

See references/curse-of-knowledge.md when your own message reads clearly but lands flat on others—it has diagnosis and remedies for shared-context blind spots.

Applying SUCCESs to Product

Landing Pages

• Simple: one clear value proposition above the fold
• Unexpected: counterintuitive claim or statistic
• Concrete: specific outcome ("save 4 hours/week" not "save time")
• Credible: customer logos, specific testimonials
• Emotional + Stories: customer pain point and transformation narrative

Product Demos

• Simple: show ONE core workflow, not every feature
• Unexpected: start with the "aha moment", not a tour
• Concrete: use real data, not "Lorem ipsum"
• Credible: show how [specific company] uses it
• Emotional + Stories: "Let me show you what happens when [customer] has this problem..."

Onboarding

• Simple: one action per screen
• Unexpected: delight with a quick win early
• Concrete: show real results, not abstract promises
• Credible: "Join 5,000 teams already using..."
• Emotional + Stories: celebrate first success; "here's how [user] got started..."

See references/applications.md when applying SUCCESs to a specific format—it has element-by-element tables, fill-in templates, and before/after examples for landing pages, demos, onboarding, presentations, email campaigns, internal comms, and documentation. See references/case-studies.md for full worked teardowns (JFK's moonshot, the Subway diet, Don't Mess with Texas) when you want to see all six traits operating together in a famous message.

Common Mistakes

Quick Diagnostic

The single scoring instrument. Score each trait 1-10, fix the lowest, then re-score:

Sum the six scores and band per Scoring above.

Further Reading

For the complete framework and research:

• "Made to Stick" by Chip Heath & Dan Heath
• "Switch" by Chip Heath & Dan Heath (companion: how to make change stick)

About the Authors

Chip Heath is a professor at Stanford Graduate School of Business, and Dan Heath is a senior fellow at Duke University's CASE center. Together they have written four New York Times bestsellers; Made to Stick spent over two years on the list, and its SUCCESs framework is used by educators, marketers, nonprofits, and product teams worldwide.