Hung Quoc To

---
name: mnemonic-device-selector-and-builder
description: Build a complete mnemonic device or memory palace for anything the user needs to memorize, recall, or remember. Use this skill whenever someone wants to memorize a list, sequence, set of terms, vocabulary, historical dates, medical facts, or any body of material they struggle to recall. Activates on requests like "help me remember", "I can't recall", "memorize this", "make a mnemonic", "build a memory palace", "use method of loci", "create a flashcard structure", "remember in order", "recall under pressure", or "stop forgetting." Covers simple devices (acronyms, peg method, chunking, rhyme schemes) and complex devices (memory palace, method of loci, location-based recall). Does NOT teach the underlying subject matter — the learner must understand the content first; this skill organizes it for retrieval.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/make-it-stick/skills/mnemonic-device-selector-and-builder
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: draft
source-books:
  - id: make-it-stick
    title: "Make It Stick: The Science of Successful Learning"
    authors: ["Peter C. Brown", "Henry L. Roediger III", "Mark A. McDaniel"]
    chapters: [7, 8]
tags: ["learning-science", "cognitive-psychology", "evidence-based-learning", "memory-techniques", "mnemonics", "method-of-loci"]
depends-on: []
execution:
  tier: 1
  mode: hybrid
  inputs:
    - type: text
      description: "The material to memorize: a list, sequence, set of terms, body of concepts, or any content the user needs to retrieve reliably"
  tools-required: [Read, Write]
  tools-optional: []
  mcps-required: []
  environment: "Any agent environment with conversational output capability."
discovery:
  goal: "Select the right mnemonic type for the material and build a complete, ready-to-use memory device — not a template, but an actual constructed device the user can practice immediately."
  tasks:
    - "Gather what the user needs to memorize: type, volume, order sensitivity, and recall context"
    - "Select mnemonic tier (simple vs. complex) using decision criteria"
    - "For simple material: construct acronym, peg associations, or chunking scheme"
    - "For complex material: build a memory palace with location assignments and vivid image anchors"
    - "Deliver completed device with a 3-session rehearsal schedule"
  audience: ["students", "professionals", "lifelong learners", "educators", "anyone preparing for high-stakes recall"]
  triggers:
    - "Help me memorize this list"
    - "I keep forgetting these terms"
    - "Build a memory palace for this content"
    - "Create a mnemonic for me"
    - "I need to remember this in order"
    - "Use method of loci to help me recall this"
    - "How do I stop forgetting what I study?"
  not_for:
    - "Teaching or explaining the subject matter itself (the user must understand it first)"
    - "Building automated flashcard software"
    - "Creating study schedules (use retrieval-practice-study-system)"
  environment: "Conversational or document-based: lists, notes, vocabulary sets, sequence data, concept outlines"
  quality:
    completeness_score:
    accuracy_score:
    value_delta_score:
---

# Mnemonic Device Selector and Builder

## When to Use

You have material you understand but cannot reliably retrieve when needed. Mnemonic devices are not shortcuts around learning — James Paterson, the Welshman who became a competitive memory athlete, discovered this the hard way: he memorized names and dates for his psychology exams using mnemonics but "didn't have mastery of the concepts, relationships, and underlying principles. He had the mountaintops but not the mountain range." Mnemonics are retrieval infrastructure, not comprehension. Use this skill *after* the user already understands the material.

Typical situations where this skill applies:

- Memorizing a list, sequence, or set of terms under time pressure (exam, presentation, certification)
- Needing to retrieve structured knowledge in a specific order (procedure steps, ranked items, historical sequences)
- Managing high-volume material across multiple topics (medical content, legal codes, multi-part exam essays)
- Preparing to recall knowledge under performance stress (exam hall, job interview, live presentation)

**Mode: Hybrid** — The agent builds the complete mnemonic device. The human practices it through spaced retrieval sessions.

---

## Step 1: Gather What Needs to Be Memorized

**Why:** The mnemonic type must fit the material's structure. The wrong device wastes effort — using a memory palace for five items is overkill; using an acronym for thirty interconnected concepts fails under exam pressure.

Collect:

- **The material itself.** Ask the user to list or paste what must be memorized. If they reference a document, read it.
- **Volume:** How many items, concepts, or sequences? (rough count)
- **Order sensitivity:** Must items be recalled in a specific order, or can they be retrieved in any sequence?
- **Recall context:** Where and when will this be retrieved? (exam hall, live conversation, procedural performance, casual recall)
- **Time to practice:** How many days before the recall event?

If the user has not yet fully understood the material, flag this before proceeding:

> "Mnemonic devices organize what you already know for fast retrieval — they don't replace understanding. If you haven't worked through this material yet, do that first, then come back here to build the retrieval structure."

---

## Step 2: Select Mnemonic Type

**Why:** Simple devices are faster to build and sufficient for small, discrete sets. Complex devices (memory palace) require more construction time but scale to large volumes and high-pressure sequential recall.

### Tier 1 — Simple Devices

Use when **all** of the following are true:
- 10 items or fewer
- Order is not critical, or the sequence is short and linear
- Items are discrete (words, numbers, names, labels) rather than concept-clusters
- Recall context is low-stakes or the device only needs to survive a short time

| Device | Best For | Example |
|--------|----------|---------|
| **Acronym** | Short lists, unordered sets, terms with clear initial letters | ROY G BIV → colors of the rainbow; HOMES → the Great Lakes |
| **Reverse acronym (acrostic)** | Lists where initials don't spell a word | "I Value Xylophones Like Cows Dig Milk" → Roman numeral values (I, V, X, L, C, D, M) |
| **Peg method** | Ordered lists up to 20 items | 1=bun, 2=shoe, 3=tree... each peg holds a vivid image of the item to remember |
| **Chunking** | Long strings of digits or symbols | Phone number 6153926113335 → 615-392-611-3335 (shorter working memory loads) |
| **Rhyme or song structure** | Sequences where rhythm aids recall | Musical phrase → lyrics → encoded image for each segment |

### Tier 2 — Memory Palace (Method of Loci)

Use when **any** of the following are true:
- More than 10 items, or multiple concept-clusters
- Material must be retrieved in a specific order under performance stress
- The recall event is high-stakes (exam, certification, live presentation)
- Items are concept-clusters, not just words (each item has sub-details that must also surface)

**The core mechanism:** Images are easier to recall than words. The brain retrieves a vivid spatial image as a single unit (like "tugging a stringer of fish" — pull one, the whole catch surfaces). Associating content to locations converts abstract material into a mental walkthrough of a familiar space.

**Decision note on the Mark Twain variant:** When the material has inherent quantity or duration (lengths of reigns, timeline spans, measurement-anchored sequences), consider the Twain estate-walk format: stake locations along a physical or imagined path where distance represents a meaningful unit (years, steps, percentages). The path becomes a to-scale diagram that children and adults can literally walk, trot, or revisit.

---

## Step 3: Build the Simple Device

**Why:** A constructed device is ready to practice immediately. A template forces the user to do the hard creative work alone, defeating the purpose of the skill.

### For Acronym / Acrostic

1. List the items. Extract the first letter of each key term.
2. Arrange letters to form a real word (acronym) or create a memorable sentence where each word starts with the extracted letter (acrostic).
3. If no natural word exists, try rearranging the order (if order is not critical) or use a vivid, absurd sentence.
4. Output: the acronym or sentence, plus the mapping (which letter = which item).

**Example — Great Lakes west to east:**  
Ontario, Erie, Huron, Michigan, Superior → HOMES (reordered: Huron, Ontario, Michigan, Erie, Superior)  
Recall cue: "Picture a cluster of HOMES sitting on ice floes."

### For Peg Method (ordered lists up to 20)

1. Confirm the standard peg rhyme: 1=bun, 2=shoe, 3=tree, 4=store, 5=hive, 6=tricks, 7=heaven, 8=gate, 9=twine, 10=pen.
2. For each item to remember, create a vivid, bizarre interaction between the peg image and the target item.
3. Bizarre interactions encode more deeply than mundane ones — the more impossible the scene, the stronger the memory hook.
4. Output: numbered list of (peg image + target item + vivid interaction scene).

**Example — First 3 steps of a procedure:**  
Step 1 (collect data) → bun: "A giant bun rolls down a hill, squashing a pile of spreadsheets and data printouts."  
Step 2 (analyze patterns) → shoe: "A shoe stomps on a magnifying glass that is scanning a graph."  
Step 3 (write report) → tree: "A tree is covered in leaves that are all printed report pages."

### For Chunking

1. Break the full string into groups of 3-4 characters.
2. If groups have natural meaning (phone numbers, zip codes, product codes), use those boundaries.
3. Add rhythm or pronunciation patterns so chunks become speakable units.
4. Output: chunked string with suggested verbal rhythm.

---

## Step 4: Build the Memory Palace (Six-Step Construction)

**Why:** A memory palace's power comes from specificity — a vague imagined space gives vague retrieval cues. Each of the six steps transforms abstract material into concrete, location-anchored imagery that survives exam-hall stress.

**Pre-condition:** The user must understand the material before building. James Paterson's students at Bellerbys College only visited cafés to build memory palaces after "thoroughly covering the material in class." The palace organizes knowledge; it does not create it.

### Step 1: Consolidate and Reduce the Material

Gather all sources (notes, slides, reading). Reduce to **key ideas in phrase form, not full sentences**. These are the items each location will anchor.

- Wrong: "Restraint theory, proposed by Herman and Mack, suggests that the attempt to not overeat paradoxically increases the probability of overeating because disinhibition causes loss of dietary control."
- Right: "Restraint → disinhibition → overeating"

**Why:** Full sentences cannot be imaged. A short phrase collapses into a single vivid scene. A long sentence requires multiple scenes and breaks the location-one-to-one-idea contract.

### Step 2: Select the Palace Location

Choose a real physical space the user knows extremely well — well enough to mentally walk through it in detail with eyes closed.

Good choices:
- A frequently visited café, restaurant, or library
- Your home (room by room, or a single room with many fixtures)
- A commute route with distinctive landmarks
- A childhood street or school

For **the Mark Twain variant (quantity-anchored sequences):** Use a path (driveway, road, hallway) where physical distance represents a meaningful unit. Twain staked 817 feet of his estate driveway — one foot per year of English history — so the monarchs' reigns became walkable, measurable segments. Use this format when your material has duration, quantity, or timeline structure.

**Why the space must be familiar:** The memory palace works because spatial memory is ancient and robust. You already know how your home is laid out without conscious effort. The palace hijacks that effortless spatial recall to carry new, effortful content.

### Step 3: Identify Locations Within the Palace

Walk through the space mentally. Identify 8-15 distinct, fixed features in a logical traversal order.

- For a café: door → host stand → first booth → bar counter → espresso machine → window seat → back table → exit
- For a room: door → left wall bookshelf → armchair → lamp → desk → right wall window → closet door → ceiling fan

Write the sequence. These are your "loci" — the location anchors.

**Why ordered traversal matters:** If order is important (essay structure, procedural steps, historical sequence), the walk direction encodes the order. Marlys, preparing for her A-level psychology exam, moved through Pret-a-Manger clockwise — each station cued the next paragraph in sequence, so she could not skip ahead or lose her place.

### Step 4: Assign One Key Idea to Each Location

Map each reduced key idea (from Step 1) to a specific location (from Step 3), one-to-one.

- Door → Restraint theory (Herman and Mack)
- First booth → Boundary model of hunger and satiety
- Bar counter → Cultural biases in obesity data
- ...and so on

**Why one idea per location:** Assigning two ideas to one location collapses them — retrieval cues blur. If there are more ideas than locations, either expand the palace (add a second room or building) or group closely related sub-ideas under a single phrase.

### Step 5: Populate Each Location With a Vivid, Bizarre Character or Scene

For each location, invent an absurd, memorable scene that encodes the key idea. The scene must:

- Feature a recognizable character or object (a movie character, a celebrity, an animal, a specific person)
- Show that character doing something impossible or extreme — action creates stronger recall than static images
- Directly embody the concept, not just label it

**Marlys's example:** At Pret-a-Manger, the "restraint theory" location showed La Fern (the man-eating plant from *Little Shop of Horrors*) restraining her friend Herman from a plate of mac and cheese just out of reach. When Marlys mentally entered the café and saw La Fern, she immediately wrote: *"Herman and Mack's restraint theory suggests that attempting not to overeat may actually increase the probability of overeating."* The scene encoded the author names, the theory name, and its counterintuitive direction.

**Why bizarre and active:** Humans remember pictures more easily than words, and impossible or extreme scenes encode more durably than plausible ones. A seated person reading a book at the counter is forgettable. A yak riding a unicycle while eating an encyclopedia is not.

### Step 6: Rehearse the Walk — Three Sessions

The palace is built. Now practice retrieval, not review.

**Session 1 (same day, within 2 hours of building):** Walk the palace from beginning to end without looking at notes. At each location, reconstruct the scene and state the key idea aloud or in writing. If a location is blank, skip it, finish the walk, then return to fill gaps.

**Session 2 (24-48 hours later):** Repeat the walk from memory. Check against source material. Repair any broken scenes — strengthen weak images by making them more bizarre or adding sensory detail (smell, sound, movement).

**Session 3 (3-5 days later, or 24 hours before the recall event):** Full walk plus a "random access" test: name a location out of order and retrieve the idea without tracing the full route. This tests whether the location truly anchors the concept or whether you are just remembering a list.

**Why three sessions?** Spaced retrieval practice (not passive re-reading of the palace) is what converts the device into durable long-term memory. One review immediately after construction captures working memory, not long-term storage.

---

## Step 5: Output — Deliver the Completed Device

**Why:** Handing the user a blank framework defeats the skill's purpose. Deliver a complete, specific, ready-to-practice device.

### For Simple Devices

Deliver:
- The full acronym/acrostic/peg list/chunked string — written out completely
- The mapping: each letter/peg/chunk → what it encodes
- One recall cue (a vivid summary sentence or image to start the device)
- The 3-session rehearsal schedule: when to practice and what counts as success

### For Memory Palace

Deliver:
- The palace location and traversal route (in order)
- For each location: [Location name] → [Key idea] → [Scene description]
- A "walk summary" — the full sequence in a single compact list for reference
- The 3-session rehearsal schedule

**Success signal:** The user can walk the palace (or recite the acronym) from memory with zero reference material and retrieve every anchored idea with enough detail to write a paragraph or perform a task — within Session 2.

---

## Examples

### Example 1: Simple — Acronym for Roman Numeral Values

**Material:** I=1, V=5, X=10, L=50, C=100, D=500, M=1000 (ascending order)  
**Device:** Acrostic — *"I Value Xylophones Like Cows Dig Milk"*  
**Mapping:** I=I(1), V=V(5), X=X(10), L=L(50), C=C(100), D=D(500), M=M(1000)  
**Recall cue:** Picture a xylophone-playing cow digging in a milk bath.  
**Rehearsal:** Say the sentence, then state each value without looking. Repeat 24h later.

### Example 2: Complex — Memory Palace for a 5-Topic Exam

**Context:** Three essay topics for a psychology exam, each with 12 key points.  
**Palace 1 (Topic: Dieting):** Pret-a-Manger café, clockwise traversal, 12 locations  
- Door → Restraint theory (La Fern restraining Herman from mac and cheese)  
- Window → Boundary model (a bright neon boundary line dividing the table)  
- Counter → Cultural bias (customer in national costume arguing with the server)  
*(... 9 more locations ...)*

**Palace 2 (Topic: Aggression):** Krispy Kreme shop, 12 locations  
**Palace 3 (Topic: Schizophrenia):** Starbucks, 12 locations  

**Walk rehearsal:** Marlys spent 10 minutes before her exam mentally walking all three cafés, listing the 12 key ideas per topic. She then wrote her essays from her structured notes — without anxiety about forgetting what she had learned.

### Example 3: Twain Estate-Walk Variant — Ordered Sequence With Quantity

**Material:** English monarchs' reigns, William the Conqueror through Victoria (817 years total)  
**Palace:** A driveway or hallway, 817 units long — each unit represents one year  
**Stake placement:** At each reign boundary, place a distinct image-stake (whale = William the Conqueror, because both start with W and both are "the biggest of their kind")  
**Recall:** Walk the path, call out monarch and dates at each stake. Children can physically walk the estate road, or adults can mentally traverse a hallway where each floor tile equals one year.  
**Why this works:** Duration is physically embodied in distance. A 46-year reign is visibly longer than a 2-year reign — proportional memory rather than arbitrary list order.

---

## Critical Warning: Mnemonics Come After Learning

Mnemonic devices are *retrieval infrastructure*, not *learning infrastructure*. James Paterson learned this through competitive failure: he memorized facts for exams without mastering the underlying relationships, and his knowledge collapsed under conceptual questions. The memory palace at Bellerbys College worked for Marlys because Paterson had *already thoroughly covered the material in class* before taking students to construct palaces in cafés.

If the user does not yet understand the material:
1. Flag this clearly.
2. Recommend they work through the content first (retrieval practice, concept mapping, or active study).
3. Return to this skill when they can explain the ideas in their own words.

Mnemonics organize what you know. They cannot substitute for knowing it.

## License

This skill is licensed under [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/).
Source: [BookForge](https://github.com/bookforge-ai/bookforge-skills) — Make It Stick: The Science of Successful Learning by Peter C. Brown, Henry L. Roediger III, Mark A. McDaniel.

## Related BookForge Skills

This skill is standalone. Browse more BookForge skills: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

FILE:references/mnemonic-types-and-selection.md
# Mnemonic Types and Selection Reference

Source: Make It Stick, Chapters 7 and 8 (Brown, Roediger, McDaniel)

---

## Two-Tier Taxonomy

### Tier 1: Simple Devices

All operate on the same principle — a familiar, pre-memorized structure carries new content as associations.

| Device | Mechanism | Capacity | Order | Best Use |
|--------|-----------|----------|-------|----------|
| Acronym | First letters → real word | 3-10 items | Fixed or free | Short discrete lists |
| Acrostic | First letters → memorable sentence | 3-10 items | Fixed | Lists where no word forms |
| Peg method | Number rhymes (1=bun, 2=shoe...) carry images | Up to 20 items | Ordered | Sequential lists |
| Chunking | Long string → grouped sub-strings | Any length | Fixed | Digits, codes, long identifiers |
| Rhyme/song | Musical phrases carry encoded images | Variable | Fixed | Material with rhythm affinity |

**Peg rhyme (1–10):** 1=bun, 2=shoe, 3=tree, 4=store, 5=hive, 6=tricks, 7=heaven, 8=gate, 9=twine, 10=pen. After 10: 11=penny-one/setting sun, 12=penny-two/airplane glue, etc.

### Tier 2: Complex Devices

| Device | Mechanism | Capacity | Order | Best Use |
|--------|-----------|----------|-------|----------|
| Memory palace (method of loci) | Key ideas anchored to locations in familiar space | Effectively unlimited (add rooms/buildings) | Optional — traversal order encodes sequence | Large volumes, high-stakes sequential recall |
| Twain estate-walk variant | Locations along a path where distance = unit (years, steps) | Proportional to path length | Strictly ordered | Sequences with inherent quantity or duration |

---

## The Paterson Case Study: What Mnemonics Cannot Do

James Paterson, Welshman, World Memory Championships competitor, and teacher at Bellerbys College, Oxford:

- Learned mnemonics hoping to memorize coursework quickly without deep study
- Won first place in beginner category at Cambridge memory competition (2006); placed 12th at World Championships that year
- Can memorize a shuffled deck of cards in under 2 minutes; sequences of 74+ spoken digits without error
- Discovered that memorizing names and dates without understanding concepts left him without "the mountain range, valleys, rivers, or the flora and fauna" — only mountaintops

**Lesson:** Mnemonics organize what has been learned. They do not create understanding. Paterson changed his teaching practice: he covers material thoroughly in class before taking students to cafés to build memory palaces.

---

## Memory Palace: Why It Works

From the science in Chapter 7:

- Humans remember pictures more easily than words. An image of an elephant is easier to recall than the word "elephant."
- Spatial memory is ancient and robust — we navigate familiar spaces without conscious effort.
- The method of loci (Greek origin) associates mental images with specific physical locations to cue memories on demand.
- Vivid, bizarre, action-based scenes encode more durably than neutral or static ones.
- A strong mental image "proves as secure and bountiful as a loaded stringer of fish — tug on it, and a whole day's catch comes to the surface."

---

## The Mark Twain Variant: Location = Quantity

From Harper's magazine article by Mark Twain, as cited in Make It Stick:

- Twain originally tried partial sentences to remember his speeches — unsatisfactory, because "snippets of text all look alike."
- Switched to crude pencil sketches — each sketch reliably cued the next section of his talk.
- For his children learning English monarchs: staked 817 feet of his farm driveway, one foot = one year.
- Each reign was marked with a white-pine stake; each monarch got a vivid image (whale = William the Conqueror, hen = Henry I).
- Children trotted the course reciting names, dates, and reign lengths from the physical stakes.

**Application:** When material has inherent duration or quantity (historical timelines, budget ratios, phase lengths), encoding distance-as-unit is more memorable than encoding an arbitrary list order.

---

## Michela's 6-Step Process (Bellerbys College Student)

1. Pull together all material (lecture slides, reading, notes)
2. Reduce to key ideas — not whole sentences
3. Select the palace location (a café, campus building, or familiar space)
4. Tie each key idea to a specific, visualizable location within the palace
5. Populate each location with something "crazy" — a vivid character or impossible scene that encodes the idea
6. At exam time: walk the palace mentally, list the key ideas, fill gaps by moving past blanks and returning

**Michela's insight:** The palace serves not as a learning tool but as a method to organize what has already been learned so it is readily retrievable. The confidence of knowing the structure is "a huge stress buster."

---

## Image Power and Retrieval Cues

- The brain retrieves context before content: telling someone where a conversation happened causes the details to "come flooding back."
- Images cue memories — a strong spatial or visual cue can unlock entire chains of related content.
- Paterson's 1,000-image system: each 3-digit number from 000 to 999 has a unique image built from phonetic sounds (6=Sheh/Jeh, 1=Tuh/Duh, 5=L → 615 = SheTuhL = shuttle). Allows memorizing 74+ spoken digits at 1-per-second pace.

---

## Selection Criteria Summary

| Condition | Use |
|-----------|-----|
| ≤10 discrete items, any order | Acronym or acrostic |
| ≤20 items, ordered | Peg method |
| Long digit/code string | Chunking |
| Material with rhythm | Rhyme or song |
| >10 items OR concept-clusters | Memory palace |
| Sequence with quantity/duration | Twain estate-walk variant |
| High-stakes, sequential, under pressure | Memory palace (always) |

---
name: learning-practice-auditor
description: |
  Audit any set of study habits, training program, or course design for ineffective learning practices and replace them with evidence-based alternatives. Use this skill when someone wants a study habits audit, suspects they are making learning mistakes, reports that their studying is not working, relies on rereading, highlighting, or cramming, wonders whether their training design actually produces learning, or asks "what am I doing wrong?" Also triggers on: ineffective studying complaints, rereading concerns, learning styles assumptions, cramming before an exam, blocked practice schedules, highlighting as primary review method, "I study for hours but nothing sticks," or any study strategy review. Works for individual learners, teachers, corporate trainers, instructional designers, and coaches. Detects five named anti-patterns — rereading trap, massed practice delusion, illusions of knowing cluster, learning styles myth, errorless learning myth — with mechanism explanations, severity ratings, and direct routing to the corrective skill. Do NOT use this skill to build a study schedule (use retrieval-practice-study-system), to design a practice sequence (use desirable-difficulty-classifier), or to calibrate mastery confidence (use learning-calibration-audit) — this skill diagnoses the problem and routes to those solutions.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/make-it-stick/skills/learning-practice-auditor
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: draft
source-books:
  - id: make-it-stick
    title: "Make It Stick: The Science of Successful Learning"
    authors: ["Peter C. Brown", "Henry L. Roediger III", "Mark A. McDaniel"]
    chapters: [1, 2, 3, 5, 6]
tags:
  - learning-science
  - cognitive-psychology
  - evidence-based-learning
  - learning-audit
  - anti-patterns
  - study-habits
depends-on:
  - retrieval-practice-study-system
  - desirable-difficulty-classifier
  - learning-calibration-audit
execution:
  tier: 1
  mode: hybrid
  inputs:
    - type: description
      description: "Description of current study habits, training design, or learning approach — can be a verbal description, a course outline, a study schedule, or a list of current practices"
  tools-required: []
  tools-optional: [Read, Write]
  mcps-required: []
  environment: "Any agent environment. Works from a verbal description or a document. No file access required."
discovery:
  goal: "Identify which ineffective learning practices are present, classify each by name and severity, explain the mechanism that makes each feel effective but produces weak retention, and route to the appropriate corrective skill."
  tasks:
    - "Gather the learner's or designer's current practices through targeted intake questions"
    - "Scan for detection signals of each of the five anti-patterns"
    - "Classify each detected anti-pattern by name, severity (critical / moderate / low), and primary mechanism"
    - "Explain why each pattern feels productive — the illusion it creates"
    - "Prescribe a corrective action that names the specific replacement skill to invoke"
    - "Produce a structured audit report with findings ranked by severity"
  audience: ["students", "teachers", "corporate trainers", "instructional designers", "coaches", "lifelong learners"]
  triggers:
    - "Why isn't my studying working?"
    - "I've read this three times and still can't remember it"
    - "Review my study habits"
    - "Is cramming bad for learning?"
    - "I highlight everything but still fail tests"
    - "What am I doing wrong when I study?"
    - "Audit this training program for effectiveness"
    - "I'm a visual learner — should I only use videos?"
    - "My students are studying but not retaining"
    - "Why do I feel confident but fail the exam?"
  not_for:
    - "Building a complete spaced-practice schedule — use retrieval-practice-study-system"
    - "Classifying difficulty levels in a course design — use desirable-difficulty-classifier"
    - "Calibrating mastery confidence and running a dynamic testing cycle — use learning-calibration-audit"
    - "Designing a full curriculum from scratch — this skill diagnoses; other skills redesign"
  quality:
    completeness_score:
    accuracy_score:
    value_delta_score:
---

# Learning Practice Auditor

## When to Use

Something about how you or your learners study is producing less retention than expected. You may be putting in hours that do not convert to durable learning. You may be designing training that graduates confident-feeling but underprepared learners.

This skill is the diagnostic hub: it identifies which of five named ineffective practices are present, explains the mechanism creating the illusion of learning, rates the severity, and routes to the specific corrective skill.

**Typical entry points:**
- Learner: "I study for hours but blank on tests"
- Learner: "I highlight everything but still can't recall it"
- Teacher or trainer: "Why aren't my learners retaining this?"
- Instructional designer: "Is there anything wrong with this training structure?"
- Anyone asking: "Am I studying the wrong way?"

**Mode: Hybrid** — The agent runs the audit and produces the report. The human and/or agent then invokes the recommended corrective skills.

**This skill diagnoses. It does not redesign.** After the audit, each corrective action names the skill to invoke next.

---

## Step 1: Intake — Gather Current Practices

**Why this step:** Anti-pattern detection requires knowing what the learner or designer is actually doing, not what they think they are doing. Many learners describe their method as "studying" without specifying what that means. The intake questions force specificity.

Ask the following. If the user has already provided answers in their message, extract the answers without asking again.

### Required
1. **What are you trying to learn, and why?**
   (Subject, course, skill, domain — and the performance event: exam, job task, certification, presentation)

2. **Walk me through a typical study session from start to finish.**
   (What does the learner actually do, in sequence, with the material?)

3. **How do you decide when you know something well enough to move on?**
   (The mastery signal — feeling of familiarity, re-reading smoothly, immediate practice score, etc.)

4. **How is the learning structured over time?**
   (One long session vs. spaced sessions; one topic completed before the next; mixed topics within a session)

### Helpful if available
5. **Do you have a course outline, training schedule, or study plan I can read?**
   → If yes, use Read to scan it for blocked/massed structure signals.

6. **What does assessment look like?** (Multiple-choice, essay, performance demo, on-the-job transfer)

7. **Have you already taken any tests or received feedback on your performance?**

If context is still insufficient after asking, note the gap in the audit report and flag it as a finding ("Unable to assess [pattern] — insufficient information about [X]").

---

## Step 2: Anti-Pattern Detection

**Why this step:** Each anti-pattern has specific detection signals that appear in how the learner describes their practice. This step converts free-form description into a structured finding list.

Check each anti-pattern against the intake answers. Mark each as **Detected**, **Absent**, or **Insufficient information**.

### AP-1: Rereading Trap

**What to look for:**
- "I review my notes / re-read the chapter / highlight the key parts"
- Primary study method is reading or looking at material rather than testing recall
- Mastery signal is "it feels familiar" or "I can follow along when I read it"
- Study sessions described as long reading or annotation sessions

**Mechanism (explain this to the user when detected):**
Each time you reread well-organized text, your processing becomes faster and smoother — a state called *fluency*. That fluency feels like understanding and mastery, but it is really your brain's familiarity with the visual form of the text. It cannot distinguish between "I have encoded this in long-term memory" and "I have seen these words before." On a test, you must retrieve — reconstruct from memory — and fluency does not train that. The 2010 study: students who took a recall test after reading retained **50% more** a week later than those who reread. Crammers in a 1978 study forgot **50% of their initial recall within two days**; retrieval-practice groups forgot only **13%**.

**Corrective action:** Replace rereading sessions with self-testing sessions → invoke **`retrieval-practice-study-system`**

---

### AP-2: Massed Practice Delusion

**What to look for:**
- "I do all the problems for chapter 5 before moving to chapter 6"
- Training sessions run drill repetitions on one skill until it feels solid, then move on
- Study sessions are concentrated blocks on one topic
- Cramming before an exam described as the primary retention strategy

**Sub-pattern — Blocked Practice Trap:**
Problems or practice tasks are grouped by type. This removes the critical "what kind of problem is this?" sorting decision — which is exactly what real performance requires. College students practicing geometry volumes: blocked practice averaged **89% correct** during training but only **20%** on a test one week later. Interleaved practice: **60%** during training, **63%** on the test — a **215% improvement** in transfer. (Ch3)

**Sub-pattern — Familiarity Trap:**
After massed repetition, the material feels familiar (System 1 recognition). But the test requires System 2 retrieval and application. Rapid, blocked practice encodes learning in a cognitively simpler neural representation than spaced, varied practice — less flexible, less transferable.

**Mechanism:**
Rapid repetition draws on short-term working memory. Durable encoding requires a consolidation process that unfolds over hours and days. Massed practice produces fast visible gains that feel like mastery, but the gains are not consolidated. In the surgical microsurgery study: residents who had 4 lessons spaced one week apart outperformed those trained in a single day on *all* measures — elapsed time, movement efficiency, and success rate — one month later. **16%** of the massed-practice group damaged tissue beyond repair.

**Corrective action:** Replace massed and blocked practice with spaced, interleaved, and varied practice → invoke **`desirable-difficulty-classifier`** to classify present and absent difficulty strategies and get redesign recommendations.

---

### AP-3: Illusions of Knowing Cluster

**What to look for:**
- Mastery signal is "it feels familiar" or "I recognized the answer when I saw it"
- High confidence before a test, low score after
- "I studied this — I don't know why I blanked"
- Learner or trainer expresses surprise at gaps revealed on assessment
- Anyone relying on "just reading through" as a review method

**Note:** This anti-pattern overlaps with AP-1 and AP-2. Log it separately when the primary problem is *miscalibrated confidence*, not just the study method used.

**Mechanism:**
You rely on System 1 signals — fluency, familiarity, ease of processing — to judge mastery. These signals are unreliable. The Dunning-Kruger research: students at the **12th percentile** in logic ability believed they were at the **68th percentile** on average. Fluency illusion: re-reading a clear text increases the sensation that it is simple and already known. Hindsight bias: after learning the answer, you feel you "knew it all along," which makes you underestimate future study needs.

**Corrective action:** Run a calibration cycle to identify the specific distortion and install reliable mastery signals → invoke **`learning-calibration-audit`**

---

### AP-4: Learning Styles Myth

**What to look for:**
- "I'm a visual learner, so I only use videos"
- Training is segmented by assessed learning style
- Learner or designer says matching style to instruction is important for retention
- Learner avoids certain modalities because they are "not their style"

**The Pashler Validity Test:** For a study to prove learning styles theory, it must: (1) classify learners by style, (2) randomly assign them to style-matched vs. style-mismatched instruction on the same content, (3) show that style-matched learners outperform style-mismatched learners. In the 2008 Pashler et al. review: **no published study meets this design standard**. Those that do flatly contradict the theory. Studies found that matching instruction to the *nature of the content* (visual for geometry, verbal for poetry) benefits *all* learners regardless of their style preference.

**Mechanism:**
Learning preferences are real — but preference does not equal differential effectiveness. A learner's self-reported "style" predicts what they *prefer*, not what produces the best retention. Designing instruction around style matching misses the variance drivers that actually matter: prior knowledge, retrieval practice, spacing, and structure-building ability. More than **70 competing style theories** exist with contradictory dimensions and no cross-validation — itself a strong signal the construct lacks scientific coherence.

**Corrective action:** Drop style-based instructional segmentation; shift to content-nature matching and apply evidence-based strategies to all learners regardless of style preference → invoke **`desirable-difficulty-classifier`**

---

### AP-5: Errorless Learning Myth

**What to look for:**
- Training shows the answer before asking the learner to attempt it
- Flash cards are answer-first or answer-alongside
- Instructor corrects immediately before learner generates a response
- Stated rationale is "we don't want to practice errors"

**Mechanism:**
Generating an answer — even a wrong one — before seeing the correct answer strengthens the subsequent memory of the correct answer more than passive presentation. This is the *generation effect*: word pairs where learners had to fill in a missing letter (foot → s_ _e) produced better later recall than pairs presented intact (foot → shoe). Errors made in *generative attempts* followed by corrective feedback are part of the encoding process, not its enemy. Preventing the attempt removes the cognitive effort that creates durable encoding.

**Key distinction:** Uncorrected misconceptions are harmful. The solution is corrective feedback — not preventing the attempt.

**Corrective action:** Restructure practice to require generation before exposure — pre-tests, cued retrieval, retrieval-first flash cards → invoke **`retrieval-practice-study-system`**

---

## Step 3: Classify Severity

**Why this step:** Not all detected anti-patterns require the same urgency. Severity determines what to fix first and what to route immediately vs. note for later.

For each detected anti-pattern, assign a severity:

| Severity | Criteria | Action |
|---|---|---|
| **Critical** | This is the *primary* study or training method; no evidence-based alternative is in use | Immediate redesign — route to corrective skill now |
| **Moderate** | Anti-pattern coexists with some effective strategies but is undermining them | Targeted replacement of the identified component |
| **Low** | Present but minor; dominant strategy is already evidence-based | Flag for next redesign cycle |

---

## Step 4: Produce the Audit Report

**Why this step:** A written report makes findings actionable. The learner or designer can share it, return to it, and use the corrective routing as a checklist.

Structure the report as follows:

```
## Learning Practice Audit — [Subject / Program Name]

### Summary
[1-3 sentence overview: how many anti-patterns found, dominant severity level, top recommendation]

### Findings

#### [Anti-Pattern Name] — Severity: [Critical / Moderate / Low]
**Detected signals:** [What in their description triggered this finding]
**Mechanism:** [Why it feels effective but produces weak retention — in plain language]
**Evidence:** [1-2 specific research findings with numbers]
**Corrective action:** [Named replacement practice] → invoke `[skill-name]`

[Repeat for each detected anti-pattern]

### What to Do Next
[Prioritized list of corrective skills to invoke, in order of severity]
1. [Corrective skill] — addresses [anti-pattern(s)]
2. ...

### What Is Already Working
[Any detected evidence-based practices — note and reinforce these]
```

---

## Examples

### Example 1 — Individual Student (Critical: Rereading + Massed Practice)

**User description:** "I study organic chemistry by reading the chapter twice, then doing all the practice problems for each reaction type before moving on. I feel pretty solid during my sessions but I've failed two midterms."

**Audit findings:**
- **AP-1: Rereading Trap — Critical.** Primary review method is re-reading. The fluency gained from reading the chapter twice is not producing retrievable memory. The learner is using feeling-solid as the mastery signal, which tracks fluency not recall.
- **AP-2: Massed Practice Delusion (Blocked Practice) — Critical.** All practice problems for one reaction type before moving to the next = blocked massed practice. This eliminates the "which type of problem is this?" discrimination skill that the exam actually tests. The 20% vs. 63% result on blocked vs. interleaved geometry test is directly applicable.
- **AP-3: Illusions of Knowing — Moderate.** "I feel pretty solid during sessions but failed two midterms" = textbook miscalibration. The mastery signal is unreliable.

**Corrective routing:**
1. `retrieval-practice-study-system` — replace re-reading with self-quizzing and build spacing schedule
2. `desirable-difficulty-classifier` — redesign the problem practice to interleave reaction types
3. `learning-calibration-audit` — install reliable mastery signals to replace the fluency-feeling

---

### Example 2 — Corporate Trainer (Moderate: Learning Styles Design)

**User description:** "We have our training team assess employees' learning styles before onboarding. Visual learners get diagrams-first modules; auditory learners get voice-over walkthroughs. We invested in this system two years ago."

**Audit findings:**
- **AP-4: Learning Styles Myth — Critical.** The entire curriculum segmentation is organized around a theory with no empirical validation (Pashler et al., 2008). Investment in assessment tools and differentiated modules is producing no learning benefit relative to matched instruction. The content-nature matching finding is relevant: geometry-style content (spatial workflows, process maps) should be visual for *all* learners, regardless of assessed style.

**Corrective routing:**
1. `desirable-difficulty-classifier` — audit the onboarding modules for evidence-based difficulty strategies that will benefit all learners regardless of style
2. Redirect the investment in style assessment toward spaced-practice scheduling and retrieval-based knowledge checks

---

### Example 3 — Teacher (Low: Partial Massed Practice)

**User description:** "I do a mixed review at the end of each unit. I mostly teach one topic per day but sometimes bring in earlier material. Students self-quiz once a week using flashcards."

**Audit findings:**
- **AP-2: Massed Practice — Low.** One topic per day is still somewhat blocked, but the weekly mixed review and flashcard self-quizzing are evidence-based practices that partially offset this. The dominant strategy is already better than pure massed practice.
- No other anti-patterns detected from this description.

**Recommendation:** This practice is already above average. The flashcard self-quizzing is the highest-value element — reinforce and expand it. For the next redesign cycle: consider interleaving topics within sessions, not just end-of-unit reviews.

---

## Reference

Full evidence profiles, all research citations, and detailed sub-pattern descriptions for each anti-pattern:
→ `references/anti-pattern-reference-table.md`

For mechanism details on illusions of knowing, see also:
→ `learning-calibration-audit` references

## License

This skill is licensed under [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/).
Source: [BookForge](https://github.com/bookforge-ai/bookforge-skills) — Make It Stick: The Science of Successful Learning by Peter C. Brown, Henry L. Roediger III, Mark A. McDaniel.

## Related BookForge Skills

Install related skills from ClawhHub:
- `clawhub install bookforge-retrieval-practice-study-system`
- `clawhub install bookforge-desirable-difficulty-classifier`
- `clawhub install bookforge-learning-calibration-audit`

Or install the full book set from GitHub: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

FILE:references/anti-pattern-reference-table.md
# Anti-Pattern Reference Table

Full evidence profiles for each ineffective learning practice documented in *Make It Stick* (Brown, Roediger, McDaniel). Use this table when you need the complete mechanism, research citations, and severity ratings during an audit.

---

## AP-1: The Rereading Trap

**Core mechanism:** Each pass through the text increases processing fluency — the sensation that the material is easy to understand. Fluency is mistaken for mastery. The learner overestimates how much they will remember on a future test, because the test will require *retrieval*, not recognition.

**Detection signals:**
- Primary review strategy is highlighting, underlining, or annotating text
- Learner says "I've read it three times, I should know this"
- Learner feels confident right after reviewing but blanks on tests
- Study sessions consist of reading notes rather than self-testing

**Sub-pattern — Fluency Illusion:**
When a learner rereads clear, well-organized text, processing becomes faster and easier with each pass. This processing ease (fluency) is a poor proxy for durable retention. The learner confuses *recognition* (can follow the text when it is in front of them) with *recall* (can reconstruct it from memory). Ch5 (p. 115): "Students who study by rereading their texts can mistake their fluency with a text, gained from rereading, for possession of accessible knowledge of the subject and consequently overestimate how well they will do on a test."

**Research evidence:**
- 1978 study: cramming (massed re-study) led to higher scores on an *immediate* test but on a second test two days later, crammers had forgotten **50%** of what they recalled initially; those who practiced retrieval instead forgot only **13%**.
- 2010 study (reported in the New York Times): Students who read a passage and then took a recall test retained **50% more** information a week later than students who only reread the passage.
- Single quiz after a lecture produces better retention than rereading lecture notes (Ch1 claims list, Ch2 passim).

**Consequences of continued use:**
- Systematically overestimates mastery → test performance surprises are common
- Material fades within days; not consolidated into long-term memory
- Time is spent on low-yield re-exposure instead of high-yield retrieval

**Corrective action:** Replace rereading with retrieval practice — invoke `retrieval-practice-study-system`.

---

## AP-2: Massed Practice Delusion

**Core mechanism:** Rapid-fire repetition of a single skill or concept within one session produces visible, rapid improvement. This improvement is real but draws primarily on short-term memory. Because consolidation requires hours to days, the rapid gain is not durably encoded. The learner observes fast progress and concludes the method is superior — but the gains evaporate.

**Detection signals:**
- Training program runs through all examples of one type, then moves to the next type
- Study session = "I'll do 50 of these problems right now"
- Course design: module 1 fully complete → module 2 fully complete → etc.
- Learner feels "on top of it" while doing a session but cannot recall material a week later

**Sub-pattern — Blocked Practice Trap:**
Problems or examples are grouped by type (block 1 = all wedge volumes, block 2 = all spheroid volumes). This eliminates the "what type of problem is this?" decision that is required in real performance. In a study of college students learning volumes of geometric solids: massed/blocked practice averaged **89% correct** during training vs. 60% for interleaved; but on a test one week later, massed practice averaged only **20% correct** vs. **63% for interleaved** — a **215% improvement** for interleaving. (Ch3)

**Sub-pattern — Familiarity Trap:**
After massed repetition, material feels familiar. Familiarity is a System 1 signal (automatic, fast) that is often mistaken for mastery (which requires System 2 verification — delayed recall, transfer, novel problem solving). Ch5 explains Kahneman's System 1/System 2 framework and how fluency-based familiarity hijacks self-assessment.

**Research evidence:**
- Surgical microsurgery study (38 residents): residents with lessons spaced one week apart outperformed those trained in a single day on *all* measures a month later. **16%** of the massed-practice group damaged experimental vessels beyond repair and could not complete their surgeries. (Ch3)
- Beanbag study: 8-year-olds who practiced at 2-foot and 4-foot distances performed best on a 3-foot test, compared to children who only practiced at 3 feet. Variable practice > blocked massed practice. (Ch3)
- Bird classification and painter attribution studies: interleaved study produced superior test scores; massed-study participants *preferred* massed practice and still believed it was superior even after seeing their own test results. (Ch3)

**Consequences of continued use:**
- Training produces confident but incompetent graduates
- Skills fail to transfer to novel situations (poor discrimination ability)
- Fast apparent learning masks slow real consolidation

**Corrective action:** Replace massed practice with spaced, interleaved, and varied practice → invoke `desirable-difficulty-classifier` to identify missing difficulty strategies.

---

## AP-3: Illusions of Knowing Cluster

This is a family of related distortions that inflate perceived mastery. Each has a distinct mechanism. The full taxonomy and calibration instruments are documented in `learning-calibration-audit`.

| Illusion | Mechanism | Signal |
|---|---|---|
| Fluency illusion | Processing ease mistaken for retrieval ability | Feels confident while reading, blanks on test |
| Hindsight bias / Knew-it-all-along | After learning the answer, past ignorance is underestimated | "I knew that" after being shown the correct answer |
| Dunning-Kruger overconfidence | Incompetent people lack the skill to judge their own incompetence | Grossly overestimated test score; bottom quartile students rated themselves 68th percentile when actually at 12th |
| Curse of knowledge | Expert underestimates learning time for a novice | Teacher's explanation misses the foundational steps students actually need |
| False consensus | Assumes others share your understanding | Surprised when teammates do not "obviously" know what you know |
| Imagination inflation | Imagining an event increases belief it occurred | Rehearsed explanations feel like actual competence |
| Social memory contamination | Others' errors infect your memory | Group study partners' incorrect beliefs become your own |

**Research evidence:** Dunning-Kruger: students at 12th percentile believed they were at **68th percentile** in logical reasoning. After training in logic, the bottom-quartile students could accurately estimate their own performance. Without training, they held their inflated estimates despite seeing peers' superior performance. (Ch5)

**Corrective action:** → invoke `learning-calibration-audit` to run the full distortion diagnosis and calibration cycle.

---

## AP-4: Learning Styles Myth

**Core mechanism:** The theory proposes that each learner has a preferred modality (visual, auditory, reading/writing, kinesthetic — "VARK") and learns best when instruction matches that style. The myth is appealing because learner preferences are real. The research failure is: preferences ≠ differential effectiveness. No published evidence validates the critical claim — that matching instruction to style *improves outcomes* relative to mismatched instruction.

**Detection signals:**
- Training program segments learners by "learning style" assessment
- Instructor provides visual-only materials for "visual learners" and skips written materials
- Learner says "I'm a visual learner, so slides work better for me than reading"
- Curriculum design driven by style matching rather than content-nature matching

**The Pashler Validity Test (2008):**
Pashler, McDaniel, Rohrer, and Bjork established the evidence standard a study must meet to validate learning styles:
1. Classify learners by their assessed learning style
2. Randomly assign learners to different instructional modes teaching the same content
3. Give all learners the same test afterward
4. Show that style-matched learners outperform style-mismatched learners, AND that different styles yield different optimal modalities

**Finding:** Virtually no published study meets this design requirement. Those that do *flatly contradict* the theory. Moreover: when instructional mode matches the *nature of the content* (visual for geometry, verbal for poetry), *all* learners do better, regardless of their style preferences. Content-nature matching > style matching. (Ch6)

**Additional context:** A 2004 survey for Britain's Learning and Skills Research Centre identified **more than 70 distinct learning styles theories** in the marketplace. The report's authors called the field a "bedlam of contradictory claims." An attendee at a learning conference who had completed a style assessment reported: "I learned that I was a low auditory, kinesthetic learner. So there's no point in me reading a book or listening to anyone for more than a few minutes." This exemplifies the corrosive effect: learners artificially limit themselves. (Ch6)

**Consequences of continued use:**
- Students pigeonhole themselves and avoid effective modalities outside their "style"
- Organizations waste resources on style-matched training with no evidence of benefit
- Misses the actual variance driver: differences in prior knowledge, structure-building ability, and use of retrieval practice

**Corrective action:** Shift from style-based design to content-nature matching and apply proven strategies (retrieval, spacing, interleaving) regardless of style preferences → invoke `desirable-difficulty-classifier`.

---

## AP-5: Errorless Learning Myth

**Core mechanism:** The myth holds that presenting learners with immediate, correct answers before they attempt retrieval prevents the formation of incorrect memories and maximizes confidence. The research shows the opposite: attempting to generate an answer, even when wrong, strengthens memory of the correct answer more than passive presentation does.

**Detection signals:**
- Flash cards show the answer on the same side as the prompt
- Training materials show the solution before asking the learner to attempt it
- Instructor corrects students immediately before they have attempted an answer
- "We don't want them to practice errors" as the stated rationale

**Research evidence:**
- The "generation effect": word pairs studied with a cue (foot → s_ _e) produced higher later recall than pairs studied intact (foot → shoe). The effort of generating the answer from a partial cue strengthens the memory trace. (Ch2)
- Pre-testing: trying to solve a problem *before being taught the solution* leads to better learning, even when the attempt produces errors. (Ch1 claims list)
- Delayed practice retrieval: when a recall attempt was delayed by 20 intervening word pairs rather than immediate, later recall was stronger, because the greater effort required consolidated the memory further. (Ch2)

**Key distinction:** Errors made during *learning attempts* (generative errors, before feedback) strengthen encoding. Errors made due to *misconceptions left uncorrected* are harmful. The corrective is feedback, not preventing the attempt.

**Consequences of continued use:**
- Learners receive information passively, which produces weak encoding
- Confidence may feel high (material was always presented correctly) but retrieval on tests fails
- The difficulty of attempting retrieval — which is the mechanism of durable learning — is eliminated

**Corrective action:** Build in pre-testing, retrieval attempts, and generative cues before presenting answers → invoke `retrieval-practice-study-system`.

---

## Severity Classification

| Severity | Definition | Appropriate Response |
|---|---|---|
| **Critical** | Anti-pattern is the primary study or training method; no evidence-based alternative is in use | Immediate redesign; route to corrective skill now |
| **Moderate** | Anti-pattern coexists with some effective strategies; it is undercut the effective ones | Targeted replacement; redesign the identified component |
| **Low** | Anti-pattern present but minor; dominant strategy is already evidence-based | Note and flag for next redesign cycle |

---

*Source: Make It Stick (Brown, Roediger, McDaniel). Chapters 1, 2, 3, 5, 6.*

---
name: learning-calibration-audit
description: |
  Diagnose and correct false confidence in learning mastery using cognitive science research. Use when you feel confident about a topic but keep failing tests, want to audit your metacognition for illusions of knowing, are preparing for a high-stakes assessment and need to verify actual mastery, or suspect your study method is producing Dunning-Kruger overconfidence. Also use for: identifying which of 7 specific cognitive distortions — fluency illusion, hindsight bias, Dunning-Kruger overconfidence, curse of knowledge, false consensus, imagination inflation, social memory contamination — is inflating your self-assessment accuracy; distinguishing reliable mastery indicators (delayed recall, novel problem transfer, peer explanation) from unreliable ones (rereading fluency, immediate recall, familiarity warmth); selecting calibration instruments (self-quizzing, cumulative quizzing, peer instruction) matched to the specific distortions detected; designing a dynamic testing cycle (assess → identify gaps → target practice → retest) as an iterative calibration protocol; and producing a calibration report with a retest schedule. Applies across all learning contexts — exam preparation, professional skill development, corporate training, language learning, technical certification. Works on document sets such as study plans, quiz results, self-assessment notes, and course materials.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/make-it-stick/skills/learning-calibration-audit
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: draft
depends-on: []
source-books:
  - id: make-it-stick
    title: "Make It Stick: The Science of Successful Learning"
    authors: ["Peter C. Brown", "Henry L. Roediger III", "Mark A. McDaniel"]
    chapters: [5, 6, 8]
tags: ["learning-science", "cognitive-psychology", "evidence-based-learning", "metacognition", "self-assessment", "cognitive-bias", "calibration", "overconfidence", "dunning-kruger", "study-skills", "training-design"]
execution:
  tier: 1
  mode: hybrid
  inputs:
    - type: document
      description: "Learning materials, study plans, quiz results, self-assessment notes, or a plain-text description of what you are studying and how you assess your mastery"
  tools-required: [Read, Write]
  tools-optional: [Grep]
  mcps-required: []
  environment: "Any agent environment. Works with pasted text or document files."
discovery:
  goal: "Identify which cognitive distortions are inflating the learner's confidence, match calibration instruments to the specific distortions found, design a dynamic testing cycle, and produce a calibration report with a retest schedule"
  tasks:
    - "Gather learning context: subject, study methods, and how mastery is currently being assessed"
    - "Diagnose calibration issues by checking for signals of each of the 7 cognitive distortions"
    - "Classify each detected distortion and explain its mechanism"
    - "Recommend calibration instruments matched to the detected distortions"
    - "Design a 3-step dynamic testing cycle as the iterative correction protocol"
    - "Produce a calibration report with detected distortions, selected instruments, and retest schedule"
  audience:
    roles: ["student", "teacher", "corporate-trainer", "instructional-designer", "coach", "lifelong-learner"]
    experience: "any — no prior cognitive science knowledge required"
  triggers:
    - "Learner feels confident but performs poorly on actual tests or transfer tasks"
    - "Learner relies on rereading, highlighting, or recognition-based review as primary study method"
    - "Learner wants to audit their mastery claims before a high-stakes assessment"
    - "Trainer suspects trainees are overestimating skill acquisition from passive instruction"
    - "Learner has studied the same material repeatedly but retention does not seem to improve"
    - "Learner feels they 'know it' when reading notes but blanks when tested without them"
  not_for:
    - "Designing a spaced retrieval practice schedule from scratch — use practice-schedule-designer"
    - "Building interleaved practice sequences — use the interleaving skill"
    - "General study strategy advice without a calibration problem present"
---

# Learning Calibration Audit

## When to Use

You believe you have learned something — but tests, applications, or conversations with others expose gaps you did not know existed. Your self-assessment is miscalibrated: confidence is running ahead of actual mastery.

This skill diagnoses which specific cognitive distortions are inflating your confidence, then prescribes the calibration instruments and testing cycle that will bring self-assessment into alignment with actual performance.

**Do not use this skill if:** You need to design a full spaced-practice schedule. Use `practice-schedule-designer` for that. This skill focuses on the calibration problem — diagnosing and correcting false confidence — not on scheduling practice intervals.

---

## Context and Input Gathering

Before running the audit, collect:

### Required
- **Subject or skill being studied:** What are you trying to master? (e.g., "organic chemistry reaction mechanisms," "Python data structures," "leadership communication")
- **Current study methods:** How are you currently reviewing and assessing your learning? (e.g., rereading, flashcards, practice tests, writing summaries)
- **How you judge mastery right now:** What signal tells you that you know something? (e.g., "it feels familiar," "I can follow along when I reread it," "I got it right on the quiz right after class")

### Important
- **Assessment results, if available:** Any quiz scores, test results, or practice exam feedback
- **Study materials:** Notes, outlines, flashcard decks, or course materials you are working with

### Optional
- **Stakes and timeline:** Is there an upcoming exam, certification, or performance event? When?
- **Prior calibration attempts:** Have you already tried self-quizzing or practice tests? What happened?

If the context is not yet described, ask for it before proceeding.

---

## Process

### Step 1: Identify Unreliable Mastery Signals

**Action:** Review the learner's stated method of judging mastery and check it against the list of unreliable indicators. Flag any that are present.

**WHY:** Unreliable mastery signals produce false confidence because they respond to familiarity and processing ease rather than to retrievable, transferable knowledge. A learner who judges mastery by fluency with their notes has confused ease of reading with depth of encoding. Until unreliable signals are identified, the learner has no reason to change their method — the feeling of knowing is strong and feels valid.

**Unreliable mastery indicators — flag if any are in use:**
- Reading fluency: "When I reread my notes, it all makes sense"
- Familiarity warmth: "It feels familiar when I see it"
- Immediate recall: "I got it right immediately after the lecture"
- Highlighting coverage: "My notes are thoroughly marked up"
- Passive recognition: "I can follow along when the answer is explained"
- Massed repetition: "I reviewed it five times this week"

**Reliable mastery indicators — check which are in use:**
- Delayed free recall: Successfully retrieved from memory after a gap (days, not minutes)
- Novel problem transfer: Applied the concept correctly to an unfamiliar problem type
- Peer explanation: Explained the concept clearly to someone who didn't know it, and they understood
- Error prediction: Accurately anticipated which questions or situations would be difficult before encountering them
- Interleaved performance: Correctly identified which concept or method to use when mixed with similar-looking problems

**Output:** List the unreliable signals in use and note which reliable signals are absent.

---

### Step 2: Diagnose Cognitive Distortions

**Action:** For each unreliable signal flagged in Step 1, identify which cognitive distortion mechanism is producing it. Use the 7-distortion taxonomy in `references/cognitive-distortions.md` for the complete reference. The distortions most likely to appear are described here with their detection signals.

**WHY:** Naming the specific distortion mechanism is what makes the calibration intervention effective. "You are overconfident" gives the learner nothing to act on. "Your confidence is driven by fluency illusion — ease of reading your notes is being mistaken for retrievable knowledge" gives the learner a specific mechanism to interrupt and a specific instrument to replace it with. Each distortion type requires a different correction instrument; a generic "study harder" recommendation will not work.

**Detection checklist — check each distortion:**

**Fluency Illusion**
Detection signal: Learner studies by rereading and reports that material "makes sense" or "is starting to click" during review — but struggles to recall it without the text.
Mechanism: Ease of processing a familiar text is experienced as mastery. The text is doing the cognitive work, not the learner's memory.

**Hindsight Bias (Knew-It-All-Along Effect)**
Detection signal: After seeing the correct answer, learner says "I knew that" or "I almost said that" — but did not produce the answer before seeing it.
Mechanism: Correct answers, once revealed, feel like they were always accessible. The learner retrospectively misremembers their prior uncertainty as near-knowledge.

**Dunning-Kruger Overconfidence**
Detection signal: Learner in early or intermediate stages of learning rates their competence as high relative to peers, but actual performance falls well below this rating. Learner is unaware of the skill dimensions they cannot yet perceive.
Mechanism: Incompetence in a domain also undermines the metacognitive ability to recognize incompetence. The same skill gap that limits performance also limits the ability to judge performance accurately.

**Curse of Knowledge**
Detection signal: Teacher or advanced learner assumes others can follow explanations that feel obvious to the explainer. Or learner who has just mastered a topic believes they could have learned it faster — underestimating past struggle.
Mechanism: Once knowledge is consolidated, the steps required to build it become invisible. The expert cannot reconstruct the novice's perspective.

**False Consensus**
Detection signal: Learner assumes classmates or peers share their level of understanding, and uses the absence of complaints as evidence that the material is clear.
Mechanism: Humans tend to assume others share their beliefs and understanding levels. Silence from peers reads as confirmation rather than as independent uncertainty.

**Imagination Inflation**
Detection signal: Learner has repeatedly rehearsed answering a question mentally (without actually retrieving the answer) and now feels confident they can answer it. Or learner has rehearsed an explanation in their head and treats mental rehearsal as equivalent to demonstrated performance.
Mechanism: Vividly imagining an event increases the likelihood that it will later be remembered as having actually occurred. Imagined retrieval does not build the same memory trace as actual retrieval.

**Social Memory Contamination**
Detection signal: Learner studied in a group and has absorbed peers' explanations, including incorrect ones, as their own understanding. Or learner's recall of material matches a group member's account rather than the source.
Mechanism: Memory conforms to social influence. One person's recalled version of material — including errors — can overwrite another person's memory of the original, especially in collaborative review settings.

**Output:** List each detected distortion with its mechanism and the specific evidence from the learner's context.

---

### Step 3: Select Calibration Instruments

**Action:** For each detected distortion, prescribe the calibration instrument most directly targeted at its mechanism. See `references/calibration-instruments.md` for the full instrument reference.

**WHY:** Calibration instruments work by replacing unreliable feedback (processing fluency, familiarity, social confirmation) with objective performance data that the learner cannot rationalize away. Each instrument is matched to the specific mechanism of a distortion — a self-quiz defeats fluency illusion by forcing retrieval instead of recognition, but it does not help with false consensus, which requires exposure to peer variation. Prescribing the wrong instrument for the distortion type wastes effort without improving calibration.

**Instrument-to-distortion matching:**

| Detected Distortion | Primary Instrument | Why It Works |
|---------------------|-------------------|--------------|
| Fluency Illusion | Self-quizzing (closed-book free recall) | Forces retrieval without text cues; processing difficulty signals actual memory gaps, not text unfamiliarity |
| Hindsight Bias | Pre-answer confidence logging | Recording confidence before seeing the answer makes the prior state of not-knowing concrete and non-revisable |
| Dunning-Kruger Overconfidence | Cumulative quizzing across topic areas | Exposes the full range of what is not yet known; reveals the dimensions of competence the learner cannot currently perceive |
| Curse of Knowledge | Peer teaching (explain to a naive listener) | Forces reconstruction of the knowledge from the novice's baseline; gaps in explanation reveal gaps in transferable knowledge |
| False Consensus | Peer instruction with divergent pairing | Deliberately pairing with peers who gave different answers exposes assumption that consensus already existed |
| Imagination Inflation | Actual practice tests (not mental rehearsal) | Replaces imagined performance with real performance; the difference between imagined and actual recall surfaces immediately |
| Social Memory Contamination | Solo closed-book retrieval before group review | Establishes a clean individual baseline before exposure to peer accounts; deviations from source material are visible |

**Instrument descriptions (summary):**

**Self-quizzing (closed-book free recall):** Set all study materials aside. Write, speak, or type everything you can recall about the topic without looking. Then check against the source. The gaps are your actual gaps.

**Cumulative quizzing:** Quiz that reaches back across all material covered — not just the most recent session — forcing retrieval of earlier material alongside new content. Use at each study session.

**Peer instruction:** Before solving a problem or answering a question, commit to an answer individually. Then discuss with a peer who chose differently. Each person argues their reasoning. The disagreement — not the final answer — is the calibrating event.

**Pre-answer confidence logging:** Before checking any answer, rate your confidence on a simple scale (1-5 or percentage likelihood). After checking, compare prediction to outcome. Patterns of high-confidence errors are the primary diagnostic signal.

**Peer teaching (explain to a naive listener):** Explain the concept to someone who does not know it — without notes. Track where the explanation breaks down, requires hedging, or produces confusion in the listener. These are the knowledge gaps.

**Output:** A prioritized list of instruments assigned to each detected distortion.

---

### Step 4: Design the Dynamic Testing Cycle

**Action:** Structure the learner's calibration correction as an iterative 3-step cycle that continues until predicted performance matches actual performance within an acceptable margin.

**WHY:** A one-time test and a one-time correction do not recalibrate the learner — they only reveal the gap at a single point in time. The dynamic testing cycle treats each test as a calibration instrument rather than a grade: it shows where expertise currently stands, redirects effort to underperforming areas, and then retests to measure whether the gap has closed. Repeating the cycle builds the metacognitive habit of using performance data to guide study, rather than feelings of fluency or familiarity.

**Cycle structure:**

**Step A — Assess (Baseline Test)**
Administer a performance test using the calibration instrument matched to the primary detected distortion. The test must be:
- Closed-book
- Conducted after a time gap from the last study session (minimum 24 hours for most material)
- Scored with a pre-answer confidence log if hindsight bias was detected

What to record: raw score, confidence-versus-accuracy pattern, and which specific items or sub-areas were missed.

**Step B — Identify Gaps and Redirect**
For each missed item, classify the gap type:
- Encoding gap: Information was never well encoded (did not understand it at study time)
- Retrieval gap: Information was encoded but cannot be retrieved (knew it once, lost it)
- Transfer gap: Information can be retrieved in isolation but cannot be applied to novel problems

Each gap type requires different practice:
- Encoding gap: Return to the source, study the concept more carefully, then re-encode using elaborative questioning ("why does this work?" "how does this connect to X?")
- Retrieval gap: More retrieval practice, with greater spacing between attempts
- Transfer gap: Practice on varied and unfamiliar problem types that use the same underlying concept

**Step C — Retest**
After targeted practice on the identified gaps, retest on the same topics — preferably using different question formats or novel problem instances to distinguish retrieval from memorization of specific items. Compare the pre-answer confidence log across test and retest.

**Retest calibration criterion:** Continue cycling until one of these conditions is met:
- Predicted confidence and actual scores differ by less than 10 percentage points on average
- Three consecutive retests show no new gap areas emerging
- Peer teaching attempt produces no listener confusion or unanswered questions

**Cycle schedule guidance:**
- Space retest at least 48-72 hours after targeted practice (not immediately after)
- For high-stakes preparation: run the full cycle at least 3 times across the study period
- Do not drop material from the cycle after one correct answer — review it at least one more time at a longer interval

---

### Step 5: Produce the Calibration Report

**Action:** Write a structured calibration report that consolidates the audit findings and serves as the learner's working document.

**WHY:** The report externalizes the calibration data — moving it from subjective feeling to an objective, reviewable record. Learners who have a written account of their distortions, their instruments, and their retest schedule are far less likely to drift back to unreliable study habits than those who receive only verbal advice. The report also creates accountability: at the next retest, the learner can compare predicted versus actual and update the record.

**Report structure:**

```
## Calibration Report: [Subject / Skill]

### Current Mastery Assessment
[Estimated actual mastery level based on reliable indicators: what the learner can do without study materials]

### Detected Distortions
For each distortion detected:
- Distortion: [Name]
- Evidence: [What the learner is doing that signals this distortion]
- Mechanism: [Brief explanation of why this produces false confidence]

### Prescribed Calibration Instruments
For each instrument assigned:
- Instrument: [Name]
- Targets: [Which distortion(s) it corrects]
- Instructions: [How to use it — what to do, when to do it]

### Dynamic Testing Cycle Plan
- Cycle 1 Baseline Test: [Date, instrument, scope]
- Gap Analysis: [How to classify and record gaps]
- Cycle 1 Retest: [Target date — minimum 48h after targeted practice]
- Cycle 2 Baseline Test: [Date]
- [Continue for 3+ cycles if high-stakes]

### Calibration Criterion
[Which criterion defines successful recalibration for this learner and subject]

### Red Flags to Watch For
[Conditions that would indicate calibration is not working — e.g., consistently high confidence despite low scores, dropping practice tests after apparent success]
```

---

## Inputs / Outputs

### Inputs
- Description of the subject or skill being studied (required)
- Description of current study methods and mastery-judging criteria (required)
- Quiz results, test scores, or self-assessment data (optional but valuable)
- Study materials or course outline (optional)

### Outputs
- List of unreliable mastery signals in use
- Detected cognitive distortions with mechanisms and evidence
- Prioritized calibration instrument recommendations matched to distortions
- Dynamic testing cycle schedule (3-step iterative protocol)
- Written calibration report with retest schedule

---

## Key Principles

**Feeling of knowing is not knowing.** The subjective sense that material is familiar or "making sense" during review reflects processing ease, not retrievable, transferable knowledge. The gap between what feels known and what can be retrieved without cues is where false confidence lives.

**The diagnostic instrument must bypass the unreliable signal.** Closed-book retrieval defeats fluency illusion because processing ease is no longer available as a signal. Peer teaching defeats curse of knowledge because the listener's confusion is not subject to rationalization. Match the instrument to the mechanism of the distortion.

**Dynamic testing is iterative by design.** A single calibration test is not sufficient. Each cycle of assess → identify gaps → targeted practice → retest updates the calibration. Three cycles across a study period is a minimum for high-stakes preparation.

**Incompetence impairs metacognition too.** The Dunning-Kruger effect means that the largest calibration gaps often occur at low competence levels, precisely where the learner is least equipped to detect them. External feedback — peer instruction, practice test scores, peer review — is most critical here.

**Reliable indicators require a time gap.** Immediate recall after a lecture or study session is not a reliable mastery indicator — the material is still in working memory. The meaningful test is whether it can be retrieved after a delay of at least 24 hours, when working memory has cleared.

---

## Examples

### Example 1: Law Student Before Bar Exam

**Context:** A law student feels confident about contract law — they have read the chapter three times and their notes are thoroughly highlighted. But a practice bar question on contracts leaves them unable to identify the correct legal standard.

**Step 1:** Unreliable signals: rereading fluency, highlighting coverage. Reliable signals absent: no delayed free recall, no novel problem practice.

**Step 2:** Fluency illusion (primary — rereading fluency mistaken for retrievable doctrine); Imagination inflation (studying by mentally rehearsing answers without actually producing them in writing).

**Step 3:** Self-quizzing (closed-book): Write out the elements of each contract doctrine from memory before opening notes. Pre-answer confidence logging: before each practice question, rate confidence 1-5 and record. Compare to actual score.

**Step 4:** Cycle 1 baseline — 15-question practice exam on contracts, closed-book, confidence logged. Gap analysis — which doctrine elements are encoding gaps vs. retrieval gaps. Cycle 1 retest — 48 hours later, different question set, same doctrines. Continue until confidence ratings and scores align within 10 points.

---

### Example 2: Corporate Training Cohort

**Context:** A trainer observes that trainees perform well during the training day (completing exercises correctly with the reference guide available) but report confusion when applying procedures in the field.

**Step 1:** Unreliable signals in use: passive recognition (exercises done with reference guide open), immediate recall (end-of-day quiz administered right after instruction). No delayed free recall, no novel application, no peer teaching.

**Step 2:** Fluency illusion (guide availability masks retrieval difficulty); Dunning-Kruger overconfidence (trainees in early learning stage overrate competence); False consensus (trainees assume peers' silence means shared understanding).

**Step 3:** Cumulative quizzing — weekly quiz reaching back across all procedures covered. Peer instruction — before demonstrations, trainees write their expected procedure independently, then compare with a partner who differed. Peer teaching — in pairs, trainees teach a procedure without the guide; the partner signals confusion points.

**Step 4:** Cycle 1 — closed-book procedural quiz one week post-training. Gap analysis — which procedures have encoding vs. retrieval vs. transfer gaps. Targeted practice — additional drills on gap procedures. Retest — same procedures in a novel scenario context two weeks later.

---

### Example 3: Self-Study Language Learner

**Context:** A language learner reports that vocabulary "feels solid" — recognition from flashcard reviews is high and they can follow podcasts well. But speaking and writing attempts reveal many words are not available for production.

**Step 1:** Unreliable signals: familiarity warmth (flashcard recognition), passive recognition (following podcasts). Reliable signals absent: no production-side practice, no delayed free recall, no peer teaching in the target language.

**Step 2:** Fluency illusion (recognition mistaken for production-ready knowledge); Social memory contamination (if studying in groups, may have absorbed peer corrections as own knowledge without independent consolidation).

**Step 3:** Closed-book production quizzing — cover the target word; write or speak only from the definition cue. Peer instruction — set a conversation exchange where neither participant can revert to their native language for a defined vocabulary set; communication breakdowns are calibration data.

---

## References

| File | Contents |
|------|----------|
| `references/cognitive-distortions.md` | Complete 7-distortion taxonomy with detection criteria, mechanisms, real-world examples, and false positive guards |
| `references/calibration-instruments.md` | Full instrument reference: self-quizzing, cumulative quizzing, peer instruction, peer teaching, confidence logging — with implementation steps and distortion coverage |

## License

This skill is licensed under [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/).
Source: [BookForge](https://github.com/bookforge-ai/bookforge-skills) — Make It Stick: The Science of Successful Learning by Peter C. Brown, Henry L. Roediger III, Mark A. McDaniel.

## Related BookForge Skills

This skill is standalone. Browse more BookForge skills: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

FILE:references/calibration-instruments.md
# Calibration Instruments Reference

Five evidence-based calibration instruments. Each entry includes: description, which distortions it targets, implementation steps, common mistakes, and frequency guidance.

---

## 1. Self-Quizzing (Closed-Book Free Recall)

**What it is:** A retrieval practice session conducted entirely without access to notes, textbooks, or reference materials. The learner produces everything they can recall on a topic — in writing, speech, or typed form — and then checks their output against the source.

**Distortions targeted:** Fluency Illusion (primary), Imagination Inflation (secondary), Social Memory Contamination (secondary)

**Why it works:** Fluency illusion depends on the presence of the text — ease of processing a familiar text is what creates the false signal of mastery. Remove the text and the signal disappears. The learner is left with what they can actually retrieve, which is the only mastery signal that predicts future performance on tests and real-world application. Imagination inflation is disrupted because the learner must produce actual output rather than simulate producing it. Social memory contamination is disrupted because individual recall, done before group review, establishes a clean baseline.

**Implementation steps:**
1. Set aside all study materials — close books, close notes, put away reference cards.
2. Set a timer for 10-15 minutes (enough time for extended recall but not so long that the session becomes demoralizing).
3. Write, speak, or type everything you can recall about the topic. Do not edit for quality — quantity of retrieval attempts matters more than polish.
4. After time is up, open your materials and check your output: What did you get right? What did you miss? What did you get wrong?
5. Mark the gaps. The items missed or produced incorrectly are your current retrieval gaps — not things you "sort of know" but items that need more encoding or more retrieval practice.
6. Do not immediately re-study the missed items and re-quiz yourself in the same session. The gap between recall attempt and re-study is what produces the learning benefit. Space the re-study by at least several hours, ideally the next day.

**Common mistakes:**
- Peeking at notes mid-session (invalidates the exercise — any reference to notes shifts the task back to recognition)
- Stopping after 2-3 minutes when recall feels exhausted (the productive retrieval often happens in the uncomfortable stretch after initial recall runs dry)
- Re-quizzing immediately after re-study (the quick success is transient — the meaningful test is after a delay)
- Using the exercise as a once-off rather than repeating it across multiple spaced sessions

**Frequency guidance:** Once per study session, after initial encoding. Repeat at the next session (spaced recall). For high-stakes material, continue at expanding intervals: 1 day, 3 days, 7 days, 14 days.

---

## 2. Cumulative Quizzing

**What it is:** A quiz that reaches back across all material covered to date — not just the most recent session — so that earlier content is retrieved alongside new content. The quiz accumulates scope as the learning progresses.

**Distortions targeted:** Dunning-Kruger Overconfidence (primary), Fluency Illusion (secondary)

**Why it works:** Dunning-Kruger overconfidence is partly a visibility problem — learners at low competence cannot perceive the full scope of what they do not know. Cumulative quizzing forces the learner into contact with the full range of knowledge their learning arc requires, making invisible gaps visible. Learners who quiz only on the most recent material feel confident because the recent material is still relatively accessible — cumulative quizzing reveals what has faded from earlier periods and what was never properly encoded in the first place.

**Implementation steps:**
1. At the start of each study session, before reviewing new material, administer a quiz that draws from ALL material covered so far.
2. Design the quiz to cover approximately 40-50% new material (from the most recent session) and 50-60% older material (from earlier sessions, in rough inverse proportion to how recently it was covered — older material should appear at least as often as recent material).
3. Do not adjust the mix based on comfort — include material that feels solid along with material that feels weak, to verify that confident items are genuinely retrievable.
4. Score and track performance by topic area, not just overall percentage. The topic-level breakdown is where the calibration data lives.
5. Use the topic-level performance map to guide the current session's study: devote more time to topics where performance is lagging.
6. Repeat at the next session, adding the current session's material to the cumulative pool.

**Application in instructional design (for trainers):**
- Design each class or module quiz to include at least 30% items from prior modules
- Track per-learner item-level accuracy across the cumulative pool to identify individuals whose confidence exceeds their performance
- Flag learners whose overall quiz confidence is high but whose accuracy on cumulative items from early modules is below 70% — this is a Dunning-Kruger calibration signal requiring targeted review

**Common mistakes:**
- Dropping items from the cumulative pool after one correct answer (one correct retrieval is not a mastery signal — material needs to be retrieved correctly after multiple spaced attempts before it can be retired from regular quizzing)
- Cumulating only correct-answer items (errors should stay in the pool at higher frequency until they are consistently correct)
- Using multiple-choice exclusively (recognition-format questions with provided answers partially reintroduce the fluency illusion; mix in open-answer formats)

**Frequency guidance:** Every study session. Never skip the cumulative component even when time is short — reduce the new-material portion rather than the cumulative portion if necessary.

---

## 3. Peer Instruction

**What it is:** A structured method in which learners commit to individual answers before discussing them with peers who chose differently, with the goal of defending their reasoning and understanding why disagreements exist.

**Distortions targeted:** False Consensus (primary), Dunning-Kruger Overconfidence (secondary)

**Why it works:** False consensus is an assumption — the learner presumes others share their understanding because they have not tested whether they do. Peer instruction makes the assumption testable: when learners commit to individual answers and then compare, divergence from peers reveals that consensus was not actually present. The discussion process — explaining your reasoning to someone who reached a different conclusion — requires explicit articulation of the knowledge, which surfaces gaps that private review cannot expose. For Dunning-Kruger, exposure to more competent peers' reasoning provides the exemplar needed to recalibrate the learner's self-assessment.

**Implementation steps:**
1. Present the question or problem to the group. Instruct everyone to commit to an individual answer — write it down or select it — without discussing with others first.
2. Reveal the distribution of answers (via a show of hands, polling tool, or similar) without yet revealing which answer is correct.
3. Pair each learner with someone who chose a different answer. If unanimous agreement, use a harder question or ask each learner to generate the strongest argument against their own answer.
4. Pairs discuss: each person explains the reasoning behind their answer without capitulating immediately to the other. The goal is to understand the difference in reasoning, not to win.
5. After discussion, re-poll. Note whether and how the distribution shifted.
6. Reveal the correct answer and address the most common reasoning errors. Where the most confident learners were wrong, use this as an explicit calibration event.

**The calibration event:** When a learner who was certain of their answer discovers they were wrong — and discovers that a less confident peer had the right reasoning — this is the highest-value calibration event in peer instruction. It directly demonstrates that confidence is not accuracy.

**For self-directed learners without peers:** Use pre-answer confidence logging (Instrument 4) as a substitute for the peer comparison step. The comparison between your confidence before and your accuracy after serves the same function as encountering a peer who chose correctly.

**Common mistakes:**
- Skipping individual commitment before discussion (allows free-riding on the group's intelligence without calibration)
- Pairing learners who already agree (the value is in the disagreement — same-answer pairs produce no calibration)
- Revealing the correct answer before adequate discussion (short-circuits the reasoning process and triggers hindsight bias)
- Treating peer consensus as the correct answer (the group can be unanimously wrong — the correct answer must come from the subject itself, not from majority vote)

**Frequency guidance:** Use at each study group session, or at least for the questions that cover the most conceptually important material in a unit.

---

## 4. Pre-Answer Confidence Logging

**What it is:** Before answering any question or attempting any retrieval, the learner rates their confidence that their answer will be correct. After checking the answer, they compare confidence to actual accuracy. Over many items, the pattern of high-confidence errors is the primary calibration signal.

**Distortions targeted:** Hindsight Bias (primary), Fluency Illusion (secondary), Dunning-Kruger Overconfidence (secondary)

**Why it works:** Hindsight bias is a memory revision — once the correct answer is seen, the prior state of not-knowing is overwritten. Pre-answer confidence logging creates an objective, non-revisable record of the prior state. A learner who logs confidence 5/5 before an answer, gets the answer wrong, and sees this pattern repeated across multiple items cannot rationalize the gap as "I almost knew it." The log is the evidence.

**Implementation steps:**
1. Before answering any quiz question or recall prompt, record your confidence that your answer will be correct. Use a simple scale:
   - 1 = Guessing
   - 2 = Low confidence, may have something
   - 3 = Moderate confidence, think this is probably right
   - 4 = High confidence, fairly sure
   - 5 = Very high confidence, certain
2. Write the answer.
3. Check the answer against the source. Record whether you were correct.
4. After the full session, calculate your accuracy within each confidence band:
   - Of all the items I rated 5/5, what percentage did I get right?
   - Of all the items I rated 4/5?
   - And so on.
5. A well-calibrated learner shows a strong correlation between confidence band and accuracy (5/5 confidence = ~80-90% accuracy, 1/5 = ~20% accuracy). A miscalibrated learner shows high accuracy in the 1-3 range (items they thought were uncertain are actually solid) and low accuracy in the 4-5 range (items they felt certain about are not retrievable).
6. Use the miscalibration pattern to identify which topics are affected by specific distortions.

**Interpreting the patterns:**

| Pattern | Likely Distortion | Action |
|---------|------------------|--------|
| High confidence, low accuracy (mostly on recent material) | Fluency Illusion | Switch to closed-book recall; stop rereading |
| High confidence, low accuracy (across all material stages) | Dunning-Kruger Overconfidence | Seek external performance benchmarks; use peer instruction |
| Low confidence, high accuracy | Accurate knowledge without self-trust (not a distortion problem) | Recalibrate upward; this is a confidence deficit, not a knowledge deficit |
| High confidence on items revealed to be wrong, post-hoc "I knew it" | Hindsight Bias | Pre-logging itself is the intervention; maintain the log discipline |

**Common mistakes:**
- Rating confidence after writing the answer (defeats the purpose — the answer generation activates retrieval cues that inflate confidence)
- Rounding all confidence ratings to 4 or 5 to avoid the discomfort of uncertainty (creates an uninformative log — any pattern of high confidence will look the same)
- Not tracking confidence by topic area (overall accuracy hides which topic areas are most miscalibrated)

**Frequency guidance:** Use on every practice test or self-quiz session. Minimum 10 items needed to detect a pattern.

---

## 5. Peer Teaching (Explain to a Naive Listener)

**What it is:** The learner explains a concept or procedure, without notes, to someone who does not know it. The listener's confusion, questions, and inability to follow are the calibration data.

**Distortions targeted:** Curse of Knowledge (primary), Fluency Illusion (secondary)

**Why it works:** The curse of knowledge makes the explainer's internal access to the knowledge feel like evidence that others can access it too. The listener's actual responses — confusion, missed inferences, questions about steps that felt obvious — provide external feedback that is immune to the explainer's rationalizations. A learner who cannot get their explanation to produce understanding in a naive listener has discovered a gap between what they know and what they can transfer. That gap is the calibration signal.

**Implementation steps:**
1. Select the listener — someone who does not know the material. A classmate from a different subject area, a friend, a family member, or (if none available) a hypothetical naive reader whose questions you must anticipate in writing.
2. Explain the concept without consulting notes. The listener may ask questions; field them as fully as possible without reference materials.
3. After the explanation, the listener rates (on a simple 1-5 scale) whether they feel they understood the concept and whether the explanation covered all the steps they needed.
4. Identify the points where the explanation broke down: where did the listener become confused, ask for clarification, or remain unconvinced?
5. These breakdown points are encoding or transfer gaps. The learner who cannot explain a concept clearly enough for a naive listener to follow it does not yet have transferable mastery, regardless of how fluent they feel with the material themselves.
6. Return to the source material to address the gap, then attempt a second explanation (to the same or a different listener) after targeted re-study.

**For solo learners without access to a peer:** Write the explanation as if writing to a curious friend who knows nothing about the subject. Every place where you cannot write a clear sentence — where you find yourself writing "it's hard to explain" or "you'd have to know X" — is a gap. The absence of a listener does not eliminate the calibration data; the gaps in the explanation are still visible in the written output.

**Common mistakes:**
- Using a listener who already knows the material (eliminates the calibration — the listener fills in the gaps without signaling them)
- Consulting notes during the explanation (bypasses the retrieval requirement)
- Attributing listener confusion to "they're not getting it" rather than "my explanation has a gap" (the explanation must be corrected, not the listener)
- Treating a successful first explanation as a permanent mastery signal (the ability to explain decays like other memory unless practiced; re-teach after intervals)

**Frequency guidance:** At least once per major topic or concept cluster. Repeat after study gaps longer than two weeks to verify that the ability to transfer knowledge has persisted.

FILE:references/cognitive-distortions.md
# Cognitive Distortions Taxonomy

Seven named distortions that produce false confidence in learning mastery. Each entry includes: definition, mechanism, detection signals, real-world example, and false positive guard.

---

## 1. Fluency Illusion

**Definition:** Processing ease with a familiar text or task is mistaken for possession of retrievable knowledge.

**Mechanism:** When we reread material, repeated exposure reduces the cognitive effort needed to process it — the words become smoother, comprehension feels easier. This reduced effort is experienced as mastery, but it reflects the text's familiarity, not the learner's independent recall ability. The learner is essentially leaning on the text as a cognitive scaffold without noticing they're doing so. Remove the text and the performance collapses.

**Detection signals:**
- Learner studies primarily by rereading
- Learner describes understanding as "it makes sense when I read it"
- Learner's performance drops significantly when tested without reference to notes
- Highlights or underlines thoroughly but cannot reproduce core ideas in writing
- Mistakenly believes that a clear, well-written explanation means they know the content

**Real-world example:** Students who reread a chapter three times before an exam feel confident going in, but blank on questions that require them to apply or explain — rather than recognize — the content. Research on this pattern shows that students who reread consistently overestimate how well they will perform on tests compared to students who self-quiz.

**China Airlines 006 connection:** The flight crew had trained for many procedures, including engine restarts, but when the emergency unfolded in an unexpected configuration, their fluency with the checklist did not translate into correct application under stress. Knowing a procedure on paper is not the same as having it available for retrieval and application under novel conditions.

**False positive guard:** A learner who reports material "makes sense" may have genuine comprehension — especially for new conceptual material on first pass. Fluency illusion is indicated when the learner's primary ongoing study method is rereading and they have not tested retrieval without cues.

---

## 2. Hindsight Bias (Knew-It-All-Along Effect)

**Definition:** After learning the correct answer, learners revise their memory of prior uncertainty upward — they remember themselves as having "almost known" or "suspected" the answer, even when they did not produce it.

**Mechanism:** Correct answers, once seen, become retroactively available in memory. The brain incorporates the answer into its representation of the prior state, making the prior state of not-knowing harder to access. This prevents accurate learning from errors: if the learner retrospectively misremembers a gap as near-knowledge, they underestimate how much work the gap requires.

**Detection signals:**
- Learner frequently says "I knew that" or "I almost said that" when answers are revealed
- Learner's confidence rating before seeing answers would be higher than their accuracy suggests (hypothetical)
- Learner treats immediate recognition of an answer (when revealed) as evidence that they could have produced it
- Learner underestimates difficulty of past material after mastering it

**Real-world example:** After reading that John F. Kennedy Jr.'s plane crash was attributed to spatial disorientation, observers say "Of course — flying at night in haze without instruments is obviously dangerous." Before the crash, the risk was not obvious to JFK Jr., the FAA, or the passengers. Hindsight transforms a probabilistic tragedy into an apparent inevitability.

**False positive guard:** "I knew that" sometimes reflects genuine prior knowledge rather than hindsight revision. The indicator is pattern-level: a learner who consistently reports near-knowledge on items they did not produce in advance is likely exhibiting hindsight bias, not genuine prior mastery.

---

## 3. Dunning-Kruger Overconfidence

**Definition:** Learners in the early or intermediate stages of skill acquisition overestimate their competence because the metacognitive skills needed to accurately assess competence in a domain are themselves a product of expertise in that domain.

**Mechanism:** Competence in a field includes the ability to recognize quality, detect errors, and make comparative judgments of performance. Novices lack all three. A novice who cannot recognize a correct answer also cannot accurately gauge the distance between their current performance and a competent standard. They rate themselves as more competent than they are not because of arrogance but because they lack the perceptual tools to see the gaps. As competence increases, the learner begins to perceive the full complexity of the domain and their confidence often temporarily decreases before rising again on a more accurate foundation.

**Detection signals:**
- Learner rates their competence well above their actual tested performance
- Learner does not improve their self-assessment after exposure to higher-quality exemplars or peer performance
- Learner is in an early stage of learning but expresses confidence comparable to intermediate or advanced practitioners
- Negative feedback does not update the learner's self-rating

**Research basis:** Dunning and Kruger showed that students who scored in the 12th percentile on logic tests rated their ability at the 68th percentile on average. Crucially, exposing low performers to the correct answers of high performers did not improve their self-assessment accuracy — they lacked the ability to use the high-quality exemplar as a calibration benchmark. Only targeted skills training (learning how to evaluate the logic of an argument) enabled accurate self-assessment.

**False positive guard:** High confidence is not itself a signal of Dunning-Kruger. Some high-confidence learners are genuinely competent. The indicator is the combination of high confidence AND poor actual performance AND the absence of self-correction when feedback is provided.

---

## 4. Curse of Knowledge

**Definition:** Learners or teachers who have mastered a subject underestimate how long it took them to learn it and overestimate how readily a novice will follow their explanations.

**Mechanism:** As knowledge is consolidated, the component steps that built it fade from working access. The expert no longer reconstructs the path to the answer — they simply see the answer. This makes it nearly impossible to accurately model the novice's experience. The expert's explanation skips steps that are now invisible to them but are critical to the novice. The expert also underestimates the amount of practice that built their own current fluency.

**Detection signals:**
- Teacher or advanced learner is surprised that students cannot follow an explanation that seems obvious
- Learner who recently mastered material believes they could have learned it faster than they did
- Explainer skips intermediate steps without realizing it
- Explanations receive confused responses that the explainer does not predict
- Teacher cannot identify which part of an explanation the student is stuck on

**Real-world example:** Physics professors find it harder than graduate students to explain introductory concepts — because the professor has long since forgotten what it is like not to understand Newton's laws as a single unified framework. Graduate students, closer to their own learning experience, can identify the stumbling blocks more accurately.

**Tapping experiment:** In a controlled study, one participant tapped the rhythm of a well-known song while another guessed the song from the taps alone. The tapper estimated the listener would guess correctly 50% of the time; actual success rate was 2.5%. The tapper could hear the melody in their head and could not imagine the listener not hearing it.

**False positive guard:** Poor teaching is not always caused by the curse of knowledge. If a teacher doesn't know the material well enough themselves, that is an encoding or retrieval gap, not a curse-of-knowledge problem. The distortion applies specifically to material the teacher/learner genuinely knows well.

---

## 5. False Consensus

**Definition:** Learners (and teachers) assume that others share their level of understanding or confusion, leading them to treat the absence of peer complaints as confirmation of their own comprehension level.

**Mechanism:** Humans systemically underestimate the idiosyncratic nature of their own perspective. When we understand something, we perceive that understanding as the natural outcome of encountering the material — and assume others who encountered the same material share our understanding. When we are confused, we may assume others must be equally confused (and therefore that the material is simply hard), or we assume others understand and stay silent to avoid appearing incompetent. Both patterns prevent accurate self-calibration.

**Detection signals:**
- Learner uses "we all found that confusing" or "everyone understands this part" as self-assessment signals
- Learner does not test their understanding against peers' actual responses — only against their assumption of peers' responses
- Learner in a group study session agrees with the group's summary without independently verifying their own recall
- Student assumes that because classmates don't ask questions, the class collectively understands — and by extension, so do they

**False positive guard:** Consensus can be a genuine calibration signal if it is based on actual peer performance data (quiz scores, peer instruction responses). The distortion occurs specifically when consensus is inferred from social silence rather than from observed peer performance.

---

## 6. Imagination Inflation

**Definition:** Vividly imagining performing a task — solving a problem, delivering a presentation, recalling information — produces a false sense that the actual performance has been practiced or confirmed.

**Mechanism:** The brain's memory systems do not reliably distinguish between remembered events and vividly imagined events. When we mentally rehearse answering a question, some of the same neural processing occurs as when we actually answer it — but without the performance feedback (was the answer correct? what exactly was recalled?) that actual retrieval would provide. The subjective experience of the mental rehearsal — "I can imagine doing this clearly" — is mistaken for evidence that the underlying performance is ready.

**Detection signals:**
- Learner describes study as "going over it in my head" or "mentally reviewing the material"
- Learner feels prepared for a presentation or performance because they have "rehearsed it mentally"
- Learner has imagined answering exam questions but not actually attempted them in writing or speech
- Learner's confidence increases after mental review sessions despite no new retrieval practice having occurred

**Research basis:** Adults asked whether they had ever broken a window with their hand were more likely on a later inventory to report the event occurred during their lifetime if they had been asked to vividly imagine it. Mental simulation of an event increases its apparent truth. Applied to learning: imagined retrieval produces the feeling of mastery without its substance.

**False positive guard:** Mental rehearsal is not inherently valueless — it can support procedural sequencing and anxiety management. The distortion occurs when mental rehearsal substitutes for actual performance rather than supplementing it.

---

## 7. Social Memory Contamination

**Definition:** Learners who study or review in groups absorb peers' accounts of material — including their errors — into their own memory, which then replaces their original encoding of the source material.

**Mechanism:** Memory is reconstructive and social. When a group member recalls a detail of shared material, that account enters the listener's memory as an additional version of the event. If the group member's version conflicts with the learner's original encoding, the social version tends to win — especially if the group member is perceived as confident, knowledgeable, or simply spoke first. The learner later retrieves the socially-constructed account believing it to be their own independent recollection of the source.

**Detection signals:**
- Learner's recall of material closely matches a peer's explanation rather than the original source
- Learner studies primarily through group discussion and review sessions
- Learner is unable to clearly identify which parts of their understanding came from their own reading versus group discussion
- Errors in the learner's recall match errors made by a group member during review

**Real-world example:** A study group reviewing a historical timeline agrees on an incorrect date that one member confidently stated. Later, all members "remember" the incorrect date, each believing it came from their own reading of the original material.

**Donald Thomson case:** An Australian psychologist was arrested for a rape he could not have committed. The victim's description of her attacker precisely matched Thomson — whom she had been watching on television during the rape. Her System 1 gave the police a description drawn from social (media) exposure, not from the actual event. Social-origin memories are experienced as indistinguishable from direct-experience memories.

**False positive guard:** Group study that produces genuine clarification of misunderstanding — where one member's correct recall updates another member's error — is a beneficial form of social memory update, not contamination. Contamination is indicated when group accounts override correct source encodings with incorrect ones.

---
name: growth-mindset-and-deliberate-practice
description: |
  Diagnose fixed vs growth mindset patterns and design a deliberate practice protocol for expertise development. Use when someone wants to develop expertise in a skill domain, is struggling to improve despite repeated practice, attributes their performance plateau to talent limits, praises or criticizes someone for being a "natural," says "I'm just not good at this," avoids challenges to protect their reputation, or asks how to get to 10000 hours effectively. Applies Dweck's 4-quadrant model (fixed/growth mindset × performance/learning goal orientation) to classify the learner's current stance, identifies fixed-mindset signals and attribution patterns, then designs a deliberate practice plan using Ericsson's 5 characteristics. Growth mindset is the prerequisite — without it, deliberate practice collapses into avoidance. Together they form a complete talent vs effort expertise-building pathway. Produces: mindset diagnostic report + deliberate practice plan with feedback loops, mental model targets, and practice structure.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/make-it-stick/skills/growth-mindset-and-deliberate-practice
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: draft
source-books:
  - make-it-stick
chapters: [4, 7, 8]
tags:
  - learning-science
  - cognitive-psychology
  - evidence-based-learning
  - growth-mindset
  - deliberate-practice
  - expertise
depends-on: []
execution:
  tier: 1
  mode: hybrid
  inputs:
    - type: conversation
      description: "Learner's domain, current performance level, and responses to difficulty or failure"
    - type: none
      description: "Skill can run from a brief description of the learner's situation"
  tools-required: [TodoWrite]
  tools-optional: [Read, Grep]
  environment: "Works from any context; richer input produces more specific output"
---

# Growth Mindset and Deliberate Practice

## When to Use

Use this skill when you are working with a learner who:
- Has **plateaued in a skill domain** despite repeated effort — improvement has stalled
- **Attributes failure to fixed ability** — "I'm not talented enough," "some people just have it"
- **Avoids challenging practice** — sticks to tasks they can already perform well
- **Praises or blames innate traits** — calls someone a "natural" or says they "just don't have the gift"
- **Wants to build expertise** — is asking how to reach mastery, or wondering if 10,000 hours is real
- **Shows test anxiety or fear of failure** — avoids difficulty because struggling feels like evidence of inadequacy

Preconditions: you need at minimum:
- The **domain** in which the learner wants to develop expertise (music, coding, writing, athletics, etc.)
- At least one signal about how they **respond to difficulty** (do they persist, retreat, blame themselves?)

**Agent:** Before starting, confirm you have enough to place the learner on the 4-quadrant model. If domain and failure-response are both unknown, ask for them before proceeding.

## Context and Input Gathering

### Input Sufficiency Check

```
User message → Extract domain + difficulty-response signals
                    ↓
Environment → Scan for past performance descriptions, stated goals, praise language
                    ↓
Gap analysis → Can I place the learner on the 4-quadrant model?
                    ↓
     Both domain and response missing? ──YES──→ ASK (one question)
                    │
                    NO
                    ↓
              PROCEED with diagnosis
```

### Required Context

- **Domain:** What skill or field is the learner trying to develop?
  → Check prompt for: named subject, profession, activity, "get better at X"
  → If missing, ask: "What domain or skill are you trying to develop expertise in?"

- **Response to difficulty:** How does the learner react when they fail, struggle, or hit a plateau?
  → Check prompt for: attribution language ("not talented," "just practicing"), avoidance signals, help-seeking
  → If missing, ask: "When you hit a setback in this area — something you tried and failed at — what do you typically do or think?"

### Observable Signals (extract from description)

- **Attribution patterns:** Does failure trigger "I'm not capable" (fixed) or "I need a better strategy" (growth)?
- **Challenge selection:** Does the learner pick tasks at the edge of current ability, or stay in the comfort zone?
- **Praise language used:** Do they praise or admire innate talent in others? Do they describe their own successes as "natural"?
- **Effort theory:** Do they believe that needing to work hard is evidence of lesser ability?

### Default Assumptions

- If no difficulty-response is given: assume the learner has some fixed-mindset patterns (most adults do, especially in domains where they received intelligence-based praise as children).
- If domain is unspecified but expertise-building language is present: treat domain as TBD and note that the practice design will need it.
- If no current level is given: assume early-to-intermediate learner who has some foundation but has not yet invested hundreds of hours in deliberate solo practice.

## Process

Use `TodoWrite` to track all steps before beginning.

```
TodoWrite([
  { id: "1", content: "Gather learner domain and difficulty-response signals", status: "pending" },
  { id: "2", content: "Classify on the 4-quadrant mindset model", status: "pending" },
  { id: "3", content: "Identify fixed-mindset signals and attribution patterns", status: "pending" },
  { id: "4", content: "Design deliberate practice protocol using 5 characteristics", status: "pending" },
  { id: "5", content: "Set up feedback loops and coach/peer review structure", status: "pending" },
  { id: "6", content: "Produce mindset diagnostic report + deliberate practice plan", status: "pending" }
])
```

---

### Part A: Mindset Diagnostic

---

#### Step 1: Gather Difficulty-Response Signals

**ACTION:** Collect data on how the learner responds to failure, setbacks, challenge selection, and praise — across at least three different contexts if available.

**WHY:** Mindset is not a stable trait — it is a pattern of attributions that shows up most clearly under pressure. A learner who expresses enthusiasm for growth when relaxed may revert to fixed-mindset behavior the moment they fail publicly. The signal that matters is the *response to failure*, not the stated belief about ability. Dweck's research consistently showed that behavior under adversity, not self-report, is the diagnostic indicator.

**Detection signals to look for:**

| Signal | Mindset indicator |
|--------|-------------------|
| "I'm just not a math person" | Fixed — ability is a stable, inherited trait |
| "I wasn't born with musical talent" | Fixed — innate endowment, not accumulated skill |
| "That mistake tells me what to work on next" | Growth — failure is information |
| "He's a natural — it comes easily to him" | Fixed praise frame — attributes success to gift, not effort |
| "I worked hard and it paid off" | Growth attribution — effort caused outcome |
| "I avoided the competition because I might embarrass myself" | Fixed + performance goal — protecting reputation |
| "I picked an easier problem so I'd look competent" | Fixed + performance goal — validation seeking |
| "I stayed up late drilling the hard parts" | Growth + learning goal — effort toward mastery |

**Agent:** Extract these signals explicitly from the learner's description. Note both what the learner *says* about ability and what their *behavior* reveals. These often diverge.

Mark Step 1 complete in TodoWrite.

---

#### Step 2: Classify on the 4-Quadrant Model

**ACTION:** Place the learner in one of four quadrants formed by two axes: **Mindset** (Fixed ↔ Growth) and **Goal Orientation** (Performance goal ↔ Learning goal).

**WHY:** Mindset and goal orientation are related but distinct. A person can believe their abilities are fixed and still pursue learning goals (they just won't persist when it gets hard). A person can hold a growth mindset but be trapped in performance goals (they know effort builds ability, but social comparison dominates). The combination determines both *what behavior you will see* and *which intervention addresses the root cause*. Treating a performance-goal problem with a mindset intervention alone, or vice versa, produces partial results.

**The 4-Quadrant Model:**

```
                   LEARNING GOAL
                   (build mastery)
                        │
  Fixed Mindset ────────┼──────── Growth Mindset
  (ability fixed)       │         (ability grows)
                        │
                 PERFORMANCE GOAL
                 (validate ability)
```

**Quadrant descriptions:**

| Quadrant | Mindset | Goal | Behavior pattern | Risk |
|----------|---------|------|-----------------|------|
| Q1: Growth + Learning | Growth | Learning | Seeks challenges, interprets failure as data, persists on hard problems | Low — this is the target state |
| Q2: Fixed + Learning | Fixed | Learning | Studies hard but collapses when effort does not produce results; may believe effort is pointless if "not talented" | Moderate — effort theory intervention needed |
| Q3: Fixed + Performance | Fixed | Performance | Avoids challenge, chooses easy tasks, quits when failure threatens self-image | High — most resistant to change |
| Q4: Growth + Performance | Growth | Performance | Persists through difficulty but is driven by comparison and validation; may be demotivated without external feedback | Moderate — goal reframing needed |

**Classify the learner** based on their signals. Note which quadrant and cite the specific signals that placed them there.

**Examples:**

- A fifth-grader praised repeatedly for being "so smart" who now picks easier puzzles to protect their reputation → Q3 (Fixed + Performance). The praise itself caused the shift.
- A musician who says "I'm not naturally talented, but I practice every day and always pick the hardest passages to drill" → Q1 (Growth + Learning). Already in target state; reinforce.
- A developer who knows that "anyone can learn to code with effort" but only takes projects where they already know the answer → Q4 (Growth + Performance). Growth mindset is present; goal reorientation needed.

Mark Step 2 complete in TodoWrite.

---

#### Step 3: Identify Fixed-Mindset Signals and Attribution Patterns

**ACTION:** Surface the specific fixed-mindset traps and errorless-learning myths that are limiting this learner. Name the attribution pattern (what the learner says causes failure) and the intervention it calls for.

**WHY:** Fixed mindset manifests in predictable patterns, but the surface behavior varies. A star athlete who avoids practice because "naturals shouldn't need it" and a student who quits after one bad grade are both showing fixed-mindset behavior — but the intervention differs. Naming the specific pattern matters because growth-mindset interventions work by directly contradicting the attribution: you cannot change a belief you have not identified. Dweck's 7th-grade intervention succeeded precisely because it gave students a *specific reframe* ("effort forms new neural connections") rather than a vague pep talk.

**Fixed-mindset traps to detect:**

1. **Natural talent trap:** "Real experts don't need to work hard. If I have to struggle, I don't have what it takes." This leads to avoidance of the very practice that builds expertise.
   - Intervention: Show that Michelangelo's Sistine Chapel required four torturous years; Mozart's reconstructive memory was the product of acquired skill, not sixth sense.

2. **Errorless learning myth:** "If I'm making mistakes, the practice isn't working." This causes learners to stay in the comfort zone, doing what they can already do — which does not build new capabilities.
   - Intervention: Errors are essential feedback. Deliberate practice requires striving *beyond* current level; mistakes signal you are practicing in the right zone.

3. **Effort-equals-inability belief:** "Smart people don't need to try. My need for effort proves I'm not intelligent."
   - Intervention: Effortful learning changes the brain — myelination of relevant axons, formation of new synaptic connections, hippocampal neurogenesis. Effort is the mechanism, not the evidence of limitation.

4. **Test-anxiety loop:** Fear of failure consumes working memory capacity needed to perform, causing worse outcomes, which confirms the fear. Students with this pattern expend working memory monitoring their performance ("Am I making mistakes?") rather than solving problems.
   - Intervention: Teach that difficulty is expected and productive. A French study found that sixth graders taught "errors are a natural part of learning" showed significantly better working memory use on subsequent tests.

5. **Performance-goal trap:** Choosing challenges calibrated to showcase existing ability, not to build new ability. This delivers short-term validation but zero expertise growth.
   - Intervention: Reframe the measure of success from "did I look competent?" to "did I encounter and resolve something I couldn't do before?"

**Output:** A short list of detected traps with the specific signals that revealed each one, and the reframe each trap calls for. This is the input to the growth-mindset intervention (presented to the learner) and to Step 4 (used to calibrate practice zone).

Mark Step 3 complete in TodoWrite.

---

### Part B: Deliberate Practice Design

---

#### Step 4: Design Practice Protocol Using 5 Characteristics

**ACTION:** Structure a practice plan that satisfies all five characteristics of deliberate practice as defined by Ericsson's research.

**WHY:** Mere repetition is not deliberate practice. Most learners who plateau are repeating what they can already do — reinforcing existing capability without extending it. Ericsson's research on experts across chess, music, sports, medicine, and science found that expert performance is the product not of innate gifts but of the quantity and quality of practice. Crucially, the *quality* dimension is not met by simple repetition; it requires a specific structure. Expertise is built layer by layer, through thousands of hours of this specific structure — not through general experience or logging time.

**The 5 Characteristics of Deliberate Practice:**

1. **Goal-directed:** Each session targets a specific, identified weakness or skill gap — not general improvement.
   - *How to apply:* Before each session, name the one thing being improved. "Today I am working on X" — where X is specific enough that at the end you can say whether you improved it.
   - *Why this matters:* Without a target, practice defaults to what the learner is already good at. The difficulty of identifying specific weaknesses is itself a form of metacognitive work that accelerates learning.

2. **Striving beyond current level:** Practice should be just beyond current competence — difficult enough to produce errors and require effort, not so difficult as to be overwhelming.
   - *How to apply:* Use the "struggle zone" — find the point where the learner succeeds roughly 50-70% of the time. If success rate is above 80%, increase difficulty. If below 40%, reduce it.
   - *Why this matters:* Success at already-mastered tasks produces fluency but not new capability. The neural rewiring, myelination increases, and mental model expansion that characterize expertise development happen in response to striving, failure, and correction — not to smooth performance.

3. **Feedback loops:** Immediate, accurate feedback on each attempt, enabling correction before errors become habits.
   - *How to apply:* Identify the feedback source — a coach, a peer reviewer, a scoring system, audio/video self-review. Define at what granularity feedback will arrive (per attempt, per session, per week). See Step 5 for structure.
   - *Why this matters:* Without feedback, a learner cannot distinguish effective from ineffective technique. Practice without accurate feedback may reinforce the wrong patterns, making expert performance harder to reach, not easier. Deliberate practice usually requires a coach or trainer who can identify performance gaps the learner cannot see from the inside.

4. **Solitary and sustained:** A significant portion of deliberate practice should be individual, focused, and uninterrupted — not social, performance-oriented, or diluted by multitasking.
   - *How to apply:* Reserve dedicated time blocks (minimum 60-90 minutes) for solo deliberate practice sessions, separate from performance contexts. Ericsson found the best experts spent the largest percentage of their total hours in solitary, deliberate practice.
   - *Why this matters:* Social practice contexts introduce performance pressures (avoid looking bad) that conflict with the error-seeking behavior required for skill extension. Solitary practice enables the learner to deliberately put themselves in situations they cannot yet handle.

5. **Mental model accumulation:** Over time, deliberate practice builds a library of complex mental models — patterns for action in a vast vocabulary of situations — that is the substrate of expert judgment.
   - *How to apply:* After each practice session, name the new pattern or case type encountered. Maintain a running catalog of mental models in the domain (e.g., for a chess player: board configurations; for a programmer: algorithm patterns; for a writer: sentence structures). Review and extend this catalog periodically.
   - *Why this matters:* Expert performance is not faster reflexes — it is richer pattern recognition. A chess master can contemplate many alternative moves and their cascading consequences because they have accumulated a vocabulary of board configurations. The goal of deliberate practice is to build this vocabulary, not merely to log hours. Ten thousand hours of low-quality repetition does not produce this; ten thousand hours of deliberate practice does.

**Practice Protocol Template:**

```
Domain: [field]
Current level: [brief description]
Primary weakness being targeted: [specific gap, from Step 3]

Session structure:
- Duration: [minimum 60-90 min uninterrupted]
- Warm-up: [brief review of prior session's patterns]
- Core work: [specific drill or task targeting weakness, at struggle-zone difficulty]
- Error capture: [note every failure and what it revealed]
- Pattern cataloging: [add any new mental model to running catalog]
- Feedback: [when and how, from whom or what — see Step 5]

Weekly cadence:
- [N] solo deliberate practice sessions per week
- [N] performance/application sessions per week (separate — not deliberate practice)
- [N] feedback review sessions per week

Difficulty progression:
- Increase difficulty when: success rate > 70% for two consecutive sessions
- Reduce difficulty when: success rate < 40% for one session
```

Mark Step 4 complete in TodoWrite.

---

#### Step 5: Set Up Feedback Loops and Coach/Peer Review

**ACTION:** Define who provides feedback, at what frequency, at what level of granularity, and how that feedback connects back to practice design revision.

**WHY:** Feedback is not merely motivating — it is *calibrating*. Deliberate practice without accurate feedback can consolidate incorrect technique, build the wrong mental models, and create confident incompetence. Ericsson's research showed that expert performers who reach the highest levels almost universally worked with coaches or trainers who could identify problems the performer could not perceive from within their own practice. The learner's internal model of their own performance is systematically biased — they cannot see what they cannot yet see. External feedback closes this perceptual gap.

**Feedback structure to design:**

| Feedback type | Source | Frequency | Granularity |
|---------------|--------|-----------|-------------|
| Immediate corrective | Coach, scoring system, peer reviewer | Per attempt or per session | Specific technique: "your fingering on bar 12 is incorrect," not "play better" |
| Pattern-level | Self-review (audio/video) + coach | Weekly | Which error types keep recurring — targets for next week's practice |
| Progress tracking | Objective performance metrics | Monthly | Are measurable outcomes improving at a rate consistent with deliberate practice investment? |
| Mental model check | Coach interview or self-quiz | Monthly | Can the learner articulate the pattern they encountered this week in their domain's vocabulary? |

**If a coach is unavailable:**
- Use video or audio self-review with a specific checklist of technique dimensions
- Find a peer at slightly higher skill level who can provide corrective feedback in exchange for reciprocal review
- Use scoring systems with granular breakdowns (not just pass/fail — specific component scores)
- Document every error in writing immediately after it occurs, with a hypothesis about cause

**Feedback-to-practice cycle:**

```
Session → Error capture → Pattern identification → Practice target update
    ↑                                                         │
    └─────────────────────────────────────────────────────────┘
```

The feedback loop is not complete until the feedback *changes the next session's target*. Feedback that is absorbed but not acted on does not improve performance. After each feedback cycle, update the "primary weakness being targeted" in the practice protocol.

Mark Step 5 complete in TodoWrite.

---

#### Step 6: Produce Output — Mindset Diagnostic Report and Deliberate Practice Plan

**ACTION:** Assemble the findings from Steps 1-5 into a two-part output: (A) the mindset diagnostic report, and (B) the deliberate practice plan.

**WHY:** These two outputs serve different purposes and different audiences. The mindset diagnostic report is a mirror — it names what the learner currently believes about their own ability and shows them specifically how those beliefs produce the behaviors limiting their growth. It should be specific enough to be recognizable, not generic. The deliberate practice plan is an operational document — it gives the learner something to do in the next session and a structure to follow over the next 90 days. Together they address both the prerequisite (mindset) and the method (practice design). A practice plan given to a learner in Q3 (Fixed + Performance) without addressing the mindset first will be resisted or abandoned when it produces the discomfort of striving.

**Output Part A — Mindset Diagnostic Report:**

```markdown
# Mindset Diagnostic Report

## Domain
[Field / skill area]

## Quadrant Classification
[Q1-Q4, with the two-axis labels]

## Signals That Placed You Here
- [Signal 1]: [What behavior or attribution revealed this]
- [Signal 2]: ...

## Fixed-Mindset Traps Detected
- [Trap name]: [Specific manifestation in this learner] → [Reframe]

## Growth-Mindset Intervention
[One or two sentences tailored to the learner's specific attributions — not generic motivation,
but a direct reframe of the exact belief pattern identified above]

## What Changes When Mindset Shifts
[Concrete description of how the learner's behavior will look different
once the growth mindset is operative — specific to this domain]
```

**Output Part B — Deliberate Practice Plan:**

```markdown
# Deliberate Practice Plan

## Domain and Current Level
[Field, brief level description]

## Primary Expertise Target (90-day horizon)
[Specific capability that will be meaningfully advanced through this plan]

## Practice Protocol
[Populated template from Step 4]

## Feedback Structure
[Populated table from Step 5, adapted to this learner's access to coaches/tools]

## Mental Model Catalog (starter entries)
[3-5 domain patterns the learner will track and extend through practice]

## Milestones
- 30 days: [Observable indicator of progress]
- 60 days: [Observable indicator]
- 90 days: [Observable indicator]

## What This Will Feel Like
Deliberate practice is usually not enjoyable. It requires striving at the edge of current ability,
which means frequent failure and discomfort. This is not a sign the practice is not working —
it is a sign it is. The discomfort is the myelination happening.
```

Mark Step 6 complete in TodoWrite.

---

## Inputs

- **Domain:** The field or skill in which the learner is developing expertise
- **Difficulty-response signals:** How the learner reacts to failure, setbacks, and challenges (can be brief)
- **Current level:** Optional but useful — helps calibrate the struggle zone

## Outputs

- **Mindset Diagnostic Report** — quadrant classification, detected traps, and tailored growth-mindset reframe
- **Deliberate Practice Plan** — session structure, feedback loops, mental model catalog, and 90-day milestones

## Key Principles

- **Mindset is a prerequisite, not a companion.** A fixed-mindset learner will abandon deliberate practice at the first stretch of discomfort. The mindset diagnosis must happen first and the reframe must be credible to the learner — not a pep talk, but a mechanistic explanation of how effort changes the brain.

- **Effort does not equal ability limitation.** The belief that "needing to work hard proves I'm not talented" is the most corrosive fixed-mindset pattern. It causes learners to avoid precisely the practice that builds expertise. The research finding is the inverse: the best performers invested the *most* hours of deliberate practice, not the fewest.

- **Praise shapes attribution.** Praising a learner for being "smart" or "talented" after a success produces fixed-mindset behavior more reliably than praising effort. In Dweck's study, 90% of students praised for effort chose harder subsequent challenges; the majority praised for intelligence chose easier ones. This has direct implications for how feedback should be framed.

- **The struggle zone is the practice zone.** If a learner is succeeding easily, they are practicing what they already know. The neural adaptations that produce expertise — myelination, new synaptic connections, pattern vocabulary expansion — are driven by striving, failure, and correction. Easy practice produces fluency; it does not produce expertise.

- **Ten thousand hours requires deliberate structure.** Ericsson's finding is not that 10,000 hours of any practice produces expertise. It is that the experts studied had invested approximately that much time in *deliberate* practice — goal-directed, beyond-current-level, feedback-rich, solitary striving. General experience, performance contexts, and low-stakes repetition do not count toward this total.

- **Mental model accumulation is the outcome measure.** The visible product of thousands of hours of deliberate practice is not faster fingers or harder muscles — it is a richer vocabulary of domain patterns. The expert chess player who can contemplate dozens of move sequences has accumulated a pattern library through deliberate practice that a novice cannot access. This is what expertise is. Practice design should target the expansion of this pattern library explicitly, not just the accumulation of hours.

## Examples

**Example 1: Student with performance plateau**

Learner description: "I've been playing guitar for three years but I feel stuck. I'm decent at songs I already know but every new technique I try just sounds bad. I watch other players and they just seem to have natural feel for it."

Diagnosis:
- Step 1: "Natural feel" attribution → fixed-mindset signal. Avoidance of new techniques because they "sound bad" → errorless-learning myth.
- Step 2: Fixed + Performance goal (Q3). Sticks to repertoire where they already sound competent; abandons new techniques quickly.
- Step 3: Traps: natural talent trap ("they just have feel for it"), errorless learning myth ("sounds bad = doing it wrong = stop"), performance goal trap (practice sessions are performance, not striving).

Practice plan:
- Practice domain: Guitar technique
- Primary weakness: New technique acquisition (currently abandoned when imperfect)
- Protocol: 3x/week, 90-min solo sessions. First 15 min: review one technique from last session. Core 60 min: target one specific new technique at 60% success rate (slow, isolated, deliberately imperfect). Error capture: record audio, note what the mistake reveals. Final 15 min: pattern catalog entry.
- Feedback: Weekly audio self-review against a checklist of the technique's components; monthly lesson with a teacher.
- Mindset reframe: "Sounding bad during practice is evidence the practice is working. The discomfort is the learning. A guitarist who only practices what already sounds good is maintaining repertoire, not building technique."

---

**Example 2: Developer who knows growth mindset but stagnates**

Learner description: "I know that anyone can learn to code with effort. But I keep taking projects where I already know the solutions. I'm good but I haven't learned anything new in two years."

Diagnosis:
- Step 1: States growth-mindset belief; behavior contradicts it. Avoids projects with unknown solutions.
- Step 2: Growth + Performance goal (Q4). Growth mindset is genuine; goal orientation is the problem — external validation (competent performance) dominates over skill acquisition.
- Step 3: Trap: performance-goal trap. Effort theory is correct but applied to already-known territory.

Practice plan:
- Practice domain: Software engineering
- Primary weakness: Novel problem-solving under uncertainty
- Protocol: 2x/week, 90-min solo sessions. Target: algorithm or architecture problem type where failure rate is 40-60%. No looking up solutions until 30+ minutes of genuine striving. Error capture: document what the failed attempt revealed about the knowledge gap. Pattern catalog: name the algorithm or design pattern encountered.
- Feedback: Peer code review with explicit focus on "what did you not know before this?" — not quality review, but knowledge-acquisition review.
- Goal reframe: "The measure of a good practice session is not a working solution — it is a specific thing you encountered that you could not do before. That is the unit of progress."

---

**Example 3: Learner already in Q1 (Growth + Learning)**

Learner description: A pianist who deliberately drills the hardest passages at slow tempo, says "I practice what I can't do, not what I can," and keeps a notebook of fingering solutions discovered through practice.

Diagnosis:
- Step 2: Growth + Learning goal (Q1). Already in target state.
- This learner does not need a mindset intervention. The role of this skill is to verify the practice structure satisfies all 5 characteristics (particularly: is feedback granular enough? is the mental model catalog being maintained?) and reinforce what is already working.

Practice guidance: Audit current practice against 5 characteristics. Likely gap: feedback loop may not be closing back into practice target revision. Recommendation: explicitly name the updated practice target at the start of each session based on last session's error capture.

## References

- For detailed evidence on the 4-quadrant model and Dweck's praise research, see [mindset-framework.md](references/mindset-framework.md)
- For Ericsson's deliberate practice research, expert domain examples, and the 10,000-hour finding, see [deliberate-practice-reference.md](references/deliberate-practice-reference.md)
- Source: *Make It Stick* by Brown, Roediger, and McDaniel, Chapters 4, 7, and 8

## License

This skill is licensed under [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/).
Source: [BookForge](https://github.com/bookforge-ai/bookforge-skills) — Make It Stick by Unknown.

## Related BookForge Skills

This skill is standalone. Browse more BookForge skills: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

FILE:references/deliberate-practice-reference.md
# Deliberate Practice Reference

## Ericsson's Core Finding

Anders Ericsson's research across chess players, musicians, athletes, surgeons, and scientists found that expert performance is not a product of innate talent or genetic predisposition. It rises from thousands of hours of what he calls sustained deliberate practice.

Key claim: "The central idea here is that expert performance is a product of the quantity and the quality of practice, not of genetic predisposition, and that becoming expert is not beyond the reach of normally gifted people who have the motivation, time, and discipline to pursue it."

The 10,000-hour finding: Expert performers studied by Ericsson had invested an average of ten thousand hours (or ten years) in their domains. Crucially, the best among them had spent the **largest percentage** of those hours in solitary, deliberate practice — not in performance contexts, group sessions, or low-effort repetition.

## What Deliberate Practice Is (and Is Not)

**Is deliberate practice:** Goal-directed, beyond-current-level striving that produces errors, corrects them through feedback, and builds new mental models and physiological adaptations.

**Is not deliberate practice:**
- General experience ("I've been doing this for 20 years")
- Performance contexts (concerts, competitions, demos)
- Social or collaborative practice that reduces challenge to avoid embarrassment
- Low-effort repetition of already-mastered skills
- Massed practice at comfortable difficulty

## The 5 Characteristics

### 1. Goal-Directed
Each deliberate practice session targets a specific identified weakness or skill gap. Not "play better" but "master the transition between bar 12 and 13 at tempo 90."

### 2. Beyond Current Level
Practice must be calibrated to the zone where failure occurs. If a learner succeeds most of the time, they are practicing what they already know. Deliberate practice requires striving that produces errors at a rate indicating genuine challenge.

### 3. Feedback Loops
Immediate, accurate feedback on each attempt is required. Without feedback, learners cannot distinguish effective from ineffective technique. Expert performers almost universally worked with coaches who could perceive performance gaps the performer could not see from within.

### 4. Solitary and Sustained
The most productive deliberate practice is individual, focused, and separated from performance contexts. Social practice settings introduce the desire to look competent, which conflicts with the error-seeking behavior deliberate practice requires. Extended focused sessions (not fragmented attention).

### 5. Mental Model Accumulation
The primary output of deliberate practice, accumulated over thousands of hours, is a rich library of domain patterns — specific configurations, moves, techniques, cases — that the expert can recognize and act upon rapidly. This is what distinguishes expert from novice performance: not faster reflexes, but richer pattern vocabularies.

## The Neural Mechanism

Deliberate practice produces measurable physiological change:

- **Myelination:** Increased practice builds greater myelin sheathing along related axon pathways, improving signal strength and speed. Studies of piano virtuosos show myelination increases specific to piano performance — not generalized. "Observed myelination changes in piano virtuosos are specific to piano virtuosity."
- **Chunking:** Extended training causes the brain to recode motor and cognitive sequences into the basal ganglia as chunked units that can be executed without serial conscious decisions. Expertise enables performance that outpaces deliberate thought.
- **Neurogenesis:** Associative learning (connecting new items) stimulates creation of new neurons in the hippocampus, supporting memory consolidation.

These changes are domain-specific. Practice in one domain does not confer neural advantage in another.

## The Mental Model Library

Whatever the field, expert performance is thought to be garnered through the slow acquisition of a larger number of increasingly complex patterns — patterns used to store knowledge about which actions to take in a vast vocabulary of different situations.

Example — chess: A champion chess player in studying board positions can contemplate many alternative moves and the countless directions each might precipitate. This is not faster processing of fewer options. It is pattern recognition across a much larger vocabulary of board configurations built through thousands of hours of deliberate play analysis.

Example — music: A pianist describing her practice explains that after a week away from a piece, she returns to find herself using a fingering pattern she had not consciously planned but that "feels entirely natural and familiar." She credits her subconscious drawing from long years of practice — this is the pattern library operating below deliberate awareness.

Example — medicine and other expert domains: Ericsson's finding that expert surgeons, chess players, musicians, and athletes all share this pattern-library structure suggests it is domain-general. The library's contents are domain-specific; the mechanism is not.

## The 10,000 Hours Caveat

The 10,000-hour finding has been widely misapplied as "log 10,000 hours of anything and become an expert." The correct reading:

- The experts Ericsson studied had invested approximately this much time in **deliberate practice specifically** — not general time in the domain
- The best performers invested more of their hours in solitary deliberate practice than those who plateaued at lower levels
- Quality × quantity matters — 10,000 hours of low-quality repetition does not produce expert-level pattern libraries

Michelangelo on the Sistine Chapel: "If people knew how hard I worked to get my mastery, it wouldn't seem so wonderful after all." Four torturous years. The public perception of genius obscures the deliberate practice behind it.

## Practical Implications for Practice Design

1. **Identify specific weaknesses before each session** — not general improvement, but specific gap
2. **Calibrate to the struggle zone** — aim for 40-60% success rate; adjust if too easy or too hard
3. **Capture errors immediately** — write down what failed and what it reveals
4. **Separate deliberate practice from performance** — these require incompatible mental states
5. **Track mental model growth explicitly** — name new patterns encountered, build a catalog
6. **Structure feedback to update practice targets** — feedback that does not change the next session's target is incomplete

## Sources

- Anders Ericsson, deliberate practice research (multiple studies, 1993-present)
- Brown, Roediger, McDaniel, *Make It Stick*, Chapter 7 (Increase Your Abilities)
- Brown, Roediger, McDaniel, *Make It Stick*, Chapter 8 (Make It Stick — trainer section)

FILE:references/mindset-framework.md
# Mindset Framework Reference

## Dweck's Entity vs Incremental Theory of Intelligence

Carol Dweck's research identifies two fundamental beliefs about the nature of intelligence:

- **Entity theory (fixed mindset):** Intelligence is a fixed trait, determined at birth by genes. You have a certain amount of it, and you cannot change it. Performance on tasks reveals how much intelligence you have.
- **Incremental theory (growth mindset):** Intelligence is a malleable quality that grows through effort and learning. Effortful learning forms new neural connections, literally changing the brain's structure over time.

These two beliefs produce systematically different responses to difficulty, failure, and challenge.

## The 4-Quadrant Model: Mindset × Goal Orientation

Mindset (Fixed ↔ Growth) and Goal Orientation (Performance ↔ Learning) are related but independent dimensions. A learner can hold a growth mindset while being trapped in performance goals (seeking validation, not mastery), or can hold a fixed mindset while pursuing learning goals (studying hard but collapsing when effort does not produce results).

| | Learning Goal | Performance Goal |
|---|---|---|
| **Growth Mindset** | **Q1 — Target state.** Seeks challenge, interprets failure as data, persists adaptively. | **Q4 — Social validation loop.** Knows effort builds ability but driven by comparison/recognition. |
| **Fixed Mindset** | **Q2 — Effort paradox.** Works hard but believes ultimate ceiling is innate. Effort without expected results triggers helplessness. | **Q3 — Avoidance trap.** Avoids challenge to protect self-image. Picks tasks calibrated to showcase existing ability. Most resistant to change. |

## The Role of Praise

Praise type is a causal factor in mindset formation, not merely a reflection of existing mindset. Dweck's fifth-grade study demonstrated:

- Students praised for being **smart** → majority chose easier subsequent puzzles (protecting the "smart" label)
- Students praised for **effort** → 90% chose harder subsequent puzzles (treating difficulty as the point)

The mechanism: praising intelligence communicates that intelligence is the valued trait, and that it is demonstrated by easy success. This leads learners to avoid situations that might reveal a limit.

Key quote from Dweck: "Emphasizing effort gives a child a rare variable they can control. Emphasizing natural intelligence takes it out of a child's control, and it provides no good recipe for responding to a failure."

## Attribution Patterns and Learned Helplessness

Dweck's initial research question was: why do some learners become helpless after failure while others try harder?

Finding: The critical variable is **attribution** — what the learner believes caused the failure.

- **Helpless response:** "I failed because I'm not smart enough." Failure is attributed to fixed, internal, global trait → no action available → learned helplessness.
- **Mastery-oriented response:** "I failed because my strategy was wrong" or "I didn't work hard enough." Failure is attributed to variable, specific, controllable factor → new strategy available → renewed effort.

## The 7th-Grade Workshop Study

Dweck ran a study with low-performing 7th graders at a New York City junior high school. Both groups learned about the brain and study techniques. One group additionally received an explanation that:

- Effortful learning causes the brain to form new connections
- These connections, over time, make you smarter
- Intellectual development is not unfolding of innate potential — it results from new connections formed through effort

Result: Teachers (unaware of the intervention) observed that the second group became significantly more aggressive learners and higher achievers over the school year.

The mechanism was not motivation — it was a specific belief change about the causal mechanism linking effort to outcome.

## Test Anxiety as a Fixed-Mindset Signal

A French study of sixth graders demonstrated the working-memory cost of fixed-mindset beliefs during testing:

- Difficulty creates feelings of incompetence → anxiety
- Anxiety consumes working memory capacity monitoring performance ("Am I making mistakes?")
- Less working memory available for problem-solving → worse performance
- Worse performance confirms the fear → reinforces fixed mindset

Students taught that "difficulty is a crucial part of learning, errors are natural and expected, and practice helps" showed significantly better use of working memory on subsequent difficult tests.

Implication: Fixed-mindset beliefs create a cognitive load penalty during performance. Growth-mindset beliefs reduce this penalty by normalizing difficulty.

## The Errorless Learning Myth

The belief that errors signal failure rather than progress causes learners to stay in the comfort zone. The research finding is the inverse: striving that produces errors — and then corrects them — is the mechanism of skill acquisition. Error-free practice means you are practicing what you already know.

Paul Tough's synthesis (via Dweck): Success depends less on IQ than on grit, curiosity, and persistence. Character is built through encountering adversity and overcoming it — not through being protected from it.

## Sources

- Carol Dweck, mindset studies (multiple, 1978-present)
- Paul Tough, *How Children Succeed* (2012)
- French sixth-grade test-anxiety study (multiple researchers)
- Brown, Roediger, McDaniel, *Make It Stick*, Chapters 4 and 7

---
name: evidence-based-training-designer
description: "Redesign a corporate training program, employee training curriculum, employee onboarding, or in-service training so that learning actually sticks past the end of the session. Use this skill when a company's training is built on lecture-heavy workshops, single-topic day-long blocks, or passive e-learning modules that employees promptly forget; when an L&D team needs to convert a massed-practice curriculum into an evidence-based architecture; when a trainer or workshop design lead is building a new training program from scratch and wants to apply learning science from the start; when onboarding for a sales, technical, or certification role needs to produce durable competence rather than a test-passing event; when management asks why employees cannot apply training back on the job; when training program design needs to show measurable retention and transfer, not just satisfaction scores. This skill applies the corporate training models from Farmers Insurance (interleaved four-domain curriculum, FORE scaffolding, vision-poster goal anchoring, 5-4-3-2-1 sales system), Jiffy Lube (tell-show-do-review certification cycle, 80% threshold, biennial recertification), and Andersen Windows (2-hour job rotation, worker-led improvement, kaizen events) to redesign any training program. It does NOT design individual practice schedules for individual learners — use practice-schedule-designer for that."
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/make-it-stick/skills/evidence-based-training-designer
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: draft
source-books:
  - id: make-it-stick
    title: "Make It Stick: The Science of Successful Learning"
    authors: ["Peter C. Brown", "Henry L. Roediger III", "Mark A. McDaniel"]
    chapters: [8]
tags: ["learning-science", "cognitive-psychology", "evidence-based-learning", "corporate-training", "learning-and-development"]
depends-on: [practice-schedule-designer]
execution:
  tier: 2
  mode: hybrid
  inputs:
    - type: document
      description: "Training context: content domains, audience, duration, current program format, and performance gap being addressed"
  tools-required: [Write]
  tools-optional: [Read]
  mcps-required: []
  environment: "Any agent environment; L&D professional or trainer describes their program in text form or answers guided intake questions"
discovery:
  goal: "Audit the current training design for anti-patterns, select a curriculum architecture template (interleaved spiral, certification cycle, or job-rotation model), then produce a redesigned program plan with session structure, spaced retrieval schedule, and evaluation protocol"
  tasks:
    - "Gather training context: content domains, audience profile, duration, and current design"
    - "Audit current design for massed-practice and passive-delivery anti-patterns"
    - "Select the appropriate architecture template based on training type and goal"
    - "Design interleaved curriculum with generation exercises, not lecture-then-drill sequences"
    - "Add spaced retrieval follow-up protocol extending beyond the training event"
    - "Output redesigned program plan with session map, evaluation criteria, and transfer checkpoints"
  audience: "L&D professionals, corporate trainers, instructional designers, operations managers, franchise training coordinators, and HR business partners responsible for employee onboarding or continuing education"
  triggers:
    - "User needs to redesign a training program that is not producing job-transfer"
    - "User is building a corporate training curriculum from scratch"
    - "User's training is structured as full-day single-topic blocks"
    - "Employees pass training assessments but cannot apply skills on the job"
    - "Franchisee or multi-site operation needs a consistent certification model"
    - "L&D team wants to introduce evidence-based learning science into their design process"
    - "In-service or continuing education training is a weekend dump of PowerPoint lectures"
---

# Evidence-Based Training Designer

## When to Use

Your organization runs training. People sit through it. Then they go back to work and do the same things they did before. This is not a motivation problem or a content problem — it is a design problem.

The research is unambiguous: massed instruction (covering one topic exhaustively before moving to the next), passive delivery (lecture and slide), and single-event learning (a workshop with no follow-up) produce fast performance during training and rapid forgetting afterward. The architecture of most corporate training is optimized for the trainer's convenience, not the learner's retention.

This skill redesigns training programs around three mechanisms that the research shows actually produce durable, transferable skill:

1. **Spaced practice** — material is revisited across time with gaps that force retrieval
2. **Interleaving** — multiple content domains are mixed within sessions rather than separated into day-long blocks
3. **Generation** — learners produce answers, solve problems, and practice application before being given the answers, not after

**Preconditions to verify before continuing:**

- Can the user name the content domains the training needs to cover? If not, clarify this before designing.
- Is there a performance gap to address, or is this purely for compliance? Performance-gap training warrants a different intensity of design than compliance box-checking.
- What is the post-training context? Do employees return to a job where they will practice these skills, or is the training a one-time certification event?

**What this skill does NOT cover:**

- Individual learner practice schedules (use `practice-schedule-designer`)
- Motivation, engagement, or gamification strategies independent of learning architecture
- Authoring tool selection or e-learning production

---

## The Core Design Failure to Fix

Before any design work, name the pattern being replaced. Most corporate training failures trace to one of three structural defects:

| Anti-Pattern | What It Looks Like | What It Costs |
|---|---|---|
| **Massed-domain blocking** | Day 1: sales skills. Day 2: product knowledge. Day 3: compliance. No return to prior topics. | Topics learned in isolation cannot be integrated or transferred. Employees forget Day 1 material by the time they need to combine it with Day 3 material on the job. |
| **Passive-delivery dependency** | Content delivered via lecture, slides, or video. Practice is an afterthought at the end of a module. | Learners generate no memory retrieval during the training event itself. Recognition in the room does not predict recall on the job. |
| **Training-as-event** | One workshop, one week, one seminar. No scheduled follow-up. | The forgetting curve begins immediately. Without spaced retrieval after the event, 70–80% of content is inaccessible within a week. |

State the diagnosis explicitly before moving to architecture selection.

---

## Step 1 — Gather Training Context

**Why:** Architecture selection and session design depend on the specific combination of content type, audience experience level, training duration, and transfer context. Guessing at these leads to generic recommendations that do not fit the actual situation.

### Required (ask if missing)

- **What are the content domains?** Name each area the training must cover. (Example: Farmers Insurance covers four — sales techniques, marketing systems, business planning, brand advocacy. Jiffy Lube covers service procedures per vehicle position plus management skills.)

- **What is the audience profile?** Are participants new employees, licensed professionals, franchise operators, experienced workers moving to a new role? Experience level determines how much initial orientation is needed before interleaving begins.

- **What is the total training duration?** Hours, days, weeks. Both the initial program and any scheduled follow-up.

- **What is the current program format?** Walk through a recent session — what happens first, second, and for how long? This surfaces the anti-patterns.

- **What does successful transfer look like?** What specific behavior change is expected 30 days after training ends? This defines the evaluation target and shapes the retrieval protocol.

### Useful (gather if available)

- **Is there a certification or compliance requirement?** Jiffy Lube's model requires demonstrated mastery (80% threshold + supervisor sign-off) before employees can work on customers' vehicles. Compliance constraints affect the certification design.

- **Is there a multi-location or franchise context?** Distributed training requires written standards (like Andersen Windows' step-by-step written job guides) to ensure consistency across sites without a permanent trainer present.

- **What is the post-training work environment?** Andersen Windows workers rotate every two hours by design; their training architecture mimics this by building cross-training into the job itself. If the post-training environment is inherently varied, this reduces the burden on the training program to create variation artificially.

---

## Step 2 — Audit Current Design for Anti-Patterns

**Why:** A redesign proposal lands better when it names what is wrong specifically, not generically. The audit also surfaces which anti-patterns are present so the architecture selection in Step 3 can correct them directly.

Work through the user's description of their current program and score each dimension:

**Domain structure:**
- Are all sessions on one domain completed before moving to the next? → Massed-domain blocking present
- Are multiple domains touched within each session? → Interleaving present (assess quality)

**Delivery method:**
- Is content delivered primarily via lecture, video, or slides? → Passive-delivery dependency present
- Are learners generating answers (solving problems, role-playing, predicting outcomes) before being told correct answers? → Generation present (assess frequency)

**Follow-up structure:**
- Does the training have a scheduled follow-up protocol (quizzes, check-ins, return practice sessions) after the initial event? → If no, training-as-event anti-pattern present

**Output a brief audit summary** before making architecture recommendations:

> "Your current program has the following anti-patterns: [list]. The most costly pattern for your transfer goal is [name the primary one] because [specific consequence for their context]."

---

## Step 3 — Select the Architecture Template

**Why:** Three corporate training models from the research map to three different training contexts. Selecting the right one (rather than applying a generic interleaving prescription) produces a design that fits the actual constraints of time, certification need, and workforce structure.

### Template A — Interleaved Spiral Curriculum (Farmers Insurance Model)

**Best for:** New-hire programs covering 3–6 distinct but related content domains over several days to weeks. Contexts where domains are mutually reinforcing (sales technique, product knowledge, business planning, and brand advocacy each add meaning to the others). High-trust, high-engagement contexts where learner buy-in matters.

**Core mechanics:**
1. **Vision anchor (Day 1, ~30 minutes):** Before any content, learners create a concrete representation of what success looks like for them personally at a meaningful future horizon (Farmers used a poster exercise with magazines and scissors). The image on the poster becomes the anchor to which all subsequent learning is connected. This is not a warm-up exercise — it is a generation activity that activates prior knowledge and establishes a motivational frame that the trainer can return to throughout the program.
2. **Interleaved session design:** No session is devoted exclusively to one domain. Every session touches all domains, returning to each with increasing complexity. The Farmers model cycles through all four domains multiple times per day, not once per day.
3. **FORE scaffolding:** Build a client/customer discovery framework early (in the Farmers case, asking about Family, Occupation, Recreation, and Enjoyment). Introduce it as an icebreaker in Day 1, reuse it as a sales discovery tool in Day 2, deepen it as a needs-analysis framework in Day 3. The same structure gains new meaning at each return — this is the mechanism of interleaved learning.
4. **Concrete metrics embedded in the content:** The Farmers 5-4-3-2-1 system (5 new marketing initiatives per month, 4 cross-marketing programs, 3 appointments scheduled daily, 2 kept, 1 new customer per day averaging 2 policies) turns abstract sales goals into a traceable system. Metrics are not presented as a slide — they emerge from a session where participants calculate backwards from their vision poster to derive what their weekly targets must be.
5. **Role-reversal practice:** Participants alternate between practitioner and client roles. Being the client is not a rest — it is a retrieval exercise that exposes gaps in understanding you did not know you had.

**Session design rule:** Divide each session into segments of no more than 25–30 minutes on any single domain. After that segment, pivot to a different domain. Return to the first domain later in the same day with a new application of the same concept.

### Template B — Certification Cycle (Jiffy Lube Model)

**Best for:** Procedural skills with safety, quality, or regulatory requirements. Franchises, service operations, healthcare, technical trades. Contexts where a minimum competency threshold must be demonstrated before the employee can work unsupervised.

**Core mechanics:**
1. **E-learning with embedded retrieval:** Pre-work is not passive video. It is interactive modules with frequent embedded quizzes — not summative tests at the end, but retrieval questions interspersed throughout. Learners must score 80% or better before proceeding to on-job training. This threshold forces mastery before hands-on work begins.
2. **Tell-show-do-review cycle:** For each procedural skill —
   - **Tell:** Explain what the step is and why it exists (not just what to do, but the reasoning that enables error recovery)
   - **Show:** Demonstrate the step with the learner observing
   - **Do:** Learner performs the step with the trainer present; the written standard is on-hand as the reference, not in the trainer's head
   - **Review:** Supervisor evaluates performance against the written standard and certifies competency in the permanent record
3. **Written standards as the invariant:** Every job is performed to a documented standard that specifies each step and its execution criteria. Without written standards, consistency across shifts and locations degrades; four workers produce four variants of the same product. The written standard also enables self-directed practice — a learner can rehearse against the checklist independently.
4. **Biennial recertification:** Certification is not permanent. Every two years, employees recertify to keep skills current and adapt to procedural and technical changes. This builds spaced retrieval into the organizational system, not just the individual's behavior.
5. **Progressive certification path:** As a technician completes certification in one position, they begin training for the next, until they have trained in all positions including management. The training is the career path, not a one-time event.

### Template C — Job Rotation and Worker-Led Improvement (Andersen Windows Model)

**Best for:** Manufacturing, operations, production environments where cross-training, quality consistency, and continuous improvement are all active goals. Contexts where workers have tacit knowledge about the production process that managers do not have.

**Core mechanics:**
1. **2-hour job rotation:** Workers rotate between positions on a fixed cycle (Andersen uses 2 hours). This is not a staffing convenience — it is an interleaved learning mechanism. Each rotation forces the worker to retrieve procedural knowledge from a different position, builds understanding of the integrated process, and broadens the worker's capacity to respond to unexpected events.
2. **Written standards at every station:** As in the certification model, every station has a written standard. Rotation without standards produces variability; rotation with standards produces cross-trained workers who all meet the same quality bar.
3. **Tell-show-do-review for onboarding:** New workers are paired with experienced workers; training is entirely on-job. The sequence is identical to Template B: tell, show, do, review — with feedback referenced to the written standard.
4. **Worker-led improvement (Kaizen events):** The key reversal in this model is that workers, not managers, are the subject-matter experts on the production process. When a production target is not being met, workers are asked to identify the problem and redesign the process to solve it. This is a structured generation activity: by articulating the problem, proposing changes, and teaching the redesign to others, workers deepen their own understanding of the process far beyond what passive training produces. The Andersen Cottage Grove plant reduced space requirements by 40%, doubled production, and cut costs in half over five months using this model.
5. **Stretch goals as learning catalysts:** Incremental improvement targets require incremental change. Stretch goals (that cannot be reached through incremental methods) require workers to fundamentally rethink the process — which is a high-quality generation task that produces durable, systemic understanding.

---

## Step 4 — Design the Interleaved Curriculum

**Why:** The architecture template tells you what shape the program has. This step converts that shape into a concrete session map the trainer can execute.

### For Template A (Interleaved Spiral)

Build a session-by-session map with the following structure:

- **Session opening (10–15 min):** Retrieve prior learning. Ask participants to recall what they learned in the previous session without notes — not as a test but as a warm-up that reactivates prior knowledge before new content is introduced. Correct gaps immediately.
- **Domain rotation (blocks of 20–25 min each):** Cycle through all content domains within the session. Each block should end with a brief generation task (a question to answer, a scenario to respond to, a metric to calculate) before moving on. Do not complete a domain block before pivoting.
- **Integration pivot:** Once all domains have been touched, run a scenario or exercise that requires participants to use knowledge from multiple domains simultaneously. This is the payoff of interleaving — cross-domain integration that blocked instruction cannot produce.
- **Session close (10 min):** Participants write down three things they learned and one question they still have. This is a generation and retrieval activity, not a satisfaction survey.

### For Template B (Certification Cycle)

Map each job certification as a unit:

- Pre-work (e-learning with embedded quizzing) → scored to 80% threshold
- On-job tell-show-do-review → supervisor-evaluated against written standard
- Certification recorded in permanent file
- Begin next certification unit
- Biennial recertification scheduled automatically

Track all progress on a visible dashboard (the Jiffy Lube "virtual dashboard" model) that shows each employee where they are in the certification path. Visibility motivates completion and allows managers to spot bottlenecks.

### For Template C (Job Rotation / Continuous Improvement)

Map the rotation schedule:

- Rotation frequency (Andersen: 2 hours)
- Written standard location for each station (physical or digital)
- Crew leader assignment and coaching responsibilities
- Improvement cycle trigger: when a production target is missed, convene a worker-led problem-solving session rather than issuing a directive
- Kaizen event protocol for major restructuring: cross-functional team (engineer + maintenance + crew leader + production workers), dedicated time (1 week), defined stretch goals, structured review process

---

## Step 5 — Add Spaced Retrieval Follow-Up Protocol

**Why:** The training event is where learning begins, not where it ends. Without a structured follow-up protocol, the forgetting curve reclaims most of what was learned within a week. The follow-up protocol is not optional — it is the mechanism that converts short-term training performance into long-term job competence.

The follow-up protocol has three components:

**1. Scheduled retrieval quizzes (post-training)**

For programs using Template A or B, schedule quizzes at:
- 48 hours after training ends (first retrieval while some memory remains — strengthens consolidation)
- 1 week after training (second retrieval — requires more effort, produces more durable trace)
- 1 month after training (third retrieval — the point at which most organizations declare "done"; this is actually when the most important retention work happens)

Quizzes should be low-stakes (not graded punitively) and delivered in the work context (mobile device, email, brief team meeting). The Qstream platform model — short spaced retrieval questions delivered via mobile — is a direct implementation of this protocol at scale.

**2. Transfer check-ins (manager-led)**

At 30, 60, and 90 days post-training, a manager or team lead conducts a brief structured conversation:
- "Walk me through how you handled [situation the training addressed] this week."
- "What part of the training has been hardest to apply? What's getting in the way?"
- "Show me [specific skill] using the written standard."

This is not a performance review — it is a coaching conversation that also functions as a retrieval event. Narrating what you did and why deepens encoding.

**3. Recertification trigger (for Template B)**

Set a calendar-based recertification schedule (Jiffy Lube uses 2 years). Recertification is not a formality — it is the organizational mechanism for spaced practice at scale. Build it into HR systems so that it happens automatically, not when someone remembers to schedule it.

---

## Step 6 — Output: Redesigned Training Program Plan

**Why:** An abstract recommendation does not change what trainers do on Monday. A concrete program plan does.

Produce a program plan document with the following sections:

**Program overview:**
- Training goal and transfer target (what behavior change, measurable within 90 days)
- Content domains (named and scoped)
- Architecture template selected and rationale
- Total duration (initial event + follow-up protocol)

**Session map:**
- For each session: date/number, duration, domain sequence, exercises, generation tasks, and closing retrieval activity
- Anti-pattern warnings embedded at each session: "Resist the urge to complete this domain block before moving to the next — the discomfort of switching is the mechanism of learning"

**Written standards checklist:**
- For Templates B and C: list each job/procedure that requires a written standard; flag which ones exist and which need to be created before training begins

**Follow-up protocol:**
- Exact dates for post-training retrieval quizzes
- Transfer check-in questions for 30/60/90-day conversations
- Recertification calendar trigger (if applicable)

**Evaluation criteria:**
- Leading indicators: quiz scores at 48 hours, 1 week, 1 month
- Lagging indicators: on-job performance metrics at 30/60/90 days
- Anti-pattern check: is anyone reverting to passive review or single-session cramming as a supplement to the program? Flag and correct.

---

## Worked Examples

### Example A: Sales Onboarding Redesign (Template A)

**Situation:** A regional insurance agency brings on 15 new agents per quarter. Current program: 3-day bootcamp with Day 1 on sales, Day 2 on products, Day 3 on compliance. No follow-up after day 3. Agents report forgetting most of what they learned within 2 weeks.

**Audit:** Massed-domain blocking (one domain per day), passive delivery (primarily slide lectures), training-as-event (no follow-up). Primary cost: domains learned in isolation cannot be integrated when a real customer conversation requires combining sales technique with product knowledge and compliance awareness simultaneously.

**Architecture:** Template A — Interleaved Spiral Curriculum.

**Redesign:**
- Day 1 opens with a vision exercise (not a slide deck): agents build a concrete picture of what a successful agency looks like for them in 3 years, deriving the revenue and policy targets backward from that vision.
- Each day cycles through all three content domains in 25-minute segments. Day 1 introduces a client discovery framework (FORE equivalent) as an icebreaker; Day 2 returns to it as a product-needs tool; Day 3 applies it in a compliance conversation.
- Every session includes role-reversal practice: one agent plays prospect, one plays agent. The "prospect" role is as instructive as the "agent" role because gaps in understanding become visible when you have to respond spontaneously to questions.
- Post-training: retrieval quizzes delivered by email at 48 hours, 1 week, and 1 month. Manager check-in at 30 days: "Walk me through a recent prospect conversation — what did you ask first, and why?"

---

### Example B: Technical Certification Rollout (Template B)

**Situation:** A multi-site automotive service franchise (8 locations, 65 employees) has no consistent certification process. New hires shadow an experienced worker for a few days, then work unsupervised. Service quality varies significantly by location.

**Audit:** No written standards (four workers, four variants), no threshold-gated certification, no recertification schedule. Training is apprenticeship by observation — modeling without structured retrieval or documented criteria.

**Architecture:** Template B — Certification Cycle.

**Redesign:**
- Create written standards for each of the 8 service positions. Each standard lists every step and the acceptable quality criteria for each step.
- Pre-work: interactive e-learning for each position, with retrieval questions every 3–5 minutes of content. Threshold: 80% before on-job training begins.
- On-job training follows tell-show-do-review for each step in the written standard. Supervisor certifies each step; certification is recorded in a shared file.
- New employees begin certification in one position, complete it, then begin the next position. All employees eventually certified in all 8 positions.
- Recertification calendar: every 2 years, all employees recertify in their primary positions; flag any procedural changes requiring immediate recertification.

---

### Example C: Production Floor Cross-Training (Template C)

**Situation:** A manufacturing facility has high variability in output quality across shifts. Workers are specialized in their station and cannot cover for absent colleagues. Management issues directives when targets are missed but does not see improvement.

**Audit:** No job rotation (workers locked to single stations — equivalent to massed practice), no written standards at each station, problem-solving directed by management rather than generated by workers.

**Architecture:** Template C — Job Rotation and Worker-Led Improvement.

**Redesign:**
- Implement 2-hour rotation across all stations within each cell. Pair rotation with written standards at each station so rotation produces cross-trained competence, not confusion.
- Onboard new workers via tell-show-do-review, with an experienced worker as the trainer at each station.
- When a production target is missed, convene the production team (not a manager meeting) to identify the problem: "What is causing this, and what would make it better?" Document and implement worker proposals.
- For a major productivity problem: run a 1-week Kaizen event with a cross-functional team (engineer + maintenance + crew leader + workers). Define a stretch goal that requires fundamental redesign. The team teaches each other the constraints of the process and redesigns it collaboratively. The teaching and problem-solving process is itself the learning.

---

## Quick Reference: Architecture Selection

```
TRAINING TYPE                          → TEMPLATE
------------------------------------------------------------
New-hire onboarding, 3–6 domains       → A: Interleaved Spiral Curriculum
Procedural/technical certification     → B: Certification Cycle
Production/operations cross-training   → C: Job Rotation + Worker-Led Improvement
Compliance/in-service (single event)   → B: Certification Cycle + spaced retrieval follow-up

ANTI-PATTERN DETECTED                  → FIX
------------------------------------------------------------
One domain per day                     → Interleave: cycle through all domains each session
Lecture-dominant delivery              → Replace with generation: role-play, calculate, produce
No post-training follow-up             → Add retrieval quizzes at 48h, 1 week, 1 month
No written standards                   → Document each step before on-job training begins
No recertification                     → Schedule biennial recertification in HR system

GENERATION EXERCISE TYPES              → WHEN TO USE
------------------------------------------------------------
Vision poster / future-state image     → Day 1 anchor; activates motivation and prior knowledge
FORE / discovery framework             → Build early, reuse in new contexts across sessions
Role reversal (be the customer)        → Every session; surfaces gaps recognition cannot reveal
Calculate-backward (metrics to vision) → Business/sales training; makes metrics personally meaningful
Worker-led problem diagnosis           → When performance targets are missed; generates understanding
Kaizen / redesign event                → When stretch goals require fundamental process change
```

---

## References

- `references/three-architecture-templates.md` — Full specifications for each template including session timing tables, written standard format, and certification record design
- `references/generation-exercise-library.md` — 12 generation exercise types (vision poster, FORE, role-reversal, calculate-backward, scenario simulation, etc.) with facilitation instructions and domain applicability
- `references/spaced-retrieval-follow-up-protocol.md` — Exact quiz cadences by training duration, sample question formats, Qstream and mobile delivery options, and 30/60/90-day check-in question banks

## License

This skill is licensed under [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/).
Source: [BookForge](https://github.com/bookforge-ai/bookforge-skills) — Make It Stick: The Science of Successful Learning by Peter C. Brown, Henry L. Roediger III, Mark A. McDaniel.

## Related BookForge Skills

Install related skills from ClawhHub:
- `clawhub install bookforge-practice-schedule-designer`

Or install the full book set from GitHub: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

---
name: evidence-based-classroom-designer
description: |
  Design or redesign any course, class, or training session using evidence-based instructional principles. Use this skill when a teacher, instructor, or instructional designer wants to improve student retention and achievement through classroom design, course design, quiz design, or active learning strategies — even if they don't mention "retrieval practice" or "spaced repetition." Triggers include: instructor wants to reduce failure rates in a gateway course; teacher finds students forget material within days of a lecture; instructor relies on midterm and final exams as the only assessment; teacher wants to move from passive lecturing to active learning without losing content coverage; instructor wants to close the achievement gap between well-prepared and under-prepared students; course designer wants to embed low-stakes quizzing into a curriculum; teacher wants to raise student performance on Bloom's higher-order thinking levels; instructor wants to redesign student engagement without adding complexity. Works for K-12 teachers, university professors, corporate trainers, and instructional designers. Do NOT use this skill to build a personal study system for a single learner (use retrieval-practice-study-system), to create a practice schedule alone (use practice-schedule-designer), or to audit a single learning activity for difficulty structure (use desirable-difficulty-classifier).
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/make-it-stick/skills/evidence-based-classroom-designer
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: draft
source-books:
  - id: make-it-stick
    title: "Make It Stick: The Science of Successful Learning"
    authors: ["Peter C. Brown", "Henry L. Roediger III", "Mark A. McDaniel"]
    chapters: [8]
tags: ["learning-science", "cognitive-psychology", "evidence-based-learning", "teaching", "classroom-design", "instructional-design", "course-design", "quiz-design", "active-learning", "student-engagement"]
depends-on:
  - retrieval-practice-study-system
  - practice-schedule-designer
  - desirable-difficulty-classifier
execution:
  tier: 2
  mode: hybrid
  inputs:
    - type: document
      description: "Course syllabus, lesson plan, curriculum outline, or description of the current course structure and assessment approach"
  tools-required: [Read, Write]
  tools-optional: []
  mcps-required: []
  environment: "Any agent environment with file read/write access. Instructor provides course details or uploads a syllabus."
discovery:
  goal: "Audit the current course design against 6 evidence-based criteria, then apply a 4-part teacher protocol to produce a concrete redesigned course plan with an assessment calendar, specific intervention designs, and a transparency script for students."
  tasks:
    - "Gather course details: subject, level, class size, frequency, current assessment structure"
    - "Audit current design against the 6-criteria learning environment checklist"
    - "Apply the 4-part teacher protocol (explain, teach, create difficulties, be transparent)"
    - "Design specific interventions: quiz schedule, reflection exercises, interleaving plan, Bloom's audit"
    - "Produce redesigned course plan with assessment calendar and student transparency script"
  audience: ["K-12 teachers", "university instructors", "corporate trainers", "instructional designers", "curriculum coordinators"]
  triggers:
    - "Students are forgetting material within days of a lecture"
    - "The only assessments are a midterm and a final exam"
    - "Failure rates in a gateway course are too high"
    - "I want to move from lecturing to active learning"
    - "I want to close the achievement gap in my class"
    - "I need to embed low-stakes quizzing into my curriculum"
    - "My students don't retain what they learn"
    - "I want to redesign my course for better student engagement"
  not_for:
    - "Building a personal study system for a single learner (use retrieval-practice-study-system)"
    - "Designing a spacing schedule only (use practice-schedule-designer)"
    - "Auditing a single learning activity (use desirable-difficulty-classifier)"
  environment: "Course-level: syllabus, lesson plan, assessment calendar, or instructor description of current course structure"
  quality:
    completeness_score:
    accuracy_score:
    value_delta_score:
---

# Evidence-Based Classroom Designer

## When to Use

You are an instructor, teacher, or course designer who wants to improve how much students actually learn and retain — not just how much is covered. Typical situations:

- Your gateway course has high failure or withdrawal rates, and you suspect the problem is the assessment structure, not the students
- Students perform adequately on exams but forget the material within days — they're cramming, not learning
- Your course relies on high-stakes midterm and final exams as the only practice and feedback mechanism
- You want to introduce active learning but don't know which specific interventions are worth the effort
- You teach a high-structure discipline (biology, engineering, economics) and want to help under-prepared students succeed without lowering standards

Before starting, verify:
- Is a course outline, syllabus, or description of the current course structure available? (If not, ask the instructor to describe the course: subject, level, class size, number of meetings, current assessments)
- What is the instructor's primary concern? (Failure rates, retention, engagement, achievement gap, workload?)

**Mode: Hybrid** — The agent designs the course structure, intervention calendar, and transparency materials. The instructor executes and adapts them to their specific classroom.

---

## Context & Input Gathering

### Required Context (must have — ask if missing)

- **Course description:** Subject, level (K-12 / university / professional), class size, meeting frequency, total duration
  → Check for: uploaded syllabus, course outline, pasted description
  → If missing, ask: "Please describe your course: what subject, what level, how many students, how often do you meet, and how long does the course run?"

- **Current assessment structure:** What assessments exist? When are they scheduled? What weight do they carry?
  → Check for: exam dates in syllabus, grading breakdown table, assignment list
  → If missing, ask: "How are students currently graded? What assessments exist, and when do they happen?"

- **Primary concern:** What is not working, or what does the instructor want to improve?
  → Check for: explicit problem statement in the prompt ("students forget," "high failure rate," "passive lectures")
  → If missing, ask: "What problem are you trying to solve with this redesign?"

### Observable Context (gather from environment)

- **Subject type:** Affects intervention design (procedural vs. conceptual vs. declarative material)
  → Look for: course name, discipline cues, learning objectives in syllabus

- **Existing active-learning elements:** Prior attempts at quizzing, group work, or reflection exercises
  → Look for: in-class activities section of syllabus, assignment descriptions

### Default Assumptions

- If class size is not specified → design for a class of 25-40 (adjust if instructor clarifies)
- If no assessment structure provided → assume two high-stakes exams (midterm + final), no low-stakes practice
- If no primary concern specified → focus on the most common problem: low-stakes practice is absent and students rely on cramming

### Sufficiency Threshold

```
SUFFICIENT when ALL of these are true:
  ✓ Subject and level are known
  ✓ Current assessment structure is described (or default assumption is acceptable)
  ✓ Primary concern or goal is stated
BLOCK if: no subject and no description — cannot design interventions without knowing what students are learning
```

---

## Process

### Step 1 — Gather Course Profile

Collect and record:
1. **Course basics:** Subject, level, class size, meeting frequency (e.g., 3x/week × 15 weeks), total seat time
2. **Learning objectives:** What must students be able to do by the end? At what cognitive level (recall, application, analysis, synthesis)?
3. **Current assessment calendar:** When do assessments occur? What types? What percentage of grade?
4. **Current in-class structure:** Lecture-only? Group work? Discussion? Problem sets?
5. **Student population:** Are they primarily well-prepared, mixed, or under-prepared? Are there equity concerns?

**WHY:** Intervention design must be calibrated to the specific constraints of the course. A 25-person seminar meeting twice a week calls for different mechanics than a 200-person lecture hall meeting three times a week. Gathering specifics first prevents generic recommendations that cannot be implemented.

Output: A course profile summary (3-5 sentences) confirmed with the instructor before continuing.

---

### Step 2 — Audit Current Design Against 6 Criteria

Evaluate the current course against each criterion. Rate each: **Present / Partial / Absent.**

| Criterion | What to look for | Research basis |
|-----------|-----------------|----------------|
| **C1. Low-stakes retrieval practice** | Frequent quizzes, self-tests, or recall exercises that occur during the course (not only at midterm/final) | Testing effect: retrieval consolidates learning and arrests forgetting. Quizzed material retained at 92% vs 79% for non-quizzed in Columbia IL study |
| **C2. Spaced and cumulative review** | Assessments or exercises that reach back to prior material — not only the most recent unit | Spacing forces reconstruction from long-term memory, strengthening the neural pathway. Cumulative quizzing builds complex mental models |
| **C3. Interleaving across topics** | Topics or problem types mixed across sessions rather than blocked by unit | Interleaving requires students to "reload" prior knowledge and identify which approach applies, building discrimination and transfer |
| **C4. Consequences (low-stakes)** | Practice exercises count toward the course grade, even at very low weight | Students in graded low-stakes practice classes outperform students in classes where the same exercises are ungraded |
| **C5. Transparency about how learning works** | Instructor explicitly explains why desirable difficulties are used and what the research shows | Students who understand the mechanism tolerate the discomfort of effortful practice and persist longer |
| **C6. Calibration feedback** | Students receive timely feedback that reveals what they know vs. what they think they know | Without calibration, students rely on fluency illusions and study the wrong material. The "illusion of knowing" is the primary cause of exam failure despite adequate study time |

For each criterion rated **Partial** or **Absent**, note the specific gap (e.g., "C1 absent: only two exams, no in-class quizzing").

**WHY:** Most course designs fail on C1 and C2 — they schedule high-stakes practice too infrequently and too late. Students in low-structure courses (lecture + two exams) have no mechanism to discover gaps before the exam, no incentive to practice distributed retrieval, and no feedback on whether their self-assessed confidence matches actual mastery. The audit makes the specific gaps visible before designing interventions.

For detailed difficulty classification across all six strategies (including generation, elaboration, variation), invoke `desirable-difficulty-classifier` OR apply the 6-criteria audit above directly.

Output: A filled audit table with Present/Partial/Absent ratings and gap notes.

---

### Step 3 — Apply the 4-Part Teacher Protocol

Apply each of the four protocol elements to the specific course. For each, produce a concrete implementation plan — not just a principle.

#### Protocol Part 1: Explain How Learning Works

Design a brief transparency module to deliver at the start of the course (or first class). Include:

- **The testing effect:** Explain that retrieval practice — not rereading — produces durable learning. Students who quiz themselves retain far more than students who reread the same content.
- **Desirable difficulties:** Explain that the discomfort of struggling to recall something is not a signal of failure — it is the mechanism of learning. If quizzing feels easy, the interval is too short.
- **Growth mindset tie-in:** Explain that intellectual ability is not fixed. Effortful learning changes the brain. Setbacks are information, not verdicts.
- **Course-specific preview:** Tell students exactly which practices in this course are intentionally difficult and why (e.g., "The daily quizzes in this course are harder than you might expect. That difficulty is the point.").

*Example — Wenderoth's framing:* "The whole idea of the testing effect is that you learn more by testing yourself than by rereading. I know this contradicts how most of you study. So I'm going to model it in class, and I'm going to show you your results over the semester so you can see it working."

**WHY:** Students who understand the mechanism tolerate the discomfort of effortful practice and persist longer. Students who don't understand it interpret quiz difficulty as unfairness and disengage. Wenderoth's research shows that students who are told they "have the illusion of knowing" and understand what that means come to her with solvable problems rather than complaints about trick questions.

#### Protocol Part 2: Teach Students How to Study

Design at least two study strategies to explicitly teach (not just recommend):

- **Free recall exercise:** Assign students to spend 10 minutes at the end of each class writing everything they remember from that session — without notes. Then check their notes and identify gaps. *Wenderoth assigns this daily; it guides what students bring to the next class.*
- **Testing groups (not study groups):** Restructure any group work so the group wrestles with a question together — books closed — rather than having the most knowledgeable person explain to the others. *Wenderoth finds that testing groups build exploration and understanding; study groups build dependency.*
- **Summary sheets:** Assign a weekly synthesis artifact — a single page illustrating the week's material with connections, arrows, and key ideas. This forces synthesis across a week of content before it fragments. *Wenderoth uses cartoon-style physiology sheets; the format can be adapted to any discipline.*

For detailed retrieval practice implementation for individual students, invoke `retrieval-practice-study-system` OR apply the free recall and self-quizzing pattern above directly.

**WHY:** Students are not taught how to study effectively and tend toward the least effective strategies (rereading, highlighting). Explicitly modeling correct study technique — rather than assuming students know it — is a prerequisite for the active-learning interventions in the course to work. Students who don't know how to retrieve cannot benefit from a high-structure course.

#### Protocol Part 3: Create Desirable Difficulties in the Classroom

Design 3-5 specific interventions drawn from the following menu. Select based on the audit gaps (Step 2) and the course constraints.

**Intervention A — Daily or bi-weekly low-stakes quizzes**
- Format: 3-5 questions at the start or end of class; closed notes; short-answer preferred over multiple-choice
- Timing: Every class, or every other class — not only at exam time
- Content: Mix current material with material from 2-3 sessions ago (cumulative reach-back)
- Grading: Count toward course grade at very low weight (e.g., 15-20% total, drop 3-4 lowest)
- Ground rules (critical): Set clear rules at the start of term — e.g., 4 free absences, no makeups; students either take it or they don't. This prevents negotiation overhead that makes quiz systems unsustainable.

*Example — McDermott (Washington University):* 4-question quiz in the last 3-5 minutes of every class meeting (28 meetings, 2×/week). Anything covered to date is fair game. Students drop 4 quizzes; no makeups. Quizzes = 20% of grade. By end of semester, students report quizzes helped them keep up and discover gaps early.

*Example — Sobel (political economics):* Cumulative low-stakes quizzing throughout the term. Each quiz can draw from any material covered so far. Students build incrementally complex mental models rather than cramming disconnected units.

**Intervention B — Pre-class generation exercises**
- Before the class where a new concept is taught, assign a brief problem or question the students cannot yet fully solve
- Students wrestle with the problem before seeing the solution; they arrive primed to receive instruction
- This "generation effect" produces stronger encoding than reading the explanation first

*Example — Matthews/West Point Thayer method:* Students read for specific learning objectives before each class; class opens with a quiz on those objectives; then students "take to the boards" — higher-order questions requiring integration, worked at the board in groups; one student per group gives a recitation to the class. Zero lecture. The grade rests on consistent daily participation.

**Intervention C — Board work and active recitation**
- Assign student groups to work through higher-order questions at the board (or equivalent: whiteboard apps, shared documents)
- One student per group explains the group's answer to the class — recitation, not just written output
- Keep questions at analysis/synthesis level (Bloom's level 4-6), not just recall

**Intervention D — Bloom's taxonomy answer keys**
- For each major exam or assessment, provide a Bloom's-level answer key: one answer for knowledge-level recall, a more complete answer for comprehension, a deeper answer for analysis, and the strongest answer for synthesis/evaluation
- Ask students to locate where their answer fell on the taxonomy and identify what they would need to know to reach the next level

*Example — Wenderoth:* Students receive the Bloom's key with their graded tests. They identify their level for each answer. The exercise shifts the question from "did I get it right?" to "at what level did I understand this?" and produces a specific, actionable study target.

**Intervention E — Learning paragraphs (periodic writing)**
- Once or twice a month, pose a synthesis question at the end of class ("How is X like Y?", "You just got your test back — what would you do differently?")
- Students write a 5-6 sentence response. Low stakes. Collect and read; comment in the next class so students know they were read.
- Purpose: stimulate retrieval and reflection before the week's learning is lost; give science or technical students deliberate writing practice.

**Designing the spacing and interleaving structure:**

For detailed spacing and interleaving schedule design across topics, invoke `practice-schedule-designer` OR apply this pattern directly:
- Map topics across the course timeline; identify where topics are currently blocked (all of Topic A, then all of Topic B)
- Restructure to alternate: introduce Topic A, introduce Topic B, return to Topic A at a higher complexity level, return to Topic B, etc.
- In physical or life sciences: align this with the vertical curriculum structure (e.g., Columbia IL: six simple machines in middle school → underlying physics in high school → applied engineering problem solving later)

**WHY:** Research consistently shows that students in high-structure classes (daily/weekly low-stakes practice) outperform students in low-structure classes (lecture + two exams) — and the gap is largest for under-prepared students. The key finding from Wenderoth's biology experiments: high-structure classes significantly reduced failure rates in gateway biology while simultaneously raising performance on Bloom's higher-order levels. The mechanism is that low-structure courses leave students to self-regulate their study, and most students self-regulate poorly until they have been taught otherwise.

#### Protocol Part 4: Be Transparent Throughout

Ongoing transparency (not just at the start of the course):

- After each quiz, briefly explain why you designed the question the way you did
- When students struggle with a difficult question, name the difficulty: "This question is designed to be hard to recall — that difficulty is producing stronger encoding right now"
- When quiz grades disappoint, redirect from blame to calibration: "This tells you something accurate about what you know. That's the point of doing this now rather than at the final exam."
- Reference student language: if a student says "that was a trick question," use it as a teaching moment about the illusion of knowing. *Wenderoth's observation: students who understand the illusion of knowing come to office hours with solvable problems, not complaints.*

**WHY:** Transparency is not a one-time orientation. The discomfort of effortful practice recurs throughout the semester, and students need a recurring framework for interpreting that discomfort as signal rather than failure. Without ongoing explanation, students who struggle will attribute difficulty to bad teaching rather than effective learning design.

---

### Step 4 — Design Specific Interventions

Based on the audit results and the 4-part protocol, produce:

**4a. Quiz schedule design**
- How many quizzes, at what frequency, on what content reach-back window
- Ground rules (free misses policy, no-makeup rule, weighting)
- Sample questions for the first 3 quizzes that demonstrate the cumulative reach-back pattern

**4b. Reflection exercise plan**
- Which reflection exercises to use (free recall, learning paragraphs, summary sheets)
- When in the class period they occur and how long they take
- How they are collected or reported (written, verbal, whiteboard)

**4c. Interleaving plan**
- A revised topic sequence showing where topics are interleaved rather than blocked
- Identification of which topics have natural conceptual connections that make interleaving high-value

**4d. Bloom's level design**
- For at least one major assessment: a Bloom's-level answer key template showing what a knowledge-level, comprehension-level, and analysis-level answer looks like for one representative question
- Instructions for distributing this key to students post-assessment

**WHY:** Without concrete artifacts — a quiz schedule, a sample question set, an interleaving map — instructors revert to their existing structure because it is familiar and low-effort. The interventions must be specifiable enough to execute in the first week of class.

---

### Step 5 — Produce Redesigned Course Plan and Assessment Calendar

Produce a complete redesigned course plan including:

1. **Transparency module** (first class): 10-15 minute script or outline explaining the testing effect, desirable difficulties, and how learning works
2. **Assessment calendar** (full course): When each type of assessment occurs (quiz, exam, reflection exercise, summary sheet), what it covers, and its grade weight
3. **Intervention calendar** (weekly): For each week of the course, which specific interventions occur (e.g., Week 3: 2 quizzes with reach-back to Week 1; board exercise on Topic B; summary sheet due Monday)
4. **Ground rules document**: The course-level policies for low-stakes practice (free misses, no-makeup rules, weighting)
5. **Student-facing explanation**: A 1-paragraph explanation for the syllabus or first-day handout that tells students why the course is designed the way it is

**WHY:** The goal is a course design that can be handed to another instructor and implemented without additional planning. Generality disappears at the level of execution; specificity is what makes redesign actionable.

Output: Write the redesigned course plan to `redesigned-course-plan.md`.

---

## Inputs

| Input | Required | Description |
|-------|----------|-------------|
| Course description | Yes | Subject, level, class size, meeting frequency, duration |
| Current assessment structure | Yes (or default assumed) | What assessments exist, when, what weight |
| Primary concern or redesign goal | Yes | What is not working or what the instructor wants to improve |
| Course syllabus or outline | Preferred | The document to audit and redesign |
| Student population description | No | Mix of prepared/under-prepared; equity concerns |

## Outputs

| Output | Format | Description |
|--------|--------|-------------|
| `redesigned-course-plan.md` | Markdown | Full redesigned course plan with all 5 components from Step 5 |

### Output Template: redesigned-course-plan.md

```markdown
# Redesigned Course Plan: [Course Name]

**Instructor:** [Name or role]
**Course:** [Subject, level, class size, meeting frequency]
**Primary concern addressed:** [e.g., "High failure rate in gateway biology"]
**Redesign date:** [Date]

## Design Audit Results

| Criterion | Rating | Gap |
|-----------|--------|-----|
| C1. Low-stakes retrieval practice | Present / Partial / Absent | [gap note] |
| C2. Spaced and cumulative review | Present / Partial / Absent | [gap note] |
| C3. Interleaving across topics | Present / Partial / Absent | [gap note] |
| C4. Consequences (low-stakes) | Present / Partial / Absent | [gap note] |
| C5. Transparency about learning | Present / Partial / Absent | [gap note] |
| C6. Calibration feedback | Present / Partial / Absent | [gap note] |

## Interventions Selected

[List of 3-5 interventions from Step 3, with brief rationale for each]

## Transparency Module (First Class)

[10-15 minute outline or script]

## Assessment Calendar

| Week | Assessment | Type | Covers | Grade weight |
|------|-----------|------|--------|-------------|
| 1 | ... | ... | ... | ... |
| ... | ... | ... | ... | ... |

## Weekly Intervention Calendar

| Week | Quizzes | Reflection exercises | Board work | Other |
|------|---------|---------------------|------------|-------|
| 1 | ... | ... | ... | ... |
| ... | ... | ... | ... | ... |

## Ground Rules Document

[Policies for low-stakes practice: free misses, no-makeup rule, weighting]

## Student-Facing Explanation (for Syllabus)

[1 paragraph]
```

---

## Key Principles

**1. Low-stakes retrieval practice is the highest-leverage classroom intervention**
The single most impactful change a teacher can make is to add frequent, low-stakes retrieval practice — quizzes that happen during the course rather than only at the end. The Columbia, Illinois middle school study found 92% retention on quizzed material vs. 79% on non-quizzed material in the same class. McDermott's university course achieves this with 4 questions in the last 5 minutes of every class meeting. The investment is minimal; the learning gain is substantial.

**2. High-structure courses close achievement gaps**
Wenderoth's biology experiments show that high-structure classes (daily and weekly low-stakes exercises) significantly reduce failure rates in gateway biology courses while simultaneously raising Bloom's-level performance. The gap narrows most for under-prepared students — those without a prior history of effective learning habits. High-structure is not remediation; it is structure that helps all students and helps struggling students most.

**3. Consequences matter, even at very low stakes**
Students in courses where practice exercises count toward the grade — even at minimal weight — outperform students in the same course where the exercises carry no consequences. The exercises being identical means the difference is purely in motivation to engage. Low-stakes grading is not coercive; it is the signal that the exercises are real, not optional.

**4. Transparency is a design element, not a nice-to-have**
When students understand why effortful retrieval feels uncomfortable and why that discomfort signals learning, they tolerate it and persist. When they don't understand it, they interpret difficulty as unfairness and disengage. Transparency is not soft pedagogy — it changes the behavioral response to difficulty and determines whether the rest of the course design can work.

**5. The Thayer method proves high-structure scales across disciplines**
West Point's Thayer method — specific learning objectives before every class, daily quizzing at the start, board work on higher-order questions, student recitation — has been sustained across almost 200 years and multiple disciplines. Matthews's courses run with essentially zero lecturing. The method works best for students who need structure to develop study discipline, and it scales from elite academies to Riverside Military Academy's more varied student population.

**6. Cumulative reach-back builds the mental model, not just the fact list**
Sobel's cumulative quizzing approach allows any quiz to draw from any material covered to date. This is not review for review's sake — it is the design mechanism that forces students to build connections between concepts over the course of the term, producing complex mental models rather than isolated fact recall. The final exam is never a shock because the student has been practicing toward it all semester.

---

## Examples

### Example 1: University Gateway Biology Course (High Failure Rate)

**Scenario:** A biology professor teaches a 150-student introductory biology lecture course that serves as a gateway requirement. Failure and withdrawal rates are around 30%. The course currently has 2 midterms and a final exam, weekly readings, and a lab section. Most students rely on cramming.

**Audit result:** C1 absent (no low-stakes quizzing), C2 absent (exams are not cumulative), C3 partial (topics are sequential, not interleaved), C4 absent (no graded practice), C5 absent (no explanation of learning principles), C6 partial (exams provide calibration, but too infrequently).

**Redesign interventions selected:**
- Weekly 5-question quiz (cumulative, 20% of grade, 3 lowest dropped)
- Daily free recall exercise: 10 minutes at end of lecture, written, no notes
- Bloom's answer keys distributed with each graded exam
- Transparency module in week 1 (testing effect + growth mindset)
- Summary sheets due every Monday (illustrate prior week's material)

**Expected outcome (based on Wenderoth's results):** Statistically significant reduction in failure rates; higher-order thinking scores on exams improve; under-prepared students show the largest gains.

---

### Example 2: High School History (Passive Lecture Problem)

**Scenario:** A high school history teacher with 28 students finds that students are disengaged during lectures and score poorly on unit tests despite apparently paying attention. The course has 8 unit tests across the year, plus a final. No quizzing between tests.

**Audit result:** C1 absent, C2 absent (unit tests are not cumulative), C3 absent (one unit at a time, fully blocked), C4 absent, C5 absent, C6 partial.

**Redesign interventions selected:**
- Bi-weekly 3-question quiz (reach back 2 units, 15% of grade, 2 lowest dropped)
- Board exercise: students assigned to groups, each answers a synthesis question on whiteboards ("How did the economic causes of WWI compare to those of WWII?") — one student explains to the class
- Vertical topic curriculum: re-expose earlier units at greater complexity as year progresses
- First-class transparency module with student-friendly language

**Assessment calendar shift:** From 8 disconnected unit tests to 8 unit tests + 14 bi-weekly quizzes with cumulative reach-back + 4 synthesis writing exercises.

---

### Example 3: Corporate Professional Training (Post-Workshop Forgetting)

**Scenario:** A corporate L&D team runs a two-day sales training workshop for 40 new agents. Participants rate the sessions highly, but sales managers report that skills and knowledge are not visible in behavior 30 days later. The team suspects the workshop format — intensive lecture + role play, then nothing — is the problem.

**Audit result:** C1 absent (no retrieval practice after the workshop), C2 absent (no spaced review), C3 partial (topics covered across 2 days but not interleaved), C4 absent (no consequences for post-workshop engagement), C5 absent, C6 absent.

**Redesign interventions selected:**
- Replace the final half-day of the workshop with a generation exercise: participants work on a real case before the solution is presented
- Schedule 3 follow-up quiz modules at 1 week, 3 weeks, and 6 weeks post-workshop (mobile-delivered, 5 questions each, draws from workshop + prior quiz content)
- Brief transparency segment on day 1 of the workshop: explain why the difficult generation exercise is the point, not an obstacle
- Interleave the four training topics (sales, marketing systems, business planning, brand advocacy) across both days rather than covering each in sequence — adapted from Farmers Insurance's new-agent training model

**Expected outcome:** Knowledge and skills are visible in behavior at 30 and 60 days because the design includes distributed retrieval practice after encoding, not only during it.

---

## References

- `references/case-studies.md` — Detailed case studies: Wenderoth (University of Washington biology), Matthews/Thayer method (West Point), McDermott (Washington University), Sobel (political economics), Columbia IL school district results
- `references/bloom-taxonomy-implementation.md` — Bloom's taxonomy levels with classroom examples, Wenderoth's answer key template, question classification guide for creating higher-order quiz items
- `references/design-checklist.md` — Printable 6-criteria course design checklist with rating scale and redesign prompt for each criterion
- `references/transparency-scripts.md` — Sample first-class transparency scripts for university (biology/sciences), high school (humanities), and corporate training contexts; student-facing language for syllabi

## License

This skill is licensed under [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/).
Source: [BookForge](https://github.com/bookforge-ai/bookforge-skills) — Make It Stick: The Science of Successful Learning by Peter C. Brown, Henry L. Roediger III, Mark A. McDaniel.

## Related BookForge Skills

Install related skills from ClawhHub:
- `clawhub install bookforge-retrieval-practice-study-system`
- `clawhub install bookforge-practice-schedule-designer`
- `clawhub install bookforge-desirable-difficulty-classifier`

Or install the full book set from GitHub: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

FILE:references/bloom-taxonomy-implementation.md
# Bloom's Taxonomy Implementation for Classroom Design

Source: Brown, Roediger, McDaniel — *Make It Stick: The Science of Successful Learning*, Chapter 8; Bloom's taxonomy developed 1956 by committee chaired by Benjamin Bloom.

---

## The Six Levels

| Level | Name | What the learner does | Sample verbs |
|-------|------|----------------------|-------------|
| 1 | Knowledge | Recall facts, terms, definitions | Define, list, name, identify, recall |
| 2 | Comprehension | Explain underlying facts and ideas in own words | Describe, explain, summarize, paraphrase |
| 3 | Application | Use knowledge to solve problems | Apply, demonstrate, solve, calculate, use |
| 4 | Analysis | Examine ideas and relationships; make inferences | Analyze, compare, contrast, distinguish, infer |
| 5 | Synthesis | Combine knowledge and ideas in new ways | Design, create, construct, formulate, compose |
| 6 | Evaluation | Use learning to judge ideas based on evidence | Evaluate, critique, justify, assess, argue |

Most traditional lecture + exam courses test primarily at levels 1-2. High-structure courses with retrieval practice and board work push students toward levels 3-6.

---

## Wenderoth's Bloom's Answer Key — Template

For each exam question, provide four answers keyed to Bloom's levels. This is distributed to students with their graded exams.

**Example question (physiology):** "Explain how decreased blood pressure triggers aldosterone release."

| Level | Answer |
|-------|--------|
| Knowledge | "Decreased blood pressure triggers the release of aldosterone from the adrenal cortex." |
| Comprehension | "When blood pressure drops, the kidneys detect reduced perfusion and release renin. Renin triggers the angiotensin-aldosterone cascade, ultimately stimulating aldosterone release from the adrenal cortex." |
| Analysis | "The response to decreased blood pressure involves a multi-step hormonal cascade (renin → angiotensin I → angiotensin II → aldosterone) that is regulated by negative feedback. Aldosterone increases sodium reabsorption in the distal tubule, which draws water back into the circulation and raises blood pressure. The cascade is a designed correction mechanism, not a simple on/off switch." |
| Synthesis/Evaluation | [Full mechanistic answer integrating the RAAS pathway, downstream effects on potassium excretion, interaction with atrial natriuretic peptide as a counter-regulatory system, and the clinical implications for patients with heart failure or hypertension.] |

**Post-exam instruction to students:**
"Look at your answer to each question. Find where it falls on this taxonomy. Then identify: what specific knowledge would move your answer one level higher? That is your study target for the next unit."

---

## Designing Questions at Each Bloom's Level

### For quizzes (daily/bi-weekly)
Target levels 1-3. Quick to answer, easy to grade, appropriate for the frequency.

- Level 1: "Name the three components of the RAAS cascade."
- Level 2: "In your own words, explain why interleaving is more effective than blocked practice."
- Level 3: "A student is cramming for an exam two days from now. Which of the following study strategies would produce the most durable retention? Why?"

### For board work and recitation (in-class)
Target levels 3-5. Require integration and application; worth the discussion time.

- Level 3-4: "You are designing a study schedule for a medical student with 4 weeks before a comprehensive exam. What principles would guide your design?"
- Level 5: "Construct an argument for why a high-structure course might actually widen the achievement gap rather than narrow it. What evidence would you need to refute that argument?"

### For major exams
Include a mix of levels 2-6. Provide Bloom's answer keys for all questions.

---

## Classifying Your Existing Questions

To audit where your current exam questions fall on the taxonomy, ask:

- Can a student answer this by recalling a memorized fact or definition? → Level 1
- Can a student answer by restating the text in their own words? → Level 2
- Does answering require applying a concept to a new (not previously seen) problem? → Level 3+
- Does answering require identifying relationships, making inferences, or distinguishing between cases? → Level 4+
- Does answering require producing something new or making a judgment based on evidence? → Level 5-6

**Warning sign:** If more than 60% of your exam questions fall at level 1-2, the course is testing memory, not learning. High-structure interventions (retrieval practice, board work) are most valuable when paired with assessments that require students to use what they know.

FILE:references/case-studies.md
# Case Studies: Evidence-Based Classroom Design in Practice

Source: Brown, Roediger, McDaniel — *Make It Stick: The Science of Successful Learning*, Chapter 8 ("Make It Stick: Tips for Teachers")

---

## Mary Pat Wenderoth — University of Washington, Biology

Wenderoth teaches physiology and introductory biology. Her course design is the most fully documented example in the source book.

### Interventions

**Transparency at the outset.** Wenderoth opens every course by teaching students about the testing effect, the principle of desirable difficulties, and the illusion of knowing. She explains that highlighting a textbook in four colors — while it looks like work — is largely wasted time after the first read. She models retrieval in class by posing a question every 5 minutes and instructing students not to look at notes: "Stop. Do not look at your notes. Just take a minute to think about it yourself."

**Free recall (daily, 10 minutes).** Students spend 10 minutes at the end of each class writing everything they remember — on a blank page, without notes. They must sit for all 10 minutes even when they run out of ideas at 2 minutes. After 10 minutes, they check their notes and focus on what they forgot. This drives the agenda for what they bring to the next class.

**Testing groups.** Wenderoth transforms study groups into testing groups. In a study group, the person who knows the most explains and the others listen — producing dependency and shallow encoding. In a testing group, the whole group wrestles with a question together without opening any textbook. Wenderoth sends one student to the whiteboard to explain a concept they feel uncertain about; the rest test that student by asking questions that lead toward the full answer. All textbooks stay closed.

**Summary sheets (weekly, due Monday).** Students submit a single page on which they illustrate the prior week's material — physiology-appropriate format: large cartoons dense with callouts, directional arrows, blowups, labels showing "this causes this, which causes this, which feeds back on those." The sheet forces synthesis across the week's content and requires students to understand how systems are connected, not just what they are called.

**Learning paragraphs (monthly, low stakes).** On Fridays when she judges the workload reasonable, Wenderoth assigns a 5-6 sentence response to a synthesis question: "How is the GI tract like the respiratory system?" or "You just got your tests back; what would you do differently next time?" She reads every response and comments on them in class so students know they were read. Purpose: capture a week's learning before it fragments; give science students deliberate writing practice.

**Bloom's taxonomy answer keys.** For every graded exam, Wenderoth provides an answer key organized by Bloom's level: one answer reflecting knowledge-level recall, a more thorough answer reflecting comprehension, a more complex answer reflecting analysis, and so on. Students receive the key with their graded tests, locate where their answers fell on the taxonomy, and identify what they would need to know to reach the next level. This shifts the post-exam conversation from "did I get it right?" to "at what cognitive level did I understand this?"

### Results

High-structure classes (daily and weekly low-stakes exercises) compared to low-structure classes (traditional lecturing + high-stakes midterm and final):
- Significantly reduced student failure rates in gateway biology courses
- Narrowed the achievement gap between poorly prepared and well-prepared students
- Showed exam performance at higher Bloom's taxonomy levels
- Finding on consequences: in classes where practice exercises count toward the grade (even at very low stakes), students achieve higher success over the course of the term compared to classes where the exercises are identical but carry no grade consequences

---

## Michael D. Matthews — West Point, Engineering Psychology

### The Thayer Method

Developed almost 200 years ago by Sylvanus Thayer, an early superintendent of the U.S. Military Academy. Still in active use.

**Structure:**
- Specific, explicit learning objectives are set for every class meeting — students know exactly what they are expected to master before attending
- Responsibility for meeting those objectives sits with the student, not the instructor
- Every class opens with a quiz on the learning objectives from the assigned reading
- On most days, students "take to the boards" — assigned to groups, sent to slates covering all four walls of the classroom, given a higher-order question to answer
- Higher-order questions require integration of ideas from the reading and application at a conceptual level — not just the quiz-level recall
- One student per group gives a recitation to the class, explaining how the group answered the question; the group's work is then critiqued
- No conventional lecturing; every class meeting is organized around student generation, demonstration, or group problem-solving

**Matthews's approach to reading:**
"If you've read every word of this chapter, you're not being very efficient." Students are instructed to read for answers to specific questions — not to slide their eyes over the words. Efficient reading is targeted retrieval practice, not passive reading.

**Key result cited by Matthews:**
The method is especially effective for students who are not self-motivated to work outside of class — the high-structure requirement creates the discipline that some students lack. Echoes Wenderoth's finding that high-structure courses help under-prepared students most.

### Student example: Cadet Kiley Hunkler (Rhodes Scholar)

For MCAT preparation, Hunkler created learning objectives in her head for each course block, then read toward those objectives rather than reading every word. "I took a practice test every three days, saw what I got wrong, and adjusted." She describes this as "shooting an azimuth" — periodically checking whether you're on course toward your objective. Her approach: understand constructs, not memorize facts. "What is this question asking, what's the broader theme here, and does that match up with what I've outlined for this section?"

---

## Kathleen McDermott — Washington University at St. Louis, Psychology

### Daily Quizzing System

**Course:** Human Learning and Memory — 25 students, meets 2x/week, 14 weeks

**Quiz format:**
- 4 questions, given in the last 3-5 minutes of every class
- Questions address the high points of the lecture, the readings, or both
- Any material covered to date is fair game — not only the current session
- McDermott draws from past material when she judges it was not fully grasped

**Ground rules (set explicitly at the start of term):**
- Students may drop 4 quizzes across the semester — no questions asked
- In exchange, absences need not be justified
- No missed quizzes will be made up — ever
- Quizzes count for 20% of the course grade
- Two midterms + a final exam; the last two exams are cumulative

**Student response over the term:**
- First few weeks: students email asking for makeup accommodations for legitimate absences
- McDermott reiterates: 4 free absences, no makeups
- By end of semester: students report quizzes helped them keep up with the course and discover when they were getting off track early enough to correct

**McDermott's framing for instructors:** "The key with quizzes is to establish very clear ground rules for the student, and make them manageable for the professor. As a student, you're either there and you take it, or you're not. For the professor, no hassling over makeup tests."

---

## Andy Sobel — Political Economics (University-Level)

**System:** Cumulative low-stakes quizzing throughout the course.

**Principle:** Any quiz can draw from any material covered so far in the course, not only the most recent unit. This forces students to maintain and build on prior learning throughout the term rather than treating each unit as a self-contained episode to be learned, tested, and forgotten.

**Effect:** Students build incrementally complex mental models over the course of the semester, strengthening conceptual learning and developing deeper understanding of relationships between ideas and systems. The final exam is not a shock because the student has been continuously practicing retrieval across the whole course timeline.

---

## Columbia, Illinois Public School District

**Initial research:** Collaborative study with district middle school teachers to test the effects of integrating low-stakes quizzing into curriculum.

**Results:** Teachers who participated in the research adopted the practices; teachers who did not participate but observed results adopted them anyway.

**Expansion:** Research extended into history and science classes in the district's high school. Frequent retrieval practice is used both to bolster learning and to help teachers focus instruction on areas where student understanding needs improvement.

**Curriculum redesign:** The district is redesigning curriculum with the Common Core State Standards, vertically aligning sciences curriculum so students are re-exposed to subjects at various stages of their school careers — producing naturally spaced and interleaved instruction. Example: Middle school students learn to identify the six basic machines and how they work; they return to these concepts in subsequent grades, learning the underlying physics, and later how these tools combine and apply to different problems.

**Key result cited in Chapter 2 (testing effect):** Students who were regularly quizzed on science material retained it at 92%; students who were not quizzed retained 79% — a 13-percentage-point gap from a low-cost, low-effort intervention.

---

## Farmers Insurance — Corporate New-Agent Training

An example of interleaving applied at corporate scale.

**Structure:** 1-week intensive training program for ~2,000 new agents annually. Four training topics: sales, marketing systems, business planning, brand advocacy.

**Design:** Rather than covering each topic in sequence (all of sales, then all of marketing, then all of business planning), the four topics are interleaved throughout the week. Each session cycles back to previous topics in a new, enlarged context — requiring participants to recall what they learned earlier and apply it to the new situation.

**Effect:** At each return to a topic, understanding deepens and new skills take form. Participants learn to integrate the four domains rather than treating them as separate disciplines. A tool introduced as a social icebreaker (FORE: Family, Occupation, Recreation, Enjoyment) morphs across the week into a sales prospecting framework — the same idea, deepened through repeated application in different contexts.

**Key principle illustrated:** Interleaving is not randomness — it is deliberate sequencing that forces participants to reload prior knowledge at each return, building the mental model progressively rather than accumulating isolated units.

FILE:references/design-checklist.md
# 6-Criteria Course Design Checklist

Source: Brown, Roediger, McDaniel — *Make It Stick: The Science of Successful Learning*, Chapter 8

Use this checklist to audit any course, training program, or instructional design. Rate each criterion and use the redesign prompts to address gaps.

---

## How to Use

1. For each criterion, assign a rating: **Present / Partial / Absent**
2. Note the specific evidence that supports your rating (or the specific gap)
3. If rated Partial or Absent, use the redesign prompt to plan your intervention

A course with all 6 criteria rated **Present** is a high-structure, evidence-based design. A course with 3 or more rated **Absent** is a low-structure design and is likely producing high forgetting rates and poor transfer.

---

## The Checklist

### C1. Low-Stakes Retrieval Practice

**What it requires:** Frequent quizzes, self-tests, or recall exercises that occur *during* the course — not only at midterm and final. Students must retrieve information from memory, not recognize it from a list.

**Rating criteria:**
- **Present:** Quizzes occur at every class or every other class; short-answer or recall format; cumulative reach-back built in
- **Partial:** Occasional quizzes but not systematic; or quizzes exist but are low-frequency (once per unit)
- **Absent:** Only midterm and final; no in-course retrieval practice

**Redesign prompt if Absent or Partial:**
"Add 3-5 question quizzes at the start or end of class, at least every other meeting. Use short-answer format. Draw from current material plus material from 2-3 prior sessions. Count toward grade at 15-20%, drop 3-4 lowest."

**Research anchor:** Quizzed material retained at 92% vs. 79% non-quizzed, Columbia IL middle school science study (3-semester study).

---

### C2. Spaced and Cumulative Review

**What it requires:** Assessments or exercises that reach back to prior material — not only the current unit. Students are required to maintain and build on prior learning throughout the term.

**Rating criteria:**
- **Present:** Quiz and exam content draws from any point in the course to date; earlier material returns in new contexts; final exam or capstone is explicitly cumulative
- **Partial:** Some reach-back in quizzes but exams are unit-by-unit; or spacing exists but is unintentional
- **Absent:** Each unit is fully self-contained; no assessment requires prior material; all quizzes and tests cover only the most recent content

**Redesign prompt if Absent or Partial:**
"Redesign quiz content windows to draw from any material covered so far. Make the final exam explicitly cumulative and explain to students that this is how the course works from day one. If covering a new concept, ask at least one quiz question that connects it to a concept from an earlier unit."

**Research anchor:** Sobel's cumulative quizzing builds incrementally complex mental models; students who practice cumulative recall build stronger conceptual frameworks than those who compartmentalize.

---

### C3. Interleaving Across Topics

**What it requires:** Topics or problem types are mixed across sessions rather than blocked by unit. Students must "reload" prior knowledge when switching topics, which strengthens discrimination and transfer.

**Rating criteria:**
- **Present:** Topics are explicitly interleaved; the course returns to earlier topics at greater complexity levels; the syllabus shows vertical alignment or spiraling
- **Partial:** Some interleaving occurs in labs or projects but lectures are blocked; or interleaving is occasional, not systematic
- **Absent:** All content is strictly sequential; each topic is completed before the next begins; no deliberate spiraling

**Redesign prompt if Absent or Partial:**
"Map the course topics and identify where natural conceptual connections exist across units. Restructure to introduce Topic A at a basic level, introduce Topic B, then return to Topic A at a higher complexity level with Topic B as context. Use the Columbia IL vertical alignment model as a template."

**Research anchor:** Interleaving produces better transfer to novel problems than blocked practice because it requires students to identify which approach applies — the same discrimination required in real application.

---

### C4. Consequences (Low Stakes)

**What it requires:** Practice exercises count toward the course grade, even at minimal weight. The exercises being graded (rather than purely optional) is the mechanism that motivates engagement.

**Rating criteria:**
- **Present:** All practice exercises carry a grade contribution, even small; the grading policy is stated clearly in the syllabus
- **Partial:** Some practice is graded; some is optional; students can achieve a high grade without engaging with low-stakes practice
- **Absent:** All practice exercises are optional and ungraded; only midterm and final count toward the grade

**Redesign prompt if Absent or Partial:**
"Make all low-stakes practice count toward the final grade, even at 10-20% total. Use a drop policy (drop 3-4 lowest) rather than a makeup policy to make the system sustainable for you and the student. State the policy explicitly in week 1."

**Research anchor:** Wenderoth's research: students in classes where exercises count toward the grade achieve higher success over the term than students in classes where the exercises are identical but carry no consequences.

---

### C5. Transparency About How Learning Works

**What it requires:** The instructor explicitly explains why the course is designed the way it is — including what the research shows about retrieval practice, spacing, and desirable difficulties — and continues to reference this throughout the term.

**Rating criteria:**
- **Present:** First-class orientation module covers testing effect and desirable difficulties; instructor references the design rationale throughout the term when students encounter difficulty; student-facing syllabus language explains the design
- **Partial:** Brief mention of why quizzes are used, but no detailed explanation; instructor does not revisit the rationale when students struggle
- **Absent:** No explanation of course design philosophy; students experience difficulty without a framework for interpreting it; complaints about quiz difficulty go unexplained

**Redesign prompt if Absent or Partial:**
"Add a 10-15 minute transparency module to the first class. Explain the testing effect, the illusion of knowing, and what desirable difficulties are. Reference the design rationale each time students encounter a difficult exercise. Provide student-facing language in the syllabus explaining why the course is structured this way."

**Research anchor:** Wenderoth: students who understand the illusion of knowing bring solvable problems to office hours rather than complaints about trick questions. Transparency changes the behavioral response to difficulty.

---

### C6. Calibration Feedback

**What it requires:** Students receive timely feedback that reveals what they actually know vs. what they think they know. Feedback is actionable — it shows specific gaps rather than just a score.

**Rating criteria:**
- **Present:** Quiz feedback is provided at or within one class meeting; students can compare their recalled answer to the correct answer; Bloom's-level answer keys distributed with major assessments
- **Partial:** Grades are returned but without itemized feedback; or feedback is delayed too long (> 1 week) to be actionable
- **Absent:** Students receive only a letter grade or percentage; no diagnostic feedback on which concepts were missed or at what cognitive level

**Redesign prompt if Absent or Partial:**
"Return quiz feedback within the same class meeting or the next one. For major exams, distribute Bloom's-level answer keys so students can identify what cognitive level their answer reached and what they would need to know to improve. Use quiz data to identify topics where student understanding needs re-teaching."

**Research anchor:** Without calibration feedback, students rely on subjective confidence (the fluency illusion) to guide study decisions — and overconfident students study the wrong material.

---

## Summary Scorecard

| Criterion | Rating | Priority for redesign |
|-----------|--------|----------------------|
| C1. Low-stakes retrieval practice | | |
| C2. Spaced and cumulative review | | |
| C3. Interleaving across topics | | |
| C4. Consequences (low stakes) | | |
| C5. Transparency about learning | | |
| C6. Calibration feedback | | |

**Interpretation:**
- 6 Present: High-structure, evidence-based design
- 4-5 Present: Good foundation; address remaining gaps
- 2-3 Present: Low-structure; significant forgetting likely; start with C1 and C5
- 0-1 Present: Low-structure design; students are almost certainly cramming; prioritize C1, C4, and C5 as the minimum viable redesign

FILE:references/transparency-scripts.md
# Transparency Scripts for Course Design Communication

Source: Brown, Roediger, McDaniel — *Make It Stick: The Science of Successful Learning*, Chapter 8

These scripts are starting points. Adapt tone, examples, and specifics to your course, level, and student population.

---

## University / Sciences (10-12 minutes)

*Intended for: First class of a gateway or introductory course. Instructor has added daily or bi-weekly quizzes and active learning exercises.*

---

"I want to spend the first 10 minutes of this course talking about how you learn — not what you're going to learn in this class, but how your brain actually stores and retrieves information. Because most of you have been using study strategies that feel productive but aren't, and this course is designed differently.

Here's the first thing you need to know: rereading does not produce learning. I know that sounds wrong, because rereading feels like it's working. When you reread your notes or your highlighted textbook, you get more fluent with the material. It starts to feel familiar. And familiar feels like knowing.

But familiarity is not memory. The feeling that you know something is not the same as actually being able to use it. There is a term for this: the illusion of knowing. It is one of the most reliable predictors of exam failure despite genuine effort. You've studied for hours; you feel prepared; you fail the exam anyway.

What actually builds durable memory is retrieval — the act of pulling something from memory when you can't immediately see the answer. This is called the testing effect, and it is one of the most replicated findings in cognitive psychology. When you struggle to recall something, you strengthen the memory pathway to it. When you look at your notes and recognize the answer, you do not.

This course is designed around that principle. We will have short quizzes frequently — more often than you probably expect. Those quizzes will sometimes cover material from several weeks ago. They will often feel harder than you expected, especially early in the course. That difficulty is not a sign that you haven't studied enough. That difficulty is the mechanism.

Another thing you should know: your intellectual ability in this course is not fixed. When learning is effortful, it changes your brain. When you struggle with a concept and eventually grasp it, you are literally building new connections. Students who persist through that struggle become stronger learners over time. Students who interpret the struggle as a sign they don't belong in this discipline — and give up — are misreading the signal.

There are a few specific things I'm going to ask you to do in this course that may feel strange. I'm going to ask you to write down everything you remember from class for 10 minutes with your notes closed. I'm going to send you to the board to explain things you're not sure you fully understand. I'm going to ask you questions about material we covered three weeks ago.

All of these are hard. All of them are working.

I'll explain my design choices as we go. If something feels difficult or frustrating, come see me — and come ready to talk about what specifically you don't know. We can work with that."

---

## High School (8-10 minutes)

*Intended for: First day of a high school course. Teacher has added bi-weekly quizzes and changed some class activities from passive listening to board work or writing.*

---

"I want to tell you something about this class before we get started. This class is probably set up a bit differently from what you're used to, and I want to explain why so you don't think I'm just trying to make your life harder.

Here's the honest truth about studying: most of what you've been told to do doesn't work very well. Highlighting your notes in multiple colors. Rereading chapters before a test. Reading your flashcards over and over until you recognize the answers. None of these are actually good ways to learn something permanently. They feel productive — and that's the problem. They give you the feeling of knowing without the actual ability to remember.

What actually works is harder. It's testing yourself — trying to remember something before you're sure you can. It's writing down everything you can recall about yesterday's lesson without opening your notebook. It's working through a problem before I've explained the solution. It's being asked about something you learned three weeks ago.

All of those are uncomfortable. They all feel like you're failing. You'll hit a wall at two minutes during a free recall exercise and think "I don't know anything." That's normal. That's the point. Every time you struggle to pull something from memory, you're making that memory stronger.

In this class, we're going to do quizzes — short ones, pretty often. These aren't meant to trap you. They're meant to give you and me accurate information about what you actually know. They're also worth a small part of your grade, because I want you to actually do them. But no single quiz is going to define your grade.

I'll always tell you why I'm doing what I'm doing. If I ask you to do something that seems weird or hard, ask me. I'll explain the reason."

---

## Corporate / Professional Training (5-7 minutes)

*Intended for: First session of a multi-day workshop or training program. Facilitator has added a generation exercise or pre-class challenge.*

---

"Before we get into the content today, I want to be transparent about how this training is designed, because it's probably not what you're used to.

Most professional training follows the same format: expert presents content, participants listen and take notes, everyone rates the session highly, nothing sticks. That's not a criticism of the trainers or the participants — it's how we've been conditioned to think about training. But the research on memory is clear: passive listening followed by nothing produces almost no durable learning.

What produces durable learning is retrieval. Testing yourself. Generating answers before you've been given them. Coming back to the same content multiple times over days and weeks rather than absorbing it in one sitting.

This training is designed to do those things. In about 20 minutes, you're going to be handed a problem you don't yet have all the tools to solve. You're going to work on it anyway — in groups. That generation exercise is not a trick. The struggle of working toward a solution before you've been taught it makes the subsequent instruction significantly more effective. You'll encode it faster and retain it longer.

We're also going to follow up with you over the next several weeks with short check-ins that revisit what you learned here. Those are not tests. They're scheduled practice — the mechanism that converts a workshop into a skill.

The goal of all of this is simple: we want what you learn here to still be in your head and your hands 60 days from now, not just during this week. Everything we're doing is in service of that."

---

## Student-Facing Syllabus Language (1 paragraph)

*Adaptable for any course level. Insert into the course philosophy or assessment section of the syllabus.*

---

**Version A (University):**
"This course uses evidence-based instructional design. You will encounter frequent low-stakes quizzes, exercises that require you to recall material without notes, and questions about content from earlier in the semester. These practices are intentional. Research in cognitive psychology consistently shows that the difficulty of retrieving information — rather than recognizing it — is precisely what builds durable memory and transferable understanding. The quizzes are not meant to trap you; they are the mechanism by which you learn. If the approach feels unfamiliar or frustrating, please come to office hours — and bring specific questions about what you don't yet understand."

**Version B (High School):**
"In this class, we use research-backed learning strategies that may feel different from other classes. You'll take short quizzes regularly, including on material from earlier units. You'll sometimes work through problems before I've shown you the solution. These activities are harder than rereading your notes — and that difficulty is the point. Every time you struggle to recall something, you're strengthening your memory of it. I'll explain the reasons behind everything we do. Ask me if something doesn't make sense."

**Version C (Corporate / Professional):**
"This training program uses spaced retrieval practice to improve long-term skill retention. You will receive brief follow-up exercises at 1, 3, and 6 weeks after the workshop. These are short (5 questions, ~5 minutes) and are designed to maintain what you learned rather than test your performance. Participants who complete the follow-up exercises consistently demonstrate stronger retention and application 60 days post-training than those who attend the workshop only."

---
name: text-prospecting-sequence-builder
description: |
  Build a situation-appropriate text prospecting sequence with timing, tone, and per-touch templates.

  Trigger this skill when you need to:
  - Text a prospect after a networking event or trade show meeting ("text message prospecting", "text after meeting")
  - Follow up on a hot inbound lead via SMS ("text a prospect", "SMS sales")
  - Rescue a no-show appointment with a text ("post-no-show text")
  - Send a text after leaving a voicemail ("text after voicemail", "post-vm text")
  - Know when it is and is not appropriate to text a prospect ("when to text a prospect")
  - Build a text sequence with correct timing and cadence ("text sequence", "mobile outreach")
  - Check whether a draft text message violates the 7 professional text rules
  - Understand the Bridge-Because pattern adapted for short-form text

  NOT for: writing a cold text to a complete stranger (text requires permission earned through prior contact —
  use cold-call-opener-builder or prospecting-message-crafter first). This skill assumes you have a legitimate
  reason to text: you met the person, they engaged with your content, or they came in as a warm inbound lead.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/fanatical-prospecting/skills/text-prospecting-sequence-builder
metadata:
  openclaw:
    emoji: "📚"
    homepage: "https://github.com/bookforge-ai/bookforge-skills"
status: published
source-books:
  - id: fanatical-prospecting
    title: "Fanatical Prospecting"
    authors:
      - Jeb Blount
    chapters:
      - 20
tags:
  - sales
  - prospecting
  - text-messaging
  - sms
  - sdr
  - bdr
depends-on:
  - prospecting-message-crafter
execution:
  tier: 2
  mode: hybrid
  inputs:
    - type: document
      description: "Prospect context + situation type (post-networking / hot-inbound / post-voicemail / post-no-show) + what has been agreed to so far (if anything)"
  tools-required: [Read, Write]
  tools-optional: []
  mcps-required: []
  environment: "Document directory — agent reads user-provided context file or inline description and writes the text sequence to text-sequence-output.md"
discovery:
  goal: "Produce a situation-appropriate text sequence with per-touch message copy, timing, and rationale that passes the 7-rule professional text check"
  tasks:
    - "Verify the permission/familiarity gate: confirm prior contact exists before building any sequence"
    - "Identify the situational protocol: post-networking / hot-inbound / post-voicemail / post-no-show"
    - "Draft each touch using the Bridge-Because pattern adapted for short-form text"
    - "Set timing and cadence per the protocol (not too soon, not too many, not too formal)"
    - "Run the 7-rule anti-pattern check on every message before finalizing"
    - "Write the sequence to text-sequence-output.md"
  audience:
    roles: [sdr, bdr, ae, founder-self-seller]
    experience: beginner
  when_to_use:
    triggers:
      - "Just left a networking event and want to follow up via text within 24 hours"
      - "A hot inbound lead came in and you want to text before the trail goes cold"
      - "Left a voicemail and want to reinforce with a text"
      - "A prospect missed a scheduled appointment and you want to rescue it"
      - "Someone asks what to say in a text to a prospect"
      - "Checking whether a drafted text is professional enough to send"
    prerequisites:
      - "Prior contact with the prospect through at least one other channel (meeting, phone call, email, social interaction)"
    not_for:
      - "Texting a cold prospect with zero prior contact (zero familiarity = spam, not prospecting)"
      - "Building multi-touch email cadences (use cold-email-writer)"
      - "Scripting a live phone call (use cold-call-opener-builder)"
      - "Repairing a message bridge or bridge type (use prospecting-message-crafter)"
  environment:
    codebase_required: false
    codebase_helpful: false
    works_offline: true
  quality:
    scores:
      with_skill: 0
      baseline: 0
      delta: 0
    tested_at: ""
    eval_count: 0
    assertion_count: 0
    iterations_needed: 0
    what_skill_catches:
      - "Enforces the familiarity gate — refuses to build a cold text sequence (no prior contact = no text)"
      - "Names the 4 situational protocols (post-networking / hot-inbound / post-voicemail / post-no-show) and routes to the correct one"
      - "Applies Bridge-Because pattern in short-form text: personalized context + because + direct ask"
      - "Enforces the 7 professional text rules: identify yourself, complete sentences, 1-4 sentences max, no abbreviations, full URLs only, proof before sending, track numbers"
      - "Sets correct timing per protocol (within 24 hours for networking; immediate for hot inbound)"
      - "Caps the sequence at 2 text attempts before shifting to phone/email"
      - "Checks for direct solicitation language in nurture/engagement texts and flags it"
    what_baseline_misses:
      - "Texts cold prospects without establishing familiarity first"
      - "Does not identify the situation type — writes one generic text for every scenario"
      - "Uses emoji, slang, abbreviations, or shortened links"
      - "Writes more than 4 sentences — texts that feel like emails"
      - "Does not identify themselves (assumes prospect has their number saved)"
      - "Sends texts three or four times when no response — creating ill will"
      - "Includes a direct solicitation in a nurture or engagement text"
---

# Text Prospecting Sequence Builder

## When to Use

Text is a **permission-earned channel**. You can call a stranger, email a stranger, and meet a stranger in person — but you almost never text a stranger. Text occupies the same mental space as family, friends, and close colleagues. When a salesperson lands there uninvited, they are not a prospector — they are spam.

This skill builds text sequences for situations where permission has already been established through prior contact:

- You met someone at a networking event, trade show, or conference and agreed to connect
- A warm inbound lead came in (download, demo request, referral) and you want to reach them while intent is high
- You left a voicemail and want to reinforce it on the same channel sweep
- A prospect missed a scheduled appointment and you want to quickly offer a rescue

**Do not use this skill to text a cold prospect.** If no prior contact exists, build a bridge first using `prospecting-message-crafter`, reach out by phone or email, and earn the familiarity that makes texting effective.

**Why text works when used correctly:** A Lead360 study of 3.5 million lead records found that a text sent alone converts at 4.8 percent. The same text sent after a phone contact increases conversion by 112.6 percent. Familiarity is the multiplier — not the message itself. (Blount, p. 256)

## Context and Input Gathering

Before building the sequence, gather or ask the user for:

**Required:**
1. Situation type — post-networking / hot-inbound / post-voicemail / post-no-show
2. What was agreed or communicated in the prior contact (vague "let's connect," confirmed appointment, inbound download, etc.)
3. Prospect's name and role
4. Anything personal or specific mentioned in the prior conversation (used to personalize)

**Recommended:**
5. What outcome you want from this text sequence (appointment / call / reschedule)
6. Any trigger event or relevant detail at the prospect's company (for hot-inbound or post-networking)

**If a draft text already exists:** read it, run the 7-rule check in Step 4, and revise before producing the sequence.

## Process

### Step 1 — Verify the Permission Gate

Before writing a single character, confirm prior contact exists. Ask:

> "Has there been at least one prior touchpoint with this prospect — an in-person meeting, a phone call, an email exchange, or a social media interaction?"

If the answer is no, **stop**. Direct the user to `cold-call-opener-builder` or `prospecting-message-crafter` to initiate contact through a more forgiving channel first. Texting a cold prospect creates immediate negative association and may result in the number being reported as spam.

**Why this gate matters:** The personal nature of the text channel is precisely what makes it powerful — and what makes unauthorized entry feel like a violation. A text from an unknown number asking for time feels like spam regardless of message quality. (Blount, p. 255)

### Step 2 — Identify the Situational Protocol

Route to the correct protocol based on what happened before this text:

| Situation | Protocol | Primary Goal |
|---|---|---|
| Met at networking event / trade show / conference | Post-Networking | Anchor the vague "let's get together" into a real appointment |
| Inbound lead (download, demo request, referral) | Hot-Inbound | Reach the lead while intent is high; set appointment or qualify |
| Left a voicemail and want to reinforce | Post-Voicemail | Increase the probability the prospect engages with your message |
| Prospect missed a scheduled appointment | Post-No-Show | Rescue the meeting without creating awkwardness |

Each protocol has a different timing, tone, and call-to-action. Do not mix them — a post-no-show text written in a hot-inbound tone feels pushy; a hot-inbound text written in a post-networking tone feels too casual for the urgency.

**Why situational routing matters:** Text messaging as a channel offers almost no room for error — a wrong tone at the wrong moment and the prospect ignores you permanently. Matching the text's energy to the situation's context maximizes the chance of a reply. (Blount, pp. 256-261)

### Step 3 — Draft the Sequence Using Bridge-Because in Short Form

For each touch in the sequence, build the message using the Bridge-Because pattern adapted for text constraints. Unlike a phone opener or email that has room for a full WIIFM-Bridge-Because-Ask arc, a text must compress this into 1-4 sentences.

**Text Bridge-Because structure:**
> [Identify yourself + company] + [personalized context that connects to their world] + [because: what's in it for them] + [specific ask]

Keep each message to **one to four sentences and under 250 characters when possible**. Complete sentences only — no abbreviations, no slang, no emoji.

**Protocol-specific sequence templates:**

---

**Post-Networking Protocol (5-step sequence):**

*Context: You met at an event, had a positive conversation, and made a vague agreement to connect.*

- **During the conversation (spoken, not texted):** Casually say: "Sounds good — I'll text you and we can get together." This pre-empts any later surprise that you are texting them. If the conversation was positive, they will not object.

- **Immediately after walking away (action, not text):** Send a personalized LinkedIn connection request from your phone. This anchors your name and face before the text arrives.

- **Touch 1 — Within 24 hours (text):**
  > "[Name], this is [Your Name] from [Company]. Great talking with you at [event] — [something specific from conversation]. I'd like to follow up on [what you discussed]. How about [specific day/time]?"

- **Touch 2 — One day later if no response (text):**
  > "[Name], [Your Name] from [Company] again — wanted to make sure my earlier text got through. How about [alternative specific day/time] to connect?"

- **If Touch 2 fails:** Shift to phone and email. Do not send a third text. Repeated texts without response create ill will. (Blount, p. 257)

- **Bonus action:** Send a handwritten note via mail within one week of the event. This stands out from everyone else who promised to follow up and didn't. (Blount, p. 257)

---

**Hot-Inbound Protocol (2-touch sequence):**

*Context: A warm lead came in via download, demo request, referral, or website form.*

- **Touch 1 — As soon as possible, ideally within minutes (text):**
  > "[Name], this is [Your Name] from [Company]. I saw you [downloaded / requested / were referred] — thanks for reaching out. I'd like to connect quickly. Are you available [specific day/time] for a brief call?"

- **Touch 2 — Next business day if no response (text):**
  > "[Name], [Your Name] from [Company]. Following up on my text from yesterday. I have time [specific day/time] — does that work for a quick call?"

- **If Touch 2 fails:** Move to phone and email follow-up. The inbound intent window closes fast — do not let text be your only channel for hot leads.

---

**Post-Voicemail Protocol (1-touch supplement):**

*Context: You just left a voicemail on the same prospecting sweep. The text reinforces the voicemail.*

- **Touch 1 — Immediately after leaving the voicemail (text):**
  > "[Name], this is [Your Name] from [Company] — I just left you a voicemail. [One-sentence reason for reaching out]. How about [specific day/time] for a brief call?"

Do not send a second text after a post-voicemail text. The voicemail and the text together are your combined touch. If neither gets a response, log it and move to the next prospect in your sequence.

---

**Post-No-Show Protocol (1-2 touch rescue):**

*Context: The prospect had a scheduled appointment and did not show up.*

- **Touch 1 — Within 15-30 minutes of the missed appointment (text):**
  > "[Name], this is [Your Name] from [Company] — I had us scheduled for [time] today. No worries if something came up. How about we reschedule to [specific day/time]?"

- **Touch 2 — Next day if no response (text):**
  > "[Name], [Your Name] from [Company]. Wanted to try once more on rescheduling our call — would [specific day/time] work?"

- **If Touch 2 fails:** Move to phone and email. Do not express frustration or passive-aggressiveness in any text. Tone in a no-show situation is especially fragile. (Blount, p. 257)

### Step 4 — Run the 7-Rule Anti-Pattern Check

Before finalizing any text in the sequence, check each message against these seven rules. Flag any violation and revise before outputting.

| Rule | What to check | Why it matters |
|---|---|---|
| 1. Identify yourself | Does the text start with your name and company? | Prospects rarely have your mobile number saved. Anonymity = spam. (Blount, p. 261) |
| 2. Professional tone, complete sentences | Are there fragments, sarcasm, or abrupt phrasing? | Text lacks vocal tone; incomplete sentences read as harsh or dismissive. (Blount, p. 261) |
| 3. 1-4 sentences, under 250 characters | Is the message longer than four sentences? | Text is not email. A wall of text signals lack of respect for the channel. (Blount, p. 261) |
| 4. No abbreviations or slang | Does the text include LOL, OMG, BTW, or any informal shorthand? | Abbreviations are unprofessional and may confuse the prospect. (Blount, p. 262) |
| 5. Full URLs only | If linking to an article or resource, is the full URL used? | Shortened URLs feel suspicious and reduce click trust. (Blount, p. 262) |
| 6. Proof before sending | Has the message been read aloud once before finalizing? | Text errors are irreversible and permanent. One re-read catches most mistakes. (Blount, p. 262) |
| 7. No direct solicitation in nurture or engagement texts | Does a nurture or engagement text ask for anything? | Nurture texts work because they give value with no ask. The moment you solicit, you break the pattern. (Blount, p. 261) |

**Additional anti-patterns to flag:**
- **Emoji** — do not use emoji in any prospecting text. The channel feels personal; emoji reads as unprofessional in a sales context. (Blount, p. 261)
- **Images or attachments** — text is not the channel for sending decks, images, or PDFs. This belongs in email.
- **More than 2 attempts without a response** — sending a third text signals desperation and creates ill will.

### Step 5 — Output the Sequence

Write the finalized sequence to `text-sequence-output.md` in the working directory. Include:

- The situation type and protocol selected
- Each touch with: message copy ready to send, timing instruction, and one-line rationale
- The 7-rule check result for each message (pass/flag)
- Any anti-patterns found in a user-provided draft and what was changed

## Inputs

| Input | Required | Source |
|---|---|---|
| Situation type (post-networking / hot-inbound / post-voicemail / post-no-show) | Yes | User states |
| Prior contact description (what was said, agreed to, or triggered) | Yes | User provides |
| Prospect name and role | Yes | User provides |
| Personalization detail from prior conversation | Recommended | User provides |
| Desired outcome (appointment / call / reschedule) | Recommended | User states |
| Existing draft text (if any) | No | User pastes inline |

## Outputs

| Output | Location | Description |
|---|---|---|
| `text-sequence-output.md` | Working directory | Complete sequence with per-touch copy, timing instructions, 7-rule check, and rationale |
| Anti-pattern diagnosis (if draft provided) | Inline in conversation | What was wrong, why, and what was changed |

## Key Principles

**1. Permission is everything.** Text is the most personal prospecting channel. Familiarity earned through prior contact is not a preference — it is a prerequisite. Without it, every text is spam regardless of message quality. (Blount, p. 255)

**2. Short-form only.** Text is not a delivery vehicle for pitches, case studies, or paragraphs. The constraint of 1-4 sentences forces the Bridge-Because pattern to its sharpest form: one personalized observation, one reason, one ask.

**3. Conversational, not salesy.** The tone that works in text is the same tone you would use with a recent acquaintance — warm, direct, low-pressure. Any hint of "buy now" language triggers the same reaction as a stranger texting you an ad.

**4. Two attempts maximum.** After two unreturned texts, shift channels. Repeated texts to someone who is not responding create resentment, not familiarity. The same prospect who ignores your second text may engage readily if you reach them by phone a week later.

**5. Reserve your best value-added content for text.** When nurturing a prospect over months, save the most relevant articles, insights, or news items for text rather than email. Text messages are read immediately; email competes with hundreds of others. (Blount, p. 260 — Matt case study)

## Examples

---

### Example 1 — Post-Networking Follow-Up (SDR / SaaS Event)

**Situation:** You met Jennifer, VP of Engineering at a mid-size fintech company, at a developer conference. You had a 10-minute conversation about her team's challenge with deployment reliability. She said "yeah, we should connect sometime." You did not explicitly agree on a time.

**During the conversation (spoken):** "Sounds great — I'll text you and we can find a time."

**Immediately after (action):** Send LinkedIn connection request from phone with a note: "Great meeting you at DevCon — looking forward to connecting."

**Touch 1 (within 24 hours):**
> "Jennifer, this is Alex from Reliably — great talking with you at DevCon about your deployment pipeline situation. I'd like to follow up on that. How about a 20-minute call Thursday at 2 PM?"

| Element | Content |
|---|---|
| Identify | Name + company in first line |
| Personalization | Event name + specific topic from conversation |
| Because | Implicit in the reference — she knows why connecting matters |
| Ask | Specific day and time, low-friction framing |
| 7-rule check | Pass: identifies self, complete sentences, under 4 sentences, no abbreviations, no links, proofed |

**Touch 2 (next day, no response):**
> "Jennifer, Alex from Reliably again — making sure my text got through. Also open Thursday at 4 PM or Friday morning if either of those works better."

**If no response after Touch 2:** Shift to phone call and email. Do not text again.

---

### Example 2 — Hot Inbound After Content Download (BDR / Marketing Automation)

**Situation:** Michael, Director of Marketing at a B2B software company, downloaded your guide on email deliverability at 9:47 AM. This is a warm inbound — intent is high right now.

**Touch 1 (within minutes of the download):**
> "Michael, this is Sarah from SendPath — I saw you downloaded our email deliverability guide. Happy to walk you through how we've helped marketing teams in your space improve send rates by 40+%. Are you free for a quick call today at 2 PM or tomorrow at 10?"

| Element | Content |
|---|---|
| Identify | Name + company |
| Bridge | References the specific download — shows you are paying attention |
| Because | Specific outcome (40%+ send rate improvement) relevant to their role |
| Ask | Two specific time options — assumptive, not passive |
| 7-rule check | Pass: complete sentences, under 250 chars, no slang, no shortened links, proofed |

**Touch 2 (next business day, no response):**
> "Michael, Sarah from SendPath. Following up on my text from yesterday — still happy to share what we're seeing with deliverability for B2B marketing teams. Does tomorrow at 10 AM or Thursday at 3 PM work for a quick call?"

---

### Example 3 — Post-No-Show Appointment Rescue

**Situation:** David, Operations Director at a logistics company, was scheduled for a 30-minute discovery call at 11 AM today. He did not join. You do not know why — it may have been an emergency, a calendar conflict, or he simply forgot.

**Touch 1 (15-30 minutes after the missed appointment):**
> "David, this is Marcus from FlowOps — I had us scheduled for 11 AM today. No worries if something came up. How about we reschedule to Thursday at 11 AM or Friday at 2 PM?"

| Element | Content |
|---|---|
| Tone | Neutral and low-pressure — no frustration, no passive aggression |
| Identify | Name + company, not assumed |
| Ask | Two specific alternatives, assumptive not apologetic |
| 7-rule check | Pass: identifies self, complete sentences, 2 sentences, no slang |

**Touch 2 (next day, no response):**
> "David, Marcus from FlowOps again. Wanted to try once more on rescheduling — would Thursday at 11 AM work, or should I reach out by email to find a better time?"

The offer to switch to email signals respect for their communication preference and often prompts a quick reply.

---

## References

Detailed supporting materials in the `references/` folder (if extended):

- `references/bridge-types-and-templates.md` — full Bridge-Because templates by situation type
- `references/7-rules-text-checklist.md` — printable pre-send checklist for the 7 professional text rules
- `references/multi-channel-sequence-map.md` — how text integrates within phone-email-social prospecting campaigns

**Source chapter:** Blount, Jeb. *Fanatical Prospecting*, Chapter 20 "Text Messaging" (pp. 253-262 / PDF pp. 253-262).

**Referenced research:** Lead360 study of 3.5 million lead records from 400+ companies — text following phone contact increases conversion by 112.6 percent vs. text sent alone at 4.8 percent (cited in Blount, p. 255-256).

**Case study reference:** Matt's 9-month text nurture campaign — reserve best value-added content for text, use non-product articles to maintain top-of-mind engagement without direct solicitation (Blount, pp. 259-260).

**Dependent skill:** This skill builds text sequences that implement the Bridge-Because pattern produced by `prospecting-message-crafter`. If you do not yet have a bridge or because for this prospect, build the message nucleus there first.

## License

Content derived from *Fanatical Prospecting* by Jeb Blount (Wiley, 2015). This skill is licensed under [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)](https://creativecommons.org/licenses/by-sa/4.0/). You are free to share and adapt this material provided you give appropriate credit to Jeb Blount and BookForge, and distribute any derivative works under the same license.

## Related BookForge Skills

- `prospecting-message-crafter` — **prerequisite hub skill**: build the Bridge-Because message nucleus before deploying it via text. This skill is the channel adapter; message-crafter is the content engine.
- `cold-call-opener-builder` — deploys the Bridge-Because in the 5-step telephone framework; use when text fails to get a response after 2 attempts
- `cold-email-writer` — builds multi-touch email sequences; use alongside text in a balanced multi-channel prospecting system
- `prospecting-objective-setter` — defines the correct ask (appointment / qualifying info / close) that text sequences must end with
- `balanced-prospecting-cadence-designer` — maps text into a full multi-channel prospecting cadence so no single channel is over-relied upon

---
name: social-selling-touch-planner
description: |
  Plan and execute a multi-touch social selling strategy that builds familiarity across LinkedIn, Twitter, and other social channels — layered on top of phone and email to increase open rates, response rates, and appointment conversion.

  Trigger this skill when you need to:
  - Build a social selling plan using the Law of Familiarity and the Five Levers framework
  - Design a LinkedIn prospecting cadence for a target account list
  - Create a multi-touch familiarity plan for cold, warm, or conquest prospects
  - Generate connection request templates and social touch messages that don't pitch
  - Warm up prospects before phone or email outreach to increase engagement
  - Understand how to use social touches as a layer alongside phone/email (not a replacement)
  - Set up a daily social selling time block that fits inside the prospecting schedule
  - Build a personal branding content calendar for social channels
  - Understand the Five Levers of Familiarity: Persistent Prospecting, Referrals, Networking, Brand, Personal Branding
  - Design a referral engine that systematically asks for introductions
  - Create a social cadence for 20-50 cold prospect touches, or 1-10 for warm prospects
  - Apply the Five Cs of social selling: Connecting, Content Creation, Content Curation, Conversion, Consistency
  - Identify which social channels to prioritize based on where prospects hang out
  - Build a Strategic Prospecting Campaign (SPC) for conquest accounts using social + outbound

  NOT for: writing a cold call script (use cold-call-opener-builder), building a multi-touch email cadence
  (use cold-email-writer), or diagnosing pipeline math (use prospecting-ratio-manager). This skill produces
  the social layer plan and templates; the actual message nucleus is built in prospecting-message-crafter.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/fanatical-prospecting/skills/social-selling-touch-planner
metadata:
  openclaw:
    emoji: "📚"
    homepage: "https://github.com/bookforge-ai/bookforge-skills"
status: published
source-books:
  - id: fanatical-prospecting
    title: "Fanatical Prospecting"
    authors:
      - Jeb Blount
    chapters:
      - 12
      - 13
tags:
  - sales
  - prospecting
  - social-selling
  - linkedin
  - multi-touch
  - sdr
  - bdr
depends-on:
  - prospecting-message-crafter
  - prospect-list-tiering
execution:
  tier: 2
  mode: hybrid
  inputs:
    - type: document
      description: "Target account list (CSV, markdown table, or pasted text) plus the user's active social channels (LinkedIn, Twitter, etc.) and optional notes on current brand/content activity and existing familiarity level per account"
  tools-required:
    - Read
    - Write
  tools-optional:
    - WebFetch
  mcps-required: []
  environment: "Document directory containing the prospect list and any account notes. Agent reads input files, builds the Five-Lever allocation table, weekly social cadence, and connection/message templates, then writes outputs to the working directory."
discovery:
  standard
---

# Social Selling Touch Planner

## When to Use

You have a list of target accounts and you want to make your phone calls and emails land better. The problem is that cold prospects with zero familiarity with you or your company require 20 to 50 touches before they will engage — and most of those touches, delivered by phone alone, will hit voicemail and silence.

Social selling does not replace phone or email. Contact and conversion rates from phone and email dwarf conversion rates from social channels alone. What social selling does is reduce the number of touches needed to cross the **Familiarity Threshold** — the point at which a prospect recognizes your name, trusts you enough to take your call, open your email, and eventually agree to a meeting.

Use this skill when:
- You want to build a systematic familiarity-building plan before calling a cold list
- You are managing 20-100 strategic accounts that need consistent multi-channel touches
- You want LinkedIn outreach cadences that do not pitch on the first message
- You are running a Strategic Prospecting Campaign (SPC) on conquest accounts
- You need templates for connection requests, content engagement, and social inbox messages
- You want to build a referral engine into your existing accounts and professional network

**This skill does not:**
- Write your cold call script (use `cold-call-opener-builder`)
- Build a multi-touch email sequence (use `cold-email-writer`)
- Build your prospecting message nucleus (use `prospecting-message-crafter`)
- Tier your accounts or build your call priority order (use `prospect-list-tiering`)

Build the message nucleus in `prospecting-message-crafter` first. Then use this skill to deploy it as a social layer on top of your phone and email cadence.

---

## Context and Input Gathering

### Required (must have — ask if missing)

- **Target account list:** The accounts and contacts to plan social touches for. Accepted formats: CSV file, markdown table, or pasted text. At minimum: company name and contact name.
  - Check the working directory for: `prospect-list.csv`, `accounts.csv`, `tiered-prospect-list.md`, or any account list file.
  - If not found, ask: "Can you share your target account list? Even a simple list of names, companies, and their LinkedIn profile URLs will work."

- **Social channels in use:** Which platforms are you active on or willing to use? LinkedIn is the default for B2B. Twitter, Instagram, and Facebook may apply depending on the audience.
  - Ask if not stated: "Which social channels do you currently use or plan to use for prospecting?"

### Recommended (improves plan quality)

- **Current familiarity level per account:** Are these cold contacts (zero prior interaction), warm contacts (met at an event, replied to an email), or existing customers and referral sources?
- **Account tiers from `prospect-list-tiering`:** If the user has already tiered their list, import tier assignments directly. Conquest accounts (Tier 4) get the most intensive social plan. Lower tiers get a lighter automated cadence.
- **Existing content or brand activity:** Does the company or the rep have content being published? What is the current posting frequency?
- **Value proposition and ICP:** Used to design a content curation strategy that resonates with the right audience.

### Default Assumptions

- If no tier data is available, treat all accounts as cold (Tier 1-2) and design for the 20-50 touch benchmark.
- If only LinkedIn is mentioned, default to a LinkedIn-primary plan with a note that Twitter/other channels can be added.
- If no content activity exists, default to curation-first (sharing others' content) with a placeholder for original content over time.

---

## Process

### Step 1 — Audit Current Familiarity by Account

Before assigning social touches, establish a baseline: how familiar are these prospects with the rep or brand already? The number of touches required drops sharply as familiarity increases.

**Familiarity tiers (from the Law of Familiarity):**

| Familiarity State | Touch Estimate to Engage | Typical Source |
|---|---|---|
| Zero familiarity | 20–50 touches | Cold list, data vendor, no prior contact |
| Low familiarity | 10–20 touches | Met once, saw a post, same group |
| Moderate familiarity | 5–10 touches | Spoke by phone, replied to email, referral |
| High familiarity | 1–5 touches | Existing customer, warm referral, regular engager |

**Why audit first:** Applying a 20-touch social cadence to a prospect who already knows the rep is wasteful and annoying. Applying a 3-touch cadence to a cold stranger is statistically insufficient. Calibrating to current familiarity level sets the right cadence length and intensity from the start. (Blount, Ch. 12, pp. 96-97)

**For each prospect, record:**
- Familiarity state (zero / low / moderate / high)
- Evidence (e.g., "met at trade show," "opened 3 emails," "cold — no prior contact")
- Which of the Five Levers has already been applied (see Step 2)

If a tiered prospect list from `prospect-list-tiering` is available, map the pyramid tiers to familiarity states: Tier 1-2 = zero/low, Tier 3-4 = low/moderate, Tier 5-6 = moderate/high.

---

### Step 2 — Assign the Five Levers of Familiarity by Account Segment

The Five Levers are the mechanisms through which familiarity is built over time. Each lever operates differently and requires a different investment. Not every lever applies to every account — assign based on account tier and available resources.

**The Five Levers:**

| Lever | What It Is | Best For | Investment |
|---|---|---|---|
| **Persistent Prospecting** | Consistent daily multi-channel touches: calls, emails, voicemails, social interactions | All accounts — the baseline lever | Low time per touch, high volume |
| **Referrals** | Customer referrals, personal referrals, professional referrals from your network | Conquest accounts, hard-to-reach decision-makers | Medium — requires discipline to ask |
| **Networking** | Face-to-face events, chambers, trade shows, associations — the "real social prospecting" | Local territory or vertical-specific accounts | Medium-high — requires presence |
| **Brand** | Company marketing machine: advertising, content, events, trade shows | Large company reps benefit; small company reps must actively contribute | Low to rep (leverage marketing); high if building brand yourself |
| **Personal Branding** | Building your own reputation as a subject matter expert through content, public speaking, social media | Long-term play — all segments benefit; especially powerful for conquest and enterprise | Medium-high — ongoing commitment |

**Lever assignment logic:**

- **Conquest accounts (Tier 4):** Deploy all five levers. Request referrals from existing customers at the account. Attend events where their stakeholders appear. Engage them on social across multiple channels. Build personal brand content that addresses their specific problems.
- **Cold accounts (Tier 1-2):** Start with Persistent Prospecting + Personal Branding (social content and engagement). Add Referrals if a connection path exists.
- **Warm/inbound accounts (Tier 5-6):** Persistent Prospecting + social connection anchoring. Referrals if applicable.

**Why assign levers explicitly:** Reps who don't have a lever plan default to either phone-only (missing the familiarity compound effect of social) or social-only (missing the conversion power of outbound). The Five Levers ensure the full familiarity-building toolkit is deployed strategically, not randomly. (Blount, Ch. 12, pp. 97-104)

**Output for this step:** A Five-Lever allocation table — one row per account segment with lever assignments marked.

---

### Step 3 — Design the Multi-Touch Social Cadence

Build the weekly social touch schedule for each account segment. The cadence sequences touch types across a 4-6 week period designed to move the prospect across the Familiarity Threshold before a direct outbound contact.

**Touch sequence framework (LinkedIn-primary, 4-week cold prospect cadence):**

| Week | Day | Touch Type | Action | Note |
|---|---|---|---|---|
| 1 | Mon | Profile view | View the prospect's LinkedIn profile | Triggers a profile view notification |
| 1 | Thu | Follow | Follow the prospect on LinkedIn/Twitter | Visibility in their notifications |
| 2 | Mon | Engage content | Like or comment on a post they shared | Genuine, brief comment — not pitchy |
| 2 | Wed | Share content | Share an article relevant to their world | No direct mention of the prospect |
| 2 | Fri | Engage content | Comment on their company page post | Establishes pattern of presence |
| 3 | Mon | Connection request | Send personalized connection request | See template in Step 4 |
| 3 | Thu | Share content | Share second relevant article | Shows consistency, not one-off |
| 4 | Mon | Engage content | Comment on their post or reshare | Deepen presence |
| 4 | Thu | Social inbox message | Send first direct message after connection | Bridge-Because pattern (see Step 4) |
| 4 | Fri | Phone/email | First outbound call or email | Now anchored by social presence |

**Why this sequence matters:** Connection requests sent to cold strangers get ignored or declined. Spending 2-3 weeks engaging with the prospect's content before sending a connection request dramatically increases acceptance rates. By the time the direct message arrives, the prospect has seen your name 5-8 times and the interaction doesn't feel cold. (Blount, Ch. 13, p. 123)

**Cadence adjustments by familiarity state:**

| Familiarity | Weeks Before Direct Outreach | Touches Before Connection Request |
|---|---|---|
| Zero | 3-4 weeks | 4-6 touches |
| Low | 1-2 weeks | 2-3 touches |
| Moderate | Same week | 1 touch (or none) |
| High | Immediate | Skip cadence — connect and message same day |

**Daily time block:** Schedule 30-45 minutes per day for social prospecting activities — before or after the Golden Hours (the primary phone block). This is the only time social gets. Do not let it bleed into calling time. (Blount, Ch. 13, p. 128)

**Channel selection principle:** Go where your prospects hang out. For B2B, LinkedIn is the primary channel. If prospects are active on Twitter or other platforms, add those. Do not try to manage more than two to three channels consistently — effort dilutes beyond that. (Blount, Ch. 13, pp. 112-113)

---

### Step 4 — Draft Connection and Message Templates Using the Bridge-Because Pattern

Every outbound social message — whether a connection request or a direct inbox message — must follow the same principle as all prospecting messages: lead with what is in it for the prospect, not with what you want.

**Connection request template (personalized):**

> "Hi [Name] — I've been following your posts on [topic/industry]. Your recent piece on [specific topic] resonated with what I'm seeing with [relevant context]. I work with [role type] who are dealing with [relevant problem]. I'd like to add you to my network. — [Your name]"

**What NOT to do in a connection request:**
- Do not pitch a product or service
- Do not ask for a meeting
- Do not send a generic "I'd like to add you to my professional network" message
- Do not paste your email template into LinkedIn

**First inbox message template (post-connection, Bridge-Because pattern):**

> "Hi [Name] — Thanks for connecting. I noticed [specific observation about their company or a post they shared]. Most [role type] I work with are [dealing with / focused on / concerned about] [specific problem]. Because [specific insight or outcome you've helped similar people achieve], I thought it might be worth a quick conversation. How does [specific day + time] work for you?"

This template uses the **Bridge-Because pattern** from `prospecting-message-crafter`:
- Bridge: the observation about their specific situation
- Because: the reason they should give time (outcome, insight, or social proof)
- Ask: specific, direct, assumptive time request — not "let me know if you'd ever like to chat"

**Social inbox message rules:**
1. Never pitch in the first message after connecting. (Blount, Ch. 13, p. 111)
2. Wait until the prospect has seen your name at least 3-5 times before sending a direct message.
3. Only send a direct social message after connection is established — unsolicited LinkedIn InMail to cold strangers is expensive and low-conversion.
4. After crossing the Familiarity Threshold with a prospect, the social inbox becomes a valid supplement to email for brief, low-stakes messages.

**Referral ask template (for existing customers):**

> "[Name], thanks again for your business — I'm glad it's going well. I'm working to add more customers like you. Would you be able to introduce me to [specific person or type of person] in your network who might benefit from what we've done together?"

The referral ask formula: give a great experience → ask with a specific introduction target. The discipline to ask is more important than the technique. (Blount, Ch. 12, p. 100)

**Why these templates follow Bridge-Because:** Social buyers don't want to be pitched. They want to connect, interact, and learn. A message that opens with the prospect's problem and offers a reason for the conversation gets a response. A message that opens with your product gets you blocked. (Blount, Ch. 13, pp. 110-111)

---

### Step 5 — Schedule Social Touches into the Time Block

Map the social cadence onto the daily prospecting time block so it executes consistently without displacing phone and email activity.

**Daily social block structure (30-45 minutes, before or after Golden Hours):**

| Minutes | Activity |
|---|---|
| 0-10 | News stream scan: monitor LinkedIn/Twitter feed for trigger events and engagement opportunities from prospect list |
| 10-20 | Engage: like, comment, reshare 3-5 posts from prospects on the active cadence |
| 20-30 | Connect: send 2-3 new connection requests to prospects who have received 3+ touches |
| 30-40 | Message: send 1-2 social inbox messages to prospects who connected in prior weeks |
| 40-45 | Content: share or post one piece of curated or original content to feed |

**Why time-block social:** The social channel is designed to be addictive. Without a hard time limit, reps lose 2-3 hours of calling time to scrolling and liking. The cumulative impact of 30 disciplined daily minutes compounds over weeks into a meaningful familiarity effect. The individual sessions do not feel like much — the pattern is what works. (Blount, Ch. 13, p. 128)

**Content curation for the daily block:**

The social channel must be fed daily to maintain presence. Curating others' content is far more sustainable than creating original content and still produces familiarity and expert-positioning effects. Three sources for curation:
1. Industry publications and trade media (set up Google Alerts or RSS)
2. Thought leaders your prospects follow (reshare their content with a brief comment)
3. Company marketing content (approved — check with marketing first for brand compliance)

**Original content (optional, high-leverage):**

If time and appetite exist, original content — articles, short-form LinkedIn posts, videos, presentations — compounds faster than curation because it creates passive connections. Prospects who find your content relevant and follow you based on it represent inbound familiarity at scale. For most reps starting out, begin with curation; add original content after the curation habit is established.

**Personal branding checkpoint:** Before anything is posted, answer two questions:
1. Does this support my reputation as someone who solves problems and can be trusted?
2. Does this help prospects recognize my name in a positive way?

If either answer is "no" or "unsure," do not post it. (Blount, Ch. 13, p. 114)

---

### Step 6 — Write Outputs to File

Produce three output files:

1. **`five-lever-allocation-table.md`** — One row per account segment, with familiarity state, touch-count target, and active lever assignments for each account.
2. **`weekly-social-cadence.md`** — The 4-6 week touch sequence by day and activity type, customized to the user's channel mix and account list size.
3. **`social-templates.md`** — Connection request templates, first inbox message templates, referral ask templates, and content sharing examples — labeled with Bridge-Because element markers.

**Why externalize outputs:** The plan fails if it lives only in the rep's head. A written cadence creates a daily execution checklist. Written templates eliminate the "what do I say?" pause that causes reps to skip social touches. The allocation table lets the rep calibrate effort-per-account rationally. (Blount, Ch. 12, pp. 115-116)

---

## Inputs

| Input | Required | Format | Notes |
|---|---|---|---|
| Target account list | Yes | CSV, markdown, or pasted text | Company + contact name minimum |
| Social channels in use | Yes | User states | LinkedIn default; add others as relevant |
| Account tiers (from `prospect-list-tiering`) | Recommended | `tiered-prospect-list.md` | Enables calibrated lever assignment |
| Current familiarity notes | Recommended | Per-account notes or user description | Adjusts touch-count targets |
| Value prop / ICP | Recommended | `value-prop.md` or stated inline | Powers content curation and message bridges |
| Existing content activity | Optional | User description | Affects content lever recommendation |

---

## Outputs

| Output | Format | Description |
|---|---|---|
| `five-lever-allocation-table.md` | Markdown table | Per-segment lever assignments + familiarity state + touch target |
| `weekly-social-cadence.md` | Markdown table | 4-6 week day-by-day touch plan by channel |
| `social-templates.md` | Markdown | Connection requests, inbox messages, referral asks — Bridge-Because labeled |

---

## Key Principles

**Social is a layer, not a primary channel.** Phone and email produce contact and conversion rates that dwarf social media alone. Social selling's job is to reduce the number of outbound touches needed by building familiarity before the call. The rep who uses social as a layer on top of balanced prospecting outperforms the one who goes social-only every time. (Blount, Ch. 13, pp. 108-110)

**20 to 50 touches for cold prospects — not 3.** Most reps give up after 5-8 attempts. The data says cold prospects with zero familiarity require 20-50 touches before they engage. Social touches count. Each profile view, content engagement, and connection builds toward the Familiarity Threshold. Persistence is the first lever for a reason. (Blount, Ch. 12, pp. 96-97)

**Never pitch in the first social touch.** Social buyers want to connect, interact, and learn. A pitch in a connection request or first inbox message signals low trust and produces blocking, reporting, and damaged reputation. Lead with observation, offer insight, build enough familiarity before asking for anything. (Blount, Ch. 13, p. 111)

**The Five Levers compound.** A prospect who has seen your LinkedIn content, been introduced via a referral, met you briefly at a trade show networking event, and has received a few emails over 6 weeks will answer your phone call. No single lever gets you there alone. Stack them deliberately on your highest-value accounts. (Blount, Ch. 12, pp. 97-104)

**Consistency beats volume.** 30 disciplined daily minutes produces more than 3-hour binge sessions once a week. Social algorithms, notification patterns, and human memory all reward consistency. Build the daily block and protect it. (Blount, Ch. 13, p. 128)

**Familiarity is a two-edged sword.** Negative impressions (inflammatory posts, a poorly written profile, too-personal sharing) create familiarity that works against you. Every post, comment, like, and share is visible to prospects. Manage the message as carefully as the cadence. (Blount, Ch. 13, pp. 119-120)

**Balance familiarity-building with prospecting today.** It is easy to spend all day building familiarity instead of making calls. Familiarity building is an investment in the future — it does not pay today's quota. Protect Golden Hours for direct outbound activity and keep social in its time block. (Blount, Ch. 12, p. 104)

---

## Examples

---

### Example 1 — SDR Running LinkedIn on 100 Enterprise Accounts

**Situation:** An SDR at a SaaS company has 100 enterprise accounts in their territory. All are cold — no prior contact. LinkedIn is the primary research and familiarity channel. Phone and email are the primary outbound channels.

**Inputs:** Tiered prospect list (100 accounts, all Tier 1-2). LinkedIn only. No existing content activity.

**What the skill produces:**

- **Lever allocation:** Persistent Prospecting (all 100) + Personal Branding (LinkedIn content curation). Referrals and Networking flagged as a future layer once Tier 4 conquest accounts are identified.
- **Cadence design:** A 4-week social cadence with 30 accounts per week cycling through view → follow → engage → connect → message. At any given time, 20-30 accounts are in active social cadence.
- **Time block:** 30 minutes daily, before the morning calling block. 10 minutes of news scan and engagement, 15 minutes of connection requests and inbox messages, 5 minutes of content sharing.
- **Templates:** Personalized connection request that references the prospect's industry role and a specific post they shared; first inbox message using Bridge-Because pattern with the SDR's value proposition; no pitch language in either template.

**Output files:** Five-lever allocation table with 100 accounts (all marked Persistent + Personal Branding), weekly social cadence (week 1: observe and follow, week 2: engage content, week 3: connect, week 4: message + first call), and a social-templates.md with 3 connection variants and 2 inbox message templates.

---

### Example 2 — AE Warming 30 Strategic Accounts

**Situation:** An Account Executive manages 30 named accounts. Twelve are conquest Tier 4 accounts — high value, no prior relationship. The other 18 are Tier 2-3 with some qualification data but no open buying windows.

**What the skill produces:**

- **Lever allocation for Tier 4 (12 conquest accounts):** All five levers. Social cadence runs for 8 weeks (longer, because Tier 4 accounts warrant deeper investment). Referral mapping is included — who in the rep's existing customer base has connections at these accounts? Networking events in the industry vertical where these buyers appear are flagged.
- **Lever allocation for Tier 2-3 (18 accounts):** Persistent Prospecting + Personal Branding. Monthly social engagement touch keeps the rep's name visible while qualification work continues on other channels.
- **Templates:** Strategic bridge inbox message for conquest accounts — references a trigger event from LinkedIn (funding, expansion, hiring) and offers a specific insight, not a product pitch.
- **Referral ask:** A template for the rep's top 3 existing customers, asking for introductions to specific named contacts at the conquest accounts.

---

### Example 3 — Founder Building Personal Brand While Prospecting

**Situation:** A founder-seller is prospecting a mix of 50 SMB accounts while also trying to build enough personal brand presence on LinkedIn to start generating inbound leads over a 6-month horizon.

**What the skill produces:**

- **Lever allocation:** Persistent Prospecting (immediate, all 50 accounts) + Personal Branding (LinkedIn content, primary lever for long-term inbound). Networking (attend two local chamber or industry events per month). Referrals (systematic ask process built into every closed deal).
- **Content plan:** Week 1-4: curate 1 article per day from industry sources with a 1-sentence insight comment. Month 2 onward: 2 original short posts per week (problem-focused, no product mention). Over 6 months, build toward 1 original article per week.
- **Cadence:** Social block is 45 minutes daily. In the near term, 80% of time goes to engagement and connection; 20% to content. By month 3, the ratio shifts to 60% engagement / 40% content as the content habit is established.
- **Benchmark:** Building from zero on LinkedIn takes 6 months to 2 years to develop enough following to produce meaningful inbound leads. The founder sets a 6-month review point: if personal brand content is not generating 2-3 inbound inquiries per month by month 6, double outbound volume to compensate. (Blount, Ch. 13, p. 131)

---

## References

Detailed supporting materials:

- `references/five-levers-taxonomy.md` — Full definitions and tactics for each of the Five Levers of Familiarity, including sub-types of referrals (customer, personal, professional) and personal branding channels (LinkedIn content, public speaking, podcasts, webinars)
- `references/social-cadence-templates.md` — Full template library: connection request variants by industry, inbox message variants by value category (emotional / insight-curiosity / tangible-logic), referral ask scripts, content curation examples with commentary
- `references/five-cs-of-social-selling.md` — Full definitions and execution guidance for Connecting, Content Creation, Content Curation, Conversion, and Consistency, including tool categories (engagement tools, creation tools, curation tools, distribution tools, intelligence tools)
- `references/channel-selection-guide.md` — Decision framework for choosing primary and secondary social channels based on where the ICP hangs out; LinkedIn-primary guidance for B2B

**Source chapters:** Blount, Jeb. *Fanatical Prospecting.* Wiley, 2015.
- Chapter 12: "The Law of Familiarity" (pp. 96-104)
- Chapter 13: "Social Selling" (pp. 105-131)

**Depends on:**
- `prospecting-message-crafter` — Bridge-Because pattern used in all social inbox messages; must be run first to build the message nucleus
- `prospect-list-tiering` — Pyramid tier assignments drive lever allocation and cadence intensity per account

---

## License

Content derived from *Fanatical Prospecting* by Jeb Blount (Wiley, 2015). This skill is licensed under [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)](https://creativecommons.org/licenses/by-sa/4.0/). You are free to share and adapt this material provided you give appropriate credit to Jeb Blount and BookForge, and distribute any derivative works under the same license.

---

## Related BookForge Skills

Install dependencies via clawhub:

```
clawhub install fanatical-prospecting/prospecting-message-crafter
clawhub install fanatical-prospecting/prospect-list-tiering
```

- **`prospecting-message-crafter`** (required) — Build the Bridge-Because nucleus that powers all social inbox messages before writing any social templates
- **`prospect-list-tiering`** (required) — Tier your account list before assigning levers; tier assignments drive cadence intensity and lever deployment
- **`cold-call-opener-builder`** — Deploy the message nucleus in the 5-step telephone framework for the outbound call that follows the social warm-up
- **`cold-email-writer`** — Build the multi-touch email cadence that runs in parallel with the social cadence
- **`prospecting-time-block-planner`** — Schedule the social selling time block within the full prospecting day alongside Golden Hour calling blocks
- **`balanced-prospecting-cadence-designer`** — Design the full multi-channel cadence of which this social layer is one component

---
name: prospecting-time-block-planner
description: |
  Build a protected weekly prospecting calendar that separates Golden Hours (when buyers are buying) from Platinum Hours (before/after business hours for research and admin), calculates what each Golden Hour is worth in dollars, and installs a Power Hour protocol that eliminates distractions during focused dial blocks. Use this skill when someone asks "time management for sales", "when should I prospect", "golden hours", "power hour", "prospecting block", "calendar for sales", "how to protect prospecting time", "distractions killing my sales", "time equalizer", "platinum hours", "morning vs afternoon prospecting", "what time should I make cold calls", "how do I structure my sales day", "schedule for SDR", "how to stop email from killing my prospecting", "how to make more calls in less time", "why am I not hitting my dial targets", "how to concentrate my prospecting power", "hourly worth formula", or "sales time allocation framework". This skill gathers the rep's annual quota goal, working hours, current calendar constraints, and top distractors — then produces four artifacts: (1) hourly-worth calculation showing the dollar cost of every non-selling minute during prime time, (2) a Golden Hours and Platinum Hours weekly allocation tuned to the rep's territory and prospect time zones, (3) a 6-rule Power Hour protocol with a named distraction-elimination checklist, and (4) a ready-to-use weekly time-block calendar template. Based on Chapter 8 of Fanatical Prospecting by Jeb Blount.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/fanatical-prospecting/skills/prospecting-time-block-planner
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: published
depends-on: []
source-books:
  - id: fanatical-prospecting
    title: "Fanatical Prospecting: The Ultimate Guide to Opening Sales Conversations and Filling the Pipeline by Leveraging Social Selling, Telephone, Email, Text, and Cold Calling"
    authors: ["Jeb Blount"]
    chapters: [8]
tags: [sales, prospecting, time-management, productivity, calendar, sdr, bdr, inside-sales, outside-sales, power-hour, golden-hours, distraction-elimination]
execution:
  tier: 2
  mode: hybrid
  inputs:
    - type: document
      description: "Rep's annual quota or income goal, working weeks per year, available selling hours per day, current calendar commitments, prospect time zones, and top 3–5 distractions that interrupt their prospecting blocks"
  tools-required: [Read, Write]
  tools-optional: []
  mcps-required: []
  environment: "Document/calendar text directory — reads user situation brief; writes prospecting-time-block-plan-{date}.md to the working directory"
discovery:
  goal: "Calculate the dollar value of each Golden Hour, allocate prime selling time to protected prospecting blocks, and deliver a weekly calendar template with a Power Hour distraction-elimination protocol"
  tasks:
    - "Gather quota goal, working hours, calendar constraints, and distraction inventory from the rep"
    - "Calculate hourly worth using the Annual Goal ÷ Working Weeks ÷ Golden Hours formula"
    - "Identify Golden Hours based on prospect availability window for the rep's territory and time zone"
    - "Assign Platinum Hours (before/after Golden Hours) for research, CRM, proposals, and admin"
    - "Design the Power Hour protocol with specific distraction-elimination rules"
    - "Write a weekly time-block calendar template as the primary output artifact"
  audience:
    roles: [sdr, bdr, ae, inside-sales-rep, outside-sales-rep, founder-self-seller]
    experience: beginner-to-intermediate
  triggers:
    - "Rep is not hitting dial or touch targets despite feeling busy all day"
    - "Rep is spending Golden Hours on admin, CRM, or email instead of prospecting"
    - "Rep wants to know exactly when to prospect vs. when to do everything else"
    - "Rep is setting up a new weekly routine after a quota change or territory reassignment"
    - "Manager is implementing a time-blocking discipline across the team"
  prerequisites: []
  not_for:
    - "Calculating how many total dials or touches are needed to hit quota — use fanatical-prospecting:pipeline-ratio-calculator"
    - "Writing the actual call script for the prospecting block — use fanatical-prospecting:cold-call-opener-builder"
    - "Prioritizing which prospects to call during the block — use fanatical-prospecting:prospect-prioritization-pyramid"
    - "Setting the objective for each prospecting touch — use fanatical-prospecting:prospecting-objective-setter"
  environment: "Document set — reads situation brief from working directory or user input; writes weekly time-block calendar plan"
  quality: placeholder
---

# Prospecting Time Block Planner

## When to Use

You are feeling busy every day but not hitting your prospecting targets. Or you are setting up your week and want to know exactly when to make calls, when to do research, and when to handle email and CRM — and you want that structure to be protected from interruptions.

This skill applies the Golden Hours / Platinum Hours framework from Jeb Blount's Chapter 8 to your specific quota, calendar, and time zone. It calculates what each selling hour is worth in dollars, builds a protected weekly calendar, and installs a Power Hour protocol that eliminates the distractions that are costing you commission.

**Who this skill is for:** SDRs, BDRs, inside sales reps, outside sales reps, and founder-sellers who run outbound prospecting as part of their daily work. Especially valuable for reps who are "always busy" but whose activity numbers are not matching their intentions, and for reps who check email first thing every morning.

**Output:** `prospecting-time-block-plan-{date}.md` — hourly-worth calculation, Golden/Platinum Hours allocation, Power Hour distraction protocol, and a weekly calendar template.

---

## Context & Input Gathering

### Required

To build the calendar accurately, the skill needs:

1. **Annual income goal:** Your quota or on-target earnings for the year (e.g., "$120,000").
2. **Working weeks per year:** How many weeks you are actually selling — subtract vacation, holidays, and expected sick days. Most reps land between 46 and 50 weeks.
3. **Selling hours per day:** How many hours per day are genuinely available for sales activity — not counting lunch, commute, and mandatory non-sales meetings. Typical range is 5–7 hours.
4. **Prospect time zone window:** When are your prospects reachable? A B2B rep in EST calling West Coast companies has a different Golden Hours window than a rep in PST calling the East Coast. If prospects span multiple time zones, note the overlap window.
5. **Current calendar commitments:** Recurring meetings, mandatory team calls, commute blocks, or fixed client commitments that cannot move.
6. **Top 3–5 distractions:** What actually interrupts your prospecting? Email notifications, Slack, mobile phone, colleagues stopping by, CRM rabbit holes, or social media are the most common.

### Useful (read from working directory if available)

- **`pipeline-ratios.csv`** — activity-to-outcome conversion rates (dials per connect, connects per meeting) help size how many Power Hour blocks are needed
- **`prospect-list.csv`** — if prospect geography spans multiple time zones, this calibrates the Golden Hours window

### Defaults

If no documents are provided, the skill asks for the six inputs above in plain conversation. A sentence or two per item is enough to begin. If the rep is uncertain about working weeks or selling hours, the skill applies standard defaults (48 working weeks, 6 selling hours per day) and flags them for adjustment.

---

## Process

### Step 1: Calculate Hourly Worth

**Action:** Apply the hourly-worth formula to the rep's annual income goal:

```
Annual Income Goal
÷ Working Weeks per Year
÷ Golden Hours per Week
= Your Hourly Worth ($)
```

**Example calculation:** Rep with a $75,000 annual goal.
- Working weeks: 48 (52 weeks minus 2 weeks vacation, 1 week holidays, 1 week miscellaneous)
- Selling hours per day: 6 (8-hour day minus 1-hour lunch and 1-hour non-sales overhead)
- Golden Hours per week: 30 (6 hours × 5 days)
- $75,000 ÷ 48 = $1,563/week ÷ 30 = **$52 per Golden Hour**

Once this number is calculated, apply it immediately: if the rep spends 90 minutes on email and CRM during Golden Hours, that is $78 of commission revenue traded for inbox management.

**WHY:** Most reps have never done this math. The abstract idea that "time is money" produces no behavioral change. A specific dollar figure — "$52 per hour" — does. When the rep knows that checking Slack during their morning prospecting block costs $13 in real commission, the distraction has a price tag. This is what converts the CEO mindset from a motivational phrase into an active decision-making tool throughout the day.

**Output:** A single line: "Your Golden Hours are worth **$[X] per hour**."

---

### Step 2: Identify Golden Hours

**Action:** Map the rep's territory against their own working day to identify the window during which buyers are reliably reachable and making purchasing decisions.

**Golden Hours definition:** Business hours in the prospect's time zone — the window when decision makers are at their desks, answering phones, and taking meetings. Typically 8 AM–5 PM in the prospect's local time.

**Time zone calibration:**
- Rep in EST, prospects in EST: Golden Hours are 8 AM–5 PM local (standard)
- Rep in EST, prospects in PST: Golden Hours shift to 11 AM–8 PM EST (afternoon-heavy)
- Rep in PST, prospects in EST: Golden Hours shift to 8 AM–2 PM PST (morning-heavy)
- Prospects spanning both coasts: 11 AM–2 PM EST / 8 AM–11 AM PST is the reliable overlap window; extend outward from there

**Inside sales note:** Golden Hours are your most protected dial blocks. Outside sales reps add in-person visit windows that should align with the prospect's availability, not drive-time convenience.

**Block the calendar:** Mark Golden Hours as non-negotiable prospecting and selling time. Nothing — email, CRM updates, proposals, colleague requests — happens in these blocks unless it is directly revenue-generating.

**WHY:** The single biggest cause of missed dial targets is not laziness — it is Golden Hours contamination. Non-selling activities feel important and they often are. But proposals, CRM entry, and email management are support functions, not selling functions. Doing them during the window when buyers are available is trading your highest-value hours for your lowest-value tasks. Reps who protect Golden Hours with the same discipline they would apply to a hot prospect meeting consistently outperform those who do not.

**Output:** A labeled time window: "Golden Hours: [START TIME]–[END TIME] [TIME ZONE], Monday–Friday."

---

### Step 3: Assign Platinum Hours

**Action:** Allocate time blocks before and after the Golden Hours window for all non-selling activities that are necessary but should not happen during prime prospecting time.

**Platinum Hours definition:** The 1–2 hours before the Golden Hours window opens (early morning) and the 1–2 hours after it closes (late afternoon or evening). This is when top-earning reps handle:

- Building and updating prospecting lists
- Pre-call research and call objective planning
- Proposal and presentation development
- Contract preparation and approvals
- Social selling activity (LinkedIn connection requests, content engagement)
- Email prospecting (composing outbound sequences, reading and responding to replies)
- CRM data entry and updates
- Reports and administrative tasks
- Calendar management

**The morning Platinum Hour rule:** Do not check email first thing in the morning. Email is "the derailer of all derailers" — opening it before your first prospecting block puts you at the mercy of other people's priorities before you have completed your most important task of the day. Reserve the first morning Platinum Hour for list preparation and pre-call planning; handle email in a scheduled block after your first Power Hour, or in the afternoon Platinum Hours.

**WHY:** Platinum Hours exist to make Golden Hours frictionless. When call lists are prepared, research is done, and objectives are set before the dial block begins, the rep can focus entirely on the call — no context-switching, no stopping mid-block to look up a contact. The preparation done in Platinum Hours directly multiplies the output of the Golden Hours that follow.

**Output:** Labeled morning and afternoon Platinum Hours blocks on the weekly calendar.

---

### Step 4: Design the Power Hour Protocol

**Action:** Install focused dial blocks inside the Golden Hours window. These are the Power Hours — 30–60 minute windows dedicated entirely to a single prospecting activity.

**Power Hour rules (the 6-rule protocol):**

1. **One activity only.** During a phone Power Hour, dial the phone. During an email Power Hour, write and send emails. Do not mix activity types within a single block.
2. **Email off.** Close the email application entirely. Do not have it visible on screen. This is not "I'll just glance at it" — it is closed.
3. **Mobile device in a drawer (or another room).** The average person looks at their phone every 7 minutes. A phone on the desk is a distraction machine even when silent. Physical distance is required.
4. **No CRM research during the block.** All research was completed in Platinum Hours before the block started. During the Power Hour, the rep works from a prepared list with notes already in place.
5. **Notes on paper during the block; log to CRM after.** Take brief notes on a printed list or notepad during calls. Log everything in CRM in a dedicated 20–30 minute block immediately after the Power Hour ends.
6. **Hold interruptions at the door.** Post a visible "Do Not Disturb" signal — a door sign, a status indicator in Slack, or headphones on. Inform colleagues and managers in advance that this time is a protected block.

**Block structure:** Schedule 3 Power Hours spread across the Golden Hours day — one in the morning window, one midday, one in the afternoon. A rep making 25–50 teleprospecting calls per Power Hour will complete their daily dial target in 1–2 hours of protected time.

**WHY:** Multitasking is not possible during prospecting. The human brain does not actually run tasks in parallel — it switches rapidly between tasks, creating the illusion of multitasking while accumulating switching overhead. A rep who interrupts calls to log CRM notes, check Slack, and research the next prospect makes roughly one call every 8 minutes. The same rep in a concentrated Power Hour makes 8–10 calls in that same time. This is Horstman's Corollary: work contracts to fill the time available. A 60-minute block with no exit routes forces the rep to move faster and stay focused. Eighty percent of all the appointments a rep needs can be set in 1–2 concentrated hours per day when those hours are properly blocked.

**Output:** A labeled Power Hour protocol embedded in the weekly calendar, with 6 rules printed at the top.

---

### Step 5: Build the Distraction-Elimination Plan

**Action:** Using the rep's self-reported distraction inventory (gathered in Context & Input Gathering), produce a specific countermeasure for each distractor.

**Common distractors and their countermeasures:**

| Distractor | Countermeasure |
|---|---|
| Email notifications | Close email application during Power Hours; schedule 2–3 email blocks per day in Platinum Hours |
| Mobile phone (texts, social, apps) | Phone in desk drawer or a different room; enable Do Not Disturb mode on device during blocks |
| Slack / team chat | Set status to "In a prospecting block — DM me after [TIME]"; close or silence Slack |
| Social media (LinkedIn, X, Facebook) | Block these sites at the browser level during Power Hours using a browser extension or system-level restriction |
| CRM rabbit holes | Complete all prospect research in the pre-block Platinum Hour; commit to "no CRM during calls" as a team norm |
| Colleague drop-ins | Post a physical "Do Not Disturb" sign or schedule the Power Hour in a meeting room |
| Internal meetings | Audit recurring meetings that fall in Golden Hours; request reschedules to Platinum Hours or off-peak windows |

**The email opening rule:** Never check email first thing in the morning before completing the first prospecting block. This is the single highest-leverage rule for protecting morning Golden Hours. If something is genuinely urgent, the sender will call or text — not just send an email.

**WHY:** Each interruption does not just cost the time of the interruption itself. Research on attention recovery shows that returning to deep focus after an interruption takes additional minutes beyond the distraction itself. In Laura's case study from the book, she lost 7 minutes per interruption — not from the interruption alone but from re-orienting, finding her place on the list, and rebuilding mental momentum. Eleven interruptions in a two-hour block cost her far more than 11 × 7 = 77 minutes; they degraded the quality of every call between interruptions as well.

**Output:** A named distraction elimination plan embedded in the weekly calendar artifact, mapped to the rep's specific distractors.

---

## Output Template

```markdown
# Prospecting Time Block Plan
**Date:** [Date]
**Rep:** [Name]
**Prepared by:** fanatical-prospecting:prospecting-time-block-planner

---

## Hourly Worth Calculation

| Input | Value |
|---|---|
| Annual income goal | $[GOAL] |
| Working weeks per year | [WEEKS] |
| Golden Hours per week | [HOURS/DAY × 5] |
| **Your hourly worth** | **$[RESULT]** |

> Every minute you spend on email, CRM entry, or admin during your Golden Hours costs you $[RESULT ÷ 60] in commission. A 30-minute email session during prime selling time costs $[RESULT ÷ 2].

---

## Golden Hours

**Window:** [START TIME] – [END TIME] [TIME ZONE]
**Prospect time zone(s):** [ZONES]
**Days:** Monday – Friday

These hours are your prime selling window. Only revenue-generating activities happen here:
- Outbound prospecting calls (Power Hours)
- Inbound lead follow-up
- Discovery calls and qualification conversations
- Demos, presentations, and closing calls

Non-selling tasks do not belong here — no matter how important they feel.

---

## Platinum Hours

**Morning Platinum Block:** [START TIME] – [END TIME]
**Afternoon Platinum Block:** [START TIME] – [END TIME]

Activities for Platinum Hours:
- [ ] Build and update call lists for today's Power Hours
- [ ] Pre-call research and call objective planning
- [ ] CRM data entry from previous day's blocks
- [ ] Email prospecting (composing sequences, reading replies)
- [ ] Proposals, contracts, and approvals
- [ ] Social selling (LinkedIn connection requests, content engagement)
- [ ] Reports and administrative tasks
- [ ] Calendar management

> **Morning rule:** Do not open email until after your first Power Hour. Your inbox is other people's priorities. Prospect first — then manage inbound.

---

## Weekly Time Block Calendar

| Time | Monday | Tuesday | Wednesday | Thursday | Friday |
|---|---|---|---|---|---|
| [MORNING PLATINUM START]–[END] | Platinum: List prep + research | Platinum: List prep + research | Platinum: List prep + research | Platinum: List prep + research | Platinum: List prep + research |
| [POWER HOUR 1 START]–[END] | **POWER HOUR 1: Dial block** | **POWER HOUR 1: Dial block** | **POWER HOUR 1: Dial block** | **POWER HOUR 1: Dial block** | **POWER HOUR 1: Dial block** |
| [CRM LOG 1 START]–[END] | CRM log + notes | CRM log + notes | CRM log + notes | CRM log + notes | CRM log + notes |
| [EMAIL BLOCK START]–[END] | Email batch | Email batch | Email batch | Email batch | Email batch |
| [POWER HOUR 2 START]–[END] | **POWER HOUR 2: Dial block** | **POWER HOUR 2: Dial block** | **POWER HOUR 2: Dial block** | **POWER HOUR 2: Dial block** | **POWER HOUR 2: Dial block** |
| [MIDDAY]–[END] | Discovery / demo / lunch | Discovery / demo / lunch | Discovery / demo / lunch | Discovery / demo / lunch | Discovery / demo / lunch |
| [POWER HOUR 3 START]–[END] | **POWER HOUR 3: Dial block** | **POWER HOUR 3: Dial block** | **POWER HOUR 3: Dial block** | **POWER HOUR 3: Dial block** | **POWER HOUR 3: Dial block** |
| [CRM LOG 2 START]–[END] | CRM log + proposals | CRM log + proposals | CRM log + proposals | CRM log + proposals | CRM log + proposals |
| [AFTERNOON PLATINUM START]–[END] | Platinum: Proposals + email | Platinum: Proposals + email | Platinum: Proposals + email | Platinum: Proposals + email | Platinum: Proposals + admin |

*Customize start/end times to your Golden Hours window and existing commitments.*

---

## Power Hour Protocol

These 6 rules apply during every Power Hour block:

1. **One activity only** — Dial the phone. Write the email. Do not mix.
2. **Email closed** — Not minimized. Closed. No notifications.
3. **Mobile phone in a drawer** — Physical separation, not just silent mode.
4. **No CRM research** — Research was done in Platinum Hours. Work from your prepared list.
5. **Notes on paper; log after the block** — Take brief notes during calls; block 20–30 min post-block for CRM logging.
6. **Block interruptions** — "Do Not Disturb" sign, Slack status set, colleagues informed.

---

## Distraction Elimination Plan

| Your Distractor | Countermeasure | When It Applies |
|---|---|---|
| [DISTRACTOR 1] | [COUNTERMEASURE] | [POWER HOURS / ALL DAY] |
| [DISTRACTOR 2] | [COUNTERMEASURE] | [POWER HOURS / ALL DAY] |
| [DISTRACTOR 3] | [COUNTERMEASURE] | [POWER HOURS / ALL DAY] |
| Email first-thing habit | First email check happens AFTER Power Hour 1, not before | Every morning |
| Phone checking (avg every 7 min) | Phone in drawer during all Power Hours | Power Hours |
| Colleague drop-ins | "Do Not Disturb" signal posted during Power Hours | Power Hours |

---

## Accountability Check

At the end of each week, answer these three questions:

1. How many of your scheduled Power Hours ran start-to-finish without interruption? (Target: 80%+)
2. Did you check email before your first Power Hour on any morning? (Target: 0 days)
3. How many dials/touches did each Power Hour produce on average? (Benchmark: 25–50 dials/hr for phone blocks)
```

---

## Key Principles

**Golden Hours and Platinum Hours are not the same.** Golden Hours are when buyers are available — they are irreplaceable. If you miss them, the revenue opportunity is gone. Platinum Hours are flexible support time that can expand or contract. Every minute of Golden Hours spent on admin is a minute that cannot be recovered; every minute of Platinum Hours spent on admin is exactly where that work belongs.

**WHY:** The failure mode is treating all working hours as interchangeable. A rep who "works hard" for 10 hours but spends 4 of those hours doing CRM and email during prime selling time has not worked 10 hard hours of selling — they have worked 6 hard hours of selling and 4 hours of support activity billed at the wrong rate. The Golden/Platinum distinction ends this confusion by assigning each type of work its correct window.

**A Power Hour is an appointment with yourself.** Cancel a scheduled meeting with a hot prospect at 9 AM because a colleague wants to grab coffee and you look irresponsible. Cancel a Power Hour for the same reason and there are no immediate consequences — which is exactly why most reps cancel their Power Hours and no one else does. Treat the block as a hard commitment, not a preference.

**WHY:** Without this mindset, every interruption seems justified in isolation. The prospect research that could be done in Platinum Hours, the quick email that could wait two hours, the colleague conversation that could happen after the block — each one individually seems minor. Collectively they eliminate the block entirely. The only defense is the same rule applied to every external appointment: the block is on the calendar, it is sacred, and it does not move.

**Work contracts to fill the time available (Horstman's Corollary).** Give yourself all day to make 50 calls and it will take all day. Give yourself 60 minutes and a prepared list and it will take 60 minutes. This is not motivational — it is how attention and urgency work. The boundary forces efficiency.

**WHY:** In Blount's coaching example, an inside sales team that had been making fewer than half their required daily dials made 22 dials in 30 minutes during a forced block exercise — more than they averaged in a full day. The mechanism was time pressure combined with single-task focus: they could not check email, research prospects, or socialize. The time constraint did not add effort; it removed escape routes, which produced the same output in 4% of the time.

---

## Examples

### Example 1: B2B Enterprise SDR (Inside Sales, East Coast prospects)

**Situation:** SDR at a SaaS company. Quota: $180,000 in sourced pipeline per quarter. Annual on-target earnings: $65,000. Working weeks: 48. Prospects are primarily East Coast, 9 AM–5 PM EST reachable.

**Hourly-worth calculation:**
- $65,000 ÷ 48 weeks = $1,354/week
- 6 selling hours/day × 5 days = 30 Golden Hours/week
- $1,354 ÷ 30 = **$45 per Golden Hour**

**Calendar design:**
- Golden Hours: 9 AM–5 PM EST
- Morning Platinum: 7:30–9 AM (list prep, LinkedIn prospecting, pre-call research)
- Power Hour 1: 9–10 AM (phone block — 35–45 dials)
- CRM + email: 10–10:30 AM
- Power Hour 2: 10:30–11:30 AM (phone block)
- Midday: 12–1 PM (demos, discovery calls, lunch)
- Power Hour 3: 1:30–2:30 PM (phone block)
- Balance of afternoon: CRM, email, follow-up calls, social prospecting
- Afternoon Platinum: 4:30–5:30 PM (proposals, pipeline admin, next-day prep)

**Distraction profile:** Email notifications (every 5 min), Slack (constant), phone on desk.
- Email: Closed during all three Power Hours; checked at 10 AM, 1 PM, and 4:30 PM only
- Slack: Status set to "Prospecting — DM for urgent only" during Power Hours
- Phone: In desk drawer from 9–10 AM, 10:30–11:30 AM, and 1:30–2:30 PM

**Result target:** 3 Power Hours × 40 dials = 120 dials/day, 600/week — consistent with Sales Gravy's inside team benchmark.

---

### Example 2: Outside Rep with Mixed In-Person and Phone Prospecting

**Situation:** Outside B2B rep covering a regional territory. Annual target: $95,000 OTE. Prospects span Central and Mountain time zones. Mix of phone-based days (Mon/Fri) and field days (Tue–Thu).

**Hourly-worth calculation:**
- $95,000 ÷ 47 weeks = $2,021/week
- 5.5 selling hours/day × 5 days = 27.5 Golden Hours/week
- $2,021 ÷ 27.5 = **$73 per Golden Hour**

**Calendar design (phone days — Mon/Fri):**
- Golden Hours: 8 AM–4 PM CT (prospects are CT/MT, so this covers both)
- Morning Platinum: 7–8 AM (prepare call list, review account notes, plan call objectives)
- Power Hour 1: 8–9 AM (phone block — 25–35 dials)
- Power Hour 2: 10–11 AM (phone block — follow-up calls from field days)
- Midday: 11 AM–1 PM (proposals, pipeline review, lunch)
- Power Hour 3: 1:30–2:30 PM (phone block)
- Afternoon Platinum: 4–5 PM (next-day prep, CRM clean-up, route planning for field days)

**Calendar design (field days — Tue–Thu):**
- Golden Hours: 8 AM–4 PM local to territory
- In-person prospecting and appointments fill the Golden Hours window
- Route planned in advance (Platinum Hours) to minimize drive time within prospect time zones
- 30-min Platinum buffer before first appointment for same-day prep

---

### Example 3: Founder-Seller (Self-Managed, No Support Staff)

**Situation:** Founder doing all sales personally. Annual revenue goal: $240,000 (B2B services). Works roughly 50 hours/week but self-manages all admin, operations, and prospecting. Prospects are primarily US West Coast.

**Hourly-worth calculation:**
- $240,000 ÷ 46 weeks = $5,217/week
- 4 focused selling hours/day × 5 days = 20 Golden Hours/week (lower because more wearing all hats)
- $5,217 ÷ 20 = **$261 per Golden Hour**

**Calendar design:**
- Golden Hours: 10 AM–2 PM PST (peak B2B phone window, post-standup hour for prospects)
- Morning Platinum: 7–10 AM (email, admin, proposals, operations — all non-selling work done here before phones open)
- Power Hour 1: 10–11 AM (phone block — 20–30 dials + LinkedIn DMs)
- CRM log: 11–11:30 AM
- Power Hour 2: 11:30 AM–12:30 PM (follow-up calls + email prospecting)
- Lunch: 12:30–1 PM
- Power Hour 3 (optional, 2× week): 1–2 PM (if pipeline pressure is high)
- Afternoon: Client delivery, operations, product work
- Evening Platinum (optional): 8–9 PM (catch-up on proposals/contracts if Golden Hours ran short)

**Key principle for founder:** At $261/hour, every 15 minutes spent on admin during the 10 AM–2 PM window costs $65. Delegating $30/hour Upwork tasks that free 2 hours of Golden Hours daily generates a 4× return on that $60/day spend.

---

## References

| File | Contents |
|---|---|
| `references/golden-platinum-hours-calendar-templates.md` | Extended weekly calendar templates for inside sales, outside sales, and founder-seller configurations; copy-paste blocks for common calendar tools |
| `references/hourly-worth-worked-examples.md` | Worked hourly-worth calculations across six income levels ($45K–$300K) with time-zone calibration notes |

---

## License

This skill is licensed under [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/).
Source: [BookForge](https://github.com/bookforge-ai/bookforge-skills) — Fanatical Prospecting by Jeb Blount (Ch. 8).

## Related BookForge Skills

For calculating how many dials per day you need to hit quota:
```
clawhub install bookforge-pipeline-ratio-calculator
```

For setting the right objective (appointment vs. qualify vs. close) for each touch in the block:
```
clawhub install bookforge-prospecting-objective-setter
```

For writing the phone opener used during Power Hours:
```
clawhub install bookforge-cold-call-opener-builder
```

For deciding which prospects to call first when the block starts:
```
clawhub install bookforge-prospect-prioritization-pyramid
```

Browse the full Fanatical Prospecting skill set: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

---
name: prospecting-ratio-manager
description: Calculate pipeline ratios and diagnose prospecting health using the Three Laws of Prospecting — use this skill when the user asks about pipeline ratios, close rate math, activity math, sales numbers, the 30-day rule, pipeline slump, feast or famine cycle, how many dials they should make, how much prospecting they need to do, whether they are prospecting enough, quota math, pipeline health, why their pipeline is empty, or why they are in a slump — even if they do not use those exact words. Produces a ratio dashboard (green/yellow/red status per law), a concrete daily activity target, and a fillable daily-tracker worksheet.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/fanatical-prospecting/skills/prospecting-ratio-manager
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: published
source-books:
  - id: fanatical-prospecting
    title: "Fanatical Prospecting"
    authors: ["Jeb Blount"]
    chapters: [5, 6]
tags: [sales, prospecting, pipeline, ratios, metrics, sdr, bdr, sales-ops]
depends-on: []
execution:
  tier: 2
  mode: hybrid
  inputs:
    - type: document
      description: "User's activity counts (dials/connects/conversations/meetings/closed deals), close rate history, quota target, and current pipeline snapshot — provided as a CSV, markdown table, pasted numbers, or verbal description"
  tools-required: [Read, Write]
  tools-optional: []
  mcps-required: []
  environment: "CSV/markdown/spreadsheet directory, or user pastes numbers directly into the prompt"
discovery:
  goal: "Diagnose prospecting health against Three Laws (Need, 30-Day Rule, Replacement) and produce a daily activity target plus daily-tracker worksheet"
  tasks:
    - "Collect activity data and close rate from user"
    - "Calculate the pipeline replacement rate from close-rate math"
    - "Diagnose status against Universal Law of Need, 30-Day Rule, and Law of Replacement"
    - "Compute daily activity target using the E+E=P performance formula"
    - "Produce a ratio dashboard with green/yellow/red status and a daily-tracker worksheet"
  audience:
    roles: [sdr, bdr, ae, founder-self-seller]
    experience: beginner-to-intermediate
  triggers:
    - "pipeline ratios"
    - "close rate"
    - "activity math"
    - "sales numbers"
    - "30-day rule"
    - "pipeline slump"
    - "feast or famine"
    - "how many dials should I make"
    - "how much prospecting do I need"
    - "am I prospecting enough"
    - "quota math"
    - "pipeline health"
    - "my pipeline is empty"
    - "why am I in a slump"
  prerequisites: []
  not_for:
    - "Writing call scripts or email sequences (use prospecting-message-crafter)"
    - "Prioritizing which accounts to call (use prospect-list-tiering)"
    - "Planning time blocks for prospecting sessions (use prospecting-time-block-planner)"
    - "Building a multi-channel prospecting cadence (use balanced-prospecting-cadence-designer)"
  environment: "Any agent environment where the user can provide numerical activity data or a pipeline snapshot"
  quality:
    required_outputs: ["ratio-dashboard", "daily-activity-target", "daily-tracker-worksheet"]
    completeness: "Every law must have an explicit green/yellow/red status with the reasoning shown"
---

# Prospecting Ratio Manager

## When to Use

Your pipeline is empty, shrinking, or unpredictable — and you are not sure whether you have a prospecting volume problem, a consistency problem, or a math problem. Or you are hitting quota but want to know exactly how much prospecting activity is required to maintain that pace as close rates fluctuate.

This skill applies three universal laws from Jeb Blount's *Fanatical Prospecting* to your actual numbers: it tells you whether you are in danger of the Universal Law of Need (desperation territory), whether the 30-Day Rule predicts a future slump from past inactivity, and whether the Law of Replacement math means your pipeline is silently draining faster than you think. It then calculates a concrete daily activity target and produces a worksheet you can fill in every day to stay honest.

**Typical triggers:**
- You feel like you are prospecting "a lot" but quota keeps slipping
- You just closed a big month and want to know if you are safe
- Your pipeline has fewer than 10 live opportunities
- You had a slow December (or any holiday / vacation month) and it is now 60-90 days later
- You are a new SDR / BDR and need a baseline to work from

**This skill does NOT cover:**
- Writing the actual call scripts or email copy (use `prospecting-message-crafter`)
- Deciding which accounts to call first (use `prospect-list-tiering`)
- Building a time-blocked prospecting schedule (use `prospecting-time-block-planner`)

---

## Context and Input Gathering

### Required Context (must have — ask if missing)

**Activity counts (last 30 days):** How many dials, connects, conversations (two-way), meetings/appointments set, and closed deals did you produce?
  -> Check working directory for: `pipeline-ratios.csv`, `activity-tracker.csv`, `activity.md`, or any CSV with columns containing "dials," "connects," "meetings," "closed"
  -> If not found, ask: "Can you share your activity numbers for the past 30 days? I need: dials made, phone conversations (real two-way), meetings/appointments set, and deals closed. Even rough estimates work — I will flag where uncertainty affects the diagnosis."

**Close rate (%):** What percentage of qualified opportunities do you typically close?
  -> If the user does not know: use 10% as the default and flag it. A rep with an unknown close rate is already operating blind.
  -> If data file is present, calculate from: `Closed Won / Total Qualified Opportunities Entered`

**Quota target:** What is your monthly or quarterly closed-revenue or closed-deal count target?
  -> If quota is revenue-based, also ask for average deal value so you can translate to deal count.

**Current pipeline size:** How many live, qualified opportunities are currently in your pipeline?
  -> If unknown: flag the data gap and proceed with what is available.

### Observable Context (gather from environment)

- CRM export or activity log files: parse for dials, connects, meetings, closed. Column name variations to check: `Calls Made`, `Outbound Dials`, `Conversations`, `Meetings Booked`, `Demos Set`, `Closed Won`, `Opp Created Date`
- Pipeline snapshot file: parse for count of open opportunities and their ages

### Default Assumptions

| Input | Default if unknown | Flag? |
|-------|-------------------|-------|
| Close rate | 10% | Yes — note it changes targets significantly |
| Working days per month | 21 | No |
| Daily dial capacity | 50 | Note as benchmark |
| Pipeline size | Unknown | Yes — Law of Replacement diagnosis will be partial |

### Sufficiency Threshold

```
SUFFICIENT when:
- At least one of: (a) 30-day activity counts, OR (b) close rate + quota target
- Quota target known (even rough)

NOT sufficient — ask before proceeding:
- No numbers whatsoever AND no files found
  -> Ask: "I need a few numbers to run the diagnosis. What's your monthly quota (as deal count or revenue), your rough close rate, and how many calls or outreach touches you made in the last 30 days?"
```

---

## Process

### Step 1: Collect and normalize activity data

Read any available file. Parse into a standard activity table:

| Metric | Last 30 Days | Notes |
|--------|-------------|-------|
| Dials made | — | Phone outbound attempts |
| Live conversations | — | Two-way exchanges (phone/video) |
| Meetings / appointments set | — | Qualified discovery or demo calls booked |
| Deals closed (won) | — | Closed-won count |
| New prospects added to pipeline | — | Net new opportunities created |
| Current pipeline size | — | Total live, qualified opportunities |

If the user provides raw numbers verbally, structure them into this table before proceeding.

**Why:** Unstructured gut feelings ("I made a lot of calls") are the primary source of self-delusion about prospecting activity. Jeb Blount's "rep who thought he made 50 calls but actually made 12" case is the canonical example. Structuring the numbers before diagnosis prevents the same error.

---

### Step 2: Calculate the pipeline replacement rate

Using the close rate, derive how many new prospects must be added to the pipeline for every deal closed.

**Formula:**

```
Replacement Rate = 1 / Close Rate (as decimal)

Example: Close rate = 10% (0.10)
Replacement Rate = 1 / 0.10 = 10

Interpretation: Every time you close 1 deal, you must add 10 new
prospects to maintain pipeline size — because statistically the other
9 prospects in that cohort will not close.
```

Calculate:
- **Minimum weekly adds** to sustain current pipeline: `(Monthly Closes Target × Replacement Rate) / 4.3`
- **Pipeline floor** (minimum viable live opportunities): `Monthly Closes Target × Replacement Rate`

**Why:** Most salespeople believe closing a deal shrinks the pipeline by 1. The Law of Replacement says it shrinks by the full cohort (at 10% close rate: by 10). This is the mathematical root cause of the feast-or-famine cycle. Without this calculation, a rep who closes 3 deals in a great week and adds 3 new prospects thinks they are even — they are actually 27 prospects underwater.

---

### Step 3: Diagnose against the Three Laws

Evaluate the user's data against each law. Assign a status (green / yellow / red) with explicit criteria.

#### Law 1 — Universal Law of Need

> The more you need a sale, the less likely you are to get it. Desperation magnifies and accelerates failure.

**Diagnosis inputs:** Current pipeline size vs. pipeline floor.

| Status | Condition | Meaning |
|--------|-----------|---------|
| 🟢 Green | Pipeline ≥ 2× pipeline floor | Healthy. You have optionality. No desperation pressure. |
| 🟡 Yellow | Pipeline is 1×–2× pipeline floor | Caution. One bad week removes your cushion. |
| 🔴 Red | Pipeline < pipeline floor | Universal Law of Need is active. Desperation signals are present or imminent. |

**Why this matters:** Red status means you are mathematically forced to close deals you cannot afford to lose. Prospects can sense that pressure. The fix is not better closing technique — it is rebuilding the pipeline volume.

#### Law 2 — 30-Day Rule (activity-to-pipeline lag effect)

> Prospecting done in any 30-day window pays off in the next 90 days. A prospecting gap now bites you 90 days later.

**Diagnosis inputs:** Monthly new prospects added (Step 1) vs. minimum monthly adds (Step 2).

Calculate a **prospecting coverage ratio:**
```
Coverage Ratio = New Prospects Added (Last 30 Days) / Minimum Monthly Adds Required
```

| Status | Coverage Ratio | Meaning |
|--------|---------------|---------|
| 🟢 Green | ≥ 1.2 | Prospecting is ahead of pace. 90-day outlook is healthy. |
| 🟡 Yellow | 0.8–1.19 | Roughly on pace. Minor gaps will appear in ~60-90 days. |
| 🔴 Red | < 0.8 | Prospecting deficit. Expect a pipeline slump in 60-90 days if not corrected now. |

If the user is currently in a slump: ask what their prospecting activity looked like 60-90 days ago. A December holiday gap causing a March slump is the Greg pattern — misdiagnosed as a closing problem, actually a lag effect from stopped prospecting.

**Why this matters:** The 30-Day Rule creates a dangerous illusion — prospecting gaps feel painless in the moment (you are busy closing) but manifest 90 days later when the pipeline is already empty and recovery takes another 30 days of daily prospecting. By then, the hole is 4 months deep.

#### Law 3 — Law of Replacement

> When you close 1 deal, you must replace the whole closing cohort — not just 1 prospect.

**Diagnosis inputs:** New prospects added (Step 1) vs. deals closed × replacement rate.

```
Replacement Deficit = (Deals Closed × Replacement Rate) - New Prospects Added

If Replacement Deficit > 0: pipeline is shrinking even if it looks "full"
```

| Status | Condition | Meaning |
|--------|-----------|---------|
| 🟢 Green | Replacement Deficit ≤ 0 | Pipeline is being replenished at or above close rate. |
| 🟡 Yellow | Deficit = 1–5 prospects | Minor lag. Catch up this week. |
| 🔴 Red | Deficit > 5 prospects | Pipeline is draining. Prospecting intensity must increase immediately. |

**Why this matters:** This is the most common invisible leak. A rep who closed 5 deals last month and added 5 new prospects thinks they are even. At 10% close rate, they are actually 45 prospects behind. The pipeline will look healthy for another 30 days, then collapse.

---

### Step 4: Calculate daily activity target

Using the quota target and close rate, work backward to a required daily activity level.

**Formula chain:**

```
Monthly Closes Needed         = Quota Target / Average Deal Value  (if revenue-based)
Monthly New Prospects Needed  = Monthly Closes Needed / Close Rate
Weekly New Prospects Needed   = Monthly New Prospects Needed / 4.3
Daily New Prospects Needed    = Weekly / 5

Conversations Needed per Day  = Daily New Prospects Needed / Meeting-Set Rate
  (use Meeting-Set Rate from Step 1 data: Meetings Set / Conversations)
  (default if unknown: 1 meeting per 5-10 conversations = 10-20% set rate)

Dials Needed per Day          = Conversations Needed / Connect Rate
  (use Connect Rate from Step 1: Conversations / Dials)
  (default if unknown: 1 conversation per 7-10 dials = 10-14% connect rate)
```

**Hourly worth check (optional but valuable):**
```
Worth per Hour = Annual Income Goal / (Working Weeks × Golden Hours per Week)
Default: $75,000 goal / (48 weeks × 30 hours/week) = $52/hour

Use this to evaluate whether non-prospecting tasks should be deferred or delegated.
```

**Why:** Without a number, "prospect more" is not an actionable directive. The daily dial target is what converts a diagnosis into a behavior. The backward calculation from quota ensures the target is anchored to revenue reality, not arbitrary benchmarks.

---

### Step 5: Produce the ratio dashboard and daily tracker

**Output 1: Ratio Dashboard** (`ratio-dashboard.md`)

```
=== PROSPECTING RATIO DASHBOARD ===
Generated: [Date]

INPUTS USED
-----------
Close Rate:             [X]%
Monthly Quota Target:   [N] deals (or $X at $Y avg deal)
30-Day Activity Data:   [provided / estimated]

KEY RATIOS
----------
Pipeline Replacement Rate:    [X] prospects per close
Pipeline Floor (minimum):     [N] live opportunities
Coverage Ratio (30-Day):      [X.X] ([Green/Yellow/Red])

THREE-LAW STATUS
----------------
Universal Law of Need:    [🟢/🟡/🔴] — Pipeline: [N] / Floor: [N]
30-Day Rule:              [🟢/🟡/🔴] — Coverage: [X.X] — [interpretation]
Law of Replacement:       [🟢/🟡/🔴] — Deficit: [N] prospects

DAILY ACTIVITY TARGET
---------------------
Deals to close per month:         [N]
New prospects needed per month:   [N]
Daily new prospects needed:       [N]
Conversations needed per day:     [N]  (at [X]% set rate)
Dials needed per day:             [N]  (at [X]% connect rate)

DIAGNOSIS SUMMARY
-----------------
[Narrative: Which laws are active, what caused it, what to do first]
```

**Output 2: Daily Tracker Worksheet** (`daily-tracker.md`)

```
=== DAILY PROSPECTING TRACKER ===
Rep: _______________    Date: _______________

DAILY TARGETS (from ratio dashboard)
  Dials:            [target]  |  Actual: _____
  Conversations:    [target]  |  Actual: _____
  Meetings Set:     [target]  |  Actual: _____
  New Prospects:    [target]  |  Actual: _____

PIPELINE STATUS
  Current Pipeline Size:      _____
  New Prospects Added Today:  _____
  Deals Closed Today:         _____
  Running Replacement Deficit: _____

LAW OF NEED CHECK  (circle one)
  Pipeline vs Floor:   ABOVE   /   AT   /   BELOW

NOTES / BLOCKERS
___________________________________________________

END-OF-DAY SELF-CHECK
  [ ] Did I hit my dial target?
  [ ] Did I add at least [N] new prospects today?
  [ ] Is my replacement deficit ≤ 0 for the week?
  [ ] If below floor: am I prospecting FIRST tomorrow, before anything else?
```

**Why:** Externalized tracking prevents the self-delusion problem. Blount's rep who "felt like" he made 50 calls but actually made 12 had no tracking sheet. The daily worksheet creates accountability by forcing a visual reckoning with the numbers at end of day, not at end of quarter when recovery options have narrowed.

---

## Inputs

| Input | Required | Format | Notes |
|-------|----------|--------|-------|
| 30-day activity counts | Recommended | CSV, markdown table, or pasted numbers | Dials, conversations, meetings, closes, new prospects added |
| Close rate | Recommended | Percentage or decimal | Default 10% if unknown |
| Monthly quota target | Required | Deal count or revenue | Revenue → also need avg deal value |
| Current pipeline size | Recommended | Integer | Needed for Law of Need diagnosis |

---

## Outputs

| Output | Format | Description |
|--------|--------|-------------|
| `ratio-dashboard.md` | Markdown | Three-law status (green/yellow/red), key ratios, daily activity target, diagnosis narrative |
| `daily-tracker.md` | Markdown | Fillable daily worksheet with targets populated from dashboard |

---

## Key Principles

**The pipeline replacement rate is the most underused number in sales.** Every rep knows their close rate but almost none do the math on what that close rate means for required daily activity. A 10% close rate does not mean 10% of your time prospecting — it means for every deal you close, you must find 10 new qualified prospects.

**The 30-Day Rule makes slumps invisible until they are severe.** The gap and the pain are separated by 60-90 days. By the time you feel the slump, the prospecting failure that caused it was 3 months ago. The only protection is daily tracking and weekly coverage ratio checks.

**Consistency beats intensity.** One week of 200 dials followed by three weeks of none does not average out. The 30-Day Rule requires steady input across the full window — the payoff comes from consistency, not bursts.

**Desperation is a symptom of a math failure, not a mindset failure.** When the Universal Law of Need is active, no closing technique will fix it. The fix is pipeline volume. Applying closing pressure when you are red on the Law of Need makes the problem worse by signaling desperation to prospects.

**Tracking must be visual and manual.** Relying on CRM auto-logging creates a false sense of productivity. Manual counting — even tick marks on a sheet — keeps you grounded in what actually happened today.

---

## Examples

### Example 1 — Jerry's end-of-quarter collapse (Universal Law of Need + Replacement)

**Situation:** SDR, mid-October. Had a strong August. Stopped prospecting heavily in September to service newly closed accounts. Now has 4 live opportunities, needs 2 closes by end of quarter. Close rate: 10%. Monthly quota: 3 deals.

**Data provided:**
- Dials last 30 days: 120 (well below their usual 300)
- New prospects added: 2
- Deals closed last 30 days: 3
- Current pipeline: 4 opportunities

**Diagnosis:**
- Pipeline floor: 3 closes needed × 10 = 30 minimum live opportunities
- Current pipeline: 4 — **Law of Need is Red**
- Replacement deficit: (3 closes × 10) − 2 added = **28 prospects underwater**
- Law of Replacement: **Red**
- Coverage ratio: 2 added / 30 needed = 0.07 — **30-Day Rule: Red**

**Dashboard output:** All three laws red. Diagnosis: Jerry did not prospect during his September close cycle. He is now 28 prospects underwater with only 4 live deals and needs 2 closes from that pool. Desperation signals are mathematically inevitable. The fix is not closing technique — it is 4-6 weeks of aggressive daily prospecting to rebuild the floor.

**Daily target:** 30 new prospects needed per month → 7 per week → 1.4 per day. At 10% meeting-set rate: 14 conversations/day. At 14% connect rate: 100 dials/day.

---

### Example 2 — Sandra's steady-state check (all laws green)

**Situation:** AE, wants to verify she is on track for Q3. Uses the skill as a monthly sanity check. Close rate: 20%. Monthly quota: 5 deals. Average deal value: $12,000.

**Data provided:**
- Dials last 30 days: 650
- New prospects added: 35
- Deals closed: 5
- Current pipeline: 38 opportunities

**Diagnosis:**
- Replacement rate: 1 / 0.20 = 5
- Pipeline floor: 5 × 5 = 25 minimum
- Current pipeline: 38 — **Law of Need: Green** (38 / 25 = 1.52×)
- Monthly adds needed: 5 × 5 = 25. Added: 35. Coverage ratio: 1.4 — **30-Day Rule: Green**
- Replacement deficit: (5 closes × 5) − 35 = −10 (surplus) — **Law of Replacement: Green**

**Dashboard output:** All three laws green. Sandra has a 10-prospect surplus, pipeline 52% above the floor, and prospecting pace 40% ahead of minimum. No action required except maintaining the current pace.

---

### Example 3 — Greg's mid-quarter course correction (30-Day Rule lag)

**Situation:** Sales rep, early March. December was slow (holiday breaks). January and February were busy with admin and onboarding new Q4 clients. Now nothing is closing. Rep thinks he has a closing problem.

**Data provided:**
- Deals closed in March so far: 0
- Meetings happening in March: 2 (both pushing to Q2)
- New prospects added last 30 days: 8
- Last full prospecting month: November (estimated 45 new prospects added)
- Close rate: 15%. Monthly quota: 3 deals.

**Diagnosis:**
- Replacement rate: 1 / 0.15 = 6.7 (round to 7)
- Monthly adds needed: 3 × 7 = 21. Added in Feb: ~8. Coverage ratio: 0.38 — **30-Day Rule: Red**
- Root cause diagnosis: December and January prospecting gaps are hitting in March. This is a prospecting problem, not a closing problem. The March stalls are prospects that were marginally viable — the cohort is stale. Calling them again for closing techniques will not help.
- Law of Need: pipeline details not provided — flag as partial diagnosis.

**Recommended action:** Stop calling the same 8 prospects. Start 30 days of daily prospecting from today. Expect the payoff in late April / May. Quota for March is likely unrecoverable — focus energy on April-May recovery.

---

## References

Full ratio-math proofs and worked examples with variable close rates (5%, 10%, 15%, 20%, 25%): see `references/ratio-math-reference.md`

Slump anatomy and recovery checklist (9-step sequence): see `references/slump-anatomy-and-recovery.md`

Source chapters: Blount, Jeb. *Fanatical Prospecting.* Wiley, 2015.
- Chapter 5: "The More You Prospect, the Luckier You Get" (pp. 43–53)
- Chapter 6: "Know Your Numbers: Managing Your Ratios" (pp. 54–58)

---

## Related BookForge Skills

- **prospecting-time-block-planner** — Once you have your daily dial target, use this skill to schedule protected prospecting blocks (Golden Hours) in your calendar.
- **balanced-prospecting-cadence-designer** — Design a multi-channel (phone, email, LinkedIn, text) cadence that reaches your daily new-prospect target across channels.
- **prospect-list-tiering** — Ensure the prospects you are adding to refill your pipeline are tiered by qualification state so you work the highest-probability accounts first.
- **call-reluctance-diagnostic** — If you know your targets but are not hitting them, use this skill to diagnose which of the Three Ps (procrastination, perfectionism, paralysis) is blocking activity.

---

## License

[CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) — BookForge Skills. Source framework: *Fanatical Prospecting* by Jeb Blount (Wiley, 2015). Chapters 5–6.

FILE:references/ratio-math-reference.md
# Ratio Math Reference

Supporting reference for `prospecting-ratio-manager` — full worked examples at variable close rates and the complete formula chain from quota to daily dials.

---

## Pipeline Replacement Rate Table

| Close Rate | Replacement Rate | Monthly adds per 1 close target | Monthly adds per 3 close target | Monthly adds per 5 close target |
|-----------|-----------------|--------------------------------|--------------------------------|--------------------------------|
| 5%        | 20              | 20                             | 60                             | 100                            |
| 10%       | 10              | 10                             | 30                             | 50                             |
| 15%       | 6.7             | 7                              | 20                             | 33                             |
| 20%       | 5               | 5                              | 15                             | 25                             |
| 25%       | 4               | 4                              | 12                             | 20                             |
| 33%       | 3               | 3                              | 9                              | 15                             |

**Key insight:** A rep with a 5% close rate who must close 3 deals per month needs to add 60 new qualified prospects per month — just to keep the pipeline static. That is 14 per week, or 2.8 per day on a 5-day week.

---

## Becky's Math (Law of Replacement Proof)

*Source: Blount, Fanatical Prospecting, Chapter 5*

Becky has 30 prospects in her pipeline. Her close rate is 10%. She closes 1 deal.

**Common (wrong) answer:** 29 prospects remain.

**Correct answer:** 20 prospects remain.

**Why:** Becky's 10% close rate means she closes 1 out of every 10 prospects she works. When she closes 1 deal, the statistical cohort that deal came from contained 10 prospects. The other 9 are not viable — they either lost interest, went with a competitor, were disqualified, or stalled indefinitely. They are consuming pipeline real estate without advancing.

Net effect: 30 − 10 = 20 remaining viable prospects.

This is a statistical argument. In any single cohort, some of those 9 might surprise you. Over time, however, your close rate predicts that you will close 1 in 10, and the rest will fall away. Planning pipeline health based on the optimistic "29 remain" view guarantees a future shortage.

---

## Full Formula Chain: Quota to Daily Dials

Worked example: SDR, $300k ARR annual quota, $50k average deal.

```
Step 1 — Deals needed per year
  $300,000 ARR / $50,000 avg deal = 6 deals/year

Step 2 — Deals needed per month
  6 / 12 = 0.5 deals/month
  (rounds to 1 deal every 2 months in practice)

Step 3 — New prospects needed per month (at 10% close rate)
  0.5 × 10 = 5 new prospects/month

Step 4 — New prospects needed per week
  5 / 4.3 = 1.2 new prospects/week

Step 5 — Conversations needed per week
  Assume meeting-set rate = 15% (1 meeting per 6.7 conversations)
  1.2 / 0.15 = 8 conversations/week = 1.6/day

Step 6 — Dials needed per day
  Assume connect rate = 12% (1 conversation per 8.3 dials)
  1.6 / 0.12 = 13.3 → ~14 dials/day minimum
```

**For a higher-volume SDR role** (monthly quota: 20 meetings set, not deals closed):

```
Meetings needed per month:  20
At 15% set rate:            20 / 0.15 = 133 conversations/month
At 12% connect rate:        133 / 0.12 = 1,108 dials/month = ~53 dials/day
```

This is close to Blount's "50 dials/day" benchmark for a standard phone-heavy SDR role.

---

## Efficiency + Effectiveness = Performance (E+E=P)

*Source: Blount, Fanatical Prospecting, Chapter 6*

**Efficiency** = Activity volume per time block (dials per hour)
**Effectiveness** = Ratio of activity to meaningful outcome (conversations per dial; meetings per conversation)

Both matter. The failure modes are symmetric:

| Scenario | Efficiency | Effectiveness | Result |
|----------|-----------|---------------|--------|
| 100 dials/hour, 0 appointments | High | Low | Wasted time — activity without outcome |
| 10 calls/hour, 1 high-quality appointment | Low | High | Suboptimized — better outcomes per call but pipeline fills too slowly |
| 50 dials/hour, 2 solid appointments | Balanced | Balanced | Target state |

The rep who made 12 calls "all day" had a dual failure: low efficiency (12 dials in 7 hours = 1.7/hour) AND low effectiveness (no appointments from 12 dials). Tracking both metrics separately pinpoints which variable to fix.

---

## Hourly Worth Calculation

*Source: Blount, Fanatical Prospecting, Chapter 8 (Time Equalizer)*

```
Worth per Hour = Annual Income Goal / (Working Weeks × Golden Hours per Week)

Example:
  $75,000 goal / (48 weeks × 30 hours/week) = $52/hour

Use case: If a task can be delegated, deferred, or batched into Platinum Hours
(before/after prime selling time) and it pays less than $52/hour in value,
executing it during Golden Hours costs the difference.

Example: Spending 3 hours on CRM data entry at $10/hour effective value
during $52/hour selling time costs $126 in opportunity, for a $30 task.
```

---

## 30-Day Rule Severity Thresholds

| Gap in prospecting activity | Expected consequence | Time to impact |
|---------------------------|---------------------|----------------|
| Miss 1 day | Minor dip, recoverable in days | ~90 days |
| Miss 1 week | Noticeable pipeline thinning | ~60-90 days |
| Miss 1 full month | Pipeline drains, slump likely | ~90 days |
| Miss 2+ months | Severe slump, desperation territory | ~90-120 days |

**Recovery benchmark:** ~30 days of consistent daily prospecting to begin pipeline recovery from a full-month gap. Results are not immediate — the 30-Day Rule applies to recovery too.

---

## Connect Rate and Meeting-Set Rate Benchmarks

These vary significantly by industry, list quality, channel, and rep experience. Use actual data whenever possible. Defaults for cold phone outreach (B2B):

| Metric | Low | Typical | High |
|--------|-----|---------|------|
| Connect rate (conversations per dial) | 6-8% | 10-14% | 18-22% |
| Meeting-set rate (meetings per conversation) | 8-12% | 15-20% | 25-35% |
| Show rate (meetings attended / set) | 60-70% | 75-85% | 90%+ |

**SDR benchmark from Blount:** 29 dials in 30 minutes → 2 appointments = ~3.5% direct-to-appointment rate (not all dials become conversations). Implies efficiency of ~58 dials/hour with solid effectiveness.

FILE:references/slump-anatomy-and-recovery.md
# Slump Anatomy and Recovery Checklist

Supporting reference for `prospecting-ratio-manager` — the 9-step slump sequence and recovery protocol from Blount's *Fanatical Prospecting*, Chapter 5.

---

## The Anatomy of a Sales Slump (9-Step Sequence)

99% of sales slumps trace directly to a failure to prospect. The sequence is consistent:

1. **Prospecting stops** — Holiday break, big-close month, administrative catch-up, or simple avoidance. (See: 30-Day Rule)
2. **Pipeline stalls** — No new prospects entering means the current pipeline ages with no fresh opportunities. (See: Law of Replacement)
3. **Closes stop** — The aging cohort produces no deals. Prospects who were marginal push further out or go dark.
4. **Confidence erodes** — Consecutive no-closes create a "losing streak" feeling.
5. **Negative self-talk** — "I've lost my edge." "Something has changed out there." "My product isn't competitive anymore."
6. **Energy and motivation drop** — The psychological weight of the slump makes prospecting feel harder, not easier.
7. **Calling the same dead-end prospects** — Rather than add new ones, the rep calls the same stale pool over and over, rationalizing it as "prospecting."
8. **Pipeline deteriorates further** — Already-stale prospects age out further. Coverage ratio continues to drop.
9. **Universal Law of Need activates** — Desperation sets in. Closes become urgent, which prospects sense. Probability of failure accelerates.

**Root cause diagnosis question:** "When did you stop prospecting consistently?"

If the answer is "3 months ago" (or the user cannot remember), the slump has been in motion since then. The current pain (no closes, pipeline empty) is the lagged consequence, not the cause.

---

## The Greg Pattern (Misdiagnosed Slump)

Symptom the rep presents: "Nothing is closing. I need better closing techniques."

Actual diagnosis: Prospecting gap from 90 days ago, now manifesting as stale pipeline.

Diagnostic question to surface this:
1. "Are you calling the same prospects over and over?"
2. "When did you last add a significant number of NEW prospects?"
3. "Was there a period 60-90 days ago when you were less active than usual — travel, holidays, a big customer emergency, a record close month?"

If any of these reveal a gap: the rep does not have a closing problem. They have a prospecting-lag problem.

**Why this misdiagnosis is common:** The gap and the pain are 60-90 days apart. The human brain looks for proximate causes ("I'm not closing this week because prospects aren't ready"). The actual cause (I stopped prospecting 3 months ago) feels remote and unrelated.

---

## The Rick Pattern (Team-Level Replacement Failure)

Symptom the manager presents: "We had two record months, then completely missed the third. The team gave up on me."

Actual diagnosis: The team stopped prospecting during the record close months. Law of Replacement was violated at scale. Pipeline drained while everyone celebrated and closed.

Recovery question for managers: "Were your salespeople prospecting at the same intensity during the close months as they were during the pipeline-building months?"

Answer is almost always no.

Fix: Establish a rule that prospecting activity continues at full rate during close months, not just pipeline-building months. Prospecting and closing are not sequential phases — they are parallel, continuous activities.

---

## Slump Recovery Protocol

**First rule of sales slumps:** When you are in one, start prospecting.

**Recovery timeline:** ~30 days of dedicated daily prospecting to begin pipeline recovery. Results will not appear immediately — the 30-Day Rule governs recovery too. Expect the first tangible pipeline improvements 30-60 days after consistent activity resumes.

**Recovery checklist:**

```
[ ] Accept that the slump is your doing — not the market, the leads, or the product
[ ] Identify the prospecting gap: when exactly did activity drop?
[ ] Stop calling stale prospects for "closing" — they are not closing
[ ] Set a daily dial target from the ratio dashboard (Step 4)
[ ] Commit to hitting that target for 30 consecutive days without exception
[ ] Use the daily tracker worksheet — visual accountability matters
[ ] Treat the first 1-2 weeks as triage: no results yet, but activity is the only path out
[ ] Do not wait for motivation — action creates motivation, not the other way around
```

**Mindset checkpoint during recovery:**
- Feeling like you are "going through the motions" in week 1-2 is normal
- The pipeline does not respond immediately; trust the math
- Each day of calling adds opportunities that will mature in 30-90 days
- The goal in recovery is not to close deals this week — it is to rebuild the cohort for next quarter

---

## The Slump Survival Ladder

From deepest slump to full recovery:

| Stage | Symptom | Required action |
|-------|---------|----------------|
| Stage 1: Crisis | Pipeline empty, Universal Law of Need active, all three laws red | Emergency: daily prospecting every day, no exceptions, for 30 days |
| Stage 2: Triage | Prospecting restarted but no closes yet | Stay the course; results are 30-60 days out |
| Stage 3: Recovery | New prospects entering pipeline; early meetings beginning | Maintain daily targets; resist urge to coast |
| Stage 4: Stable | Pipeline above floor; all laws yellow or green | Shift to maintenance mode; monitor coverage ratio weekly |
| Stage 5: Healthy | Pipeline ≥ 2× floor; coverage ratio ≥ 1.2 consistently | Full capacity; Sandra model |

---
name: prospecting-objective-setter
description: |
  Set the correct primary, secondary, and tertiary objective for any prospecting touch — before you make the call, send the email, or walk in the door. Use this skill when someone asks "what is my goal for this call", "should I try to set an appointment or just qualify", "appointment vs close — what should I go for", "what's my objective for this prospecting block", "should I qualify or pitch on this outreach", "what is the four objectives framework", "how do I decide what to ask for on a cold call", "primary secondary tertiary prospecting objective", "what should I optimize for in my cold email", "I have a new territory what should my prospecting objective be", "should I set appointments or close on the phone", "when is build familiarity the right objective", "my prospects are all unqualified what should I do first", or "how does sale complexity change my prospecting goal". Also invoke whenever a rep has a prospecting block coming up and wants to ensure every touch has a defined target outcome. This skill applies the Four Objectives framework (Set Appointment / Gather Information and Qualify / Close a Sale / Build Familiarity) to the rep's specific situation — sale complexity, channel, prospect qualification state, territory tenure, buying-window status — and produces a decision matrix mapping prospect tiers to correct primary/secondary/tertiary objectives. The output is an Objective Call Plan the rep uses to set up their next prospecting block.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/fanatical-prospecting/skills/prospecting-objective-setter
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: published
depends-on: []
source-books:
  - id: fanatical-prospecting
    title: "Fanatical Prospecting: The Ultimate Guide to Opening Sales Conversations and Filling the Pipeline by Leveraging Social Selling, Telephone, Email, Text, and Cold Calling"
    authors: ["Jeb Blount"]
    chapters: [9]
tags: [sales, prospecting, objective-setting, sdr, bdr, sales-strategy, cold-calling, inside-sales, outside-sales, qualification, pipeline, outbound]
execution:
  tier: 2
  mode: hybrid
  inputs:
    - type: document
      description: "Situation brief — product/service description, sale complexity (complex vs. transactional), sales-cycle length, sales channel (inside/outside), territory ramp-state (new/established), and target prospect tier (pre-qualified, semi-qualified, cold)"
  tools-required: [Read, Write]
  tools-optional: []
  mcps-required: []
  environment: "Document set — reads user-provided situation brief; writes prospecting-objective-plan-{date}.md to the working directory"
discovery:
  goal: "Determine the correct primary, secondary, and tertiary prospecting objective for the rep's specific situation and produce a written Objective Call Plan covering each prospect tier in their upcoming prospecting block"
  tasks:
    - "Gather the rep's sale complexity, channel type, prospect qualification level, territory ramp-state, and buying-window status"
    - "Apply the six-scenario decision framework to map situation to primary/secondary/tertiary objectives"
    - "Where needed, apply the qualify-first vs. appointment-first decision test"
    - "Produce a prospect-tier decision matrix (Primary / Secondary / Tertiary per tier)"
    - "Write prospecting-objective-plan-{date}.md as the block planning artifact"
  audience:
    roles: [sdr, bdr, ae, inside-sales-rep, outside-sales-rep, founder-self-seller]
    experience: beginner-to-intermediate
  triggers:
    - "Rep is about to run a prospecting block and wants every touch to have a defined target"
    - "Rep is confused about whether to go for appointment vs. close vs. qualification on their next call"
    - "Rep has a new territory or new product and wants to know where to start"
    - "Rep's pipeline is stagnant because they are chasing unqualified prospects without a defined objective strategy"
    - "Manager is asking the team to align their prospecting objectives to sale type and channel"
  prerequisites: []
  not_for:
    - "Writing the actual call script or email copy — use fanatical-prospecting:cold-call-opener-builder"
    - "Turning around objections and push-backs once the call is in progress — use fanatical-prospecting:prospecting-rbo-turnaround"
    - "Prioritizing which prospects to call first — use fanatical-prospecting:prospect-prioritization-pyramid"
    - "Calculating how many prospecting touches are needed to hit quota — use fanatical-prospecting:pipeline-ratio-calculator"
  environment: "Document set — reads situation brief from working directory or user input; writes Objective Call Plan"
  quality: placeholder
---

# Prospecting Objective Setter

## When to Use

You are setting up a prospecting block — a phone block, an email session, a LinkedIn outreach push, or an in-person field day — and you need to answer one fundamental question before the first touch:

**What am I trying to get from this contact right now?**

This skill applies the Four Objectives framework to your specific situation and produces a written Objective Call Plan. Every touch in your block gets a defined primary objective, so you know exactly what to ask for — and when to stop.

**Who this skill is for:** SDRs, BDRs, inside sales reps, outside sales reps, and AEs who run outbound prospecting as part of their daily work. Especially valuable for reps in new territories, reps whose pipeline is full of unqualified prospects, and any rep who has been "winging it" and wondering why activity doesn't convert.

**Output:** `prospecting-objective-plan-{date}.md` — a decision matrix with Primary / Secondary / Tertiary objectives per prospect tier, plus a one-line objective statement for each touch type in the upcoming block.

---

## Context & Input Gathering

### Required

To apply the framework accurately, the skill needs:

1. **Sale complexity:** Is your product/service complex, high-risk, or high-cost — or transactional, low-risk, low-cost?
2. **Sales channel:** Are you inside sales (phone/email/social, no in-person), outside sales with in-person prospecting, or outside sales using remote channels only?
3. **Prospect qualification state:** Are your prospects pre-qualified (you know the decision maker, the buying window, and the budget), semi-qualified (some information but gaps), or cold (little to no information)?
4. **Territory or account ramp-state:** Are you new to this territory/product/startup, or established?
5. **Buying-window awareness:** Do you know when your prospects can actually buy — contract expiration dates, budgetary periods, trigger events — or is this unknown?

### Useful (read from working directory if available)

- **`icp.md`** — Ideal customer profile: decision-maker roles, account size thresholds, buying trigger criteria
- **`prospect-list.csv`** — CRM export with qualification tier if tagged
- **`account-notes.md`** — per-account buying-window and stakeholder data

### Defaults

If no documents are provided, the skill asks the rep directly for the five inputs above. A two-to-three sentence verbal description of the selling situation is sufficient to begin.

### Sufficiency threshold

Sale complexity + channel type together determine the primary objective for the majority of scenarios. All five inputs sharpen the full decision matrix. If the rep is genuinely unsure about their sale complexity, the skill will apply the qualify-first vs. appointment-first decision test (Step 3) to resolve it.

---

## Process

### Step 1: Classify Sale Type and Channel

**Action:** Using the provided situation brief, classify the rep's situation on two axes:

**Sale type:**
- Complex / high-risk / high-cost: long sales cycles, multiple stakeholders, contractual obligations, high-level decision making, defined budgetary periods — typical of enterprise SaaS, capital equipment, professional services, major accounts
- Transactional / low-risk / low-cost: single decision maker or consistent decision-maker role, no set budgetary period, non-contractual or low-exclusivity, high probability most prospects are buyers — typical of SMB software, consumables, lower-ticket professional services

**Channel:**
- Inside sales: phone, email, text, social — no in-person prospecting
- Outside sales, remote channel: phone, email, text, social to prospects the rep will also see in person
- Outside sales, in-person: physically knocking on doors or attending venues where prospects are present

**WHY:** Sale type and channel are the two primary inputs to the Four Objectives framework. The same product can have different primary objectives depending on channel (outside sales in-person → close; outside sales via phone → appointment). Classifying these first eliminates the majority of ambiguity before the nuanced scenario rules are applied.

**Output:** A two-word classification: e.g., "Complex / Inside Sales" or "Transactional / Outside Sales (Remote)".

---

### Step 2: Apply the Six-Scenario Framework

**Action:** Map the rep's situation to one or more of the six decision scenarios. Each scenario specifies the Primary (P), Secondary (S), and Tertiary (T) objective:

**Scenario 1 — Complex / high-risk / high-cost product (any channel)**
- P: Set an appointment with a qualified decision maker, influencer, or stakeholder
- S: Gather information and qualify
- T: Build familiarity
- *Logic: A single call cannot close a complex sale. The appointment is the only outcome that advances the deal. Gathering information is secondary because qualifying before spending time on deep discovery prevents chasing unqualified deals.*

**Scenario 2 — Transactional / low-risk / low-cost + inside sales (phone/remote)**
- P: Close the sale on the spot
- S: Gather information and qualify
- *Logic: The channel (phone) and the sale type (transactional) together create the conditions for a one-call close. Closing on the spot is more efficient than setting a separate appointment.*

**Scenario 3a — Transactional / low-risk / low-cost + outside sales, remote channel (phone/email/text/social)**
- P: Set an appointment
- S: Gather information and qualify
- *Logic: Outside reps use phone/email as a booking tool, not a closing tool. The actual close happens in person.*

**Scenario 3b — Transactional / low-risk / low-cost + outside sales, in-person**
- P: Close the sale on the spot
- *Logic: In-person contact with a transactional product — the highest-probability close situation. Do not book an appointment when you are already standing in front of the buyer.*

**Scenario 4 — Highly qualified CRM database (prospects known, buying window opening)**
- P: Set appointments as the buying window opens
- S: Build familiarity (to increase engagement probability when the buying window opens)
- *Logic: You have already qualified these prospects. The remaining work is timing — being in front of them when they are ready to buy. Familiarity drives the response rate that makes appointment-setting possible.*

**Scenario 5 — Contract/budget-gated product (buying windows are locked to specific periods)**
- P: Gather information to qualify the buying window (contract expiry, budgetary period)
- S: Build familiarity
- *Then, once buying window is identified:* shift primary to Set an Appointment
- *Logic: There is no point setting an appointment — or closing — with a prospect who contractually cannot buy. The buying window qualification must come first. Once it is known, the objective shifts immediately to appointment-setting.*

**Scenario 6 — New territory, new startup, or new division**
- P: Gather information (identify decision makers, qualify buying windows and budgets)
- S: Build familiarity
- *Logic: Without data on who the right people are and when they can buy, all other objectives are premature. Data-gathering builds the foundation every other objective depends on.*

**WHY:** These six scenarios cover the vast majority of prospecting situations a rep encounters. The framework prevents the most common failure mode: reps who default to appointment-setting regardless of context (e.g., trying to book appointments with contract-locked prospects) or who gather information indefinitely without ever shifting to appointment-setting once qualification is complete.

**Output:** Identify which scenario(s) apply to the rep's situation. Note that a single rep may have different scenarios active simultaneously across different prospect tiers.

---

### Step 3: Apply the Qualify-First vs. Appointment-First Decision Test (if needed)

**Action:** If the rep is selling a complex product and is uncertain whether to qualify prospects before booking appointments or simply book all appointments and qualify in the meeting, apply this test:

**Set the appointment regardless of qualification level (appointment-first) when all four conditions are true:**
1. Product or service is non-contractual (no exclusivity lock-in)
2. High probability that most prospects are buyers — the product is something most prospects use consistently
3. No defined budgetary period — purchases can happen anytime
4. Decision-maker role is consistent and typically a single person

**Qualify first, then set the appointment when any of the following are true:**
- Product or service is complex or contractual (especially exclusive-vendor contracts)
- Sales cycle is long
- Decision making happens at a high organizational level
- There is a defined budgetary period
- Budgets require advance approval

**WHY:** Some sales trainers advocate setting appointments with every prospect regardless of qualification, reasoning that qualification should happen in the meeting. This is valid when the conditions above are met — but it creates waste when the product is contractual, the budgetary period is fixed, or the decision-maker is not a consistent single role. Blount's position: qualify first when unqualified meetings are expensive (travel, multi-stakeholder preparation, long sales cycle). Set appointments universally when meetings are cheap (inside sales, transactional product, consistent DM).

**Output:** A one-line decision: "Qualify before setting appointments" or "Set appointments, qualify in meeting" — with the condition that triggered the decision.

---

### Step 4: Define the Strike Zone

**Action:** Before completing the Objective Call Plan, verify that the rep has defined (or can define) the qualification criteria that separate a prospect worth pursuing from one that should be eliminated or deprioritized. These are the "strike zone" criteria:

- Decision-maker roles for this product/service
- Account size or revenue threshold (too small / too large)
- Buying-window indicators: contract expiration timing, trigger events, budgetary periods
- Competitors or exclusion criteria (contracts with a competitor that prevent purchase)
- Industry verticals or geographic zones relevant to this territory

If these criteria are not yet defined, prompt the rep to identify them before the prospecting block. Chasing prospects outside the strike zone is the primary cause of low conversion and wasted time.

**WHY:** Qualification criteria define which prospecting calls are worth making. Without them, reps swing at every pitch — including the ones that will never close. Blount's baseball analogy is explicit: "Don't swing at nothin' ugly." The strike zone is the filter that makes every other objective decision meaningful.

**Output:** A brief strike-zone checklist embedded in the Objective Call Plan.

---

### Step 5: Build the Prospect-Tier Decision Matrix and Write the Objective Call Plan

**Action:** Segment the rep's prospect base into tiers (based on the qualification data available), then assign Primary / Secondary / Tertiary objectives to each tier. Write `prospecting-objective-plan-{date}.md`.

Apply the familiarity touch-count reference when setting expectations for build-familiarity objectives:

| Prospect Familiarity Level | Expected Touches to Engage |
|---|---|
| Inactive customer (knows you, no recent contact) | 1–3 touches |
| Prospect in buying window, familiar with you/brand | 1–5 touches |
| Prospect familiar with brand, NOT in buying window | 3–10 touches |
| Warm inbound lead | 5–12 touches |
| Prospect with some familiarity, buying-window uncertain | 5–20 touches |
| Cold prospect, no familiarity | 20–50 touches |

Use these benchmarks to set realistic expectations: a cold-prospect objective of "set an appointment" on the first touch will fail at high rates. Familiarity must be built over multiple touches before appointment-setting becomes productive.

**WHY:** The objective plan is the operational artifact. Without writing it down, reps default to their comfort channel and habitual ask regardless of what the framework says. A written plan also makes prospecting blocks faster to execute — the rep knows before touching the phone what they are trying to achieve on each tier, which eliminates hesitation and frees cognitive capacity for the call itself.

---

## Output Template

```markdown
# Prospecting Objective Plan
**Date:** [Date]
**Rep:** [Name]
**Block type:** [Phone / Email / LinkedIn / In-person / Mixed]
**Prepared by:** fanatical-prospecting:prospecting-objective-setter

---

## Situation Classification

- **Sale type:** [Complex / high-cost OR Transactional / low-cost]
- **Channel:** [Inside sales / Outside sales (remote) / Outside sales (in-person)]
- **Territory state:** [New / Established]
- **Qualify-first decision:** [Qualify before setting appointments / Set appointments, qualify in meeting]
- **Active scenario(s):** [Scenario 1 / 2 / 3a / 3b / 4 / 5 / 6 from framework]

---

## Strike Zone

| Criterion | Qualifier |
|---|---|
| Decision-maker role(s) | [e.g., VP of Operations, Procurement Manager] |
| Account size | [e.g., 50–500 employees] |
| Buying-window trigger | [e.g., contract expiry within 6 months, new office opening] |
| Exclusions | [e.g., locked into Competitor X for 18+ months] |
| Geographic / vertical filter | [e.g., manufacturing sector, Midwest territory] |

---

## Prospect-Tier Objective Matrix

| Prospect Tier | Qualification State | Primary Objective | Secondary Objective | Tertiary Objective |
|---|---|---|---|---|
| Tier A — Fully qualified, in buying window | Decision maker known, budget confirmed, contract expiry imminent | Set appointment | Build familiarity | — |
| Tier B — Qualified, NOT in buying window | Decision maker known, buying window 6–18 months out | Build familiarity | Gather information (refine window timing) | — |
| Tier C — Semi-qualified | Some contact data, DM role uncertain or incomplete | Gather information and qualify | Build familiarity | — |
| Tier D — Cold | Little or no data | Gather information and qualify | Build familiarity | — |
| Tier E — Bogus / out-of-scope | Out of business, too small, wrong industry | Eliminate | — | — |

*Customize tiers to match your actual CRM segmentation or prospect list.*

---

## Per-Touch Objective Statement

For each touch type in this block, the ask is:

| Touch Type | Prospect Tier | Primary Ask |
|---|---|---|
| Outbound phone call | Tier A | "I'd like to schedule [X] on [specific date/time]" |
| Outbound phone call | Tier C/D | "Can you help me understand who handles [X] and when your next review cycle is?" |
| Cold email | Tier A/B | Appointment request or familiarity-building content |
| Cold email | Tier C/D | Information-gathering or familiarity-building |
| LinkedIn / social | Any cold tier | Familiarity-building: connect, comment, engage — not a pitch |
| In-person (if outside sales, transactional) | Any | Close on the spot |

---

## Familiarity Benchmarks for This Block

Cold prospects (Tier D) in this block require an estimated **20–50 touches** before appointment-setting becomes productive. Set familiarity-building as the primary objective for these contacts and do not measure this block's success by appointment rates from cold prospects alone.

---

## Block Summary

**Total touches planned:** [N]
**Tier A (appointment-primary):** [N]
**Tier B (familiarity/nurture-primary):** [N]
**Tier C/D (info-gathering-primary):** [N]
**Expected appointment sets from this block:** [N — based on tier mix and historical conversion]
```

---

## Key Principles

**Every touch has exactly one primary objective.** Not "I'll see how it goes." Before each call, email, or social touch, the primary objective is defined and written. This is what separates a prospecting block from random activity.

**WHY:** Objective clarity makes you both efficient and effective. Efficient because you can group similar-objective touches into a single block (all appointment-setting calls together, all information-gathering calls together), moving faster with less context-switching. Effective because on each touch you know exactly what to ask for and how to bridge to the prospect's world to make them say yes.

**An appointment is only an appointment when it is on both calendars.** "Call me anytime," "just stop by," and "we'll connect soon" are not appointments. A confirmed date, time, and place (physical or virtual) with the prospect expecting your arrival — that is the only definition. Accepting ambiguous commitments as appointments inflates your pipeline with phantom meetings and destroys forecast accuracy.

**WHY:** A calendar invite that is not accepted is a wish, not a commitment. Blount's research shows that reps with 80% no-show rates almost universally have the same root cause: they accepted brush-offs as appointments. The stricter definition forces the rep to obtain a genuine commitment — which is harder to get but infinitely more valuable.

**Build familiarity is a legitimate primary objective — and the only path through a cold prospect.** Reps who set appointments as the universal objective for cold prospects fail because they are ignoring the touch-count reality. A cold prospect who does not know you or your brand requires 20–50 touches before they will reliably engage. Familiarity-building as a deliberate objective — through voicemail, email, LinkedIn engagement, conference presence — systematically reduces that number over time.

**WHY:** Each voicemail they hear, each email they see, each LinkedIn interaction incrementally increases the probability of engagement on the next touch. Treating familiarity-building as a waste of time produces reps who make 20 cold calls, get no appointments, and conclude that prospecting "doesn't work." Treating it as a named objective produces reps who run Strategic Prospecting Campaigns (SPCs) that convert cold prospects into warm ones over 60–90 day cycles.

**Qualify first when unqualified meetings are expensive.** The cost of a wasted appointment varies by product and channel. For an inside sales rep with a transactional product, a bad appointment costs 20 minutes. For a field rep selling capital equipment with a 6-month sales cycle, a bad appointment costs travel time, opportunity cost, multi-stakeholder preparation, and potentially a proposal. Qualification discipline scales with the cost of a wasted meeting.

---

## Examples

### Example 1: SDR Selling Enterprise HR Software (Complex / Inside Sales)

**Situation:** SDR at a mid-market HR tech company. Product: $80K/year platform requiring IT and HR sign-off. Inside sales only (no in-person). Prospect list: 200 companies sourced from ZoomInfo, ~40% have no CRM contact data.

**Framework application:**
- Sale type: Complex / high-cost → Scenario 1
- Channel: Inside sales
- Result: P = Set appointment (with qualified DM), S = Gather information, T = Build familiarity

**Objective matrix:**
- Fully qualified prospects (decision maker known, renewal coming): P = Set appointment
- Semi-qualified (HR Director name known, no IT contact): P = Gather information (identify IT stakeholder), S = Set appointment if HR director is available
- Cold (company only, no contact): P = Gather information (find HR Director), S = Build familiarity

**Key decision:** Because the product is contractual (annual commitment, IT + HR approval), qualify first — do not set appointments with contacts who cannot actually influence the purchase.

---

### Example 2: Outside Sales Rep Selling Janitorial Supplies (Transactional / Outside Sales)

**Situation:** Field rep covering a new territory. Product: consumable, $300–2,000/quarter per account. Prospects include office buildings, manufacturing plants, and retail chains. Mix of in-person cold calls and phone follow-ups.

**Framework application:**
- Sale type: Transactional / low-cost → Scenarios 3a and 3b
- Channel: Outside sales (in-person + remote)
- Territory state: New → Scenario 6 also active

**Objective matrix:**
- In-person cold call at a business: P = Close the sale on the spot (Scenario 3b)
- Phone outreach to businesses not yet visited: P = Set appointment for in-person visit (Scenario 3a)
- All contacts in new territory: P = Gather information (who orders supplies, how much, current vendor) — Scenario 6 applies until baseline data exists

**Key decision:** For new territory calls, even in-person, the rep may need to gather information (find the right buyer) before attempting a close. Scenario 6 takes priority for the first 60 days until a functional prospect list is built.

---

### Example 3: AE Selling Benefits Brokerage (Contract-Gated / Inside Sales)

**Situation:** AE at a benefits brokerage firm. Prospects renew benefits packages annually — typically in Q4 for a Jan 1 effective date. Switching is rare outside the renewal window due to carrier contracts.

**Framework application:**
- Sale type: Complex + contract-gated → Scenarios 1 and 5 both apply
- Buying window: Locked to Q4 renewal cycle

**Objective matrix (by quarter):**
- Q1–Q2 (far from renewal): P = Gather information (identify renewal date, current broker, decision maker), S = Build familiarity
- Q3 (renewal approaching): P = Set appointment (pre-renewal discovery meeting), S = Gather information (refine needs, stakeholders)
- Q4 (renewal window open): P = Set appointment / close — highest activity period

**Key decision:** Do not attempt to set appointments with prospects in Q1 whose renewal is in Q4. It wastes the rep's time and strains the relationship. The buying window qualification must come first. Once the window is identified, shift immediately to appointment-setting.

---

## References

| File | Contents |
|---|---|
| `references/four-objectives-decision-matrix.md` | Full six-scenario reference table with qualifying conditions, objective assignments, and the qualify-first vs. appointment-first decision checklist |
| `references/familiarity-touch-counts.md` | Touch-count benchmarks by familiarity level; Strategic Prospecting Campaign (SPC) design guidance for cold-to-warm conversion |

---

## License

This skill is licensed under [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/).
Source: [BookForge](https://github.com/bookforge-ai/bookforge-skills) — Fanatical Prospecting by Jeb Blount (Ch. 9).

## Related BookForge Skills

For prioritizing which prospects to call first within your tiers:
```
clawhub install bookforge-prospect-prioritization-pyramid
```

For writing the actual call opener once your objective is set:
```
clawhub install bookforge-cold-call-opener-builder
```

For handling push-back once the call is in progress:
```
clawhub install bookforge-prospecting-rbo-turnaround
```

For calculating how many touches are needed to hit pipeline targets:
```
clawhub install bookforge-pipeline-ratio-calculator
```

Browse the full Fanatical Prospecting skill set: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

---
name: prospecting-objection-handler
description: |
  Classify prospect pushback and produce a scripted Anchor-Disrupt-Ask turnaround for any sales
  objection, reflex response, or brush-off using Blount's RBO Turnaround Framework.

  Trigger this skill when you hear or ask:
  - "objection handling" or "turn around a no" or "prospect said no"
  - "cold call objection" or "reflex response" or "brush off"
  - "not interested" or "happy with current" or "too busy"
  - "anchor disrupt ask" or "RBO turnaround" or "sales rejection"
  - "prospect pushed back" or "how do I respond to no"
  - "they said send me some information" or "call me later"
  - "they said they're happy with their current provider"
  - "turnaround script" or "handling a brush-off" or "dealing with rejection on a cold call"
  - "2-RBO rule" or "when to give up on a prospect" or "dead horse checkpoint"
  - "disrupt vs defeat" or "don't say I understand" or "never overcome objections"

  This skill classifies the pushback type (Reflex Response / Brush-Off / Objection), explains why
  each requires a different intervention, then produces a complete Anchor-Disrupt-Ask script for
  the specific pushback — including a fallback script for the second attempt and a dead-horse
  checkpoint for when to gracefully exit.

  NOT for: writing the initial cold call opener before pushback occurs (use cold-call-opener-builder),
  building the underlying bridge/because message (use prospecting-message-crafter), or planning
  a multi-touch email cadence.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/fanatical-prospecting/skills/prospecting-objection-handler
metadata:
  openclaw:
    emoji: "📚"
    homepage: "https://github.com/bookforge-ai/bookforge-skills"
status: published
source-books:
  - id: fanatical-prospecting
    title: "Fanatical Prospecting"
    authors:
      - Jeb Blount
    chapters:
      - 16
tags:
  - sales
  - prospecting
  - objection-handling
  - cold-calling
  - sdr
  - bdr
depends-on:
  - cold-call-opener-builder
  - prospecting-message-crafter
execution:
  tier: 2
  mode: hybrid
  inputs:
    - type: document
      description: "Verbatim prospect pushback + context (channel, prior statement, your call objective)"
  tools-required: [Read, Write]
  tools-optional: []
  mcps-required: []
  environment: "Document directory"
discovery:
  goal: "Produce a complete Anchor-Disrupt-Ask turnaround script, a fallback script, and a dead-horse checkpoint for the given prospect pushback"
  tasks:
    - "Gather the verbatim pushback and call context from the user"
    - "Classify the pushback as Reflex Response, Brush-Off, or Objection using the three-type taxonomy"
    - "Draft the Anchor statement (neurological buy-time mechanism)"
    - "Draft the Disrupt statement (unexpected, non-combative pull response)"
    - "Draft the Ask (assumptive, specific, no pause)"
    - "Prepare a fallback script for the second RBO attempt"
    - "Apply the 2-RBO dead-horse checkpoint"
    - "Write the complete output to rbo-turnaround-script.md"
  audience:
    roles: [sdr, bdr, ae, founder-self-seller]
    experience: beginner-to-intermediate
  when_to_use:
    triggers:
      - "Prospect just said 'I'm not interested' and the rep doesn't know what to say"
      - "Rep is building a script library for the 6 most common pushback types before a call block"
      - "Current response to 'we're happy with our provider' is 'oh, well, sorry to bother you'"
      - "Rep knows they're arguing with prospects instead of disrupting expectations"
      - "Rep is unsure whether to keep pushing or move on after two failed turnarounds"
      - "Rep says 'I understand' repeatedly and wonders why it isn't working"
    prerequisites: []
    not_for:
      - "Writing the initial cold call opener (use cold-call-opener-builder)"
      - "Building the bridge/because message nucleus (use prospecting-message-crafter)"
      - "Handling gatekeeper access blocks — those are structural, not RBOs (use gatekeeper-navigator)"
  environment:
    codebase_required: false
    codebase_helpful: false
    works_offline: true
  quality:
    scores:
      with_skill: 0
      baseline: 0
      delta: 0
    tested_at: ""
    eval_count: 0
    assertion_count: 0
    iterations_needed: 0
    what_skill_catches:
      - "Classifies pushback as Reflex Response, Brush-Off, or Objection — three types with different response logic"
      - "Produces Anchor-Disrupt-Ask structure, not a generic objection rebuttal"
      - "Names the neurological rationale for the Anchor (amygdala / fight-or-flight buy-time)"
      - "Enforces the 2-RBO rule: attempt twice, then gracefully disengage"
      - "Rejects 'I understand' as insincere filler with explicit rationale"
      - "Uses Judo/disrupt metaphor — pull not push, yielding way not combat"
      - "Includes a fallback script for the second turnaround attempt"
      - "Provides the dead-horse checkpoint and the 'NEXT' recovery trigger"
    what_baseline_misses:
      - "Treats all pushback the same — no distinction between habitual script vs conscious avoidance vs genuine objection"
      - "Responds to 'not interested' by explaining the product or arguing value — which creates resistance"
      - "Uses 'I understand' as an empathy filler, which signals insincerity not listening"
      - "Has no rule for when to stop — either gives up too early or fights past two RBOs"
      - "Does not produce a ready-to-use script — gives advice instead of a turnaround template"
      - "Does not know the amygdala / neocortex rationale for why the Anchor works neurologically"
---

# Prospecting Objection Handler

## When to Use

Your prospect just said something that made you want to hang up. "I'm not interested." "I'm really
busy." "We're happy with who we have." "Just send me some information."

This skill takes that exact pushback, classifies it, and produces a complete three-step
**Anchor-Disrupt-Ask** turnaround script you can deliver in the next five seconds — plus a fallback
script for if the first attempt doesn't work, and a clear checkpoint for when to gracefully exit.

Use this skill when:
- You are about to run a prospecting block and want scripted turnarounds for the six most common
  pushback types before you pick up the phone
- You just got a pushback you didn't handle well and want to know what you should have said
- You are unsure whether what you heard was a real objection or just an automatic reflex
- You keep "I understand"-ing your way through calls and it isn't working
- You need to know when two failed turnarounds means it is time to move on

**Where this skill fits in the call:** `cold-call-opener-builder` delivers your Five-Step opener.
The moment you finish the ask in Line 5, silence follows. If the prospect breaks that silence with
pushback, this skill takes over.

## Context & Input Gathering

Before building the turnaround, gather the following from the user:

**Required:**
1. The prospect's exact words (verbatim if possible — phrasing determines classification)
2. Your call objective (appointment / qualifying information / direct sale)
3. Channel (phone / in-person / email reply / social reply)

**Recommended:**
4. What you said just before the pushback (the opener line that triggered the response)
5. Whether you have spoken to this prospect before (first contact vs. follow-up)

**If no prior call context exists:** Proceed directly to Step 1 with the pushback text alone.

## Process

### Step 1 — Classify the Pushback

Read the verbatim pushback and assign it to one of three types. The type determines your entire
response strategy — using the wrong intervention for the wrong type will either escalate resistance
or miss the opening entirely.

**Type 1: Reflex Response**
The prospect is running an automatic script. They do not consciously mean what they said. The
words come from conditioned habit — the same phrase they use every time a salesperson calls.

*Behavioral signatures:* fast delivery, no reasoning, no "because," often not literally true
("I'm just running out the door" when they are sitting at their desk).

*Common examples:* "I'm not interested." / "We're all set." / "I'm too busy." / "We're happy."

*Why it is not a real objection:* Blount's opening illustration — he walked into a store and told
the salesperson "I'm just looking" when he actually needed help finding a product. The reflex fires
before the logical brain engages. (Blount, Ch. 16, p. 199)

**Type 2: Brush-Off**
The prospect is consciously trying to end the interaction without confrontation. They are not
lying because they disrespect you — they are lying because past salespeople have punished
honest responses with argument. The brush-off is a kindness disguised as a deferral.

*Behavioral signatures:* polite deferral tone, future-promise language, no commitment date, vague
action item.

*Common examples:* "Call me later." / "Get back to me in a month." / "Just send me some information."

*Why it is not a real commitment:* Seth Godin's diagnosis, cited by Blount: "Prospects lie because
salespeople have trained them to." Honest responses are met with pressure; deferral is safer.
(Blount, Ch. 16, p. 200)

**Type 3: Objection**
The prospect is giving you a truthful, logical rebuttal. It comes with a "because." It is rarer
than Types 1 and 2, and it actually opens a door — real objections reveal real information about
the prospect's world.

*Behavioral signatures:* slower delivery, specific reasoning, named constraint, logical structure.

*Common examples:* "We just signed a two-year contract with your competitor because they gave us a
major discount." / "Our budgets are frozen until Q3 because we just completed an acquisition." /
"I can't meet next week because I'll be at a conference."

*Why this type is different:* A genuine objection is a prospect telling you the truth. That earns
a different response — one that acknowledges the constraint, reframes the timing or stakes, and
asks for something appropriate given the reality they just described. (Blount, Ch. 16, p. 201)

**Why classify first:** A reflex response needs disruption of an automatic pattern. A brush-off
needs a challenge to a false commitment. A genuine objection needs engagement with a real
concern. The same turnaround does not work across all three. Misclassifying causes you to argue
with a habit (useless), accept a fake deferral as a real promise (self-defeating), or dismiss real
information (damaging). (Blount, Ch. 16, pp. 199–202)

---

### Step 2 — Draft the Anchor

The Anchor is the first thing you say after the pushback. Its job is neurological, not rhetorical.

When a prospect says no, your amygdala (the brain's threat-detection system) fires a fight-or-
flight response before your logical brain (neocortex) can evaluate the situation. This is the same
physiological cascade that would fire if you encountered a bear on a trail. The prospect saying no
and a bear on the trail feel identical to your nervous system — your logical brain cannot
distinguish between them fast enough to prevent the emotional reaction.

The Anchor gives your neocortex a millisecond to catch up. It is a brief, low-conflict statement
that you have rehearsed until it fires automatically — buying the moment your emotional brain
needs to stand down so your logical brain can take over the call.

**Anchor principles:**
- One line. Calm tone. No argument. No sarcasm.
- Agree with the prospect or acknowledge their statement without resistance
- Should feel like you expected this response — because you did
- Must be rehearsed until it sounds natural, not scripted

**Anchor patterns by type:**
- Reflex ("I'm busy"): "That's exactly why I called." / "I figured you would be."
- Brush-Off ("Send me info"): "Happy to. Let me ask you one quick thing first."
- Objection ("We just signed with a competitor"): "That makes perfect sense given that."

**Why the Anchor is not a tactic:** It is a neurological mechanism. You are not agreeing with the
prospect to manipulate them — you are giving your own brain the time it needs to operate from
logic rather than fear. Without the Anchor, you stumble, overexplain, or go defensive. The Anchor
is self-regulation before persuasion. (Blount, Ch. 16, pp. 204–205)

---

### Step 3 — Draft the Disrupt

The Disrupt is the core of the turnaround. It is a statement or question that does something the
prospect has been conditioned not to expect from a salesperson: it does not fight.

Every prospect who has dealt with salespeople carries a mental model of what happens when they
say no: the salesperson argues, pushes harder, asks "why not?", or tries to rationalize them out
of their position. The Disrupt breaks that pattern entirely. It is verbal judo — "the gentle or
yielding way" — achieving your objective without causing injury or generating resistance.

**The mechanism:** When humans encounter something that violates their expectation, they pause
and pay attention. That pause is your opening.

**Disrupt patterns by type:**

*For Reflex Responses — agree and reframe:*
- "I'm not interested" → "That makes sense. Most people aren't until they see [specific outcome]."
- "I'm happy with who I have" → "Awesome. If you're happy, you shouldn't even think about
  changing. All I want to do is [low-stakes request that isn't 'sell you something']."
- "I'm too busy" → "I figured you would be, so I want to find a time that's more convenient."

*For Brush-Offs — call the bluff, force engagement:*
- "Send me some information" → "Tell me specifically what you're looking for and I'll make sure
  what I send is actually relevant to your situation."
- "Call me in a month" → "Happy to. What will be different in a month that makes it a better time?"

*For Objections — acknowledge, reframe the stakes:*
- "We're locked into a contract" → "That's fair. Most of the clients I work with now were in the
  same situation when we first talked. I'm not looking to disrupt anything — I'd just like to be
  the one you call when the renewal comes up. Could we spend 10 minutes so you have a reference
  point when that happens?"

**Words to avoid:** "I understand." When you say "I understand," you sound like every other
salesperson who uses that phrase as insincere filler before launching the next pitch. It signals
you are not listening and do not care. Your prospect's brain is not ready for you to agree with
them — it is ready for you to argue. Use that expectation; do not confirm it. (Blount, Ch. 16, p. 206)

**Why disrupt not defeat:** You cannot argue another person into believing they are wrong. Every
salesperson who has "overcome objections" by pushing has either gotten a yes in spite of the
argument, or — far more often — generated more resistance and lost the prospect permanently.
Overcoming creates animosity. Disrupting creates curiosity. Pull, do not push. (Blount, Ch. 16, pp. 203–205)

---

### Step 4 — Draft the Ask

Immediately after the Disrupt, ask again for what you originally came for. No hesitation, no
pause, no preamble. The Ask in the turnaround is structurally identical to the Ask in your opener:
assertive, specific, assumptive.

**Why no pause between Disrupt and Ask:** A pause signals that you are waiting for their
permission to continue. You are not asking permission — you are assuming yes and asking for a
specific commitment. The absence of hesitation is itself a confidence signal that influences the
prospect's response. (Blount, Ch. 16, p. 206)

**Ask patterns:**
- Appointment: "How about we get together Thursday at 3:00 PM instead?"
- Qualifying information: "Can you tell me more about your situation and when [decision process]
  typically kicks off?"
- Low-stakes request: "Can I get 10 minutes on your calendar next Tuesday at 10 AM?"

**Match the Ask to your objective and the pushback type:** After a genuine objection, do not ask
for the same full meeting you originally wanted — that reads as tone-deaf. Ask for something
smaller that fits the constraint they described.

---

### Step 5 — Prepare the Fallback and Apply the 2-RBO Rule

About half the time, your first turnaround will produce a second RBO instead of a yes. This is
normal — and it is often useful. The second RBO tends to be closer to the truth than the first.
If the first was "I'm not interested" (reflex), the second might be "We actually just renewed with
a competitor" (objection). That is information.

**Fallback preparation:**
- Draft a second Anchor-Disrupt-Ask for the most likely second pushback
- The second Disrupt should be lighter — lower stakes, shorter ask, less pressure
- The tone shifts from "get the meeting" to "get the permission to come back"

**The 2-RBO Rule:** If you have attempted two full Anchor-Disrupt-Ask turnarounds and the
prospect has not moved, do not attempt a third. Gracefully disengage.

*Graceful exit script:* "I completely understand — I clearly caught you at a bad time. I'll reach
back out when the timing is better. Have a great day."

**Why stop at two:** After two turnarounds, continuing communicates that you did not hear
them, that you will ignore their stated preferences, and that future contact will feel like
harassment. Pushing past two RBOs destroys the relationship and poisons future contact attempts
with the same prospect. The prospect will move on the moment you hang up — they will not
remember this interaction the way you will. (Blount, Ch. 16, pp. 206, 208–210)

**The Dead-Horse Checkpoint:** Before attempting a second turnaround, ask yourself: is there
any signal in what they said that indicates genuine openness, or is this person actively ending the
conversation? If they are hanging up, screaming, or have explicitly said "never call me again" —
that is a dead horse. Dismount immediately. Log it, say NEXT, and dial the next number. The
horse is dead; beating it costs you money, time, and emotional reserves. (Blount, Ch. 16, pp. 208–210)

---

### Self-Check Before Writing Output

Before finalizing, verify the turnaround script passes all five checks:

- [ ] **Pushback is classified** — explicitly labeled as Reflex Response, Brush-Off, or Objection with rationale
- [ ] **Anchor is present and brief** — one line, non-argumentative, rehearsal-ready
- [ ] **Disrupt does not argue** — agrees, reframes, or calls the bluff; does not explain why the prospect is wrong
- [ ] **"I understand" is absent** — not in the Anchor, not in the Disrupt, not anywhere in the script
- [ ] **Ask is specific and assumptive** — day/time or concrete request; no hedging or passive phrasing

If any check fails, revise the failing element before writing output.

---

### Write Output

Write the complete turnaround to `rbo-turnaround-script.md` in the working directory. Include:

1. **Classification** — pushback type + one-sentence rationale
2. **Primary turnaround** — Anchor, Disrupt, and Ask labeled separately, assembled into a read-aloud script
3. **Fallback script** — a second lighter Anchor-Disrupt-Ask for the most likely second pushback
4. **Dead-horse checkpoint** — explicit note on when to exit and the graceful exit line
5. **Anti-pattern notes** — any phrases avoided and why

## Inputs

| Input | Required | Source |
|---|---|---|
| Verbatim prospect pushback | Yes | User pastes or describes |
| Call objective | Yes | User states or from `prospecting-objective-plan-{date}.md` |
| Channel (phone / in-person / email / social) | Yes | User states |
| What you said before the pushback | Recommended | User describes |
| Prior contact history | Recommended | User states |

## Outputs

| Output | Location | Description |
|---|---|---|
| `rbo-turnaround-script.md` | Working directory | Classification + primary Anchor-Disrupt-Ask + fallback + dead-horse checkpoint |
| Anti-pattern notes | Inline in conversation | What was avoided and why |

## Key Principles

**1. Classify before responding.** A reflex response, a brush-off, and a genuine objection each
requires a different intervention. Treating them identically means you will argue with a habit,
accept a fake promise, or dismiss real information. Classification takes two seconds and changes
everything. (Blount, Ch. 16, pp. 199–202)

**2. The Anchor is neurological, not tactical.** You are not agreeing with the prospect to be
clever. You are giving your own amygdala a millisecond to stand down so your neocortex can
run the call. Without the Anchor, fight-or-flight produces stumbling, over-explaining, and
defensive tone — all of which telegraph weakness and generate more resistance. (Blount, Ch. 16, p. 205)

**3. Disrupt, do not defeat.** The universal law: you cannot argue another person into believing
they are wrong. Pushing creates counter-pressure. Disrupting creates a gap in the expected
pattern — and in that gap, curiosity and movement become possible. Verbal judo: the gentle,
yielding way wins without combat. (Blount, Ch. 16, pp. 203–205)

**4. Never say "I understand."** It signals insincerity. Every prospect has heard "I understand"
from a salesperson who immediately launched into a pitch about why they are wrong. The phrase
has been conditioned into meaninglessness. Avoid it entirely. Use the Anchor instead — it does
the same emotional work without the baggage. (Blount, Ch. 16, p. 206)

**5. The 2-RBO rule protects the relationship.** Two attempts is professional persistence.
Three attempts is harassment. After two failed turnarounds, disengage gracefully, log accurately,
and prospect again on a future date. Prospects do not remember the call the way you do — what
feels like a permanent failure is usually a bad timing issue that a future call can reset.
(Blount, Ch. 16, pp. 206–210)

**6. Scripts must be rehearsed until they sound natural.** A turnaround read robotically
from memory is worse than no turnaround at all. Politicians read teleprompters fluently because
they rehearse until the words become their own. Practice the Anchor and Disrupt aloud, with a
recorder or a role-play partner, until they flow without hesitation. The script is the raw
material; rehearsal turns it into a weapon. (Blount, Ch. 16, p. 202)

## Examples

---

### Example 1 — "I'm busy" (Reflex Response)

**Prospect says:** "Look, I'm busy."

**Classification:** Reflex Response. The prospect is running an automatic script. This response
fires before their logical brain evaluates the call. "Busy" may be literally true, but the
response is not a considered decision — it is a habit. Do not argue that you won't take long.
That confirms their expectation of a fight.

**Primary Turnaround:**

| Element | Script |
|---|---|
| Anchor | "That's exactly why I called." |
| Disrupt | "I figured you would be — I want to find a time that's actually convenient for you, not interrupt you right now." |
| Ask | "How about we set something for Thursday at 3:00 PM instead?" |

**Read-aloud (no pause between elements):**
> "That's exactly why I called. I figured you would be — I want to find a time that's actually
> convenient for you, not interrupt you right now. How about Thursday at 3:00 PM?"

**Fallback (if they push back again):**
> "Absolutely. I won't keep you. Can I just get two minutes on Thursday to introduce myself — if
> it's not relevant, I'll let you go immediately. How about 3:00 PM?"

**Dead-horse checkpoint:** If after two attempts they say "No, really, I'm not interested in
anything right now" with finality — disengage. "No problem at all. I'll reach back out when the
timing is better. Have a great rest of your day."

---

### Example 2 — "We're not interested" (Reflex Response — stronger flavor)

**Prospect says:** "We're not interested."

**Classification:** Reflex Response. The stronger version of the same automatic script. This fires
before any evaluation of what is being offered. The prospect is not saying they have evaluated
your proposition — they are saying "I don't want a conversation with a salesperson right now."

**Primary Turnaround:**

| Element | Script |
|---|---|
| Anchor | "You know, that's what a lot of my current clients said the first time I called." |
| Disrupt | "Most people aren't interested before they see how much I can help them. I don't know if what I do is relevant to your situation — but doesn't it make sense to spend 15 minutes to find out?" |
| Ask | "How about Friday at 2:00 PM?" |

**Read-aloud:**
> "You know, that's what a lot of my current clients said the first time I called. Most people
> aren't interested before they see how much I can help them. I don't know if what I do is
> relevant to your situation — but doesn't it make sense to spend 15 minutes to find out?
> How about Friday at 2:00 PM?"

**Fallback (if second RBO):**
> "I completely understand. What if we kept it to a 10-minute call — just enough so you can tell
> me it's not a fit? How does Thursday morning look?"

---

### Example 3 — "We're really happy with our current provider" (Reflex Response / Brush-Off)

**Prospect says:** "We're really happy with our current provider."

**Classification:** Reflex Response with Brush-Off characteristics. The "we're happy" script is
among the most common automatic responses in business-to-business prospecting. The prospect is
not reporting a result of comparing you to their current provider — they are signaling they want
to end the conversation without conflict.

**Primary Turnaround:**

| Element | Script |
|---|---|
| Anchor | "That's fantastic!" |
| Disrupt | "Anytime you're getting great rates and great service, you should never think about changing. All I want to do is come by and get to know you a little better — and even if it doesn't make sense to do business with me right now, I can at least give you a competitive benchmark that will help keep your current provider honest." |
| Ask | "How about I stop by on Tuesday at 11:30 AM?" |

**Read-aloud:**
> "That's fantastic! Anytime you're getting great rates and great service, you should never
> think about changing. All I want to do is come by and get to know you a little better — and
> even if it doesn't make sense to do business with me right now, I can at least give you a
> competitive benchmark that will help keep your current provider honest. How about I stop by
> on Tuesday at 11:30 AM?"

**Fallback (if they push back again):**
> "Fair enough. I'll check back in with you at renewal time — when does your current contract
> come up? I'd like to make sure you have options when the time is right."

**Dead-horse checkpoint:** After two clean attempts, if they indicate no appetite for any contact,
log the renewal date if revealed, note "happy with provider — recontact at renewal," and say
NEXT.

---

## References

The full RBO library (20+ common objections with Anchor-Disrupt-Ask templates organized by type)
is in `references/rbo-turnaround-library.md`. Use that file to build a complete script library
before a call block.

Additional supporting material:
- `references/rbo-classification-guide.md` — extended classification examples and edge cases
  (how to handle ambiguous pushbacks, gatekeeper-adjacent RBOs, hybrid type responses)
- `references/dead-horse-protocol.md` — when to disengage, how to log, and how to re-approach
  the same prospect in a future cycle without poisoning the relationship

**Source chapter:** Blount, Jeb. *Fanatical Prospecting*, Chapter 16 "Turning Around RBOs:
Reflex Responses, Brush-Offs, and Objections" (PDF pp. 196–210). Three-type RBO taxonomy:
pp. 199–202. Anchor-Disrupt-Ask framework: pp. 204–206. Three annotated example scripts:
pp. 207–208. Dead-horse principle: pp. 208–210.

**Referenced frameworks:**
- Brown, Brené. *The Power of Vulnerability* — uncertainty and emotional exposure as the root
  of sales vulnerability (cited in Blount, Ch. 16, p. 196)
- Godin, Seth — prospects lie because salespeople have trained them to; honest responses are
  punished with argument (cited in Blount, Ch. 16, p. 200)
- Judo metaphor: "gentle or yielding way" — achieving objective without combat (Blount, Ch. 16,
  p. 204)

## License

Content derived from *Fanatical Prospecting* by Jeb Blount (Wiley, 2015). This skill is licensed
under [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)](https://creativecommons.org/licenses/by-sa/4.0/).
You are free to share and adapt this material provided you give appropriate credit to Jeb Blount
and BookForge, and distribute any derivative works under the same license.

## Related BookForge Skills

This skill handles pushback that occurs after the opener is delivered. Build the opener first:

```
clawhub install bookforge-cold-call-opener-builder
```

Build the message nucleus that powers the opener:

```
clawhub install bookforge-prospecting-message-crafter
```

Browse the full Fanatical Prospecting skill set:
[bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

---
name: prospecting-message-crafter
description: |
  Craft or repair a prospecting message for any channel using the WIIFM → Bridge → Because → Ask framework from Blount's Fanatical Prospecting.

  Trigger this skill when you need to:
  - Write a cold call opener, cold email, LinkedIn message, or text prospecting message
  - Figure out "what should I say" to a prospect on any outbound channel
  - Build a bridge or reason ("because") that gives a prospect a compelling reason to meet
  - Diagnose why a current script or email is getting rejected and fix it
  - Answer "what's my value prop for this call?" or "how do I frame WIIFM?"
  - Check a draft for pitch vomit, cheesy openers, weak asks, or "I'd love to" language
  - Understand the difference between Targeted and Strategic bridge types and choose the right one
  - Write a Power Statement that answers "why should they choose me over the competition?"
  - Craft a message that leads with emotional value, insight/curiosity value, or tangible/logic value
  - Stop getting hit with "not interested" the second you open your mouth
  - Improve connect-to-conversation or email reply rates across any outbound channel

  NOT for: turning around an objection or brush-off after the opener (use prospecting-rbo-turnaround),
  building a full 5-step phone call script (use cold-call-opener-builder), or writing a multi-touch
  email cadence (use prospecting-email-writer). This skill produces the core message nucleus that
  all channel skills inherit — the bridge and because that make the prospect say yes.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/fanatical-prospecting/skills/prospecting-message-crafter
metadata:
  openclaw:
    emoji: "📨"
    homepage: "https://github.com/bookforge-ai/bookforge-skills"
status: published
source-books:
  - id: fanatical-prospecting
    title: "Fanatical Prospecting"
    authors:
      - Jeb Blount
    chapters:
      - 14
tags:
  - sales
  - prospecting
  - messaging
  - copywriting
  - outbound
  - sdr
  - bdr
depends-on: []
execution:
  tier: 2
  mode: hybrid
  inputs:
    - type: document
      description: "User's current script, email draft, or message copy (paste inline or provide as .md/.txt file), plus their ICP description, value proposition, and target prospect situation. If no draft exists yet, the skill builds from scratch with gathered context."
  tools-required: [Read, Write, Grep]
  tools-optional: []
  mcps-required: []
  environment: "Markdown or text file directory with user's prospecting materials (call-script.md, email-sequence.md, value-prop.md, icp.md). Agent reads user-provided files, analyzes the draft, and writes an improved message to prospecting-message-output.md."
discovery:
  goal: "Produce a refined prospecting message with explicit WIIFM → Bridge → Because → Ask structure that passes the 'So what?' test and contains zero anti-patterns"
  tasks:
    - "Gather the user's situation: target prospect role/industry, product value prop, bridge type needed (Targeted vs Strategic), desired outcome (appointment / info / close)"
    - "Diagnose current draft (if provided) against anti-pattern checklist"
    - "Select value category: emotional, insight/curiosity, or tangible/logic"
    - "Build or refine the bridge using the prospect empathy checklist"
    - "Apply the 'So what?' test before finalizing"
    - "Produce the revised message with element labels and a brief rationale"
    - "Write output to prospecting-message-output.md"
  audience:
    roles: [sdr, bdr, ae, founder-self-seller]
    experience: beginner
  when_to_use:
    triggers:
      - "Writing a cold call opener for the first time"
      - "Cold email reply rate is under 3% and you want to diagnose why"
      - "Someone asks 'what should I say?' or 'what's my bridge?' for a target segment"
      - "A current script is generating too many 'not interested' RBOs in the first 5 seconds"
      - "Preparing to target a new ICP vertical or decision-maker role"
      - "A C-level prospect requires a researched Strategic bridge"
      - "Wanting to add emotional or curiosity hooks instead of feature dumps"
    prerequisites: []
    not_for:
      - "Turning around a reflex response or brush-off after the opener has been delivered (use prospecting-rbo-turnaround)"
      - "Building the full 5-step phone framework including pauses and silence (use cold-call-opener-builder)"
      - "Multi-touch email cadence sequencing (use prospecting-email-writer)"
      - "Diagnosing pipeline math or activity ratios (use pipeline-health-diagnostic)"
  environment:
    codebase_required: false
    codebase_helpful: false
    works_offline: true
  quality:
    scores:
      with_skill: 0
      baseline: 0
      delta: 0
    tested_at: ""
    eval_count: 0
    assertion_count: 0
    iterations_needed: 0
    what_skill_catches:
      - "Uses WIIFM-Bridge-Because structure, not just any value proposition"
      - "Distinguishes Targeted bridges (inferred, high-volume) from Strategic bridges (researched, conquest/C-level)"
      - "Detects and removes 'How are you today?' opener with pause — the #1 call-killer"
      - "Detects and removes 'I'd love to / I want to tell you about' self-centered framing"
      - "Detects pitch vomit: feature lists, company bragging, data dumps with no prospect relevance"
      - "Applies Langer's because principle: giving any reason is more powerful than giving none"
      - "Applies the 3-category value framework: emotional / insight-curiosity / tangible-logic"
      - "Applies the 18-question prospect empathy checklist to surface emotional triggers"
      - "Forces a 'So what?' test before finalizing — kills weak bridges before they hit a prospect"
      - "Writes an assumptive ask, not a passive hedge ('How about Thursday at 2?' vs 'Would it be okay if maybe we met?')"
    what_baseline_misses:
      - "Produces generic value propositions without bridging to the prospect's emotional world"
      - "Does not distinguish Targeted from Strategic bridge types"
      - "Includes 'How are you today?' pause — triggering the prospect's escape instinct"
      - "Uses self-centered framing ('I'd love to / I want to show you / we are the best')"
      - "Does not run the 'So what?' test — leaves weak bridges in the message"
      - "Does not know the Langer copy-machine study or why 'because' works even with weak reasons"
      - "Produces a passive ask ('What do you think?' vs 'How about Thursday at 2?')"
---

# Prospecting Message Crafter

## When to Use

You are about to call, email, message on LinkedIn, or text a prospect and you need to answer the hardest question in outbound sales: *What do I say?*

This skill applies to any outbound prospecting channel — phone, email, LinkedIn, text, or in-person — because every channel shares the same message nucleus: **WIIFM → Bridge → Because → Ask**.

Use this skill when:
- Writing your first cold call opener for a new prospect segment
- Your current script is getting too many "not interested" responses in the first 5 seconds
- You need a bridge for a C-level or conquest account that requires research
- An email is going out to a high-value prospect and you want to be sure it passes the "So what?" test
- You want to move from feature dumping to emotional/curiosity framing

**This skill is the hub.** The phone, email, and social channel skills inherit the bridge and because patterns produced here. Build the message nucleus first; then deploy it through the channel skill.

## Context & Input Gathering

Before building the message, gather (or ask the user for) the following:

**Required:**
1. Target prospect's role and industry (e.g., "VP of Sales at a 200-person SaaS company")
2. Your product/service and its strongest outcome (e.g., "cuts new-rep ramp time by 50%")
3. Channel you are targeting (phone / email / LinkedIn / text / in-person)
4. Desired outcome of this touch (appointment / qualifying information / direct sale)

**Recommended:**
5. Current draft of the script or email (paste inline or point to file path)
6. Any known trigger event at this account (hiring surge, funding, competitor churn, etc.)
7. Bridge type: Targeted (large pool, similar prospects, inferred pain) or Strategic (conquest, C-level, limited-access — requires research)?

**If no current draft exists:** proceed directly to Step 3 (Bridge Selection).

## Process

### Step 1 — Diagnose the Current Draft (if one exists)

Read the user's existing message and flag every anti-pattern from the checklist below. Mark each finding with its failure type so the user can see exactly what was broken.

**Anti-pattern checklist:**
- [ ] "How are you today?" opener followed by a pause — this hands control of the call to the prospect's escape instinct. The moment they realize you are a salesperson, they object. (Blount, p. 185)
- [ ] "I'd love to / I want to tell you about / I want to show you" — self-centered framing. The prospect subconsciously hears: "I want to waste your time talking about me." (Blount, p. 151)
- [ ] Pitch vomit — feature/benefit monologue, company bragging ("we're the #1 provider of..."), marketing data dumps unrelated to the prospect's world (Blount, pp. 151-152)
- [ ] No "because" — asking for time without giving a reason. Langer's copy-machine study: giving *any* reason increases yes rate from 60% to 93-94%. No because = lowest possible close rate. (Blount, p. 158-159)
- [ ] Passive ask — "What do you think?", "Would it be okay if...", "Is this a good time?" These signal low confidence and produce 30% success vs. 70% for assertive asks. (Blount, p. 166)
- [ ] "So what?" failure — the bridge is about your company's capabilities, not the prospect's situation. The prospect's internal response is "so what?" and they disengage.

**Why diagnose first:** Reps improve faster when they can see the exact line that triggers rejection. Label each failure so the user understands the root cause, not just the rewrite.

### Step 2 — Identify the Bridge Type

Decide which bridge type fits the situation. This is a risk/reward tradeoff:

**Targeted Bridge** — appropriate when:
- You have a large pool of similar prospects (50+ with similar roles/industries)
- Doing deep research on each one is not time-efficient
- You can infer a high-probability pain from industry trends, competitor behavior, or common decision-maker anxieties

*Process:* Infer the pain. Use the empathy checklist in Step 3 to surface emotional language. Iterate as you hear real responses in the field.

**Strategic Bridge** — appropriate when:
- The prospect is a C-level executive, conquest account, or limited-access contact
- You may get only one shot
- The prospect's time is so valuable that a generic bridge will be dismissed

*Process:* Research first. Pull from Google Alerts, LinkedIn profile, company press releases, CRM notes, trade articles. Look for: jargon they use, core values, recent awards/initiatives, trigger events, problems they reference publicly. Then craft a bridge using *their* language. (See `references/strategic-bridge-research-checklist.md`)

**Why distinguish these:** Using a Strategic bridge workflow on a 10,000-SMB database is economically irrational and destroys prospecting velocity. Using a Targeted bridge on a Fortune 100 CRO is lazy and will get you ignored.

### Step 3 — Choose the Value Category

Every effective bridge delivers value in at least one of three categories. Pick the category that fits the prospect's world, or combine two:

**Emotional value** — connects to a painful emotion and offers relief
- Target emotions: stress, worry, anxiety, frustration, anger, insecurity, distrust, fear
- Relief offered: peace of mind, options, lower stress, security, hope
- Use when: the prospect's role is high-stress and problems are emotionally loaded (e.g., a Sales VP whose reps are missing quota, a CISO post-breach)

**Insight/curiosity value** — offers information that gives the prospect competitive leverage
- Trigger: "Your competitors may already have this. Do you?"
- Use when: the prospect cares about maintaining a competitive edge or fears being left behind
- Requires credible third-party data or real client outcomes as proof

**Tangible/logic value** — data, case studies, specific ROI numbers
- Use when: the prospect is in a technical, data-centric, or finance role and makes decisions on evidence
- Requires specific numbers (e.g., "cut ramp time by 50%", "41% improvement over last launch")

**Why categorize:** Pitching logic to an emotionally driven prospect (or pitching anxiety to an analyst who wants numbers) causes the bridge to miss entirely. Match the value category to the role, not to your marketing department's preferred messaging.

### Step 4 — Build the Bridge Using the Empathy Checklist

Stand in the prospect's shoes. Before writing a word, answer these questions from the prospect's perspective for their specific role:

- What causes them stress or anxiety on a daily basis?
- What competitive unknown would worry them if a rival had it and they didn't?
- What failure would put their job or reputation at risk?
- What wastes their time, money, or resources?
- What would give them a meaningful win or relief right now?
- What information would they fear getting into a competitor's hands?

Use emotional language in the bridge: *frustrated, stressed, overwhelmed, concerned, behind, at risk, falling behind, peace of mind, save, protect, gain an edge.*

**Then apply the "So what?" test:** Read your bridge aloud and ask: "If the prospect heard this, would their internal response be 'So what? That's about you, not me'?" If yes, rewrite.

The bridge structure is:
> *[State what you know or have observed about their world] + [because] + [what you can offer that is relevant to their situation]*

**Why empathy first:** People make decisions based on emotion first and justify with logic. Pitching features doesn't work because it asks logical brain to evaluate before emotional brain has said yes. The bridge must land emotionally before the logical value prop adds credibility. (Blount, pp. 162-163)

### Step 5 — Write the Ask (Assumptive, Direct, Specific)

Every prospecting touch must end with a direct ask. There are three steps:
1. Ask assertively — assume you will get yes
2. Shut up — silence gives the prospect room to say yes
3. Be ready for reflex responses, brush-offs, and early objections (RBOs)

**Assumptive ask examples (use these patterns):**
- "How about we meet Thursday at 2:00 PM?" (not: "Would it be okay if we maybe got together sometime?")
- "I'll be near your office Monday. Can you do lunch?" (not: "I have the whole day open, whenever works for you.")
- "Tell me about your process for selecting vendors." (not: "I was wondering if maybe you could share...")

The ask must match the prospecting objective:
- Appointment: "How about Thursday at 2:00 PM?"
- Qualifying info: "Can you tell me more about your situation and when the decision process begins?"
- Direct sale (transactional): "Let's go ahead and get that set up."

**Why an assumptive ask:** Sales teams tracked across thousands of calls show assertive asks produce ~70% yes rates vs. ~30% for non-assertive asks. The ask is the only mechanism that produces an answer; without it, nothing happens. (Blount, p. 166)

### Step 6 — Assemble and Output the Final Message

Assemble the message in WIIFM → Bridge → Because → Ask order. Label each element inline so the user can see the structure and adapt it.

Write the output to `prospecting-message-output.md` in the working directory. Include:
- The revised message (channel-ready)
- Element labels (WIIFM / Bridge / Because / Ask)
- A brief note on which anti-patterns were removed from the original draft
- The value category used (Emotional / Insight-Curiosity / Tangible-Logic)
- Bridge type (Targeted or Strategic)
- The "So what?" test result

## Inputs

| Input | Required | Source |
|---|---|---|
| Target prospect role and industry | Yes | User provides |
| Product/service and key outcome | Yes | User provides or `value-prop.md` |
| Prospecting channel | Yes | User states |
| Desired outcome of the touch | Yes | User states |
| Current draft of the message | No (will build from scratch) | User pastes inline or provides file path |
| Known trigger events at the account | No (enhances Strategic bridges) | User provides or research |
| Bridge type preference | No (skill will recommend) | User states or skill decides |

## Outputs

| Output | Location | Description |
|---|---|---|
| `prospecting-message-output.md` | Working directory | Final message with labeled elements, anti-pattern removal notes, value category, and "So what?" test result |
| Anti-pattern diagnosis | Inline in conversation | Labeled list of what was wrong with the original draft and why |

## Key Principles

**1. Because beats everything.** Langer's copy-machine study: giving *any* reason ("because I have to make copies") raised yes rates from 60% to 93%. The word "because" triggers compliance. You don't need a perfect value prop — you need a direct, simple because. (Blount, p. 158-159)

**2. Prospects give time for their reasons, not yours.** No one cares what you want, what you'd love to do, or what your company claims to be the best at. The only message that works is the one that answers *their* WIIFM — the most pressing question on any busy person's mind. (Blount, p. 155)

**3. Emotion first, logic second.** Decisions are made emotionally and justified with logic. Bridges that connect to anxiety, stress, fear, or competitive insecurity open doors. Feature lists close them. (Blount, pp. 162-163)

**4. Simple and direct beats complex and clever.** Prospecting messages are designed for a single purpose: to quickly persuade the prospect to give you their time. Elaborate scripts overcomplicate and telegraph insecurity. A 10-second because that sounds natural outperforms a two-minute polished pitch. (Blount, p. 158)

**5. The ask determines everything.** Without a direct, assumptive ask the message has no output. Fear of rejection leads reps to hedge, qualify, and meander — which produces silence and kills momentum. Ask, then shut up. (Blount, pp. 165-166)

**6. The bridge has two types for a reason.** Spending 30 minutes researching an SMB from a 10,000-prospect database is wasteful. Sending a generic bridge to a Fortune 100 CFO is disrespectful. Match research depth to prospect value and access difficulty. (Blount, pp. 159-161)

## Examples

---

### Example 1 — Repairing a Failing Cold Call Opener (SDR / SaaS / VP Sales Target)

**Situation:** SDR at a sales enablement platform targeting VP of Sales at 100-500 person SaaS companies. Current message getting too many "not interested" in the first three seconds.

**Current failing message:**
> "Hi Mark, this is Sarah from TechStack Pro. How are you doing today? [pause] I wanted to reach out because we have an amazing new platform that helps sales teams with onboarding and enablement. We've worked with some of the biggest companies in the space and I'd love to get 30 minutes on your calendar to show you everything we can do."

**Trigger:** "How are you doing today?" + pause — hands control to the prospect's escape mechanism. "I'd love to" + feature dump — self-centered, no bridge to prospect's world. Passive ask — "get 30 minutes... to show you" signals pitch not value.

**Process:**
- Bridge type: Targeted (large pool of similar VP Sales targets, inferred pain)
- Value category: Emotional (VP Sales anxiety = new reps not producing fast enough)
- Empathy check: VP Sales is stressed when new reps miss quota for the first 90 days; fears losing good hires because onboarding is disorganized
- "So what?" test: "We have an amazing platform" → So what? Fails. Rewrite around their stress.

**Output:**
> "Hi Mark, this is Sarah with TechStack. The reason I'm calling is I work with several SaaS VP Sales teams who are frustrated that new reps take 4-6 months to hit quota — and by the time they ramp, half of them are already questioning their decision to join. We've helped companies like [similar company] cut that ramp time by over 50 percent. I don't know if it's a fit in your situation, but I'd like to find out. How about 15 minutes on Thursday at 2 PM?"

| Element | Content |
|---|---|
| WIIFM bridge | New rep ramp anxiety (emotional value — their stress, not your product) |
| Because | Specific outcome (50% ramp reduction) + social proof (similar companies) |
| Ask | Specific day/time, low-risk framing ("I don't know if it's a fit") |
| Anti-patterns removed | "How are you today?", pause, "I'd love to", feature dump |

---

### Example 2 — Building a Strategic Bridge for a C-Level Prospect (AE / Enterprise / CFO Target)

**Situation:** Enterprise AE targeting the CFO at a 1,200-person manufacturing company. LinkedIn shows they recently announced a plant expansion and are hiring aggressively. No prior contact.

**Trigger:** High-value conquest prospect, C-level, limited access — Strategic bridge required.

**Process:**
- Research: press release mentions 200 new hires across 3 facilities; LinkedIn shows CFO posted about "scaling without losing cost discipline"
- Bridge type: Strategic — use their language ("cost discipline"), reference the trigger event (expansion)
- Value category: Tangible/logic + Emotional (CFO will need evidence AND anxiety hook around cost control during growth)
- Empathy check: CFO fears that aggressive hiring creates runaway overhead and reduces EBITDA

**Output:**
> "Hi David, this is Alex from WorkForce Analytics. The reason I'm calling is I read about your expansion to three new facilities and the 200 hires you're bringing on. I imagine keeping cost discipline during that kind of growth is a real challenge — especially when onboarding overhead scales faster than productivity. I've helped CFOs at similar manufacturers maintain a tight cost-per-hire-to-productivity ratio during expansion phases. While I don't know if we'd be a fit, I have some benchmarks from your industry I thought might be useful. How about a short call Thursday at 10 AM to see if it's worth exploring?"

| Element | Content |
|---|---|
| WIIFM bridge | Uses their language ("cost discipline"), references trigger event (expansion) |
| Because | Industry benchmarks = insight/curiosity value; cost-per-hire risk = emotional |
| Ask | Specific time, assumptive, low-risk framing |
| Bridge type | Strategic — researched trigger event and their own stated priorities |

---

### Example 3 — Building from Scratch: Targeted Bridge (BDR / IT Security / CISO Target)

**Situation:** BDR at a security awareness training company. No current message. Building a Targeted bridge for the CISO segment.

**Trigger:** "What should I say to CISOs?" with no draft.

**Process:**
- No research per individual (Targeted bridge — large CISO segment)
- Empathy check: CISO anxiety = employees clicking phishing links, regulatory audit failures, board-level exposure
- Value category: Emotional (fear of breach + career exposure)
- "So what?" test: any message about "training modules" or "platform features" fails — rewrite around board-level fear

**Output:**
> "Hi Jennifer, this is Ryan with SecureForce. The reason I'm calling is most CISOs I work with tell me that phishing training is their biggest headache — not because they don't have a program, but because click rates aren't improving and the board is asking questions. We've worked with teams in your industry to cut employee click rates by over 60 percent in 90 days. I'm not sure if it's relevant to your situation, but I'd like to find out. How about 20 minutes next Tuesday at 3 PM?"

## References

Detailed supporting materials are in the `references/` folder:

- `references/bridge-types-and-templates.md` — full worked examples of Targeted vs Strategic bridges by industry and decision-maker role; template library with fill-in slots
- `references/strategic-bridge-research-checklist.md` — the full 18-question empathy checklist plus research sources (Google Alerts, LinkedIn, CRM, press, trade publications) with worked examples
- `references/value-category-examples.md` — emotional, insight/curiosity, and tangible/logic value examples by role (CISO, VP Sales, CFO, COO, CTO, Ops Director, Small Business Owner)
- `references/anti-pattern-library.md` — full examples of each anti-pattern with before/after rewrites and the psychological mechanism that makes each one fail

**Source chapter:** Blount, Jeb. *Fanatical Prospecting*, Chapter 14 "Message Matters" (pp. 132-153 / PDF pp. 150-171). Calibration references: Chapter 15 "Telephone Prospecting Excellence" (pp. 165-170 / PDF pp. 183-187); Chapter 19 "E-Mail Prospecting" (PDF pp. 239-243).

**Referenced frameworks:**
- Langer, E.J. (1978). Copy-machine compliance study — the "because" effect (cited in Blount, p. 158)
- Konrath, Jill. *SNAP Selling* — three-part value proposition: measurable objective, status quo disruption, proof (cited in Blount, p. 156)
- Weinberg, Mike. *New Sales. Simplified.* — Power Statement: prospect issues + offerings + competitive differentiators (cited in Blount, p. 157)

## License

Content derived from *Fanatical Prospecting* by Jeb Blount (Wiley, 2015). This skill is licensed under [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)](https://creativecommons.org/licenses/by-sa/4.0/). You are free to share and adapt this material provided you give appropriate credit to Jeb Blount and BookForge, and distribute any derivative works under the same license.

## Related BookForge Skills

This is the **hub skill** for the Fanatical Prospecting message framework. Six channel skills depend on the bridge and because patterns produced here:

- `cold-call-opener-builder` — deploys this message in Blount's 5-step telephone framework (attention → identify → reason → bridge → ask)
- `prospecting-email-writer` — wraps this message in the AMMO plan + Hook-Relate-Bridge-Ask email structure
- `prospecting-rbo-turnaround` — handles reflex responses and brush-offs after the opener has been delivered
- `in-person-prospecting-route-planner` — applies this message in the 5-step in-person prospecting call process
- `text-prospecting-sequence-builder` — adapts this message for text-based prospecting protocols
- `prospecting-objective-setter` — defines the correct ask (Step 5) by mapping product type and prospect qualification to the right prospecting objective

**Build this skill's output first. Then pass the bridge and because to the channel skill you need.**

FILE:references/anti-pattern-library.md
# Anti-Pattern Library

Source: Blount, *Fanatical Prospecting*, Chapters 14-15 (PDF pp. 150-171, 183-187)

Each pattern below is a documented failure mode with the exact failure mechanism, the detection language, and a before/after rewrite.

---

## AP-1: The "How Are You Today?" Pause

**Failure mechanism:**
The prospect picks up the phone in the middle of their day. In the split second after they say hello, they are curious but not yet in escape mode. The moment you say "How are you today?" and pause, their brain completes the pattern: *salesperson*. The prospect's escape instinct activates. You have handed control of the call to their fight-or-flight mechanism.

Blount (p. 185): "As soon as you said 'How are you doing?' — then you paused — your prospect's instinct to get off the phone and back to whatever they were doing kicks in. They immediately hit you with a reflex response like 'I'm not interested'... That's how you lose control of the call."

**Detection language:** Any variant of:
- "How are you today?"
- "Is this a good time?"
- "Did I catch you at a bad time?"
- Any opener followed by a pause before you identify yourself

**Rule:** Say their name to get attention, identify yourself immediately, and keep moving. No pause until after the ask.

**Before:**
> "Hi Mark, this is Sarah from TechStack Pro. How are you doing today? [pause]"

**After:**
> "Hi Mark, this is Sarah with TechStack. The reason I'm calling is..."

---

## AP-2: Self-Centered Framing ("I'd love to / I want to tell you about")

**Failure mechanism:**
The subconscious message of "I'd love to have a few minutes of your time to tell you about my company" is: "I want to come to your office and waste an hour of your life talking all about me, my products, and my wants." The prospect's internal response is disgust followed by a brush-off.

Blount (p. 151): "Messages like this add no value and generate instant resistance because subconsciously the prospect hears: 'I would love to come by your office and waste an hour of your life talking all about me, my products, and my wants.'"

**Detection language:**
- "I'd love to..."
- "I want to tell you about..."
- "I want to show you..."
- "I want to talk to you about my product..."
- Any sentence where the subject is "I" and the object is something you want

**Rule:** Every sentence in the bridge must be about the prospect's world, not your desires.

**Before:**
> "I'd love to get 30 minutes on your calendar to show you everything our platform can do."

**After:**
> "I've helped [similar companies] cut ramp time by 50% and I thought it might be relevant to your situation. How about 15 minutes Thursday at 2?"

---

## AP-3: Pitch Vomit (Feature Dump / Company Bragging)

**Failure mechanism:**
Features are logical arguments. Prospects make decisions emotionally. A product feature dump asks the logical brain to evaluate before the emotional brain has said yes — which means the logical brain has nothing to say yes about. Worse, company bragging ("we're the #1 provider of...") puts the prospect in the role of audience for your marketing presentation.

Blount (pp. 151-152): Prospects will not give up their time for "a product and service features dump," "an enthusiastic pitch about their company being 'number one this' or the 'biggest of that'," or "regurgitated lists of generic facts and figures."

**Detection language:**
- Lists of product features in the opening message
- "We are the leading provider of..."
- "Our platform offers [Feature A], [Feature B], and [Feature C]..."
- "We've been in business for X years and work with Y customers..."
- Any pitch that would make sense if you replaced the prospect's name with any other name

**Rule:** If a competitor could send the exact same message with their company name swapped in, your bridge has failed.

**Before:**
> "Our platform includes AI-powered call recording, real-time coaching, CRM integration, and advanced analytics for your entire sales team."

**After:**
> "Most sales managers I work with are frustrated because they have no visibility into why their reps are struggling on calls until it's too late to coach. We've helped teams like yours identify coachable patterns in call data and improve close rates by [X%]."

---

## AP-4: No "Because" — Asking Without a Reason

**Failure mechanism:**
Langer's copy-machine study (1978): When asked to jump in line without a reason, 60% compliance. With any reason ("because I'm in a hurry"), 94% compliance. With a nonsensical reason ("because I have to make copies"), 93% compliance. The word "because" triggers a compliance reflex. Asking for time without a reason leaves 34+ percentage points of yes on the table.

Blount (p. 158-159): "What we learn from Langer's copy machine study is when we ask people to do something for us, like give up their time, they are more likely to do so when we give them a reason."

**Detection language:**
- "...and I was hoping we could get together."
- No "because" or "the reason I'm calling is" anywhere in the message
- A request for time with no antecedent cause

**Before:**
> "Hi Mark, this is Sarah. I'm reaching out about our sales enablement platform and was hoping to set up a call."

**After:**
> "Hi Mark, this is Sarah. The reason I'm calling is [specific because tied to their world]."

---

## AP-5: The Passive, Non-Assumptive Ask

**Failure mechanism:**
Fear of rejection leads reps to hedge and qualify the ask into passivity. Passive asks signal low confidence — which causes the prospect to lose trust and downgrade willingness to commit. Blount's tracked data: assertive asks produce ~70% yes rate; non-assertive asks produce ~30%.

Blount (p. 166): "When salespeople demonstrate confidence and ask assertively for what they want, prospects say yes about 70 percent of the time. Nonassertive requests have about a 30 percent success rate."

**Detection language:**
- "What do you think?"
- "Would it be okay if maybe we got together?"
- "Is there a time that might work for you sometime?"
- "I was wondering if maybe you'd have some availability..."
- "I have the whole day open, whenever works best for you"

**Rule:** Name a specific day and time. Use assumptive language. Follow with silence.

**Weak vs. Strong Ask Pairs (from Blount, p. 166-167):**

| Weak / Passive | Assertive / Assumptive |
|---|---|
| "Is this a good time?" | "The reason I'm calling is..." |
| "I was wondering if..." | "Tell me who / how / when / what..." |
| "I have the whole day open." | "I'm bringing on new clients but have a slot at 11 AM." |
| "What do you think?" | "Why don't we go ahead and set that up?" |
| "What's the best time for you?" | "I'll be near your office Monday. Can you do lunch?" |
| "Would this be a good time?" | "How about we meet at 2:00 PM?" |

---

## AP-6: Silence-Filling After the Ask (Post-Ask Pitch Vomit)

**Failure mechanism:**
The moment after asking, fear of rejection floods the brain. The amygdala misinterprets the silence as a threat. The rep's mouth starts moving to protect against the anticipated "no." This results in overexplaining, offering the prospect a way out, or pitching features until the prospect who was about to say yes gets talked into saying no.

Blount (p. 170): "Your mouth starts moving. You attempt to overcome objections that have not even surfaced, overexplain yourself, offer your prospect a way out, and start blabbing on and on about your product's features and benefits, your company, your dog, and where you went to school. Until the prospect who was ready to say yes gets talked into saying no by you."

**Rule:** Ask. Stop. Wait.

The rule of thirds: ~1/3 of prospects say yes right away. ~1/3 say a firm no. ~1/3 give a maybe (RBO). Your job after asking is to be silent long enough for the prospect to fall into one of these three buckets. Only the third bucket requires active response (see `prospecting-rbo-turnaround`).

FILE:references/bridge-types-and-templates.md
# Bridge Types and Templates

Source: Blount, *Fanatical Prospecting*, Chapter 14 (pp. 141-145 / PDF pp. 159-162)

---

## The Two Bridge Types

### Targeted Bridge

**When to use:**
- Large prospect pool (50+ similar contacts)
- Similar decision-maker roles or industry vertical
- Inferred pain is high-probability based on industry trends or competitor intelligence
- Per-prospect research cost outweighs the marginal benefit

**How it works:**
You don't know this specific prospect's pain with certainty. You infer it from what you know about other buyers in similar situations. Your goal is a message that works most of the time with most of your prospects — one that can be delivered in 10 seconds or less and gives a reason (a "because") that is good enough to get a yes.

As you have more conversations, you iterate and refine the message based on what resonates and what generates RBOs.

**Blount's own example (pp. 160-161):**
> "Hi, Candace, this is Jeb Blount from Sales Gravy. The reason I am calling is to schedule an appointment with you to show you our new sales onboarding automation software. Many of my clients are frustrated because it takes too long to get new salespeople ramped up to full productivity and find that it's holding their business growth back. Our software typically cuts onboarding time and costs for new sales reps by 50 percent, and makes it super easy to manage new rep onboarding, giving you the peace of mind that your new hires will start selling fast. I have 2:00 PM on Thursday open. How about we get together for a short meeting so I can learn more about you and see whether it makes sense to schedule a demo?"

**What makes this work:**
- "Many of my clients are frustrated because..." — inferred pain, stated as observed trend not accusation
- Emotional language: "frustrated", "peace of mind", "start selling fast"
- Specific outcome: 50% reduction (tangible logic reinforcing emotional hook)
- Assumptive ask with specific time slot

---

### Strategic Bridge

**When to use:**
- Conquest accounts, C-level executives, limited-access contacts
- You may get only one shot
- The prospect's time is so valuable that a generic, inferred bridge will be dismissed
- High-value deal where research ROI is positive

**How it works:**
Research the individual before you reach out. Use their own language, reference their specific situation, and connect your bridge to a trigger event, initiative, or problem they have publicly acknowledged. This demonstrates that you understand their world — not just their role.

**Blount's own example (pp. 161-162):**
> "Hi, Windsor, this is Jeb Blount from Sales Gravy. The reason I am calling is to set an appointment with you. I read in Fast Company that you are adding another hundred sales reps to keep up with growth. I imagine that it has got to be a bit stressful to bring on that many reps and get them producing. I've worked with a number of companies in your industry to reduce ramp-up time for new reps. At Xjam Software, for example, we cut ramp-up time to ROI for their new reps by 50 percent. While I don't know if our solution would be a fit in your unique situation, I've got some ideas and best practices I've seen work well for companies like yours and thought you might be interested in learning more about them. How about we get together for a short meeting on Thursday at 2:00 PM?"

**What makes this work:**
- References a specific article ("I read in Fast Company that...") — demonstrates research
- Uses emotional empathy: "I imagine it has got to be a bit stressful..."
- Social proof: specific company name + specific outcome (50% at Xjam)
- Low-risk framing: "I don't know if our solution would be a fit in your unique situation"
- Assumptive ask with specific time

---

## Fill-in Templates by Bridge Type

### Targeted Bridge Template

> "Hi [Name], this is [Your Name] with [Company]. The reason I'm calling is [many of my clients in your industry / several [role] I work with] are [emotional word — frustrated / stressed / concerned] because [inferred problem that is high-probability for this role]. We've helped [similar companies / teams like yours] [specific outcome — reduce X, cut Y, improve Z]. I don't know if it's relevant in your situation, but I'd like to find out. How about [specific day] at [specific time]?"

### Strategic Bridge Template

> "Hi [Name], this is [Your Name] with [Company]. The reason I'm calling is [I saw / I read in [source]] that [specific trigger event at their company or in their world]. I imagine [emotional empathy statement — it has got to be challenging / stressful / exciting and complex] to [specific implication of the trigger]. I've worked with [company or role in similar situation] to [specific outcome — reduce X, improve Y by Z%]. While I'm not sure we'd be a fit for your unique situation, I thought [specific insight or best practice] might be worth a quick conversation. How about [specific day] at [specific time]?"

---

## Bridge Templates by Decision-Maker Role

### VP of Sales / CRO (Targeted)
Pain profile: new rep ramp time, quota attainment, rep attrition, call reluctance, pipeline coverage

> "...many VP Sales I work with are stressed because their new reps are taking 4-6 months to hit quota and by the time they ramp, some of the best ones are already questioning whether they made the right move. We've helped sales teams like yours cut ramp time by [X%]..."

### CFO (Strategic — requires research)
Pain profile: cost control during growth, EBITDA pressure, audit exposure, systems proliferation

> "...I read that you're bringing on [X hires] as part of the expansion. I imagine keeping cost discipline when headcount is scaling that fast puts real pressure on your team. We've worked with CFOs at similar companies to maintain a tight cost-per-hire-to-productivity ratio during growth phases..."

### CISO / VP Information Security (Targeted)
Pain profile: phishing click rates, board-level cyber reporting, regulatory compliance, vendor risk

> "...most CISOs I talk to are concerned because their phishing click rates aren't improving even with a training program in place — and when the board starts asking about it, it becomes a visibility problem as much as a security problem. We've helped security teams cut employee click rates by [X%] in [Y days]..."

### Operations Director (Targeted)
Pain profile: process inefficiency, manual handoffs, scaling without adding headcount, system integration gaps

> "...a lot of Operations Directors I talk to are frustrated because they're being asked to scale throughput without increasing headcount, and the manual handoffs between systems are eating hours every week. We've helped teams like yours reduce manual processing time by [X%]..."

### Small Business Owner (Targeted — low-risk ask works well)
Pain profile: wearing too many hats, cash flow, time, finding reliable vendors

> "...I'm helping several [business type] owners in [city/region] with [category — supply costs / customer acquisition / efficiency]. I thought we could meet so I can spend time learning about your business and see if what we offer might be a fit..."
*(Note: With SMBs, a learn-about-you ask works well because the risk of meeting is low and owners like to talk about their business. — Blount, p. 157)*

FILE:references/strategic-bridge-research-checklist.md
# Strategic Bridge Research Checklist

Source: Blount, *Fanatical Prospecting*, Chapter 14 (pp. 143-146 / PDF pp. 161-164)

Use this checklist when building a Strategic bridge for a conquest account, C-level contact, or limited-access prospect. The goal is to use the prospect's own language and reference their specific situation so the bridge feels personally crafted, not templated.

---

## Research Sources (Check in Order of Efficiency)

1. **CRM notes and call history** — what has already been observed about this account?
2. **LinkedIn profile** — current role tenure, recent posts, language they use, accomplishments they highlight
3. **Company website** — mission/values language, leadership team bios, recent announcements
4. **Press releases and news** — funding rounds, acquisitions, expansions, leadership changes, product launches
5. **Trade publications and industry news** — articles quoting executives at this company
6. **Google Alerts** — set up before reaching out to catch live trigger events
7. **Social media** (Twitter/X, Facebook, company pages) — posts about challenges, initiatives, or wins
8. **LinkedIn company page** — job postings (reveals strategic priorities and pain points), follower comments

---

## 18-Question Prospect Empathy Checklist

Work through these from the prospect's perspective, given their specific role and company situation:

**Stress and anxiety:**
1. What would cause them stress? When do they feel stress?
2. What makes them worry? When and why?
3. What creates anxiety? When do they feel anxious?
4. How do they feel when they run out of time for important things?
5. How do they feel when they don't have enough money or budget to accomplish their goals?
6. How do they feel when they don't have enough resources to accomplish their goals?
7. How do they feel when they don't have the knowledge to accomplish their goals?
8. How do they feel when they fail to accomplish their goals?
9. When do they get overwhelmed, and how does it feel?
10. What impacts their peace of mind or sense of security?
11. How would it feel to have limited options?
12. What is causing them to feel frustrated or stuck?
13. What makes them mad?
14. What causes them to feel distrust?
15. What causes them fear?
16. What causes them anguish?

**Competitive intelligence and curiosity triggers:**
17. What unknown would make them worry? What might a competitor be doing that would make them want to do it too?
18. What information would they fear getting into a competitor's hands? What would give them a winning edge?

---

## What to Look for in Research

When reviewing research materials, scan for:

| Signal | What to do with it |
|---|---|
| **Jargon and vocabulary** they use in posts or quotes | Mirror their language in the bridge — do not substitute your own terminology |
| **Core values** stated in mission/culture language | Reference alignment if genuine — "I noticed that your team emphasizes..." |
| **PR / Awards** — recent recognition or milestones | Acknowledge and connect to adjacent pain — growth award often means hiring challenges |
| **Trigger events** — expansion, funding, acquisition, leadership change, product launch | Name the event directly — shows you did your homework |
| **Initiatives** — digital transformation, cost reduction programs, new market entry | Connect your bridge to the initiative's success conditions |
| **Problems they reference** — public quotes about challenges | Use their exact words in the empathy statement — "I imagine it's been [their word] to..." |

---

## Crafting the Bridge From Research

**Step 1:** Identify the most emotionally loaded trigger event or initiative you found.

**Step 2:** Draft an empathy statement: "I imagine it has got to be [emotional word] to [implication of the trigger]."

**Step 3:** Connect to your outcome: "I've worked with [similar company] to [specific result] — [e.g., 50% reduction in X at Company Y]."

**Step 4:** Apply low-risk framing: "I don't know if we'd be a fit in your unique situation, but..."

**Step 5:** Ask with a specific time: "How about a short call [day] at [time]?"

**Step 6:** "So what?" test — read the full message aloud. If any sentence sounds like it is about your company's capabilities rather than their situation, rewrite it.

---

## Example: CFO at Expanding Manufacturer

**Research findings:**
- LinkedIn: recent post — "Scaling without losing cost discipline is the challenge of every growth phase"
- Press release: 200 new hires planned, 3 new facilities
- Trade article: CFO quoted saying "our biggest risk is overhead scaling faster than revenue"

**Empathy statement built from research:**
> "I saw your announcement about the three new facilities and 200 hires. And I read your quote about overhead scaling faster than revenue — I imagine managing cost discipline during that kind of growth is a daily pressure."

**Note:** The phrase "cost discipline" came from their own LinkedIn post. The phrase "overhead scaling faster than revenue" came from their direct quote. This is their language, not yours.

---
name: prospect-list-tiering
description: Tier and prioritize a prospect list using the six-level Prospecting Pyramid framework — sorting every account from unknown contacts at the base to active buying-window prospects at the tip, then producing a daily action plan that specifies which tier to call first, what to do with each tier, and how to move prospects upward through the pyramid over time. Use this skill when the user has a raw prospect list and wants to know who to call first, asks how to prioritize their accounts, wants to rank or tier their CRM, wants to tier accounts, asks about the prospecting pyramid, needs an account prioritization framework, wants to identify which prospects are in the buying window, is building or cleaning up their CRM list, wants to stop randomly dialing and start with a system, wants qualified prospects separated from cold names, asks who should be top of their daily call list, has a mix of inbound leads and cold accounts and needs an order, wants to set up a conquest account list, or says their prospecting blocks feel unproductive and they need a better structure — even if they do not use the words "pyramid," "tiering," or "prioritization."
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/fanatical-prospecting/skills/prospect-list-tiering
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: published
source-books:
  - id: fanatical-prospecting
    title: "Fanatical Prospecting"
    authors: ["Jeb Blount"]
    chapters: [10, 11]
tags: [sales, prospecting, account-prioritization, crm, pipeline, sdr, bdr]
depends-on: []
execution:
  tier: 2
  mode: hybrid
  inputs:
    - type: document
      description: "Prospect list (CSV or markdown table) plus known qualification data (lead source, company size, buying window status, trigger events) and optionally an Ideal Customer Profile"
  tools-required: [Read, Write, Grep]
  tools-optional: []
  mcps-required: []
  environment: "Directory containing prospect list files (CSV, markdown) and optionally ICP or account notes files"
discovery:
  goal: "Tier a prospect list into six pyramid levels and produce a daily action plan with the correct call order and action directive per tier"
  tasks:
    - "Classify each prospect into one of six pyramid tiers based on qualification state"
    - "Assign the correct action directive to each tier"
    - "Build a daily execution sequence (tip-first, then conquest, then lower tiers)"
    - "Identify which filters to apply when building focused batch lists"
    - "Flag data gaps that prevent accurate tiering and recommend remediation"
  audience:
    roles: [sdr, bdr, ae]
    experience: beginner-to-intermediate
  triggers:
    - "who should I call first"
    - "prioritize my prospect list"
    - "tier my accounts"
    - "prospecting pyramid"
    - "account prioritization"
    - "CRM list cleanup"
    - "qualified prospects"
    - "buying window"
    - "my prospecting blocks feel unproductive"
  prerequisites: []
  not_for:
    - "Evaluating a single prospect in isolation (no list to tier)"
    - "Writing call scripts or email copy (use prospecting-message-crafter)"
    - "Setting a prospecting objective for a specific call (use prospecting-objective-setter)"
    - "Calculating pipeline ratios or quota math"
  environment: "Any agent environment with access to a prospect list file or pasted prospect data"
  quality:
    minimum_tiers_classified: "all prospects assigned to a tier"
    required_outputs: ["tiered-prospect-list", "daily-action-plan"]
    completeness: "every tier must carry its action directive in the output"
---

# Prospect List Tiering

## When to Use

You have a prospect list — whether 20 accounts or 2,000 — and need to stop treating every name identically. Treating every prospect the same is statistically inefficient: only a small fraction of your database is in a buying window at any given moment, so random dialing guarantees most of your energy goes to prospects who cannot buy yet.

This skill applies the six-tier Prospecting Pyramid framework to sort every prospect by qualification state and buying-window proximity, then produces a daily action plan so you always start each prospecting block with the highest-probability prospects.

Typical triggers:
- You have a CRM export and need to decide who to call tomorrow morning
- You have a mix of inbound leads, referrals, and cold accounts and want a ranked order
- Your prospecting blocks feel unfocused or produce mostly dead-end conversations
- You want to identify your conquest accounts and give them dedicated attention
- You are setting up or cleaning your CRM and want a systematic tiering logic

**This skill does NOT cover:**
- Writing call scripts or email sequences (use `prospecting-message-crafter`)
- Setting the right objective for a specific call (use `prospecting-objective-setter`)
- Calculating pipeline ratios or quota math

---

## Context and Input Gathering

### Required Context (must have — ask if missing)

- **Prospect list:** The accounts and contacts to tier. Accepted formats: CSV file, CRM export, markdown table, or pasted text.
  -> Check the working directory for: `prospect-list.csv`, `accounts.csv`, `leads.csv`, any `.csv` file with company or contact columns
  -> If not found, ask: "Can you share your prospect list? A CSV export, pasted markdown table, or even a simple list of company names with any notes you have will work."

- **Known qualification data per prospect:** At minimum, the user should know *something* about each prospect beyond the name. Even partial data (lead source, company size, whether a contract is expiring) enables accurate tiering.
  -> Check prompt for: mentions of "inbound," "referral," "contract expiration," "trade show," "they reached out," "no info," "cold list," company revenue or headcount
  -> If still missing, ask: "For each prospect, what do you know? Even rough notes — things like 'they filled out our form,' 'referred by a client,' 'expiring contract in Q3,' or 'we have no info yet' — help me assign the right tier."

- **Ideal Customer Profile (ICP):** Criteria defining a qualified prospect — industry, revenue range, headcount, decision-maker role, geography, or use-case fit.
  -> Check for: `icp.md`, `icp.txt`, or ICP details in the prompt
  -> If missing: proceed with whatever qualification data exists and note which tiers may need ICP validation before calling

### Observable Context (gather from environment)

- **Account notes files:** Any per-account research documents (trigger events, stakeholder maps, competitor info) that enable more precise tiering
  -> Look for: `account-notes/`, `research/`, individual company markdown files
  -> If found: read and incorporate into tier assignments

- **CRM fields in the prospect list:** Fields like `Lead Source`, `Last Activity`, `Deal Stage`, `Contract Renewal Date`, `Account Size`, `Decision Maker Identified` are direct tier signals

### Default Assumptions

- If qualification data is entirely absent for a prospect: assign Tier 1 (Unknown) and flag the data gap
- If a prospect is a confirmed inbound lead or referral but has no further qualification data: assign Tier 5 (Hot Inbound/Referral) — lead source trumps data completeness
- If ICP fit is unknown: tier by qualification state alone; add an ICP validation note to the action directive

### Sufficiency Threshold

```
SUFFICIENT when:
- Prospect list is available (any format)
- At least some qualification signal exists for each prospect (even "no info" = Tier 1)
- ICP is known OR user confirms they will apply it manually

NOT sufficient:
- No list at all (ask user to provide one before proceeding)
```

---

## Process

### Step 1: Ingest and normalize the prospect list

Read the prospect list file. Parse it into a working table with at minimum: company name, contact name (if available), and any qualification fields present.

**Why:** Normalization reveals which data fields exist across the list and which are missing — this determines how confidently each prospect can be tiered. A list with "Lead Source" and "Contract Renewal Date" fields can be auto-tiered; a list with only company names requires the user's manual input.

For CSV files, check for these high-signal fields:
- `Lead Source` / `Source` (inbound, referral, cold, trade show)
- `Last Activity Date` / `Last Contact`
- `Contract Expiration` / `Renewal Date`
- `Deal Stage` / `Pipeline Stage`
- `Decision Maker Identified` (boolean or name)
- `Budget Confirmed`
- `Account Size` / `Revenue` / `Employees`

### Step 2: Classify each prospect into a pyramid tier

Apply the six-tier framework. The primary sort axis is **qualification state** — how much is known and how close the prospect is to a buying window.

| Tier | Name | Classification Criteria | Action Directive |
|------|------|--------------------------|-----------------|
| **T1** | Unknown | Company name only; contact info unverified or missing; no competitive/budget/stakeholder data | Correct and confirm data; begin qualifying process |
| **T2** | Basic Data Confirmed | Verified contact info including email; some competitive, budget, or demographic data; partial stakeholder map | Identify buying window and all stakeholders |
| **T3** | Buying Window Identified | Complete decision-maker and influencer contact records including social profiles; future buying window known | Implement nurturing campaigns; stay visible until window opens |
| **T4** | Conquest | Top 10-100 highest-value or largest opportunities in territory; strategic priority regardless of immediate buying window | Nurture + regular touches + trigger-event monitoring + stakeholder mapping + familiarity building |
| **T5** | Hot Inbound / Referral | Prospect contacted you (web form, trade show, referral, inbound call); recency matters — window of interest fades | Immediate follow-up to qualify and move to pipeline; do not let more than 24-48 hours pass |
| **T6** | In Buying Window | Highly qualified; buying window is open NOW due to immediate need, contract expiration, trigger event, or budget cycle | Call today; goal is to advance to a qualified opportunity or set appointment |

**Tier assignment decision logic:**
1. Is this an inbound lead or referral? → T5 (or T6 if fully qualified AND in active buying window)
2. Is the prospect confirmed in an active buying window (contract expiring, trigger event, stated need)? → T6
3. Is this a strategic conquest account (top of territory list)? → T4 (regardless of buying window status)
4. Are decision-maker contacts confirmed and a future buying window identified? → T3
5. Are basic contact details verified and some qualification data present? → T2
6. None of the above — name/company only or insufficient data → T1

**Why:** Tier assignment drives every downstream action. A Tier 1 prospect called with a closing pitch wastes both the rep's time and the prospect's goodwill. A Tier 6 prospect left un-called because they appear lower on an alphabetical list is a missed revenue opportunity. The tier is the instruction.

### Step 3: Apply list construction filters (optional refinement)

If the list is large (50+ prospects) or the user wants batch-focused prospecting blocks, apply secondary filters to create focused sub-lists for specific blocks. Use combinations from:

- **Objective:** What action do you want from this block — set appointment, gather qualification data, build familiarity, or close?
- **Channel:** Phone, email, LinkedIn, text, in-person, networking
- **Territory plan:** Geographic cluster (zip code, city, region) for field reps
- **Industry vertical:** Same-sector batching improves relevance and social proof
- **Decision-maker role:** Economic buyer vs. technical buyer vs. champion
- **Seasonal / inactive / trade-show:** Time-sensitive segments

**Why:** Channel-switching between calls burns cognitive energy. Batching by industry means you build sector-specific knowledge and pattern recognition within a single block. Territory batching reduces travel time for field reps.

### Step 4: Build the daily action plan

Produce a prioritized daily sequence that walks the pyramid from tip to base:

1. **Block 1 — Tier 6 (In Buying Window):** Call these first, while energy and confidence are highest. These prospects convert more readily, producing early wins that create momentum for the rest of the day.
2. **Block 2 — Tier 5 (Hot Inbound / Referral):** If not yet called, follow up immediately. Inbound interest decays fast.
3. **Block 3 — Tier 4 (Conquest):** Systematic nurturing and trigger monitoring for strategic accounts. Even without an open window, regular touches build familiarity.
4. **Block 4 — Tiers 1-3 (Qualifying work):** Data gathering, stakeholder identification, and nurturing campaigns for the bulk of the database. This work populates tomorrow's Tier 6 list.

**Why:** Starting with the highest-probability prospects is not just efficiency math — it is psychological architecture. Early wins create confidence. Confidence fuels the energy needed to power through the harder, lower-tier calls later in the block. Reversing the order (starting with cold names) produces friction-first blocks that most reps abandon early.

### Step 5: Flag data gaps and tier-up opportunities

Scan for:
- Prospects stuck in T1 for a long time (data gap — what would it take to move them to T2?)
- Prospects in T2 or T3 with no recent activity (nurture lapsed?)
- Conquest accounts (T4) with no stakeholder map (immediate research priority)
- Inbound leads (T5) older than 48 hours (urgency flag)

**Why:** The pyramid is a living system, not a one-time sort. Its value compounds when reps systematically advance prospects upward by filling in qualification data over time. Flagging stagnant accounts creates an explicit "move-up" task list.

### Step 6: Write outputs to file

Produce two output files:
1. `tiered-prospect-list.md` (or `.csv`) — the full list with tier assignment, tier name, action directive, and any data-gap flags
2. `daily-action-plan.md` — the sequenced call plan for the next prospecting block, grouped by tier

**Why:** Externalizing the output means the rep can execute without re-deriving priority from scratch tomorrow. The tiered list can be imported back into the CRM as a custom field or tag.

---

## Inputs

| Input | Required | Format | Notes |
|-------|----------|--------|-------|
| Prospect list | Yes | CSV, markdown table, or pasted text | Must contain at minimum company names |
| Qualification data per prospect | Recommended | Inline in list or separate notes | Lead source, buying window, stakeholder info |
| Ideal Customer Profile (ICP) | Recommended | `icp.md` or described in prompt | Used to validate fit at Tier 2+ |
| Account notes | Optional | Per-account markdown files | Improves tier accuracy for T3/T4 |

---

## Outputs

| Output | Format | Description |
|--------|--------|-------------|
| `tiered-prospect-list.md` | Markdown table | Every prospect with: tier number, tier name, action directive, data-gap flags |
| `daily-action-plan.md` | Markdown | Sequenced call plan grouped by tier, with action directives and any specific notes per account |

---

## Key Principles

**The pyramid is a qualification map, not a ranking by company size.** A small company with a known contract expiration date belongs in Tier 6. A Fortune 500 with no contact info belongs in Tier 1.

**Tier 6 prospects are scarce and time-sensitive.** At any given time, only a small fraction of your database is in an active buying window. Missing them because you worked alphabetically is an invisible but expensive mistake.

**The pyramid is a living system.** The goal of every Tier 1-3 call is to gather information that moves the prospect one tier up. Over weeks, a well-managed list produces a growing Tier 6 pool from systematic qualification work.

**Conquest accounts (Tier 4) require consistent attention.** These are strategic enough to warrant regular touches even without an open window. The Law of Familiarity says prospects buy from people they recognize. Tier 4 is where familiarity is built.

**Inbound leads (Tier 5) have a half-life.** The window of interest from a trigger event or inbound inquiry fades within 24-48 hours. Tier 5 accounts that age into Tier 3 or 4 without follow-up represent a preventable loss.

**List quality is the single biggest lever on prospecting block productivity.** A well-tiered list that puts the right prospect first has more impact on results than technique, script quality, or channel choice.

---

## Examples

### Example 1: SDR with a 300-account territory list

**Situation:** An SDR at a B2B SaaS company has 300 accounts in their CRM from a data vendor. No qualification has been done. The morning prospecting block starts in 30 minutes.

**Inputs provided:** CSV export with fields: Company, Contact Name, Email, Phone, Industry, Employee Count, Lead Source (all "Data Provider")

**What the skill does:**
- All 300 accounts start as Tier 1 (Unknown) — lead source is cold data, no qualification data present
- Identifies no Tier 5 or Tier 6 prospects in the current list
- Builds a batch-focused daily plan: pick an industry vertical, run a block calling for data gathering (confirm decision-maker name, ask one qualifying question about current vendor)
- Flags that the list needs qualification work before the pyramid can produce Tier 6 accounts
- Recommends adding these CRM fields: `DM Confirmed`, `Buying Window`, `Trigger Event`, `Budget Confirmed` to enable future tiering

**Daily action plan output:** Single block — Tier 1 qualification calls. Objective: data gathering. 20-30 calls. Goal: confirm contact, get one piece of qualification data per account.

---

### Example 2: AE with 50 strategic accounts, mixed qualification states

**Situation:** An Account Executive manages 50 named accounts. Three have contracts expiring in the next 90 days. Eight submitted an inbound demo request this week. Twelve are flagged as strategic conquest accounts. The rest are partially qualified.

**Inputs provided:** CSV with fields: Company, Contact, Stage, Contract Renewal Date, Lead Source, Decision Maker, Budget Confirmed

**What the skill does:**
- **Tier 6:** 3 accounts — contract expiration in <90 days AND decision maker known AND budget confirmed. Action: call today.
- **Tier 5:** 8 accounts — inbound demo requests this week. Action: follow up within 24 hours; qualify on the call.
- **Tier 4:** 12 accounts — conquest list, varying qualification states. Action: nurturing sequence + trigger-event check.
- **Tier 3:** 14 accounts — DM known, future buying window identified. Action: nurturing touchpoints.
- **Tier 2:** 8 accounts — contact info confirmed, no buying window yet. Action: stakeholder mapping calls.
- **Tier 1:** 5 accounts — minimal data. Action: data gathering.

**Daily action plan:** Block 1 (first 45 min) — 3 Tier 6 calls. Block 2 — follow up with 8 inbound leads. Block 3 — conquest account check-ins. Blocks 4+ — lower-tier qualifying work.

---

### Example 3: SDR cleaning up a stale CRM with 150 contacts

**Situation:** An SDR inherited a territory with 150 contacts logged by a previous rep. Last activity date is 3-18 months ago. No consistent tiering. Many records have outdated contact info.

**Inputs provided:** CRM export with Last Activity Date, Stage, partial notes

**What the skill does:**
- Identifies 4 accounts with notes indicating upcoming contract renewals → tentatively Tier 6 (needs confirmation call)
- Finds 2 accounts where notes say "referral from customer" → Tier 5 (aged, but still prioritize follow-up)
- Identifies 8 accounts with complete stakeholder maps but stale last-activity dates → Tier 3 (reactivate nurture)
- Remaining 136 accounts have incomplete or aged data → Tier 1 or 2
- Flags all Tier 1 accounts with "last activity > 6 months" for data-verify calls before any pitch attempt
- Produces a 2-week cleanup plan: 10 accounts per day, starting with the 4 potential Tier 6s

---

## References

Full tier definitions with classification criteria checklist: see inline table in the Process section above.

List construction filter reference: 14 filters enumerated in Step 3.

Source chapter: Blount, Jeb. *Fanatical Prospecting.* Wiley, 2015. Chapter 10: "Leveraging the Prospecting Pyramid" (pp. 102-109); Chapter 11: "Own Your Database" (pp. 110-113).

---

## Related BookForge Skills

- **prospecting-objective-setter** — Once you know which tier to call, use this skill to select the right objective (set appointment, gather information, build familiarity, or close) for each prospecting block.
- **prospecting-message-crafter** — Build the actual phone opener, email, or LinkedIn message for a specific prospect tier and objective.

---

## License

[CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) — BookForge Skills. Source framework: *Fanatical Prospecting* by Jeb Blount (Wiley, 2015).

---
name: in-person-prospecting-route-planner
description: Plan a Hub-and-Spoke in-person prospecting route for a field sales day — mapping drop-by prospect visits around preset appointments to eliminate random driving and maximize face-to-face touches. Use this skill when planning in-person prospecting, field sales route, territory routing, door to door sales, drop-by visits, hub and spoke territory, T-call technique, cold in-person visit, outside sales route, in-person prospecting calls, field rep territory planning, IPP route, mapping prospects around appointments, drop-in sales calls, walking your territory, outside sales day planning, maximizing field time, face-to-face prospecting plan, or when a rep says "I'm just going to drive around my territory today" (which is exactly the anti-pattern this skill prevents). Takes a field rep's preset appointments, prospect list with addresses, and available driving time, then produces a Hub-and-Spoke 5-step territory routing plan, a per-stop action plan with opener scripts, and T-call technique instructions for opportunistic walk-ins.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/fanatical-prospecting/skills/in-person-prospecting-route-planner
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: published
source-books:
  - id: fanatical-prospecting
    title: "Fanatical Prospecting"
    authors: ["Jeb Blount"]
    chapters: [18]
tags: [sales, prospecting, field-sales, territory-management, in-person, sdr, bdr]
depends-on: [prospect-list-tiering, prospecting-objective-setter]
execution:
  tier: 2
  mode: hybrid
  inputs:
    - type: document
      description: "Territory map/prospect list with addresses, scheduled appointments for the day, and daily available driving time"
  tools-required: [Read, Write]
  tools-optional: []
  mcps-required: []
  environment: "Document/map directory"
discovery:
  goal: "Produce a Hub-and-Spoke daily route plan — hubs from preset appointments, spokes from nearby prospects — with per-stop opener scripts and T-call instructions"
  tasks:
    - "Identify hubs (preset appointments) for the day"
    - "Search prospect list by proximity to each hub to build spokes (3-5 per hub)"
    - "Classify each spoke prospect by tier to assign the correct objective"
    - "Sequence stops by geography to minimize windshield time"
    - "Draft in-person opener scripts and T-call technique instructions"
    - "Produce a route sheet with time blocks and per-stop action plan"
  audience:
    roles: [outside-sales-rep, field-ae, territory-manager, account-manager]
    experience: beginner-to-intermediate
  triggers:
    - "in-person prospecting"
    - "field sales route"
    - "territory routing"
    - "door to door sales"
    - "drop-by visits"
    - "hub and spoke territory"
    - "T-call technique"
    - "cold in-person visit"
    - "outside sales route"
    - "planning my field day"
    - "driving around my territory"
  prerequisites:
    - "prospect-list-tiering — to have a tiered prospect list with addresses"
    - "prospecting-objective-setter — to have defined the correct objective per tier before walking in"
  not_for:
    - "Inside sales reps who do not make in-person calls"
    - "Account management visits to existing customers (no prospecting element)"
    - "Writing phone or email scripts — use prospecting-message-crafter"
    - "Calculating how many calls are needed to hit quota — use prospecting-ratio-manager"
  environment: "Directory containing prospect list file (CSV or markdown) with address fields, plus appointment calendar data (pasted or in a file)"
  quality:
    required_outputs: ["route-sheet.md"]
    completeness: "Every stop must have: address, prospect tier, call objective, opener script snippet, estimated time allocation"
---

# In-Person Prospecting Route Planner

## When to Use

You are a field sales rep or outside sales representative with a day of in-person activity ahead. You have one or more preset appointments on your calendar, a list of prospects in your territory, and a finite amount of driving time. The question is: how do you fill every available minute between appointments with purposeful prospecting calls — without burning the day aimlessly driving from one random stop to the next?

This skill applies the Hub-and-Spoke territory routing system to turn your preset appointments into anchors, then maps the most geographically efficient set of drop-by prospect visits around each one. The result is a single-page route sheet you can execute with confidence.

**Who this skill is for:** Outside sales reps, field AEs, territory managers, and account managers whose role includes in-person prospecting as part of a balanced prospecting approach. Works for both B2B reps calling on businesses and reps managing geographic territories (industrial parks, food service districts, healthcare corridors, retail strips).

**When NOT to use this skill:**
- You have no preset appointments (the whole system depends on hubs — if you have none, set phone appointments first, then run this skill)
- You are doing account management visits with no prospecting component
- You are an inside sales rep with no field activity

**Output:** `route-sheet-{date}.md` — a sequenced list of stops with map-order addresses, tier/objective per stop, opener script snippets, and T-call reminders.

---

## Context and Input Gathering

### Required Inputs

**Preset appointments for the day:**
- Company name, address, and estimated duration for each scheduled meeting
- Look for: `appointments.md`, `calendar-export.csv`, or ask: "What appointments do you have confirmed on your calendar today? Give me the company name, address, and how long each meeting is expected to run."

**Prospect list with addresses:**
- A list of prospects in the territory with physical addresses (or at minimum zip codes)
- Look for: `prospect-list.csv`, `territory-accounts.csv`, any `.csv` with address/zip fields
- If using the `prospect-list-tiering` skill output: look for `tiered-prospect-list.md`
- If missing: ask: "Can you share your territory prospect list? I need company names and addresses (or zip codes) to map spokes around your appointments."

**Daily available driving time:**
- Total hours available for field prospecting (subtract appointment durations and commute)
- If not stated: ask: "How many hours do you have available today for field calls, accounting for your scheduled appointments?"

### Useful Inputs

**Tier assignments from prospect-list-tiering:** If already tiered, read `tiered-prospect-list.md` to inherit tier labels and use them to assign call objectives per stop.

**CRM notes or account research files:** Per-account notes (decision-maker names, LinkedIn profiles, previous call history) enable personalized opener scripts. Look for: `account-notes/`, individual company markdown files, or CRM export fields like `Last Activity`, `Decision Maker`, `Notes`.

**Objective call plan from prospecting-objective-setter:** If already created, read `prospecting-objective-plan-{date}.md` to confirm the correct primary/secondary objective per prospect tier before assigning per-stop actions.

### Default Assumptions

- If no tier assignments exist: treat all drop-by prospects as semi-qualified (use "gather information" as the primary objective)
- If no CRM notes are available: use the prospect's website and LinkedIn profile to prepare a personalized approach before each stop
- If available driving time is not stated: assume a standard 8-hour field day minus appointment time
- If only zip codes are available (no street addresses): use zip-code proximity to hub appointments as the spoke selection criteria

### Sufficiency Threshold

```
SUFFICIENT when:
- At least one preset appointment (hub) exists for the day
- A prospect list with at minimum zip codes is available
- Daily available hours are known or can be estimated

NOT sufficient — ask for more before proceeding:
- No appointments at all (advise running a phone block first to set hubs)
- No prospect list with any location data
```

---

## Process

### Step 1: Identify the Day's Hubs

**Action:** List every preset appointment confirmed for the day. For each hub, record:
- Company name and full address
- Appointment time window (start + estimated end)
- Buffer availability: how much time is free before and after (30–60 minutes is ideal for spoke calls)

Arrange hubs in chronological order. These are the fixed anchors around which the entire day is built.

**Why:** In-person prospecting is the least time-efficient prospecting channel. A rep who drives randomly can spend 80% of their day behind the wheel and make fewer than 10 calls. The hub anchors the rep's geography — every other stop flows from the hub's location rather than from a random pick off the list. Kelly, a top rental uniform rep, sets 2–3 phone appointments first every morning precisely so he has fixed hubs to map around. Without hubs, the hub-and-spoke system collapses into an aimless drive.

**Output:** A numbered hub list with addresses and time blocks, e.g.:
```
Hub 1 — Acme Manufacturing, 123 Industrial Dr, Springfield | 9:00–10:00 AM | Buffer: 30 min before, 45 min after
Hub 2 — Riverside Services, 450 Commerce Blvd, Riverside | 1:00–2:00 PM | Buffer: 45 min before, 60 min after
```

---

### Step 2: Build Spokes — Nearby Prospects Around Each Hub

**Action:** For each hub, search the prospect list for 3–5 prospects whose addresses are geographically close. Use zip code proximity as the primary filter when no mapping tool is available:
1. Identify the hub's zip code
2. Filter the prospect list for matching or adjacent zip codes
3. If the list includes full addresses, look for same street, same industrial park, or same business district
4. Select 3–5 prospects per hub (do not exceed 5 — more spoke candidates than that creates route complexity and over-commitment)

Assign each spoke to its nearest hub. If a prospect could belong to two hubs, assign it to the hub with more available buffer time.

**Why:** Geographic clustering is the engine behind the volume numbers that make in-person prospecting worthwhile. Kasey, a restaurant supply rep, maps 3–5 prospects around each of her 4 daily account visits, producing 15–20 in-person prospecting touches per day — and opened more new accounts than any account manager in her company. Without geographic clustering, that same rep might make 4–6 calls total. The spoke selection is not about choosing the "best" prospects first — it is about choosing the most geographically proximate ones from within your prioritized tiers.

**Note on tier priority within spokes:** If you have already run `prospect-list-tiering`, prefer higher-tier prospects (Tier 4 Conquest and Tier 6 In Buying Window) when multiple geographically similar options exist. But never extend driving time significantly to reach a higher-tier prospect over a closer lower-tier one — geography governs the spoke, tier governs the objective.

**Output:** A spoke list per hub, e.g.:
```
Hub 1 spokes:
  - Spoke 1A: Midwest Textiles, 145 Industrial Dr (same park) | Tier 4 Conquest
  - Spoke 1B: Springfield Fabrication, 200 Industrial Dr | Tier 2
  - Spoke 1C: Crown Packaging, 78 Mill Rd (adjacent) | Tier 2
```

---

### Step 3: Classify Each Spoke and Assign Call Objectives

**Action:** For each spoke prospect, assign:
1. **Tier** (from `prospect-list-tiering` output, or assign manually using basic criteria)
2. **Primary objective** for this stop (from `prospecting-objective-setter` logic or the defaults below)
3. **Carry-to-close readiness:** Confirm whether you have close materials with you (order forms, contracts, sample materials, presentation deck) in case the stop converts to an immediate sales conversation

**Default objective assignments by tier:**

| Tier | Name | In-Person Primary Objective |
|------|------|-----------------------------|
| T6 | In Buying Window | Attempt close or set appointment for formal presentation |
| T5 | Hot Inbound / Referral | Set appointment or close on the spot |
| T4 | Conquest | Build familiarity + gather decision-maker intelligence |
| T3 | Buying Window Identified | Build familiarity + confirm buying window timeline |
| T2 | Basic Data Confirmed | Gather qualifying information — decision-maker name, competitive info, budget cycle |
| T1 | Unknown | Gather basic qualifying data — confirm decision-maker role, business type, size estimate |

**Why:** Walking into a prospect without a defined objective is the single fastest way to waste an in-person call. Carl, a business services rep, once walked into a prospect who was ready to close on the spot — but Carl was unprepared to present. The prospect signed with a competitor two weeks later. The objective, assigned before you walk in the door, determines what you ask for, what you carry in, and when you stop the conversation. An underprepared rep in front of a ready buyer is a more costly mistake than a well-prepared rep in front of a cold prospect.

**Output:** An annotated spoke list with tier + objective + carry-in materials check, e.g.:
```
Spoke 1A: Midwest Textiles | T4 Conquest | Objective: Build familiarity, get decision-maker name on record | Materials: business card, one-pager
Spoke 1B: Springfield Fabrication | T2 | Objective: Gather info — who handles uniform purchasing, current vendor | Materials: business card
```

---

### Step 4: Build the Opener Scripts and T-Call Technique

**Action:** For each planned spoke stop, draft a 2–3 sentence opener. For every hub visit, add a T-call reminder.

**In-Person Opener Script Template:**
```
"Hi, my name is [Your Name], I'm with [Company].
The reason I stopped by is [transparent, specific reason — leverage nearby customer, recent trigger, or relevant service].
I wanted to [primary objective: introduce myself / ask [Decision Maker] a couple of quick questions / see if there's a fit]."
```

**Opener examples by situation:**

*Neighbor leverage (most effective):*
"Hi, my name is [Name], I'm with [Company]. We've been working with [Customer Next Door] for three years — they introduced us to some of the other businesses in this park. I wanted to stop in and introduce myself to [Decision Maker] and ask a couple of quick questions about how you handle [relevant need]."

*Research-personalized:*
"Hi, I'm [Name] from [Company]. I noticed on your LinkedIn page that you recently [relevant event — expansion, new hire, new location]. We work with companies going through exactly that kind of growth. I wanted to ask [DM name] a quick question about your current [relevant area]."

*Cold walk-in (no prior research):*
"Hi, my name is [Name], I'm with [Company]. The reason I stopped in is I provide [service/product] to several businesses in this area and I wanted to learn more about your company and situation to see whether working together might be a good fit."

**What to avoid in all openers:**
- Tricks designed to mislead the gatekeeper about your purpose
- Claiming to be "just dropping something off" when you are not
- Pitching your product in the opener — gather first, pitch when invited

**T-Call Technique:**
After every hub appointment (and every spoke stop), before returning to your car: look left, look right, look behind you. Any business you have not visited that is visible from where you stand is a T-call candidate. Walk in. Use the cold walk-in opener above. T-calls are by definition unplanned — you have not done pre-research — so keep the opener simple, the objective tight (gather DM name and basic qualifier), and log everything before you drive away.

**Why:** Gatekeepers and receptionists are not obstacles — they are information sources and future allies. A rep who is transparent ("I stopped by to see if there's a fit") earns more goodwill than a rep who uses deception. Blount is explicit: "You are a professional, so be straightforward and transparent about your purpose for being there. Never use cheesy lines designed to trick gatekeepers." T-calls convert the time between hub and spoke into additional prospecting volume with zero pre-planning overhead. Kelly generates 10–20 face-to-face touches daily using T-calls as the fill layer on top of planned spokes.

**Output:** Opener scripts embedded in the route sheet per stop, plus a T-call reminder block after each hub.

---

### Step 5: Produce the Route Sheet and Time Blocks

**Action:** Assemble all hubs and spokes into a single sequenced route sheet, ordered by the most geographically efficient driving sequence (not by tier priority — geography governs sequencing). Write the output to `route-sheet-{date}.md`.

**Route sheet structure per time block:**
```
## Time Block 1: [HH:MM – HH:MM]

### Hub: [Company Name]
- Address: [Full address]
- Appointment: [Start] – [End]
- Carry in: [What you need for this meeting]

### Spoke 1A: [Company Name]
- Address: [Full address]
- Tier: [T1–T6] | Objective: [Primary objective]
- Opener: "[Opener script text]"
- Time allocation: 10–15 min
- Materials to carry: [List]

### Spoke 1B: [Company Name]
...

### T-Call Zone: After Hub 1 appointment
- Look left, right, behind. Walk into any visible business not on your list.
- Objective: Gather DM name + one qualifying fact
- Log before leaving the parking lot

---
```

**Time allocation guidelines:**
- Hub appointment: per calendar entry
- Planned spoke (T1–T3): 10–15 minutes
- Planned spoke (T4–T6): 15–25 minutes (more time if buying window is open)
- T-call (unplanned): 5–10 minutes
- Between-stop driving: 3–7 minutes within same industrial park/district; 10–15 minutes between geographic clusters
- CRM logging at end of day: 15–30 minutes — non-negotiable

**Why:** A sequenced route sheet eliminates the "what do I do next" decision cost that eats into field time. The rep leaves the car with a defined next action, re-enters with a complete record of what happened, logs it in the CRM, and drives to the next stop. Without this structure, reps waste time deciding, double-back on geography, and skip logging — which means the day's prospecting produces zero lasting database value. The route sheet is also the artifact that proves the day was productive: every stop has an outcome logged.

**Final step — CRM logging reminder:** Before leaving the last stop of the day (or on-the-spot after each call if time allows), log every stop: outcome, decision-maker name confirmed/not confirmed, next action, follow-up task date. This converts face-to-face touches into database intelligence and pipeline entries.

**Output:** `route-sheet-{date}.md` with all time blocks, hubs, spokes, opener scripts, and T-call reminders.

---

## Inputs

| Input | Required | Format | Notes |
|-------|----------|--------|-------|
| Preset appointments | Yes | Calendar export, markdown list, or pasted text | Must include company name, address, time |
| Prospect list with addresses | Yes | CSV or markdown table | Zip code minimum; full address preferred |
| Daily available hours | Yes | Number or time range | Used to determine how many spokes are realistic |
| Tiered prospect list (from prospect-list-tiering) | Recommended | `tiered-prospect-list.md` | Enables tier-based objective assignment per spoke |
| Objective call plan (from prospecting-objective-setter) | Recommended | `prospecting-objective-plan-{date}.md` | Ensures correct primary objective per tier |
| Account notes / CRM export with DM names | Optional | Per-account markdown files or CSV | Enables personalized openers |

---

## Outputs

| Output | Format | Description |
|--------|--------|-------------|
| `route-sheet-{date}.md` | Markdown | Sequenced stop list with hub/spoke structure, opener scripts, T-call reminders, time blocks, and CRM logging reminder |

---

## Key Principles

**Geographic sequence, not priority sequence.** The route is ordered by geography to minimize windshield time — not by tier priority. You may call on a Tier 2 prospect before a Tier 4 conquest account if the Tier 2 prospect is physically between your hub and the Tier 4. Tier priority governed which prospects made it onto the spoke list; geography governs the order you visit them.

**Never waste between-appointment time.** The interval between a hub appointment ending and the next hub starting is the most underutilized resource in field sales. Three to five spoke calls fit comfortably in a 45-minute window within the same industrial park or business district. The mindset shift: every minute not on the road or in a meeting is a prospecting opportunity.

**Familiarity builds through repeated geographic exposure.** A prospect who says no today recognizes your name on the phone next week. A gatekeeper who has seen your face twice is more likely to help you get to the decision maker on the third visit. In-person prospecting builds familiarity faster than any other channel because 80% of human communication is non-verbal. This is why Tier 4 (Conquest) accounts belong on the spoke list even when no buying window is open — every face-to-face touch advances the familiarity score.

**Always be prepared to close.** Even on a "gather information" call, carry your close materials — order forms, contracts, sample kit, or a demo device. You cannot predict when a decision maker will be present and ready. Carl's missed close (p. 224) is the permanent warning: "Sometimes you only get one chance with a prospect." The cost of carrying materials you do not use is zero. The cost of not having them when you need them is the deal.

**Respect the gatekeeper.** The receptionist is not an obstacle — she is an intelligence source, a future advocate, and a human being. Transparency ("I stopped by to see if there's a fit") builds goodwill that compounds over time. Deception burns the relationship permanently. The rep who goes in the back door claiming to be lost is the rep who never gets a warm introduction to the decision maker.

**T-calls are not optional.** Putting on your "sales goggles" — looking left, right, and behind after every appointment — is a trained behavior, not a personality trait. Every stop produces T-call candidates. The reps who make 10–20 daily in-person touches almost all report that T-calls account for 3–7 of those touches. T-calls also surface prospects who are not yet in the CRM database, which means they are otherwise invisible.

**In-person prospecting supplements, it does not replace, other channels.** On the best day, a field rep makes 15–20 in-person touches. A phone block can produce 25–50 contacts per hour. In-person prospecting is powerful for qualification, familiarity-building, and gatekeeper navigation — but it is not a substitute for the phone. The hub-and-spoke system makes in-person prospecting maximally efficient precisely so it can serve its role within a balanced prospecting cadence.

---

## Examples

### Example 1: B2B Outside Rep — Software for Industrial Businesses

**Situation:** Sarah sells equipment monitoring software to manufacturing and fabrication companies. She has two preset appointments in the same industrial corridor: 9:30 AM at Acme Machining and 1:00 PM at Crown Metal Works. She has a tiered prospect list with 40 accounts in the territory and 6 hours of field time.

**What the skill produces:**
- Hub 1: Acme Machining, 9:30–10:30 AM. Buffer: 45 min after.
  - Spoke 1A: Riverside Fabrication (same park, T4 Conquest) — Objective: build familiarity, confirm plant manager name
  - Spoke 1B: Midwest Precision Parts (same park, T2) — Objective: gather info, confirm decision-maker role
  - Spoke 1C: Atlas Components (2 blocks north, T2) — Objective: qualify — who handles software decisions?
  - T-call zone: 3 businesses visible from Acme parking lot, not in CRM
- Hub 2: Crown Metal Works, 1:00–2:00 PM. Buffer: 60 min after.
  - Spoke 2A–2D: 4 prospects within 1 mile on the same industrial road
  - T-call zone: adjoining business park

**Total planned stops:** 2 hubs + 7 spokes + estimated 4–6 T-calls = 13–15 face-to-face touches for the day.

---

### Example 2: Restaurant Supply Rep — Food Service District

**Situation:** Kasey sells restaurant supplies and is required to visit 4 existing accounts daily (these become her hubs). Her territory is a dense urban food service district — dozens of restaurants, delis, and catering companies within walking distance of her hub accounts.

**What the skill produces:**
- 4 hub accounts mapped chronologically across the district
- 3–5 prospects per hub drawn from her CRM by zip code and street proximity
- Opener script leverages her existing relationships: "We work with [nearby restaurant] — they mentioned you run a similar operation and suggested I stop by."
- T-calls in the same block: food trucks parked outside her hub accounts, new restaurant signage spotted during transit

**Total stops:** 4 hubs + ~16 planned spokes + T-calls = 20+ in-person touches per day (matching Kasey's actual reported daily volume from the source case study).

---

### Example 3: Rural Territory Rep — Low-Density Geography

**Situation:** Marcus sells pest control services to agricultural businesses in a rural territory. Appointments are spread 20–40 miles apart. He has 3 preset appointments and his prospect list has 80 accounts spread across a 3-county area.

**What the skill produces:**
- Hubs ordered on a geographic north-to-south route to minimize backtracking
- Spokes selected from prospects along the driving corridor between hubs (not by zip code, but by route proximity — flagged in the route sheet)
- T-call note: grain elevators, equipment dealers, and co-ops visible from main highways are prime T-call candidates even without a CRM record
- Time allocation adjusted: longer driving segments mean fewer spokes per hub (2–3 rather than 5), but total daily touches can still reach 10–12 with T-calls

**Key adaptation:** In low-density rural territories, "proximity" means along the driving route, not same-zip. The skill notes this and instructs the rep to use a highway map or route planner to identify prospects within a 5–10 minute detour off the direct path between hubs.

---

## References

Detailed script library (extended opener variations, RBO turnaround scripts for in-person push-back, gatekeeper navigation scripts): see `references/in-person-opener-scripts.md` (to be created if needed).

Route template (blank `route-sheet.md` template for reuse): see `references/route-sheet-template.md` (to be created if needed).

Source chapter: Blount, Jeb. *Fanatical Prospecting.* Wiley, 2015. Chapter 18: "In-Person Prospecting" (pp. 219–231).

T-call technique: pp. 220, 229.
Hub-and-Spoke five-step system: pp. 222–223.
Five-step in-person call process: pp. 226–228.
Preparation framework: pp. 225–226.
Kelly case study (rental uniform rep): pp. 219–220.
Kasey case study (restaurant supply rep): pp. 222–223.
Carl missed-close vignette: p. 224.

---

## Related BookForge Skills

Install the dependencies that feed into this skill:

```
clawhub install bookforge-prospect-list-tiering
```
Tier and prioritize your territory prospect list before building spokes. Output (`tiered-prospect-list.md`) is the primary spoke candidate source for this skill.

```
clawhub install bookforge-prospecting-objective-setter
```
Assign the correct primary/secondary/tertiary objective per prospect tier before your field day. Output (`prospecting-objective-plan-{date}.md`) drives per-stop objective assignments in the route sheet.

Coming soon:
```
clawhub install bookforge-gatekeeper-navigator
```
Handle in-person gatekeeper scenarios with specific response scripts for the receptionist block, the "he's not available" brush-off, and the warm handoff request.

Browse the full Fanatical Prospecting skill set: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

---

## License

[CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) — BookForge Skills. Source framework: *Fanatical Prospecting* by Jeb Blount (Wiley, 2015).

---
name: gatekeeper-navigator
description: |
  Navigate any gatekeeper situation — choose bypass vs befriend, apply the right technique, and
  draft scripts that pass the anti-manipulation check.

  Trigger this skill when you need to:
  - Get past a receptionist or administrative assistant who is blocking access to a decision maker
  - Reach a decision maker when you don't know their name, title, or direct contact information
  - Figure out whether to bypass a gatekeeper or build a relationship with them
  - Apply the sales-help-sales hack to reach a hard-to-reach prospect
  - Use the calling-other-extensions (go-around-back) technique to extract a DM name
  - Draft respectful, transparent scripts for working with gatekeepers on recurring accounts
  - Check a gatekeeper approach for manipulation, pretending, or bulldozing anti-patterns
  - Decide whether LinkedIn flanking, early/late calls, or in-person approaches fit your situation
  - Stop getting hung up on or added to a do-not-help list
  - Turn a hostile receptionist into a calendar ally over multiple visits

  NOT for: turning around a reflex response after you've already reached the prospect (use
  prospecting-rbo-turnaround), building the full 5-step phone call script once you're through
  (use cold-call-opener-builder), or crafting the bridge and because for the call itself
  (use prospecting-message-crafter). This skill handles the access layer — getting to the
  person who can say yes.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/fanatical-prospecting/skills/gatekeeper-navigator
metadata:
  openclaw:
    emoji: "📚"
    homepage: "https://github.com/bookforge-ai/bookforge-skills"
status: published
source-books:
  - id: fanatical-prospecting
    title: "Fanatical Prospecting"
    authors:
      - Jeb Blount
    chapters:
      - 17
tags:
  - sales
  - prospecting
  - gatekeeper
  - cold-calling
  - sdr
  - bdr
depends-on:
  - prospecting-message-crafter
execution:
  tier: 2
  mode: hybrid
  inputs:
    - type: document
      description: "Description of the gatekeeper situation + target prospect info + what has already been tried"
  tools-required: [Read, Write]
  tools-optional: []
  mcps-required: []
  environment: "Document directory"
discovery:
  goal: "Produce a recommended technique + scripts + anti-pattern warnings for the specific gatekeeper situation"
  tasks:
    - "Diagnose the gatekeeper situation: persona, level of resistance, prior attempts, account type"
    - "Decide bypass vs befriend using explicit criteria (one-shot vs ongoing, enterprise vs SMB)"
    - "Select the most appropriate technique from the technique library"
    - "Draft scripts using the Bridge-Because pattern from prospecting-message-crafter"
    - "Run anti-pattern audit: no manipulation, no pretending, no bulldozing"
    - "Write output to gatekeeper-navigator-output.md"
  audience:
    roles: [sdr, bdr, ae, founder-self-seller]
    experience: beginner
  when_to_use:
    triggers:
      - "Receptionist or admin is blocking access and won't connect you to the decision maker"
      - "You don't know the decision maker's name or contact information"
      - "You have been hung up on or told 'we don't give out that information'"
      - "Repeated calls are failing to get through to the right person"
      - "You want to know whether to call early/late, use LinkedIn, go in-person, or press the sales extension"
      - "You are prospecting an enterprise account and need a name before you can call"
      - "You want to befriend a receptionist on a recurring account you call regularly"
    prerequisites: []
    not_for:
      - "Handling a reflex response or brush-off after you've reached the prospect (use prospecting-rbo-turnaround)"
      - "Building the full 5-step phone call opening once you're through (use cold-call-opener-builder)"
      - "Crafting the WIIFM bridge and because for the conversation itself (use prospecting-message-crafter)"
  environment:
    codebase_required: false
    codebase_helpful: false
    works_offline: true
  quality:
    scores:
      with_skill: 0
      baseline: 0
      delta: 0
    tested_at: ""
    eval_count: 0
    assertion_count: 0
    iterations_needed: 0
    what_skill_catches:
      - "Names the sales-help-sales hack and explains when to use it"
      - "Names the calling-other-extensions hack and shows Evan's verbatim dialogue"
      - "Names the go-around-back technique for in-person prospecting"
      - "Rejects manipulation/pretending anti-patterns with explicit reasoning"
      - "Chooses bypass vs befriend using explicit account-type and access criteria"
      - "Uses respect-based engagement (connect, ask for help, hold the cheese) for ongoing accounts"
      - "Applies the Bridge-Because pattern from prospecting-message-crafter to gatekeeper scripts"
    what_baseline_misses:
      - "Treats gatekeeper navigation as a tricks problem — tries schemes that destroy credibility"
      - "Does not distinguish bypass (new conquest) from befriend (ongoing/recurring)"
      - "Does not know the sales-help-sales or calling-other-extensions hacks"
      - "Does not know the please-twice or hold-the-cheese rules"
      - "Produces a manipulative or deceptive approach without flagging the anti-pattern"
---

# Gatekeeper Navigator

## When to Use

You are trying to reach a decision maker and a gatekeeper — receptionist, administrative assistant, or automated phone system — is standing between you and the person who can say yes.

There are no tricks that reliably work. Gatekeepers are not obstacles to be defeated; they are people assigned the job of protecting someone's time. Your success depends on good manners, likeability, and people-savvy — and, when the direct path is blocked, on knowing which legitimate bypass technique fits the situation.

Use this skill when:
- You do not have the decision maker's name, title, or direct line
- A receptionist or admin is refusing to provide contact information or connect you
- You have been hung up on or added to the mental "do not help" list
- You need to decide whether to try a bypass route or invest in building the gatekeeper relationship
- You are calling a strategic account regularly and want to turn the gatekeeper into a calendar ally

**This skill handles the access layer.** Once you are through and speaking to the prospect, switch to `cold-call-opener-builder` for the 5-step telephone framework and `prospecting-message-crafter` for the bridge and because.

## Context & Input Gathering

Before proceeding, gather (or ask the user for) the following:

**Required:**
1. Target prospect's company, department, and suspected role (e.g., "VP of Procurement at a large grocery chain HQ")
2. What gatekeeper type is blocking you: receptionist/switchboard, personal administrative assistant, or automated phone system
3. What has already been tried (direct request to connect, pleas, online search, LinkedIn)
4. Account type: is this a new conquest (one-shot attempt), or an ongoing account you visit or call regularly?

**Recommended:**
5. Do you have any partial information — a department name, a first name, a title, or an employee name from a prior call?
6. What channels are available: phone, in-person access, LinkedIn, email?
7. Is the gatekeeper a blocker on the switchboard (lower-level) or a dedicated personal assistant to the decision maker?

## Process

### Step 1 — Diagnose the Gatekeeper Situation

Identify the gatekeeper's level of resistance and your information gap.

**Resistance levels:**
- **Soft block:** "I'm sorry, they're not available right now. Can I take a message?" — the gatekeeper is neutral and procedural. Respect and transparency can open this.
- **Active block:** "We don't give out that information." / "I cannot connect you if you don't have a name." — the gatekeeper has been trained to refuse. Direct frontal approach will fail.
- **Hostile block:** Gatekeeper has been hung up on mid-question or has explicitly stonewalled. Frontal approach is exhausted.

**Information gap:**
- Do you have a name? → Proceed to direct connection request with please-twice technique.
- Do you have a department but no name? → Calling-other-extensions hack.
- Do you have nothing except the main number? → Sales-help-sales hack or LinkedIn flanking.

**Why diagnose first:** The appropriate technique is determined by your resistance level and information gap. Using a bypass hack when a simple respectful request would have worked burns goodwill. Using a frontal approach when the gatekeeper has been trained to block wastes time and damages credibility.

### Step 2 — Decide: Bypass vs Befriend

This is a strategic decision based on account type and access difficulty. Neither path is always right.

**Choose Bypass when:**
- This is a new conquest account — you have never done business here and need a name or extension before you can prospect effectively
- The gatekeeper is a switchboard with no personal relationship to protect
- You have been actively and repeatedly blocked after transparent, respectful attempts
- The decision maker is walled in and direct approach has failed

**Choose Befriend when:**
- This is an ongoing account — you call or visit regularly and the gatekeeper sees you more than the decision maker does
- You have or want a long-term commercial relationship with this company
- The gatekeeper is a personal assistant who has genuine influence over the DM's calendar
- You are doing in-person territory prospecting and will return to this location repeatedly

**Why this matters:** Using bypass tactics on a recurring account destroys a relationship that could be your most reliable path to the calendar. Using befriend tactics on a cold conquest wastes time on relationship-building where a simple technique would work faster. (Blount, p. 213)

### Step 3 — Choose the Technique

Select the technique that fits your diagnosis from Step 1 and your decision from Step 2. Full technique details are in `references/gatekeeper-technique-library.md`.

**Bypass Techniques (conquest / blocked):**

**Sales-help-sales hack** — When you know the company has an outbound sales team but cannot get a name through the switchboard, call the sales department extension (usually "press 1 for sales"). Sales reps answer their phones, empathize with your situation, know who's who in the organization, and will often give you a direct line or mobile number. Be honest: "I wasn't having much luck going through the switchboard and figured as a fellow salesperson you could relate."

**Calling-other-extensions hack** — When you have partial information (a department name, a title, a vague description like "someone in corporate who handles that"), call random internal extensions. Employees are usually informal and helpful. Collect clues: "Jack in IT handles that." Use those clues when transferred back to reception — reception will often correct a close-but-wrong name ("Did you mean Zack Freedman?") and give you an extension. See Evan's case in Examples.

**LinkedIn flanking** — Gatekeepers rarely control the decision maker's social inbox. A personalized LinkedIn InMail with a specific bridge and because goes directly to the prospect.

**Early/late calls** — Decision makers often arrive before the gatekeeper and stay after. Call before 8 AM or after 5 PM.

**Email** — May bypass the switchboard entirely. Pair with `cold-email-writer` for the message.

**In-person go-around-back** — If prospecting in person and reception refuses information, try the back entrance, loading dock, or parking lot. Employees on break are often happy to help a transparent, non-aggressive stranger. Note: do not attempt this where security guards or explicit access controls are in place.

**Befriend Techniques (ongoing / recurring account):**

**Be likable and transparent** — Use your full name and company every time. Be polite, positive, and specific about why you are calling. Never give the gatekeeper a reason to put you on the do-not-help list.

**Use please twice** — "Would you please connect me to [name], please?" This is the single most effective courtesy technique for routine gatekeeper calls. (Blount citing Mike Brooks, p. 212)

**Connect genuinely** — Learn the gatekeeper's name. Ask how they are doing. Remember what they told you last time. Build the kind of relationship where they are taking your calls, not screening them.

**Ask for help directly** — A genuine, honest request — "I really need some help getting in to see [name]. I've been trying for weeks and I genuinely believe we can do something useful for your company. Can you help me?" — combined with a little self-deprecating humor can flip a skeptical gatekeeper into an advocate.

**Why the technique selection matters:** Each technique is designed for a specific access situation. Using the wrong one is not just inefficient — it can permanently close doors. The sales-help-sales hack is useless if the company has no outbound sales team. Befriend tactics on a hostile conquest gatekeeper give the blocker more opportunities to say no.

### Step 4 — Draft the Script

Once you have selected a technique, draft the exact words. Apply the Bridge-Because pattern from `prospecting-message-crafter`:

**For a sales-help-sales opener:**
> "Hi [name], my name is [your name] from [company]. The reason I'm calling is I'm trying to reach the person in your company who handles [decision area]. I wasn't having much luck going through the switchboard and I figured as a fellow salesperson you could relate and might give me a hand."

**For a transparent switchboard request:**
> "Hi, this is [full name] from [company]. Would you please connect me to [name or role], please?"

**For an ask-for-help approach with humor:**
> "I know — I keep coming back. I figured I hadn't gotten quite enough rejection today to fill my quota. [pause for laugh] Seriously though, I really need some help. I believe we can do something useful here. Would you be willing to make a quick call to [DM name] on my behalf?"

**For the calling-other-extensions handoff:**
> "Hey — I was talking to [made-up employee name] in [department] and they were transferring me to [partial name/role], but somehow I ended up with you. Would you mind sending me over?"

**Why draft the exact words:** Gatekeepers make decisions in the first three seconds of a call. A vague, halting opener signals amateur. A clear, confident, honest opener signals professional and worthy of passage. Draft before you dial, even if you never say it verbatim.

**Cross-reference:** Once you have the script structure, use `prospecting-message-crafter` to sharpen the bridge and because for the conversation with the decision maker once you are through.

### Step 5 — Anti-Pattern Audit

Before using any approach, run it against this checklist. Any yes answer is a red flag.

- [ ] **Pretending to be someone you are not.** Claiming to be a customer, a vendor partner, a colleague, or anyone other than yourself. This is deception. It destroys your credibility and the gatekeeper's goodwill permanently when (not if) it is discovered. (Blount, p. 213)
- [ ] **Using a trick or scheme.** Vague call purpose ("just calling to check in"), fake urgency ("it's regarding an important account matter"), calling a personal number without introduction. Tricks make you look foolish and land you on the do-not-help list. (Blount, p. 213)
- [ ] **Bulldozing or arguing.** Repeating the same request louder or more forcefully after the gatekeeper has said no. Arguing that the gatekeeper's refusal is wrong. Attempting to "overcome" their objection the way you would a prospect's. This generates hostility, not passage.
- [ ] **Going around without exhausting honest routes first.** Using the calling-other-extensions hack before trying a respectful direct request signals you are hiding something, even when you are not.
- [ ] **Disrespecting the gatekeeper's role.** Treating them as an obstacle, not a person. Dismissing them, cutting them off, or making them feel stupid. They have a job to do and a boss to protect. They also have a long memory.

**Why the anti-pattern audit:** Tricks work once at best. Honesty compounds. A gatekeeper you treated well remembers you. A gatekeeper you deceived will tell their boss. The bypass hacks in this skill work precisely because they are transparent and honest — they ask for help directly rather than circumventing anyone. (Blount, p. 213)

## Inputs

| Input | Required | Source |
|---|---|---|
| Company and suspected DM role | Yes | User provides |
| Gatekeeper type and resistance level | Yes | User describes situation |
| What has already been tried | Yes | User describes |
| Account type: conquest vs ongoing | Yes | User states |
| Partial info (name, department, title) | No | User provides if available |
| Available channels | No | User states or skill infers |

## Outputs

| Output | Location | Description |
|---|---|---|
| `gatekeeper-navigator-output.md` | Working directory | Bypass vs befriend decision + recommended technique + drafted scripts + anti-pattern audit results |
| Technique recommendation | Inline in conversation | Named technique with reason for selection |
| Anti-pattern flags | Inline in conversation | Any red flags from Step 5 with specific violations called out |

## Key Principles

**1. There are no tricks — only respect and technique.** Every bypass hack in this skill works because it is honest. The sales-help-sales hack succeeds because sales reps empathize with salespeople who are blocked. The calling-other-extensions hack works because a casual internal employee is willing to help a transparent stranger. Deception does not scale. (Blount, p. 212)

**2. Gatekeepers are powerful long-term allies.** A receptionist you know by name, whose kids you have asked about, who laughs at your self-deprecating humor — that person will get you on the calendar when cold callers are blocked. Long-term account relationships are won at the front desk, not by going around it. (Blount, p. 213)

**3. Respect is the multiplier.** Politeness costs nothing and compounds. Being rude, pushy, or dismissive guarantees failure. Being likable, transparent, and genuinely interested in the gatekeeper as a person is the single highest-ROI investment you can make on a recurring account.

**4. The bypass hacks are for access, not avoidance.** The sales-help-sales hack is not a way to avoid the gatekeeper — it is a way to get the information you need to call back and ask the right question. Once you have a name, you still work through reception with full transparency.

**5. Persistence is the foundation.** The most valuable prospects are the most heavily walled-in. Repeated, respectful, transparent attempts — using different techniques and channels — eventually open even the most resistant accounts. (Blount, p. 218)

## Examples

---

### Example 1 — Evan's Calling-Other-Extensions Hack (Enterprise, No Name, No Title)

**Situation:** Evan needs to reach the broadband decision maker at a large grocery chain HQ. He has no name, no title, and no direct line — only the main number. Repeated calls to reception have failed: "We don't give out that information."

**Step 1 diagnosis:** Active block. No name. Partial information (knows "someone in corporate").
**Step 2 decision:** Bypass — new conquest, no relationship to protect.
**Step 3 technique:** Calling-other-extensions hack — collect clues from internal employees.

**Execution:** Evan calls random internal extensions until a friendly employee says: "Yeah, I think a guy named Jack over in IT handles that." Evan returns to reception:

> "Hey, I was talking to Dale Jones in purchasing and he was transferring me to Jack in IT, but somehow I ended up with you. Would you mind sending me over?"

> Reception: "I'm not seeing a Jack. Did you mean Zack Freedman?"

> Evan: "Yes, sorry about that. I thought I said Zack."

> Reception: "Okay, no problem. I'll send you over now."

> Evan: "Before you do, would you mind giving me Zack's extension just in case we get disconnected?"

> Reception: "Sure, it's 5642."

**Anti-pattern check:** Evan did not claim to know Dale Jones personally — he used Dale's name as the transfer context, not as a false reference. He was honest that he was prospecting. No pretending, no tricks.

**Outcome:** Evan eventually reached Zack, established a relationship, and converted the account into his largest customer. (Blount, pp. 214-215)

---

### Example 2 — Blount's Sales-Help-Sales Hack (Conquest, Hostile Gatekeeper)

**Situation:** Jeb Blount identifies a company hiring 30 new sales reps — a perfect fit for Sales Gravy. He has no internal contact. The switchboard gatekeeper hangs up on him mid-qualifying question.

**Step 1 diagnosis:** Hostile block. No name. No title.
**Step 2 decision:** Bypass — new conquest, gatekeeper is actively hostile.
**Step 3 technique:** Sales-help-sales hack — call the sales department directly.

**Execution:** Blount calls the main number, selects the sales extension. Mike answers:

> "Hi, Mike, my name is Jeb Blount. The reason I'm calling is I'm trying to reach the person in your company who buys training programs. I wasn't having much luck going through the switchboard and I figured as a fellow salesperson you could relate and might give me a hand."

Mike immediately empathizes, gives Blount Jean's name, her mobile number, and background on the company's hiring situation.

**Why this worked:** Sales reps answer their phones. They know the organizational structure. They have stood in your shoes. Honesty and peer empathy replaced the gatekeeper entirely.

**Anti-pattern check:** No pretending. No tricks. Blount stated exactly who he was and what he wanted. He asked for help as a fellow salesperson, not as a fake vendor or internal contact.

**Outcome:** First call to Jean resulted in a meeting that included the company president and opened a formal proposal. (Blount, pp. 215-217)

---

### Example 3 — Receptionist-Befriend on a Recurring Territory Account

**Situation:** An outside sales rep sells payroll services. She calls on a mid-size manufacturing company monthly. The decision maker (VP Operations) is never available and the receptionist is the permanent gatekeeper. The rep has been told "I'll pass along your message" for three months with no callbacks.

**Step 1 diagnosis:** Soft to active block. Has DM name. Ongoing account.
**Step 2 decision:** Befriend — recurring account, long-term relationship value high.
**Step 3 technique:** Connect genuinely + ask for help.

**Script approach (calls):**
> "Hi Sarah, this is [rep name] from [company] — I'm the one who keeps calling about payroll. How are you holding up today? [Listens.] Listen, I know I keep trying to reach Mark, and I really appreciate your patience with me. I genuinely think what we're doing could save him a headache in Q3. Would you be willing to let him know I called? And — total long shot — any chance you could shoot me a five-minute window when he's actually accessible this week?"

**In-person approach (quarterly visit):**
On the third visit, bring a small, relevant value-add (a payroll compliance article from a trade publication, not a brochure). Ask about Sarah's family. Remember what she mentioned last time. The goal is not one appointment — it is becoming the rep whose calls Sarah mentions to Mark by name.

**Anti-pattern check:** No tricks. No pretending. No claiming a false relationship with Mark. The humor is self-deprecating, not manipulative.

**Long-term outcome:** Gatekeepers who genuinely like you will advocate for you. "Mark, there's a rep who's been really persistent and actually really polite about it. Do you want me to book her in?" is the outcome the befriend path is designed to produce.

## References

Supporting materials are in the `references/` folder:

- `references/gatekeeper-technique-library.md` — full technique details: sales-help-sales, calling-other-extensions, go-around-back, LinkedIn flanking, please-twice, connect/befriend protocol, with worked scripts for each
- `references/bypass-vs-befriend-decision-matrix.md` — decision matrix with account type, gatekeeper type, and prior attempt criteria
- `references/gatekeeper-anti-pattern-examples.md` — named anti-patterns (pretending, tricks, bulldozing) with detection criteria and why each backfires

**Source chapter:** Blount, Jeb. *Fanatical Prospecting*, Chapter 17 "The Secret Lives of Gatekeepers" (pp. 193-200 / PDF pp. 211-218). Case studies: Evan (pp. 196-197 / PDF pp. 214-215); Salespeople-help-Salespeople (pp. 197-199 / PDF pp. 215-217).

## License

Content derived from *Fanatical Prospecting* by Jeb Blount (Wiley, 2015). This skill is licensed under [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)](https://creativecommons.org/licenses/by-sa/4.0/). You are free to share and adapt this material provided you give appropriate credit to Jeb Blount and BookForge, and distribute any derivative works under the same license.

## Related BookForge Skills

- `prospecting-message-crafter` — build the bridge and because for the conversation once you are through the gate; `clawhub install bookforge-ai/bookforge-skills/prospecting-message-crafter`
- `cold-call-opener-builder` — deploy the 5-step telephone framework (attention → identify → reason → bridge → ask) once you reach the decision maker
- `prospecting-rbo-turnaround` — handle reflex responses and brush-offs after the opener lands
- `in-person-prospecting-route-planner` — plan hub-and-spoke territory routes that include go-around-back opportunities

---
name: cold-email-writer
description: |
  Write a complete cold prospecting email — subject line, body, and send-time recommendation — using Blount's AMMO planning framework and Hook-Relate-Bridge-Ask body structure from Fanatical Prospecting.

  Trigger this skill when you need to:
  - Write a cold email, prospecting email, or sales introduction email
  - Write an email to a prospect you have never contacted before
  - Improve an existing prospecting email that is not getting replies
  - Apply the AMMO framework (Audience / Method / Message / Outcome) to email planning
  - Build a Hook-Relate-Bridge-Ask email body that converts
  - Fix a subject line that is too long, uses a question mark, or is getting ignored
  - Check an email against the Three Cardinal Rules: Get Delivered / Get Opened / Get Converted
  - Improve email open rate, reply rate, or click-to-response conversion
  - Write a subject line under 50 characters with an action word, not a question
  - Understand what spam trigger words to avoid in a prospecting email
  - Run an email deliverability pre-check before sending
  - Write a post-trigger-event email to a prospect who just changed jobs, raised funding, or announced growth
  - Write a new-territory introduction email to a segment you have never contacted
  - Produce a complete send-ready email draft the user can send as-is or edit minimally
  - Apply the "AMMO email", "three cardinal rules email", or "Hook-Relate-Bridge-Ask" frameworks
  - Increase reply rate or reduce the number of cold emails going unanswered
  - Understand why "Hi [Name], I was browsing LinkedIn" emails get deleted immediately

  NOT for: building the core WIIFM bridge and because message nucleus that feeds this email
  (use prospecting-message-crafter first), or setting the email objective before writing
  (use prospecting-objective-setter). This skill produces a complete, send-ready email — not
  just the message component.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/fanatical-prospecting/skills/cold-email-writer
metadata:
  openclaw:
    emoji: "📚"
    homepage: "https://github.com/bookforge-ai/bookforge-skills"
status: published
source-books:
  - id: fanatical-prospecting
    title: "Fanatical Prospecting"
    authors:
      - Jeb Blount
    chapters:
      - 19
tags:
  - sales
  - prospecting
  - cold-email
  - copywriting
  - sdr
  - bdr
  - email-marketing
depends-on:
  - prospecting-objective-setter
  - prospecting-message-crafter
execution:
  tier: 2
  mode: full
  inputs:
    - type: document
      description: "Target prospect context (role, company, industry, any known trigger events), user's value prop or ICP, desired objective (appointment / qualifying info / referral / direct sale), and optionally a current email draft to improve. Paste inline or point to a .md or .txt file."
  tools-required: [Read, Write]
  tools-optional: [WebFetch]
  mcps-required: []
  environment: "Document directory — reads user-provided context files; writes cold-email-draft-{prospect}.md to the working directory"
discovery:
  goal: "Produce a complete, send-ready prospecting email with subject line, annotated body using Hook-Relate-Bridge-Ask structure, and send-time recommendation — that passes all Three Cardinal Rules (Delivered / Opened / Converted)"
  tasks:
    - "Gather prospect context, value prop, objective, and any existing draft"
    - "Build or confirm the AMMO plan: Audience / Method / Message / Outcome"
    - "Run deliverability pre-check: no bulk, no images, no attachments, limited URLs, no spam triggers, scrub bounces"
    - "Craft subject line: 40-50 characters, action word, no question mark, prospect-centric"
    - "Draft body with Hook-Relate-Bridge-Ask structure"
    - "Run Three Cardinal Rules quality gate and anti-pattern check"
    - "Produce final annotated email plus send-time suggestion"
    - "Write output to cold-email-draft-{prospect}.md"
  audience:
    roles: [sdr, bdr, ae, founder-self-seller]
    experience: beginner-to-intermediate
  when_to_use:
    triggers:
      - "Writing the first prospecting email to a new prospect or segment"
      - "Cold email reply rate is below 3% and you want to diagnose and fix it"
      - "Someone asks 'write an email to a prospect' or 'can you draft a sales email'"
      - "A trigger event just occurred (funding, new hire, expansion) and you want to send a timely email"
      - "Entering a new territory and need an introduction email template for a segment"
      - "Current email has a long subject line, contains a question in the subject, or starts with 'Hi [Name], I was...'"
      - "User wants to apply AMMO, Hook-Relate-Bridge-Ask, or Three Cardinal Rules to a draft"
    prerequisites:
      - "Prospect role, company, and industry — minimum required"
      - "Your value proposition or the outcome you help deliver — required"
      - "Desired outcome of this email touch — required"
    not_for:
      - "Building the underlying WIIFM bridge and because message (use prospecting-message-crafter)"
      - "Defining which objective to target before emailing (use prospecting-objective-setter)"
      - "Handling objections or non-replies in an email sequence (use prospecting-rbo-turnaround)"
      - "Multi-touch email cadence design — this skill writes the first email; sequence design is a separate skill"
  environment:
    codebase_required: false
    codebase_helpful: false
    works_offline: true
  quality:
    scores:
      with_skill: 0
      baseline: 0
      delta: 0
    tested_at: ""
    eval_count: 0
    assertion_count: 0
    iterations_needed: 0
    what_skill_catches:
      - "Applies AMMO planning framework (Audience / Method / Message / Outcome) before writing"
      - "Produces subject line that is 40-50 characters with an action word, no question mark"
      - "Uses Hook-Relate-Bridge-Ask body structure throughout"
      - "Runs Three Cardinal Rules quality gate (Delivered / Opened / Converted) before finalizing"
      - "Removes self-centered framing ('Hi [Name], I was browsing LinkedIn', 'I'd love to')"
      - "Removes feature dumps and replaces with prospect-centric bridge and WIIFM answer"
      - "Includes a 'because' reason that answers WIIFM — not just a value prop statement"
      - "Writes an assumptive, specific ask with a proposed day/time"
      - "Uses disruption in the ask ('I don't know if we're a fit') to reduce resistance"
      - "Checks and removes spam trigger words from subject and body"
      - "Enforces one-to-one send discipline and no attachments / images / multiple links"
      - "Addresses prospect by name only — no 'Hi', 'Hello', or 'Dear' salutations"
    what_baseline_misses:
      - "Produces a subject line with 70+ characters or a question mark"
      - "Opens with 'Hi [Name], I wanted to reach out' or 'I was browsing LinkedIn'"
      - "Writes a feature dump or company cheerleader paragraph as the email body"
      - "Does not give a 'because' reason — just states capabilities"
      - "Puts the burden on the prospect to schedule: 'let me know what works for you'"
      - "Includes images, attachments, or multiple links that trigger spam filters"
      - "Does not check spam trigger words — includes 'free', 'guaranteed', or ALL CAPS"
      - "Does not apply AMMO planning — sends the same template regardless of audience or objective"
---

# Cold Email Writer

## When to Use

You need to send a cold prospecting email to a prospect — and you want it to actually get a reply.

The average business executive receives 200+ emails per day (Harvard Business Review). Your email will be scanned in under three seconds. It will be deleted unless the subject line is compelling, the opening sentence is about the prospect (not you), and the body answers one question: *What's in it for me?*

This skill writes the complete email — subject line through closing ask — using three interlocking frameworks from Blount's *Fanatical Prospecting*:

1. **AMMO plan** — audience, method, message, outcome — before writing a word
2. **Deliverability pre-check** — so the email reaches the inbox, not the spam folder
3. **Hook-Relate-Bridge-Ask body** — the four-element structure that converts

**This skill is downstream of two dependencies:**
- `prospecting-objective-setter` — defines what you are asking for (appointment / info / referral / close)
- `prospecting-message-crafter` — builds the bridge and WIIFM nucleus that feeds the email body

If you have not run those skills, this skill will gather the required context itself. The AMMO plan subsumes both.

## Context & Input Gathering

Before writing, gather (or ask the user for):

**Required:**
1. **Prospect context** — role, company, industry; any known trigger events (funding, expansion, new hire, press coverage, competitor churn)
2. **Your value prop** — the one outcome you deliver that is most relevant to this prospect's world
3. **Desired outcome** — what action do you want the prospect to take? (schedule a call / give qualifying info / agree to a meeting / download / reply)
4. **Familiarity level** — have you called, connected on LinkedIn, or met in person before sending this email? (affects open probability and subject line strategy)

**Helpful (read from working directory if available):**
- `icp.md` — ideal customer profile with decision-maker roles and pain points
- `value-prop.md` — your value proposition and strongest client outcomes
- `prospect-notes.md` — any research on this specific prospect
- `current-draft.md` — an existing email draft to diagnose and improve

**Defaults:** If no files are provided, the skill asks the user directly. Two to three sentences about the prospect and what you sell is enough to begin.

## Process

### Step 1 — Build the AMMO Plan

**WHY:** Most prospecting emails fail because the sender skipped planning. A good email begins with a clear plan, not a blank subject line. AMMO prevents generic outreach that wastes time and burns sender reputation.

Answer the four AMMO questions before writing:

**A — Audience**
- Who is this person? Role, title, seniority, industry
- How busy are they? An executive receiving 200+ emails/day needs a shorter, more compelling email than a mid-level manager
- What do you know about their style? Do they post publicly on LinkedIn? Do they respond to data or to emotional language?
- How familiar are they with you? (Zero familiarity = prioritize subject line and hook. Some familiarity = you have more latitude in the opening)
- What problems are they likely sitting with right now?

**M — Method**
- Is this a standalone cold email, or part of a multi-touch Strategic Prospecting Campaign (SPC)?
- What tone fits: direct and brief? Soft and value-led? Hard-hitting with data?
- Should this be personalized 1:1 (conquest or C-level) or mass-customized from a template (large similar-prospect pool)?

**M — Message**
- What is the bridge? The *because* that connects their world to what you offer
- What value category fits: emotional (anxiety/relief), insight/curiosity (competitive edge), or tangible/logic (specific ROI data)?
- What language does this prospect use? Speak their jargon — COOs talk about *growth, risk, complexity, regulatory surprises*; CISOs talk about *exposure, board accountability, click rates, audit findings*

**O — Outcome**
- What is the exact action you want them to take?
- Make the outcome specific: *schedule a 20-minute call on Thursday at 3 PM* — not *connect sometime*
- Desired outcomes for prospecting email: appointment / qualifying information / introduction to a decision maker / download or webinar registration / reply that opens a sales conversation

**Output of Step 1:** A four-line AMMO summary that shapes every word of the email.

---

### Step 2 — Deliverability Pre-Check

**WHY:** An email that reaches the spam folder converts at zero. Deliverability failures are silent — the prospect never sees the message and you never know why. Run this check before writing a single word of body copy.

Run through the deliverability checklist. Each item is binary pass/fail:

- [ ] **One-to-one only** — this email goes from your address to one individual. Never bulk-send a prospecting email from a personal address. This alone clears 90% of spam hurdles
- [ ] **No images** — spam filters treat embedded images as potential malware vectors. Avoid them entirely in prospecting emails
- [ ] **No attachments** — same reason. Hackers use attachments to install malware; spam filters know this
- [ ] **Minimal hyperlinks** — ideally zero. If you must include a link: use the full URL (no shortened URLs), avoid embedding it in hyperlink text, and include at most one link total including your signature
- [ ] **No spam trigger words** — see `references/spam-trigger-wordlist.md` for the full list. Key offenders: *free, amazing, guaranteed, 100% guaranteed, do it today, increase sales, cash, save $, act now, click here*, ALL CAPS, excessive exclamation points
- [ ] **Not sending to multiple people at the same company simultaneously** — if you are emailing several contacts at one company, stagger them throughout the day
- [ ] **Scrub bounced addresses** — if an address has bounced before, remove it from your list and update your CRM before sending. Repeated sends to dead addresses trigger blacklisting
- [ ] **Extra caution for sensitive industries** — financial institutions, defense contractors, healthcare: use plain text only with no links, no images, no attachments

**If any item fails, fix it before proceeding.**

---

### Step 3 — Craft the Subject Line

**WHY:** The subject line is the gatekeeper. More than 50% of emails are opened on mobile, where the subject line is often the only thing visible. Subject lines over 50 characters see exponentially lower open rates. The three most common subject line mistakes — too long, contains a question, generic/impersonal — all send the email to the delete pile before the prospect reads a word.

**Subject line rules:**
- **Length:** 3–6 words or 40–50 characters including spaces. Under 50 characters is the hard ceiling
- **No question marks** — questions in subject lines consistently underperform across major email studies. Use action words and directive statements instead
- **Action word or pattern** — strong subject line patterns that work:
  - List-based: *"3 Reasons ABC Corp Chose Us"*
  - Referral: *"[Mutual Contact] Said We Should Talk"*
  - Role + problem: *"COO — The Toughest Job in the Bank"*
  - Trigger event: *"Your Q3 Expansion — One Risk to Watch"*
  - Compliment: *"Loved Your Post on [Topic]"*
- **Prospect-centric** — the subject line is about their world, not your product. "Cloud Based Software" is about you. "COO — The Toughest Job in the Bank" is about them
- **No salutation words** — never open the email body with "Hi", "Hello", or "Dear". No one in business uses these except salespeople. Address the prospect by name only: "Lawrence,"

**After drafting the subject line:** Count the characters. If it is over 50, cut it. If it ends with a question mark, rewrite it as a statement. If it contains your company name or product name, reconsider — the subject is about the prospect, not the sender.

---

### Step 4 — Draft the Body Using Hook-Relate-Bridge-Ask

**WHY:** Each of the four elements serves a specific conversion function. Skipping or collapsing any element breaks the sequence. The Hook earns the read. The Relate earns the emotional connection. The Bridge earns the time. The Ask earns the action.

**Hook — the opening sentence and subject line working together**

The subject line gets the email opened. The first sentence must keep them reading. You have about three seconds.

Rules for the opening sentence:
- About the prospect, not you
- Use a credible third-party source if possible (industry report, research data, peer group insight)
- No "I was browsing LinkedIn and wanted to reach out" — this is about you, not them
- No "Hi [Name]," salutation
- Connect immediately to something they care about

Example: *"Ernst & Young recently reported that the COO has the toughest role in the C-suite."* — this hooks a COO because it validates their daily reality with a credible source.

**Relate — demonstrate that you understand their world**

Show empathy. Demonstrate that you have done enough research to understand their situation. You are not pitching yet — you are showing that you get them.

Rules:
- Step into their shoes before writing this section
- If you have never been in their role, use surrogate credibility: *"The [role]s I work with tell me that..."*
- Avoid feature dumps — this section is not about your product
- Use emotional language: *harder, more stressful, more complex, overwhelming, at risk*

Example: *"The COOs I work with tell me that the increasing complexity of the banking environment has made their job harder and more stressful than ever."*

**Bridge — answer WIIFM (What's In It For Me)**

This is the most important sentence in the email. It answers the prospect's most pressing question: if I give you my time, what do I get?

Rules:
- Connect their specific problem (from the Relate section) to the specific outcome you deliver
- Use their language — speak the jargon of their role and industry
- Include a value proof point when possible: a client name, an outcome number, a relevant industry result
- Do not brag about your company, your awards, or your growth — "so what?" test: if the prospect's internal response is "so what?", rewrite

Bridge structure: *[I help] [people like you] [achieve specific outcome] [by/with specific approach]*

Example: *"My team and I help COOs like you reduce complexity and stress with strategies to optimize growth and profit, mitigate credit risk, allocate resources effectively, and minimize regulatory surprises."*

**Ask — direct, specific, low-resistance**

Every prospecting email must end with a direct ask. Make it easy for the prospect to say yes. Make it hard for them to avoid responding.

Rules:
- Propose a specific day and time: *"How about next Thursday at 3:00 PM?"* — not *"let me know when you're available"*
- Use assumptive framing: "How about..." assumes the meeting will happen. It is not asking if the meeting can happen
- Use disruption to lower resistance: *"While I don't know if we're a good fit for your situation..."* — this unexpected admission of uncertainty disarms the prospect's defenses and pulls them toward you instead of pushing them away
- Keep it short — the ask is one or two sentences, not a paragraph
- Do not add a second ask or a list of options. One ask only

Example: *"While I don't know if we are a good fit for your bank, why don't we schedule a short call to help me learn more about your unique challenges? How about next Thursday at 3:00 PM?"*

---

### Step 5 — Quality Gate: Three Cardinal Rules + Anti-Pattern Check

**WHY:** Before writing the final email, run the completed draft through a structured quality gate. Most prospecting emails fail one of these three rules. Catching the failure before sending saves your sender reputation and the prospect's patience.

**Rule 1: Will it get delivered?**
Re-run the deliverability checklist from Step 2 against the drafted email. Confirm no images, no attachments, no bulk send, no spam trigger words have crept into the body or subject.

**Rule 2: Will it get opened?**
- Subject line is 40–50 characters or fewer ✓/✗
- No question mark in subject line ✓/✗
- Subject line is about the prospect, not the sender ✓/✗
- No "Hi", "Hello", or "Dear" salutation ✓/✗

**Rule 3: Will it convert?**
Check the body against the five worst email patterns (immediate disqualifiers):
- [ ] Long, important-sounding pitch using incomprehensible jargon — no meaning, all words
- [ ] Feature dump — list of product capabilities with no prospect relevance
- [ ] Company cheerleader — "we are the #1 provider / we've been voted most innovative / we have 3 years on the INC 5000"
- [ ] Wrong name or missing name (Lawrence vs. Jim)
- [ ] Eye-glazing length — if the email requires scrolling on mobile, it is too long

**Hook-Relate-Bridge-Ask completeness check:**
- Does the opening sentence hook the prospect? Is it about them, not you? ✓/✗
- Does the Relate section show genuine empathy for their situation? ✓/✗
- Does the Bridge answer their WIIFM question? ✓/✗
- Does the Ask propose a specific day/time with assumptive framing? ✓/✗

**Fix any failures before moving to Step 6.**

---

### Step 6 — Produce Final Email + Send-Time Recommendation

**WHY:** The formatted, annotated final email is the artifact the user sends. Annotations explain the "why" behind each element so the user can adapt the structure to future emails. The send-time recommendation increases the probability the email is read when it arrives.

**Output format:**

Write the final email with each section labeled (for the user's reference, to be stripped before sending):

```
Subject: [40-50 chars, action word, no question mark]

[Prospect last name],

[HOOK — opening sentence using credible source or prospect-relevant trigger, about them not you]

[RELATE — 1-2 sentences showing you understand their specific problem, using their language]

[BRIDGE — 1-2 sentences connecting their problem to the outcome you deliver; answers WIIFM; uses their industry jargon]

[ASK — 1-2 sentences with disruption framing + specific proposed day/time]

[Your name]
[Title]
[Company]
```

**Send-time guidance:**
- **B2B prospects:** first thing in the morning to mid-morning — prospects are fresh and handling email
- **B2C prospects:** adjust to when your prospect is most likely to take immediate action on your request
- **Schedule ahead:** write emails outside Golden Hours (prime selling time) and schedule them to send during peak reading windows, so your selling hours stay on the phone and in meetings

**Write the output to `cold-email-draft-{prospect-name}.md`** in the working directory. Include:
- The send-ready email with labels stripped
- An annotated version showing each Hook / Relate / Bridge / Ask element with a one-line explanation
- The AMMO plan summary
- The deliverability check result
- The Three Cardinal Rules gate result

---

## Inputs

| Input | Required | Source |
|---|---|---|
| Prospect role, company, industry | Yes | User provides or prospect-notes.md |
| Your value prop / outcome delivered | Yes | User provides or value-prop.md |
| Desired outcome of this email | Yes | User provides or prospecting-objective-setter output |
| Known trigger events at this account | No — strengthens the Hook | User provides or WebFetch research |
| Current draft email to improve | No — skill builds from scratch | User pastes inline or file path |
| Familiarity level with this prospect | No — affects subject line strategy | User states |

## Outputs

| Output | Location | Description |
|---|---|---|
| `cold-email-draft-{prospect}.md` | Working directory | Send-ready email + annotated version + AMMO plan + deliverability and quality gate results |
| Inline diagnosis | Conversation | If a draft was provided: labeled list of what failed and why, before the rewrite |

---

## Key Principles

**1. The Three Cardinal Rules are a funnel, not a checklist.** An email that does not get delivered converts at zero. An email that gets delivered but not opened converts at zero. Only an email that clears all three rules has a chance to convert. Apply them in sequence — deliverability first, open rate second, conversion third.

**2. AMMO before writing.** The fastest path to a bad prospecting email is opening a blank message and typing. The fastest path to a good one is spending two minutes on AMMO: who is this person, what method fits, what message will connect, what outcome am I after. Planning takes two minutes. Rewriting a bad email that burned a prospect takes permanently.

**3. Subject lines over 50 characters get deleted.** Over 50% of emails are opened on mobile. A subject line cut off at character 40 on a mobile screen defeats itself. Three to six words is the target. Less is more — always.

**4. Never use a question mark in a subject line.** Every major email study confirms this. Questions doom emails to the delete pile. Use action words and directive statements. *"COO — The Toughest Job in the Bank"* outperforms *"Can we help reduce your complexity?"* on every metric.

**5. The email is about the prospect, not you.** The subject line is about them. The opening sentence is about them. The relate section is about their problems. The bridge connects their world to your solution. The ask makes it easy for them. Only the signature is about you. Read your draft and count the sentences that start with "I" or "We" — each one is a red flag.

**6. Disrupt expectations in the ask.** Blount's COO example uses a counterintuitive ask: *"While I don't know if we are a good fit for your bank..."* This disarms the prospect. They expect a pushy pitch. Getting the opposite — honesty about uncertainty — pulls them toward you instead of triggering resistance. Disruption plus a specific proposed time outperforms a confident pitch every time.

**7. One-to-one only — always.** Bulk-sending a prospecting email from your personal address is the fastest path to being blacklisted and looking like a beginner. One email. One recipient. One send. That discipline alone clears 90% of spam hurdles.

---

## Examples

---

### Example 1 — Bad-to-Good Rewrite (Based on Dave vs. Brandon, Fanatical Prospecting pp. 246–250)

**Situation:** Software sales rep sending a cold email to the CEO of a growing software consultancy.

**Original (Brandon's approach — fails all three rules):**

> Subject: Cloud Based Software
>
> Hi Jeb,
>
> I was browsing LinkedIn and wanted to reach out to you.
>
> We build custom software solutions; web, cloud, mobile, desktop. Whether you have need to modernize outdated software, build something new from scratch, or augment your team to meet a critical deadline, I'm confident we can help.
>
> We've been able to figure out how to maintain high quality and keep our rates competitive. It's a model that has led us to three straight years on the INC 5000.
>
> I'd love to schedule a time to connect and outline how we're able to do this while discussing any projects or plans you might have. Just let me know a time that works with your schedule for a free consultation & quote.

**What fails:**
- Subject line: "Cloud Based Software" — about the sender, not the recipient; contains a spam-adjacent term; says nothing about the prospect's world
- "Hi Jeb" — "Hi" is a sales turnoff; no one in business uses this except salespeople
- "I was browsing LinkedIn and wanted to reach out" — about the sender; "wanted" is past tense and self-focused; gives the prospect zero reason to keep reading
- Body: feature dump — *web, cloud, mobile, desktop* — answers nobody's question
- Relate attempt: company cheerleading about INC 5000 — "so what?" — why does the prospect care?
- Ask: "I'd love to..." — self-centered; "just let me know a time" puts the burden on the prospect; "free consultation" signals desperation
- No AMMO planning visible; same email could be sent to anyone

**Rewritten (applying AMMO + Hook-Relate-Bridge-Ask):**

> Subject: Custom Software Risk in a Scaling Firm
>
> Jeb,
>
> Gartner reports that 72% of custom software projects at growing firms run over budget or miss deadlines — most often because augmentation decisions are made under deadline pressure rather than strategic fit.
>
> The CEOs I work with at software consultancies tell me that managing build vs. augment decisions while keeping delivery quality consistent is one of the most stressful parts of scaling.
>
> My team works specifically with growing software firms to reduce delivery risk and keep margins intact as headcount scales — without the 3-month ramp time of traditional augmentation.
>
> While I don't know if we're dealing with the same issues at your firm, I'd like to spend 20 minutes finding out. How about Thursday at 2:00 PM?
>
> Brandon
> Senior Account Executive
> SoftCo

**Annotation:**
- Subject: 43 characters, action word ("Risk"), prospect-centric, no question mark
- Hook: third-party data, relevant to CEO's world, no "Hi"
- Relate: surrogate empathy ("The CEOs I work with tell me..."), emotional language ("most stressful"), speaks CEO language
- Bridge: answers WIIFM with specific outcome (delivery risk + margins + ramp time), uses their jargon
- Ask: disruption framing ("I don't know if..."), specific day/time, assumes the meeting happens

---

### Example 2 — New Territory Introduction Email (SDR / SaaS / VP of Operations Target)

**Situation:** SDR at a logistics software company entering the mid-market manufacturing vertical. No prior contact with any prospect in this segment.

**AMMO plan:**
- Audience: VP Operations, 200-500 person manufacturer, likely managing inventory and fulfillment
- Method: standalone cold email, Targeted bridge (large pool, inferred pain from industry trends)
- Message: operational complexity during inventory unpredictability is their primary stress point
- Outcome: 20-minute discovery call

**Email:**

> Subject: Inventory Visibility — 3 Patterns We See in Manufacturing
>
> [Prospect first name],
>
> A recent APICS report found that mid-size manufacturers lose an average of 11% of annual revenue to inventory errors — most of them invisible until they hit the production floor.
>
> Operations leaders I work with in manufacturing describe the same pain: they have data in three different systems and still can't tell in real-time where a delay is coming from.
>
> We help VP Operations teams at mid-market manufacturers get a single real-time view across procurement, warehousing, and fulfillment — which typically cuts emergency-order costs by 20–40% in the first quarter.
>
> I don't know if inventory visibility is a priority right now, but I've been working in this segment and have some benchmarks from your industry I thought might be worth a quick conversation. How about 20 minutes next Tuesday at 10 AM?
>
> [Name]
> [Title]
> [Company]

**Annotation:**
- Subject: 45 characters, "3 Patterns" creates curiosity, prospect-centric
- Hook: APICS data + manufacturing-specific (not generic software pitch)
- Relate: "Operations leaders I work with tell me..." — surrogate empathy + their language (three systems, real-time, production floor)
- Bridge: specific outcome (20–40% emergency-order cost reduction) + connects to their role jargon
- Ask: disruption framing, "benchmarks from your industry" adds curiosity value, specific Tuesday at 10 AM

---

### Example 3 — Post-Trigger-Event Email (AE / HR Tech / New CHRO at a Growth-Stage Company)

**Situation:** AE at an HR platform company. LinkedIn shows a new CHRO just joined a 300-person SaaS company that recently raised a Series B. The company is publicly hiring aggressively.

**AMMO plan:**
- Audience: newly appointed CHRO, starting fresh at high-growth company with mandate to build
- Method: strategic 1:1 email, personalized to trigger event
- Message: new CHROs in high-growth environments face hiring speed vs. quality tradeoff under board pressure
- Outcome: 30-minute discovery call

**Email:**

> Subject: New CHRO + Series B — One Decision That Compounds
>
> Lisa,
>
> Congratulations on joining Acme and on the Series B. A CHRO stepping in at this stage faces a specific challenge: you need to scale the team fast enough to satisfy the board while building the infrastructure that prevents a bad-hire crisis at 500 employees.
>
> New CHROs I work with at Series B companies tell me the first 90 days are critical — whatever hiring system is in place when headcount doubles tends to harden into permanent process, good or bad.
>
> We help CHROs at growth-stage companies build a scalable hiring system in the first 90 days — so that adding 100 people doesn't add 100 points of chaos.
>
> I know you're early and still finding your footing, but I've worked with several CHROs at this stage and have a framework I think would be useful to share. Would 30 minutes on Friday at 9 AM work?
>
> [Name]
> [Title]
> [Company]

**Annotation:**
- Subject: 42 characters, two trigger events (New CHRO + Series B) connected with an outcome word ("Compounds")
- Hook: congratulates without being sycophantic, immediately pivots to their challenge
- Relate: new-CHRO-specific empathy, 90-day language reflects her reality
- Bridge: "100 people doesn't add 100 points of chaos" — speaks her language, emotional + logical value
- Ask: "I know you're early" — disruption, respects her onboarding reality; specific Friday at 9 AM

*Note: this example bends the usual "no question mark" rule in the ask — the ask sentence uses "work?" which is acceptable when embedded in a two-sentence ask block with disruption framing. The subject line contains no question mark, which is the high-stakes rule. Applies judgment accordingly.*

---

## References

Detailed supporting materials are in the `references/` folder:

- `references/spam-trigger-wordlist.md` — full 200+ word/phrase list that triggers spam filters in subject lines and body copy (sourced from Comm100 research cited by Blount, p. 235)
- `references/deliverability-checklist.md` — expanded deliverability pre-check with per-industry notes (sensitive industries: financial, defense, healthcare)
- `references/subject-line-patterns.md` — library of subject line patterns with character counts, use cases, and tested examples: list-based, referral, role + problem, trigger event, compliment
- `references/email-examples-library.md` — complete annotated email examples by prospect role (COO, CFO, VP Sales, CISO, Operations Director, CHRO) and scenario type (new territory, post-trigger, re-engagement, referral introduction)
- `references/ammo-planning-worksheet.md` — AMMO planning worksheet with decision prompts for Audience, Method, Message, and Outcome; includes Targeted vs. Strategic bridge selection guide

**Source chapter:** Blount, Jeb. *Fanatical Prospecting*, Chapter 19 "E-Mail Prospecting" (pp. 232–252 / PDF pp. 232–252). Subject line data: pp. 238–241. AMMO framework: pp. 242–245. Hook-Relate-Bridge-Ask: pp. 245–252. Three Cardinal Rules: pp. 234–241. Dave vs. Brandon annotated contrast: pp. 246–250.

**Referenced external sources:**
- Harvard Business Review: average business executive receives 200+ emails per day (cited by Blount, p. 236)
- Gao, Kevin, CEO of Comm100: 200 spam trigger words/phrases (cited by Blount, p. 235)
- Lee, Kendra. *The Sales Magnet* — "glimpse factor" concept for opening sentences (cited by Blount, p. 247)

---

## License

Content derived from *Fanatical Prospecting* by Jeb Blount (Wiley, 2015). This skill is licensed under [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)](https://creativecommons.org/licenses/by-sa/4.0/). You are free to share and adapt this material provided you give appropriate credit to Jeb Blount and BookForge, and distribute any derivative works under the same license.

---

## Related BookForge Skills

**Upstream dependencies — use these before or alongside this skill:**

The message nucleus (WIIFM bridge and because) that feeds this email:
```
clawhub install bookforge-prospecting-message-crafter
```

The objective that drives the Ask in this email:
```
clawhub install bookforge-prospecting-objective-setter
```

**Downstream or parallel skills:**

For handling non-replies, brush-offs, or "send me more info" responses:
```
clawhub install bookforge-prospecting-rbo-turnaround
```

For building the full 5-step telephone follow-up after this email is sent:
```
clawhub install bookforge-cold-call-opener-builder
```

Browse the full Fanatical Prospecting skill set: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

---
name: cold-call-opener-builder
description: |
  Build a complete, annotated cold call opener script using the Five-Step Telephone Prospecting
  Framework from Blount's Fanatical Prospecting.

  Trigger this skill when you hear or ask:
  - "cold call opener" or "phone script" or "what do I say when they pick up"
  - "telephone prospecting" or "sales phone call" or "cold calling script"
  - "five-step opener" or "phone opener" or "voice mail opener"
  - "prospecting call framework" or "how do I open a cold call"
  - "write me a call script" or "SDR call opener" or "BDR phone script"
  - "what do I say on a cold call" or "cold call introduction script"
  - "how to start a sales call" or "telephone prospecting framework"
  - "call opener template" or "sales call opening lines"
  - "how to not fumble the first 10 seconds" or "call structure for outbound"
  - "voicemail script" or "gatekeeper script"

  This skill produces a fully annotated, ready-to-use 5-line phone opener script in
  Name → Identify → Reason → Bridge → Ask order — plus a voicemail variant and a gatekeeper
  variant. It enforces no "How are you today?" pause, silence after the ask, and an explicit
  "because" in the bridge. Output is an annotated script, not abstract advice.

  NOT for: building the underlying bridge/because message (use prospecting-message-crafter first),
  setting the call objective (use prospecting-objective-setter), or handling objections after the
  opener (use prospecting-rbo-turnaround).
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/fanatical-prospecting/skills/cold-call-opener-builder
metadata:
  openclaw:
    emoji: "📚"
    homepage: "https://github.com/bookforge-ai/bookforge-skills"
status: published
source-books:
  - id: fanatical-prospecting
    title: "Fanatical Prospecting"
    authors:
      - Jeb Blount
    chapters:
      - 15
tags:
  - sales
  - prospecting
  - cold-calling
  - phone-scripts
  - sdr
  - bdr
depends-on:
  - prospecting-objective-setter
  - prospecting-message-crafter
execution:
  tier: 2
  mode: hybrid
  inputs:
    - type: document
      description: "User's product/value prop, target prospect info, stated call objective. Can also accept output files from prospecting-objective-setter (prospecting-objective-plan-{date}.md) and prospecting-message-crafter (prospecting-message-output.md)."
  tools-required: [Read, Write]
  tools-optional: []
  mcps-required: []
  environment: "Document directory with prospect notes and value prop. If upstream skill outputs exist in the working directory, read them first."
discovery:
  goal: "Produce a complete, annotated 5-step phone opener script with a voicemail variant and a gatekeeper variant, ready to use on a live call"
  tasks:
    - "Gather or read upstream skill outputs: call objective and bridge/because"
    - "Confirm no prohibited patterns (How are you today?, pause, pitch vomit) are in any draft"
    - "Draft Line 1: prospect name only, no pause"
    - "Draft Line 2: your name + company, immediate and transparent"
    - "Draft Line 3: 'The reason I'm calling is...' — direct statement of intent"
    - "Draft Line 4: bridge using the because from prospecting-message-crafter output"
    - "Draft Line 5: assumptive ask matched to the objective, then silence"
    - "Write annotated opener + voicemail variant + gatekeeper variant to cold-call-opener-script.md"
  audience:
    roles: [sdr, bdr, ae, founder-self-seller]
    experience: beginner-to-intermediate
  triggers:
    - "Rep is building a cold call opener for a new product or prospect segment"
    - "Current opener is generating 'not interested' in the first 3 seconds"
    - "Rep wants a script they can actually say out loud without sounding scripted"
    - "Preparing for a cold calling block and needs a repeatable framework"
    - "Voicemail return rate is near zero and rep needs a better structure"
  prerequisites: []
  not_for:
    - "Building the bridge/because message from scratch — run prospecting-message-crafter first for the message nucleus"
    - "Deciding what objective to go for on the call — run prospecting-objective-setter first"
    - "Handling the RBO that comes after the opener — use prospecting-rbo-turnaround"
    - "Writing a full email cadence — use prospecting-email-writer"
  quality:
    scores:
      with_skill: 0
      baseline: 0
      delta: 0
    tested_at: ""
    eval_count: 0
    assertion_count: 0
    iterations_needed: 0
    what_skill_catches:
      - "Uses the 5-step Name→Identify→Reason→Bridge→Ask structure verbatim"
      - "Never inserts 'How are you today?' pause — the #1 control-killer on cold calls"
      - "Enforces silence after the ask — does not fill the pause with pitch vomit"
      - "Produces an annotated script, not abstract advice about what to do"
      - "Includes the word 'because' explicitly in the bridge line"
      - "Ask matches the stated call objective (appointment / qualifying info / direct sale)"
      - "Provides voicemail and gatekeeper variants alongside the live-answer script"
      - "Natural tone — does not sound scripted or robotic"
    what_baseline_misses:
      - "Inserts 'How are you today?' pause, handing control to the prospect's escape instinct"
      - "Does not structure the call in the 5-step order — wanders into pitch before stating reason"
      - "No explicit 'because' in the bridge — gives the prospect no reason to keep listening"
      - "Keeps talking after the ask instead of going silent — generates resistance and gives an easy out"
      - "Does not produce a voicemail variant or gatekeeper variant"
      - "Produces advice about calling instead of a ready-to-use script"
---

# Cold Call Opener Builder

## When to Use

You are about to pick up the phone and call someone who is not expecting your call. You have
10 seconds to establish why they should keep listening instead of getting off the phone.

This skill applies to any outbound phone touch where the prospect has not requested the call —
cold calls, warm calls, follow-up dials, and calls to inbound leads that haven't been spoken to
yet. It produces a **complete, annotated script** you can read aloud during a live call, not a
framework you have to interpret.

Use this skill when:
- You are building a call opener for a new product or prospect segment
- Your current opener is getting "not interested" before you finish your second sentence
- You want a voicemail you can leave that actually gets returned
- You are running a prospecting block and want a repeatable, confident structure
- You just ran `prospecting-objective-setter` and/or `prospecting-message-crafter` and are
  ready to assemble the final call script

**Dependency chain:** This skill is most effective when run after `prospecting-objective-setter`
(which determines your call objective and the ask you make in Step 5) and
`prospecting-message-crafter` (which produces the bridge and because for Step 4). If you do not
have those outputs, this skill will gather the same inputs directly.

## Context & Input Gathering

Before building the opener, collect the following. Read from working directory files if available,
otherwise ask the user directly.

**From `prospecting-objective-plan-{date}.md` (prospecting-objective-setter output) or ask:**
1. Call objective — what are you going for? Appointment / qualifying information / direct sale
2. The prospect's role, company, and industry (or a 1-sentence profile)

**From `prospecting-message-output.md` (prospecting-message-crafter output) or ask:**
3. Bridge type — Targeted (large prospect pool, inferred pain) or Strategic (conquest/C-level,
   researched)
4. The bridge sentence — the prospect-facing reason you are calling (their world, not yours)
5. The explicit "because" — the specific trigger event, insight, or outcome that earns their time
6. Your name and company name

**If no upstream outputs exist:** Ask the user for items 1–6 directly. A two-to-three sentence
verbal description of the selling situation is sufficient to proceed.

**Sufficiency threshold:** Items 1, 2, 4, and 6 are required. Items 3 and 5 can be derived from
item 4 if the user has a clear bridge statement.

## Process

### Step 1 — Confirm the Call Objective

**Action:** State the call objective explicitly and confirm it matches the correct scenario from
Blount's Four Objectives framework:

| Objective | When to use |
|---|---|
| Set an appointment | Complex/high-cost product, any channel; transactional product via outside-sales remote channel |
| Gather qualifying information | Unqualified prospects; contract-gated products; new territory |
| Close the sale directly | Transactional/low-cost product, inside sales channel or outside-sales in-person |
| Build familiarity | Cold prospects requiring 20–50 touches; secondary objective on most calls |

The objective drives the ask in Step 5. A mismatch here — for example, going for a close with a
complex product — wastes the call and confuses the prospect.

**WHY:** The ask is the only mechanism that produces a result. If the ask does not match what is
actually possible given the product, channel, and prospect qualification state, the call succeeds
technically (you delivered the opener) but fails commercially (you cannot get a yes). Confirming
the objective before writing Line 5 prevents this mismatch. (See `prospecting-objective-setter`
for the full Four Objectives decision framework.)

---

### Step 2 — Draft Line 1: Get Their Attention with Their Name

**Action:** Write Line 1 as exactly: `Hi, [Prospect First Name].`

No more. No "How are you today?" No pause. No preamble. Say their name and immediately
move to Line 2 without stopping.

**Why no "How are you today?" pause:** When you interrupt someone's day and then say
"How are you today?" and pause, the prospect has a split second to realize you are a salesperson
and that they made a mistake answering the phone. Their escape instinct kicks in — they hit you
with "Not interested" or "Who is this?" before you have said anything meaningful. That pause
transfers control of the call to the prospect's fight-or-flight response. (Blount, p. 185)

**Why the name works:** Saying another person's name is the fastest attention-getter in human
communication. For a split second, the prospect's brain stops what it was doing and registers
your call. That window is your only chance to get to Lines 2–5 uninterrupted. (Blount, p. 185)

---

### Step 3 — Draft Line 2: Identify Yourself Immediately

**Action:** Write Line 2 as: `My name is [Your Name] and I'm with [Company Name].`

Say it immediately after the name. No pleasantries. No "I was hoping to catch you." No "Sorry
to bother you" (apologetic framing signals you expect rejection and lowers confidence before
you've said anything).

**WHY:** Transparency has two benefits. First, it establishes that you are a professional who
respects the prospect's time — idle chitchat before establishing who you are signals that you
are about to pitch. Second, telling prospects who you are reduces their stress because people are
more comfortable when they know what to expect. Not knowing who is calling is itself a source
of resistance. (Blount, p. 186)

---

### Step 4 — Draft Line 3: State the Reason You Are Calling

**Action:** Write Line 3 as: `The reason I'm calling is [direct statement of intent].`

The intent statement should be a plain, honest statement of purpose — not a pitch, not a feature
claim, and not a vague "I'd love to connect." Examples:

- `The reason I'm calling is to set up a brief meeting to learn about your sales recruiting situation.`
- `The reason I'm calling is I read that you are building a new restaurant location and I wanted to learn more about your equipment selection process.`
- `The reason I'm calling is you downloaded our white paper on landing page optimization and I'd like to understand what triggered your interest.`

**WHY:** Stating the reason clearly and early does two things. First, it continues the transparency
that Line 2 started — prospects are people who do not want to be tricked or manipulated, and
telling them why you called is the single most respectful thing you can do with their interrupted
time. Second, it gives their logical brain a foothold before their emotional resistance peaks. The
prospect knows what is happening and can evaluate whether to keep listening. (Blount, p. 186)

---

### Step 5 — Draft Line 4: Bridge — Give Them a Because

**Action:** Write Line 4 using the bridge/because from `prospecting-message-crafter` output
(or build it now if not available). The bridge connects what you want with why the prospect
should care — in their language, about their world.

The bridge must:
- Include the word "because" or an equivalent connector (e.g., "I've found that...", "I've been
  working with...") that gives them a concrete reason
- Reference their world: their industry, their role, a trigger event, a known pain, a competitive
  concern — not your product features
- Pass the "So what?" test: if the prospect heard this line and thought "So what? That's about
  you, not me" — rewrite it

Bridge patterns that work:
- Trigger event: `I saw that your company just announced [event] and I've been working with several [role] teams navigating [related challenge].`
- Inferred industry pain: `Most [role]s I work with tell me that [specific pain] is their biggest challenge right now, and I have [specific outcome] that my clients are using to address it.`
- Social proof: `I work with several [similar companies] and they've been getting [specific result], and I thought it might be relevant to your situation.`

Avoid at all costs:
- `I want to tell you about our product.`
- `I'd love to show you what we have to offer.`
- `We're the number one provider of...`
- Any statement that is about you, your company, or your quota.

**WHY:** People give up their time for their reasons, not yours. The bridge is the only part of
the opener where you can earn a yes before you ask for one. Without a because, you are
interrupting someone's day and asking them to give you their time for no stated reason. Langer's
copy-machine study established that giving any reason — even a weak one — increases compliance
from 60% to 93–94%. The bridge is where that reason lives. (Blount, pp. 168, 186; Langer cited
in prospecting-message-crafter)

---

### Step 6 — Draft Line 5: Ask for What You Want, Then Go Silent

**Action:** Write Line 5 as a direct, assumptive ask matched to the call objective, then stop
talking.

Ask patterns by objective:
- **Appointment:** `How about we meet [Day] at [Time]?` or `I'd like to set a short [15/20/30]-minute call — how does [Day] at [Time] work for you?`
- **Qualifying information:** `Can you tell me more about [specific situation] and when [decision process] typically begins?`
- **Direct sale:** `Let's go ahead and get you set up — I just need [two quick pieces of information].`

After the ask: **stop talking.** Do not fill the silence. Do not apologize for the call. Do not add
"I know you're busy" or "I don't want to take up too much of your time." Do not start explaining
your product. Say the ask, then go quiet and let the prospect respond.

**WHY:** The single biggest mistake on prospecting calls is continuing to talk after the ask.
When you keep talking, you give the prospect reasons to say no, you create objections that
haven't surfaced yet, and you signal that you are not confident in your ask. The silence is
where the yes lives. Silence after an assumptive ask is uncomfortable for the caller and
comfortable for the prospect — that discomfort is the signal that you are doing it correctly.
(Blount, p. 170)

**Why assumptive:** Assertive asks produce significantly higher yes rates than passive or hedging
asks. "Would it be okay if maybe sometime we could possibly get together?" signals that you
expect rejection. "How about Thursday at 2 PM?" signals that you expect yes. The prospect's
answer is heavily influenced by the confidence level embedded in the question. (Blount, p. 170;
prospecting-message-crafter Key Principles)

---

### Self-Check Before Writing Output

Before finalizing, verify the assembled script passes all five checks:

- [ ] **No "How are you today?" pause** — Line 1 is the prospect's name and nothing else
- [ ] **Explicit "because" in Line 4** — the bridge contains a reason in the prospect's world
- [ ] **Ask matches objective** — Line 5 is asking for the thing identified in Step 1
- [ ] **No pitch vomit in Lines 3–4** — no product features, company bragging, or self-centered framing
- [ ] **Script ends at the ask** — nothing after Line 5 except [silence]

If any check fails, revise the failing line before writing output.

---

### Write Output

Write the annotated script to `cold-call-opener-script.md` in the working directory. The output
must include:

1. **Live-answer script** — all 5 lines assembled and ready to read aloud, with each line labeled
2. **Voicemail variant** — 5-step voicemail framework (see below)
3. **Gatekeeper variant** — transparent, respectful gatekeeper opener (see below)
4. **Anti-pattern notes** — a brief list of anything removed or avoided and why

## Inputs

| Input | Required | Source |
|---|---|---|
| Call objective (appointment / info / close) | Yes | `prospecting-objective-plan-{date}.md` or user states |
| Prospect name, role, company | Yes | User provides |
| Your name and company | Yes | User provides |
| Bridge/because sentence | Yes | `prospecting-message-output.md` or user provides |
| Bridge type (Targeted vs Strategic) | Recommended | `prospecting-message-output.md` or user states |
| Known trigger event or industry pain | Recommended | User provides; enhances Line 4 significantly |

## Outputs

| Output | Location | Description |
|---|---|---|
| `cold-call-opener-script.md` | Working directory | Annotated live-answer script + voicemail variant + gatekeeper variant |
| Anti-pattern removal notes | Inline in conversation | What was avoided and why |

## Key Principles

**1. No pauses. No chitchat. Get to the point in 10 seconds.** The Five-Step framework is designed
to deliver the opener end-to-end without pausing. Any pause transfers control of the call to the
prospect's escape instinct. A focused, deliberate, no-pause delivery is more respectful of the
prospect's time than a chatty one — and more effective. (Blount, p. 184)

**2. Natural tone over scripted delivery.** The framework is a guide, not a word-for-word recitation.
A script read in a robotic monotone defeats its purpose. The opener should sound like a confident
professional delivering a clear, prepared message — not an actor reading lines. Internalize the
structure; adapt the words to your voice.

**3. The bridge earns the ask.** Lines 1–3 get you through the door; Line 4 earns the right to
make the ask in Line 5. A weak bridge produces RBOs before you reach Line 5. A strong bridge —
one that connects to the prospect's actual world — reduces resistance because the prospect now
has a reason to keep listening. (Blount, pp. 168–169)

**4. Silence is a close technique.** Shutting up after the ask is not passive — it is the
active mechanism that converts a pitch into a conversation. The prospect cannot say yes if you
are still talking. (Blount, p. 170)

**5. Consistency enables improvement.** A repeatable framework means you can isolate what is
working. If your bridge is weak, you will hear it in the RBOs. If your ask is passive, you will
hear it in the hesitation. A framework you stick to is a framework you can improve. (Blount, p. 183)

## Examples

### Example 1 — SaaS Enterprise Seller: Appointment Objective

**Situation:** SDR at a sales enablement platform. Target: VP of Sales at 100–500 person SaaS
companies. Objective: set a 20-minute discovery meeting. Bridge: ramp time anxiety (Targeted,
Emotional). Bridge/because from `prospecting-message-crafter`.

**Live-answer script:**

| Line | Step | Script |
|---|---|---|
| 1 | Get attention | `Hi, Mark.` |
| 2 | Identify | `This is Sarah with TechStack Pro.` |
| 3 | Reason | `The reason I'm calling is to set up a short meeting about your sales onboarding process.` |
| 4 | Bridge/Because | `I work with several SaaS VP Sales teams who are frustrated that new reps take 4 to 6 months to hit quota — and by the time they ramp, half of them are already questioning their decision to join. We've helped companies like Acme cut that ramp time by over 50 percent.` |
| 5 | Ask + silence | `I don't know if it's a fit in your situation, but I'd like to find out. How about 20 minutes on Thursday at 2 PM?` — [silence] |

**What was avoided:** "How are you today?" pause; "I'd love to show you"; product feature list.

---

### Example 2 — Restaurant Supply to SMB: Information-Gathering Objective

**Situation:** Outside sales rep at a commercial kitchen equipment company. Target: owner/operator
of a new restaurant under construction. Objective: gather information on their equipment selection
process and timeline. Bridge: trigger event (building permit in local paper).

**Live-answer script:**

| Line | Step | Script |
|---|---|---|
| 1 | Get attention | `Hi, Ian.` |
| 2 | Identify | `This is Jeb with Acme Restaurant Supply.` |
| 3 | Reason | `The reason I'm calling is I read in the paper that you're building a restaurant over on the 44 bypass, and I wanted to learn more about your process for selecting kitchen equipment.` |
| 4 | Bridge/Because | `I realize I'm calling a little early in the process. What I've found is that when our design team works with restaurant owners before critical decisions about kitchen layout are finalized, you end up with more options and can often save significant money in construction costs and future labor with a more efficient setup.` |
| 5 | Ask + silence | `Can you tell me how you typically make those decisions and when the selection process will begin?` — [silence] |

**What was avoided:** Leading with product features; pause after name; passive ask ("would it be
okay if maybe...").

---

### Example 3 — Benefits Broker to HR Director: Appointment Objective (Strategic Bridge)

**Situation:** AE at a benefits brokerage. Target: HR Director at a 300-person manufacturer.
LinkedIn shows they recently posted about rising healthcare costs. Renewal is in Q4 (identified
via prospecting-objective-setter). Objective: set a pre-renewal discovery appointment. Bridge:
Strategic (researched trigger event).

**Live-answer script:**

| Line | Step | Script |
|---|---|---|
| 1 | Get attention | `Hi, Patricia.` |
| 2 | Identify | `This is Alex with Meridian Benefits Group.` |
| 3 | Reason | `The reason I'm calling is to schedule a brief meeting before your Q4 benefits renewal.` |
| 4 | Bridge/Because | `I noticed you recently shared something about managing healthcare cost increases — that's exactly what I've been helping HR Directors at manufacturers address. I work with several companies your size who've reduced their cost per employee by 15 to 20 percent without cutting plan quality, and I have some benchmarks from your industry I thought might be worth a look.` |
| 5 | Ask + silence | `I don't know if we'd be a fit, but it seems worth a 20-minute conversation to find out. How about next Tuesday at 10 AM?` — [silence] |

**What was avoided:** Generic "I'd love to tell you about our services"; "How are you doing?";
self-centered framing around what the rep wants.

---

## Voicemail Variant

When the call goes to voicemail, use this 5-step structure. Target: 20–30 seconds total.

1. **Identify yourself** — name and company up front
2. **Say your phone number twice** — slowly, before the message body
3. **State the reason for your call** — `The reason for my call is...`
4. **Give them a reason to call back** — a curiosity hook or specific insight they'd want
5. **Repeat name and phone number twice** — close every voicemail this way

**Voicemail example (Example 1 scenario):**
> "Hi, this is Sarah with TechStack Pro. My number is 555-0182 — 555-0182. The reason for my call is I've been working with a few VP Sales teams at SaaS companies who've cut new-rep ramp time by over 50 percent, and I have some data on how they did it that might be relevant to your team. Sarah with TechStack — 555-0182. Thanks, Mark."

Leave a voicemail when: the prospect is a high-value conquest account, their buying window is
opening, or you are running a deliberate familiarity-building campaign. Skip voicemail on cold
unqualified lists — at 20–30 seconds per voicemail, it destroys phone block efficiency for
contacts who do not know you and are unlikely to call back. (Blount, pp. 189–190)

---

## Gatekeeper Variant

When a gatekeeper answers, do not use tricks or deceptive tactics — they backfire and land you
on the do-not-help list. Use transparent, professional, direct language:

> `Hi, my name is [Name] with [Company]. I'm hoping to speak with [Decision Maker Name] —
> could you let me know if they're available?`

If the gatekeeper asks what it is regarding:
> `I'm calling about [honest 1-sentence description of reason]. I'd appreciate any help you can
> give me in connecting with [Decision Maker].`

Never pretend to be someone you are not. Never claim a relationship that does not exist.
Gatekeepers are people — treat them as such, ask for their help directly, and you will get more
of it than any clever scheme will ever produce. (Blount, Ch. 17)

---

## References

Detailed supporting materials are in the `references/` folder:

- `references/five-step-framework-examples.md` — extended example library across industries
  and call objectives; additional worked examples for inside sales, field sales, and founder
  self-seller scenarios
- `references/voicemail-callback-guide.md` — when to leave voicemail vs. dial without;
  callback rate benchmarks; voicemail templates by prospect tier; five-step voicemail framework
  with timing guidance
- `references/gatekeeper-transparency-guide.md` — gatekeeper engagement principles; what to say
  when asked "what is this regarding"; legitimate bypass tactics (alternate extensions, email,
  LinkedIn, events)
- `references/anti-pattern-library-phone.md` — phone-specific anti-patterns with before/after
  examples: "How are you today?" pause mechanics, pitch vomit triggers, apologetic openers,
  passive ask patterns, and silence-filling failures

**Source chapter:** Blount, Jeb. *Fanatical Prospecting*, Chapter 15 "Telephone Prospecting
Excellence" (PDF pp. 181–195). Five-Step Framework: pp. 183–188. Voicemail framework:
pp. 189–195. Bridge/Because foundational framework: Chapter 14 "Message Matters"
(PDF pp. 159–165).

**Cross-references:**
- *prospecting-message-crafter* — builds the bridge and because that powers Line 4
- *prospecting-objective-setter* — determines the call objective that drives Line 5
- *prospecting-rbo-turnaround* — Anchor-Disrupt-Ask framework for handling pushback after
  the opener (Ch. 16, pp. 196–210)

## License

Content derived from *Fanatical Prospecting* by Jeb Blount (Wiley, 2015). This skill is licensed
under [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)](https://creativecommons.org/licenses/by-sa/4.0/).
You are free to share and adapt this material provided you give appropriate credit to Jeb Blount
and BookForge, and distribute any derivative works under the same license.

## Related BookForge Skills

Build the message nucleus before running this skill:
```
clawhub install bookforge-prospecting-message-crafter
```

Set the right call objective before building the opener:
```
clawhub install bookforge-prospecting-objective-setter
```

Handle push-back after the opener is delivered:
```
clawhub install bookforge-prospecting-rbo-turnaround
```

Browse the full Fanatical Prospecting skill set:
[bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

---
name: call-reluctance-diagnostic
description: "Diagnose and coach through call reluctance, prospecting avoidance, and sales slumps. Use this skill when you can't make yourself prospect, are procrastinating on cold calls, avoiding the phone, or stuck in a low-activity week. Produces a diagnosis and 1-week intervention plan for: why can't I prospect, prospecting fear, three ps, perfectionism sales, paralysis from analysis, procrastinating on cold calls, slump mindset, mental toughness sales, prospecting motivation, can't pick up the phone."
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/fanatical-prospecting/skills/call-reluctance-diagnostic
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: published
source-books:
  - id: fanatical-prospecting
    title: "Fanatical Prospecting: The Ultimate Guide to Opening Sales Conversations and Filling the Pipeline by Leveraging Social Selling, Telephone, Email, Text, and Cold Calling"
    authors: ["Jeb Blount"]
    chapters: [2, 7, 21]
tags: [sales, prospecting, mindset, mental-toughness, call-reluctance, sdr, bdr]
depends-on: []
execution:
  tier: 1
  mode: plan-only
  inputs:
    - type: document
      description: "User's self-report on recent prospecting behavior, activity counts from the last 5 days, what came up instead of prospecting, and how they feel about picking up the phone"
  tools-required: [Read, Write]
  tools-optional: []
  mcps-required: []
  environment: "Markdown document for self-reflection. The plan IS the deliverable — the human executes it."
discovery:
  goal: "Diagnose the dominant prospecting performance blocker (one of three named failure modes) and produce a specific 1-week intervention plan keyed to that diagnosis."
  tasks:
    - "Gather symptom inventory from the past 5 days of prospecting behavior"
    - "Run a Seven Mindsets baseline self-score to identify lowest-rated dimensions"
    - "Apply Three Ps differential diagnosis to identify dominant failure mode"
    - "Scan user language for victim-mindset markers"
    - "Produce a diagnosis report and 1-week coaching plan with failure-mode-specific interventions"
  audience:
    roles: [sdr, bdr, ae, founder-self-seller]
    experience: beginner-to-intermediate
  triggers:
    - "call reluctance"
    - "can't make myself prospect"
    - "procrastinating on cold calls"
    - "avoiding the phone"
    - "mental toughness sales"
    - "prospecting fear"
    - "three ps"
    - "perfectionism sales"
    - "why can't I prospect"
    - "prospecting motivation"
    - "slump mindset"
  prerequisites: []
  not_for: "Reps who are not prospecting because they genuinely hate sales and the job is wrong for them — Blount explicitly calls this out: if you cannot will yourself to dial and find this unbearable, this is a career fit problem, not a coaching problem."
  environment: "Markdown self-reflection document. Minimal tooling — no CRM access required."
  quality: placeholder
---

# Call Reluctance Diagnostic

## When to Use

Use this skill at the end of a low-activity week, before a planned prospecting block when you feel resistance, or when you notice you have been consistently avoiding the phone or inbox. Common triggers:

- You had a full day scheduled for prospecting and ended it having made fewer than 10 calls
- You keep telling yourself you'll prospect "after this one thing"
- You spent your prospecting block researching, organizing, or cleaning up the CRM instead of dialing
- You keep asking "but what if they say…" before making your first call of the day
- Your manager has flagged low activity and you cannot explain why

**What this skill produces:** A written diagnosis report that names your dominant failure mode (one of three), rates your mindset baseline across seven dimensions, flags any victim-language patterns in your self-description, and prescribes a specific 1-week intervention. The plan is the deliverable — you execute it.

**This is not for:** Reps who find sales genuinely intolerable and are considering a career change. Blount is direct: if you physically cannot will yourself to dial and dread every moment of prospecting, that is a job-fit problem, not a call-reluctance problem. This skill cannot fix the wrong career.

---

## Context and Input Gathering

Before diagnosis, gather honest data. Ask yourself — or ask the user to provide — answers to these questions:

**Activity data (last 5 business days):**
- How many prospecting calls did you actually make each day? (Write a number, not "some" or "a few")
- How many were planned or expected?
- What was your ratio of dials attempted to decision-makers reached?
- How many prospecting emails or LinkedIn messages did you send?

**Blocker data (what happened instead):**
- When you should have been prospecting, what were you doing instead?
- Did you tell yourself you needed to do more research before calling?
- Did you find reasons to delay starting your calling block?
- Did you replay past rejections or "what-if" scenarios in your head before dialing?

**Emotional data:**
- On a scale of 1–10, how much resistance do you feel right now when you think about picking up the phone?
- Do you find yourself blaming external factors — the territory, the leads, your product, your manager — for your low activity?
- What language do you use when you talk to colleagues about your pipeline and why it is thin?

If the user has provided a written self-report, read it carefully before proceeding. Look for: specific activity numbers, named excuses, and any language that assigns blame to external factors.

**Default assumptions when data is thin:**
- If no activity numbers are provided, assume the issue is real and recent (not hypothetical)
- If the user cannot name a specific blocker, start with the Three Ps diagnostic and let the symptoms surface
- If activity is zero for multiple days, weight paralysis-from-analysis as the most likely primary blocker

---

## Process

### Step 1: Symptom Inventory

**ACTION:** Write out what happened in the last 5 days. Do not estimate — use actual numbers if available. Map each work day against prospecting activity.

**WHY:** Self-delusion about activity is one of the most common and costly patterns in sales. In one coaching session Blount observed, a rep claimed "easily 50 calls" — the CRM log showed 12 in 7 hours. Two early harsh rejections had tripped the rep's confidence and they stopped without realizing it. Putting actual numbers on paper forces an honest baseline and surfaces the gap between what you believed you were doing and what you were actually doing. The gap itself is diagnostic data.

**Output:** A simple 5-day table:

| Day | Planned calls | Actual calls | Decision-makers reached | What I did instead |
|-----|--------------|--------------|------------------------|-------------------|
| Mon | | | | |
| Tue | | | | |
| Wed | | | | |
| Thu | | | | |
| Fri | | | | |

If actual < planned by more than 30%, proceed to Step 2 immediately.

---

### Step 2: Seven Mindsets Baseline Self-Score

**ACTION:** Rate yourself 1–5 on each of the seven mindsets that define high-performing prospectors. Be honest — this is a private self-assessment.

**WHY:** Before diagnosing which blocker is active, you need a baseline of which mindset dimensions are weakest. Low scores consistently cluster around specific failure modes: low Relentless + low Confident tends to predict paralysis-from-analysis; low Systematic + low Optimistic predicts procrastination; low Confident + low Adaptive predicts perfectionism. The self-score is not a performance review — it is a calibration instrument.

**Rating scale:** 1 = this almost never describes me / 5 = this consistently describes me

| # | Mindset | Behavioral marker | Score (1–5) |
|---|---------|------------------|-------------|
| 1 | Optimistic and enthusiastic | I attack each day ready to prospect even after a rough stretch. I don't let yesterday's rejections set the tone for today. | |
| 2 | Competitive | I track my activity vs. peers. I feel driven to outwork my competition at outreach. | |
| 3 | Confident | I expect most conversations to go well. I manage fear and self-doubt when I dial. | |
| 4 | Relentless | I treat rejection as fuel. I never let a "no" stop me from making the next call. | |
| 5 | Thirsty for knowledge | I actively seek coaching and feedback. I invest time in learning prospecting craft. | |
| 6 | Systematic and efficient | I protect my prospecting blocks. I run targeted lists and dial efficiently without over-preparing. | |
| 7 | Adaptive and flexible | I experiment with new approaches. I adjust quickly when a channel or message stops working. | |

**Score interpretation:**
- Any dimension rated 1–2: flag as a development target
- Total score < 21 (average < 3): mindset work is foundational before tactical fixes will hold
- Lowest 1–2 dimensions: these are inputs to the Three Ps diagnosis in Step 3

Full behavioral descriptions for each mindset are in [references/seven-mindsets-rubric.md](references/seven-mindsets-rubric.md).

---

### Step 3: Three Ps Differential Diagnosis

**ACTION:** Identify the dominant failure mode from three named patterns. These have different root causes and require different interventions — lumping them together produces generic advice that fixes none of them.

**WHY:** "Call reluctance" is a catch-all label that obscures what is actually happening. Blount identifies three mechanically distinct blockers. A rep who is procrastinating needs a discipline intervention (small daily commitments). A rep who is perfectionizing needs a research-budget constraint (cap preparation time). A rep who is paralyzed needs a graduated exposure intervention (one call first). Applying the wrong intervention makes the problem worse — telling a paralyzed rep to "just be more disciplined" accelerates anxiety without removing the fear driving inaction.

---

**P1 — Procrastination**

*Root cause:* Failure of daily self-discipline. The rep believes they can make up missed prospecting later ("I'll do a big block on Friday") but the cumulative effect of daily deferrals compounds into an empty pipeline.

*Key behavioral signals:*
- Prospecting is repeatedly deferred to a future date ("tomorrow," "Monday," "end of month")
- Work blocks exist but are consumed by non-prospecting tasks
- Activity patterns show 0–3 call days followed by one burst day (boom-bust)
- The rep can prospect when forced but avoids self-directed starts

*Self-assessment questions:*
- Did you tell yourself at least once this week that you would "catch up" on prospecting later?
- Is there always one more "important" task to clear before starting to dial?
- Do you believe a few heavy calling sessions can compensate for days of low activity?

*Diagnostic flag:* If the answer to two or more of the above is yes → Procrastination is your primary blocker.

*Core intervention:* You cannot eat the elephant in one bite. Daily minimum commitments — not weekly totals. One non-negotiable calling block of 30–60 minutes at the start of each day before any other task. No exceptions.

---

**P2 — Perfectionism**

*Root cause:* Using preparation as a proxy for prospecting. The rep substitutes the feeling of "getting ready" for the act of calling. Unlike procrastination (deferral), perfectionism produces the illusion of working while producing no prospecting outcomes.

*Key behavioral signals:*
- Calling blocks are consumed by research: Google, LinkedIn, CRM history, company website
- Scripts, lists, or tools must be "just right" before the first dial
- Call volume is extremely low (single digits) despite hours allocated to prospecting
- After each voicemail or rejection, additional preparation is done before the next call

*The Jeremy benchmark (p61–62):* Jeremy spent two hours arranging his desk, scripting, and researching each prospect individually — then made 7 calls in three hours, all to voicemail. Valarie next door ran a CRM list and started dialing immediately. One hour later: 53 calls, 14 decision-makers reached, 2 appointments set, 39 emails sent. Valarie earned approximately $100,000 more in annual commissions and ranked #1 in her division. The performance delta was not skill — it was action vs. preparation. See [references/jeremy-valarie-case.md](references/jeremy-valarie-case.md) for the full breakdown.

*Self-assessment questions:*
- Did you spend more than 15 minutes per prospect on research during your calling block this week?
- Did you reorganize your CRM, desk, or call list before making your first call?
- Have you told yourself "I just need to get the script right" before dialing?

*Diagnostic flag:* If the answer to two or more of the above is yes → Perfectionism is your primary blocker.

*Core intervention:* Cap research at 3 minutes per prospect maximum during calling hours. Research goes in protected time (before 8am or after 5pm) — never inside a calling block. Messy action beats perfect inaction: "Anything worth doing is worth doing poorly" — a targeted list dialed imperfectly produces more revenue than a perfect script never delivered.

---

**P3 — Paralysis from Analysis**

*Root cause:* Fear of rejection expressed as cognitive avoidance. The rep runs "what if" scenarios instead of dialing — "What if they say no?", "What if they say X?", "What should I do if…" — until the imagined scenarios generate enough anxiety to prevent action.

*Key behavioral signals:*
- Hours pass with zero calls despite the phone being in front of the rep
- The rep can articulate many reasons why calling "right now" is not optimal
- "What if" scenarios dominate pre-call thinking
- First call is often delayed to the point of the block ending without a dial

*Note — true job mismatch vs. paralysis:* If you physically cannot will yourself to dial at all and find the act of contacting strangers genuinely intolerable, this may be job-fit rather than analysis paralysis. Blount is direct about this: coaching cannot fix a fundamental mismatch between person and role. If that is your situation, this skill is not the tool you need.

*Self-assessment questions:*
- Did you spend time this week mentally rehearsing "worst case" call scenarios before dialing?
- Did you delay your first call of any day until you felt more "ready" — and then run out of time?
- Is your avoidance tied to a specific fear (rejection, embarrassment, not knowing how to respond)?

*Diagnostic flag:* If the answer to two or more of the above is yes → Paralysis from Analysis is your primary blocker.

*Core intervention:* One call first. Not a plan, not more preparation — a single dial. The purpose of the first call is not to get an appointment; it is to break the paralysis state. After the first call, the brain updates its threat model. Make the second call. Then the third. The anxiety dissipates with action, not with preparation. Graduated exposure: commit to a "one-call block" — a scheduled 5-minute window where the only goal is to complete one prospecting call.

---

### Step 4: Mental Toughness and Victim-Language Audit

**ACTION:** Review the user's self-description (the input document or their answers in this session) for victim-language markers. Then assess the four mental toughness pillars.

**WHY:** Victim-language is the most reliable leading indicator that the Three Ps will return even after tactical interventions. A rep can be coached past this week's procrastination — but if their default attribution pattern is external blame, the blocker will re-emerge next week. Mental toughness is the upstream capability that determines whether the interventions from Step 3 will hold. Diagnosing the weakest pillar guides the recovery prescription.

**Victim-language detection — scan the user's words for these patterns:**

| Pattern type | Example phrases | Signal |
|-------------|----------------|--------|
| External blame | "The leads are bad," "My territory is impossible," "Nobody buys in this economy" | Avoids ownership of prospecting activity |
| Helplessness framing | "Nothing works," "I've tried everything," "It's pointless" | Learned helplessness — often follows repeated rejection without coaching |
| Peer comparison as excuse | "Even the top reps aren't converting," "The whole team is struggling" | Using social proof to justify inaction |
| Manager blame | "They don't give us good tools," "My manager doesn't coach me" | Deflects from self-directed activity |

If two or more of these patterns appear in the user's self-description, flag victim-language as active and include a language-change prescription in the output plan.

**Four Pillars of Mental Toughness — rate each (Weak / Moderate / Strong):**

1. **Desire** — Can you answer clearly: What do you want? How will you get it? How badly do you want it? A rep without written goals has nothing to draw on when prospecting gets hard. If desire is weak, the intervention is goal-writing before any tactical changes.

2. **Mental Resilience** — Do you bounce back from rejection within the same calling block, or does a single harsh "no" shut down your activity for the rest of the day? Resilience is built through investment in self-development: 15 minutes of professional reading per day, audio programs during commute, coaching intake.

3. **Physical Resilience** — Sleep, exercise, and nutrition directly constrain mental toughness. Sleep deprivation specifically degrades the cognitive control needed to push past avoidance. If sleep is under 7 hours or exercise is absent, flag this as a contributor.

4. **Attitude** — Are you feeding your belief system or starving it? Inputs matter: the people you spend time with, what you read and watch, whether you practice gratitude or dwell on setbacks. "When your attitude loses altitude — you lose your winning edge."

---

### Step 5: Produce the Diagnosis Report and 1-Week Intervention Plan

**ACTION:** Write a structured output document — `call-reluctance-diagnosis.md` — that names the dominant failure mode, summarizes the evidence, and prescribes specific daily actions for the next 7 days.

**WHY:** A diagnosis without a plan produces insight without behavior change. The plan must be specific (named actions, named times) and keyed to the dominant failure mode identified in Step 3. Generic "prospect more" advice fails because it does not address the root cause. The written plan functions as a commitment device — ink on paper creates accountability that a verbal intention does not.

---

## Inputs

| Input | Required | Format |
|-------|----------|--------|
| 5-day activity data (calls planned vs. actual) | Yes | Numbers or estimates |
| Description of what happened instead of prospecting | Yes | Free text |
| Self-score on Seven Mindsets (Step 2) | Yes | 1–5 ratings |
| Three Ps self-assessment answers (Step 3) | Yes | Yes/No answers |
| User's own words describing their situation | Recommended | Verbatim — needed for victim-language scan |
| Mental toughness pillar self-rating (Step 4) | Recommended | Weak/Moderate/Strong |

---

## Outputs

Produce `call-reluctance-diagnosis.md` with the following sections:

```markdown
# Call Reluctance Diagnosis

**Date:** [Today's date]
**Diagnosis session covers:** [Date range of the behavior being reviewed]

---

## Activity Summary (Last 5 Days)

[5-day table from Step 1]

**Activity gap:** [Planned calls] planned vs [Actual calls] completed — [gap %] shortfall

---

## Seven Mindsets Baseline

[Scores table from Step 2]

**Lowest-rated dimensions:** [Names and scores of bottom 1–2]
**Interpretation:** [1–2 sentence read of what the pattern suggests]

---

## Primary Diagnosis: [Name the dominant P]

**Evidence:**
- [3–5 specific behavioral signals that confirm this as the primary blocker]

**Why this matters:**
- [1–2 sentences on the financial or pipeline cost if unaddressed]

---

## Victim-Language Findings

[Either: "No victim-language patterns detected" OR a list of flagged phrases and a brief note on what pattern they represent]

---

## Mental Toughness Pillar Assessment

| Pillar | Rating | Notes |
|--------|--------|-------|
| Desire | | |
| Mental Resilience | | |
| Physical Resilience | | |
| Attitude | | |

**Weakest pillar:** [Name] — [1 sentence on why this matters now]

---

## 1-Week Intervention Plan

[Specific daily actions, keyed to dominant failure mode. See examples below.]

**Day 1–2 (Foundation):** [Immediate structural change]
**Day 3–5 (Habit build):** [Daily practice with specific time/volume commitment]
**Day 6–7 (Audit):** [Review against activity data from Step 1 baseline]

---

## Self-Talk Scripts

[2–3 specific reframes for the most active negative self-talk pattern identified]
```

---

## Key Principles

- **The Three Ps are distinct failure modes, not synonyms.** Procrastination is a discipline failure. Perfectionism is action-substitution. Paralysis is fear-driven cognitive avoidance. They overlap but have different roots and different cures. Applying the wrong intervention to the wrong P produces frustration — and often reinforces the original blocker.

- **Messy action beats perfect inaction.** Valarie's 53 imperfect calls outperformed Jeremy's 7 researched calls by every metric that matters: contacts reached, appointments set, and annual commissions earned. The gap between them was not skill, product knowledge, or territory — it was the decision to act before conditions were perfect.

- **Victim language is a leading indicator, not a trailing one.** If a rep's natural language pattern assigns blame externally, tactical interventions will not hold. The belief that performance is controlled by external factors (leads, territory, economy) prevents the rep from taking the ownership actions that would actually change outcomes. Detecting and naming this pattern is as important as diagnosing the dominant P.

- **The three controllables in sales are: your actions, your reactions, and your mindset.** Everything else — prospect behavior, market conditions, product gaps — is outside your control. Losing is a choice. Mediocrity is a choice. This is not motivational language; it is a diagnostic frame. If a rep is not prospecting, it is because they have chosen a behavior that produces inaction. Naming that choice is the first step toward changing it.

- **Mental toughness can be developed — unlike talent, it is not fixed.** The formula is: change your mindset, change your game. The four pillars (Desire, Mental Resilience, Physical Resilience, Attitude) are all developable. The rep who builds them systematically outperforms the talented rep who does not over any sustained period.

---

## Examples

### Example 1: The Procrastinator ("I'll have a big Friday")

**Scenario:** An SDR reports that she made 12 calls this week total. She had four "prospecting days" planned. On each of those days, she spent the first 90 minutes on admin, email, and CRM cleanup, telling herself she would "get to calls in the afternoon." By afternoon, other things came up.

**Dominant P identified:** Procrastination — deferral pattern with boom-bust intent ("I'll make up for it Friday").

**1-Week Plan:**
- Daily non-negotiable: 30-minute calling block starting at 8:30am, before email is opened
- Target: 15 calls per day minimum, regardless of outcomes
- Remove admin from mornings entirely — move it to end of day
- Self-talk reframe: "I cannot prospect Monday's calls on Friday. Prospecting is like eating — it has to happen every day."
- Day 7 audit: compare 5-day call log vs. prior week baseline

---

### Example 2: The Perfectionist ("I just need to research one more thing")

**Scenario:** A BDR has been allocating two hours each morning to a "prospecting block." His average daily calls: 6. He describes his process: "I check LinkedIn for each prospect, look at the company website, review their recent news, check our CRM history, then think about what angle to use." He adds: "I don't want to go in blind."

**Dominant P identified:** Perfectionism — research-as-avoidance, classic Jeremy pattern.

**1-Week Plan:**
- Research budget: 3 minutes per prospect maximum. Set a timer.
- All research happens before 8am or after 5pm — never inside a calling block
- During calling hours: run the CRM list and dial in sequence. No pre-call research.
- Target: 30+ calls per 2-hour block (Valarie's benchmark: 53 calls + 39 emails in one hour)
- Self-talk reframe: "Imperfect information on a live call beats perfect information never delivered."
- Week review: track calls made vs. calls researched — if research time exceeds call time, the block was a research block, not a prospecting block

---

### Example 3: The Paralyzed Rep ("What if they hang up on me?")

**Scenario:** An AE doing self-directed outbound describes spending 45 minutes at his desk before making his first call on a Monday morning. He has written notes about "what to say if they ask about pricing," "what if their current vendor is cheaper," and "what if they already saw our email." He made 4 calls before deciding "it wasn't a good time to call."

**Dominant P identified:** Paralysis from Analysis — "what-if binge" pattern, decision-freeze from rejection anticipation.

**1-Week Plan:**
- One-call block: Schedule a 5-minute slot every morning at 9am with a single goal: complete one call. Just one. The outcome does not matter — the completion does.
- After the first call, immediately make a second. Then a third. Do not pause to debrief between calls.
- Ban pre-call scenario planning: notes, scripts, and objection prep happen the evening before, not in the calling block. Once the block starts, the only action is dialing.
- Self-talk reframe: "The call I have not made cannot go well. The call I make — even if it goes badly — gives me real data. I will learn more from one bad call than from one hour of imagining it."
- Graduated exposure target: Week 1 goal = 10 completed calls per day. Not answered calls. Not productive calls. Completed dials.

---

## References

- [references/seven-mindsets-rubric.md](references/seven-mindsets-rubric.md) — Full behavioral descriptions and scoring guidance for all 7 mindsets (Ch 2, p27–30)
- [references/jeremy-valarie-case.md](references/jeremy-valarie-case.md) — Full case study: Jeremy vs. Valarie, call counts, appointment outcomes, $100K commission delta (Ch 7, p61–62)

## License

This skill is licensed under [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/).
Source: [BookForge](https://github.com/bookforge-ai/bookforge-skills) — Fanatical Prospecting by Jeb Blount.

## Related BookForge Skills

This skill is standalone. Browse more BookForge skills: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

FILE:references/jeremy-valarie-case.md
# The Jeremy and Valarie Case Study

Source: Fanatical Prospecting, Ch 7 (p61–62), Jeb Blount.

This case study is the definitive illustration of perfectionism as a prospecting performance blocker. It quantifies exactly what the activity gap costs in outcomes and commissions.

---

## The Setup

Jeremy and Valarie are sales reps with offices next to each other. Same company, same product, same territory access, same tools. One morning they both have a calling block. What follows is a direct observation by Blount.

---

## Jeremy's Morning (Perfectionism)

Jeremy begins by arranging his desk perfectly. Then he organizes his computer. He makes sure his script is just right.

He then researches each prospect on his list:
- Google search
- LinkedIn search
- Company website
- Detailed review of the history and call notes in the CRM

One hour passes. Then two.

Finally, he makes his first call — to the prospect he has meticulously researched. It goes to voicemail. The next call goes to voicemail. So does the third.

He sighs: "No one answers the phone these days."

After three calls he stops to rearrange things on his desk. Twenty minutes later he packs up and heads into the field to visit existing customers.

**Jeremy's result:**
- Time in "prospecting block": approximately 3 hours
- Calls made: 7
- Decision-makers reached: 0
- Appointments set: 0

---

## Valarie's Morning (Action)

Valarie sits down at her desk the same morning. She immediately runs a list on her CRM and starts dialing.

One hour later:

**Valarie's result:**
- Calls made: 53
- Decision-makers reached: 14
- Appointments set: 2 (with qualified prospects)
- Prospecting emails sent: 39

She ran into a few snags. A couple of calls would have gone better had she researched in advance. It was not perfect. She accomplished far more than Jeremy.

---

## The Commission Delta

Valarie earned approximately **$100,000 more in annual commissions** than Jeremy.

Valarie was the **number one–ranked sales rep in her division**.

---

## What This Means

The difference was not:
- Skill
- Product knowledge
- Territory quality
- Scripts
- Luck

The difference was the decision to act before conditions were perfect.

Blount's principle: "Messy success is far better than perfect mediocrity." He explicitly states he will beat any rep who spends a calling block meticulously researching each prospect by simply picking up a targeted list and calling. The activity gap is too large to compensate for with marginally better preparation.

---

## The Nuance Blount Preserves

Blount is not saying research is never appropriate. He explicitly notes:

> "If you are calling C-level prospects, or you sell a complex and expensive product, it is a good idea to research your prospect in advance so that your message is relevant to their unique situation."

**The operative word is "advance."** Research happens before and after the calling block (in protected time — "Platinum Hours"), not during it.

Perfectionism becomes a blocker when:
- Research encroaches on calling time
- "Getting ready" becomes indistinguishable from "not calling"
- The rep uses preparation as a shield against the possibility of rejection

---

## Diagnostic Use

Use this case when coaching a rep with any of these patterns:
- Low call volume despite allocated time
- Detailed pre-call research as a default behavior during calling hours
- A call-to-research ratio where research time exceeds call time
- Self-description of "I don't want to go in blind"

The question to ask: "If you spent the next hour doing exactly what Valarie did — run your CRM list and dial in sequence — what is the worst realistic outcome? And what is the likely outcome for Jeremy in the same hour?"

---

## The Research Budget Rule (Derived from This Case)

From this case, the practical intervention rule:

**3 minutes per prospect maximum during calling hours.**

If a prospect genuinely requires more research (complex sale, C-level), that research happens in Platinum Hours — before 8am or after 5pm. It is never done inside a calling block.

---

*Source: Fanatical Prospecting, Jeb Blount (Wiley, 2015), Chapter 7: The Three Ps That Are Holding You Back, pp. 61–62.*

FILE:references/seven-mindsets-rubric.md
# Seven Mindsets of High-Performing Prospectors

Source: Fanatical Prospecting, Ch 2 (p27–30), Jeb Blount.

Use this reference for the Seven Mindsets Baseline Self-Score in Step 2 of the call-reluctance-diagnostic skill.

---

## Rating Instructions

Score each mindset 1–5 based on how consistently it describes your current behavior — not who you aspire to be.

- **5** — This describes me in nearly every prospecting situation
- **4** — This describes me more often than not
- **3** — This describes me about half the time
- **2** — I recognize this as a gap; it rarely describes me
- **1** — This almost never describes me; it feels foreign

---

## The Seven Mindsets

### 1. Optimistic and Enthusiastic

High-performing prospectors have a winning, optimistic mindset. They know that negative, bitter people with a victim mindset do not succeed in sales. They attack each day with enthusiasm — fired up and ready to engage. They view each day as a fresh new opportunity to achieve.

**Behavioral markers:**
- Brushes past naysayers and complainers without being pulled into their energy
- Dives into prospecting with drive even on bad days
- Reaches inside for stored enthusiasm to make one more call when already tired
- Does not let yesterday's rejections set the tone for today's activity

**Low score signal (1–2):** Rep frequently verbalizes how bad the leads are, the market is, or how "no one is buying" — this is the victim mindset pattern. External attribution dominates self-assessment.

---

### 2. Competitive

High-performing prospectors view prospecting through the eyes of a fierce competitor. They are hardwired to win and do whatever it takes to stay on top. They begin each day prepared to win the battle for the attention of the most coveted prospects, and outwit and outhustle their competition.

**Behavioral markers:**
- Tracks own activity vs. peers voluntarily (not just when required by manager)
- Feels genuine drive to outwork and out-dial teammates
- Views each prospecting day as a contest to be won
- Does not accept being outworked by a peer

**Low score signal (1–2):** Rep is indifferent to peers' activity counts. Does not compare notes on activity in a competitive way. "Not a competitive person" framing often precedes chronic low-activity patterns.

---

### 3. Confident

High-performing prospectors approach prospecting with confidence. They expect to win and believe they are going to win. They have developed mental toughness and the ability to manage the disruptive emotions of fear, uncertainty, and doubt. They leverage confidence and self-control to persuade prospects to give up time and resources to engage in sales conversations.

**Behavioral markers:**
- Picks up the phone without significant internal resistance
- Does not catastrophize a voicemail or early "no"
- Manages fear before the call rather than being paralyzed by it
- Expects the next call to go well, even after several poor outcomes in a row

**Low score signal (1–2):** Rep reports high anxiety before calls, describes feeling "dread" when looking at the call list. Often correlated with Paralysis from Analysis (P3).

---

### 4. Relentless

High-performing prospectors have a high need for achievement. They do whatever it takes to reach their goal. They never, ever give up, believing that persistence always wins. They use rejection as motivational fuel to get up and keep going with a determined belief that their next "yes" is right around the corner.

**Behavioral markers:**
- After a rejection or difficult call, immediately makes the next dial
- Does not "need a minute" to recover between calls
- Uses a harsh "no" as reason to call the next number — not to stop
- High daily call volume despite low conversion periods

**Low score signal (1–2):** Rep stops prospecting after a cluster of rejections within a single block. Activity pattern shows single-day or single-call stopping after adversity.

---

### 5. Thirsty for Knowledge

High-performing prospectors welcome feedback and coaching. They seek out every opportunity to learn and invest in themselves by voraciously consuming books, podcasts, audiobooks, blog posts, online training, live seminars, and anything else they believe will make them better.

**Behavioral markers:**
- Reads sales or professional development material regularly (15+ minutes/day)
- Requests feedback from manager or peers after calls
- Actively listens to podcasts or audio during commute
- Views setbacks as data for improvement — "What can I learn from this?"

**Low score signal (1–2):** Rep deflects feedback, resists coaching, and has not read a sales book or taken a course in 12+ months. Learning is passive or avoided.

---

### 6. Systematic and Efficient

High-performing prospectors have the ability to execute with near-robotic efficiency. They are skilled at their craft like a professional athlete. They protect calling blocks, block their time, concentrate their power to tune out distractions, and squeeze every moment from each sales day.

**Behavioral markers:**
- Prospecting blocks are protected and used exclusively for prospecting
- Builds and maintains targeted, organized prospect lists
- Keeps research and preparation outside of calling hours
- Measures activity consistently and adjusts based on data

**Low score signal (1–2):** Rep conflates "being busy" with "prospecting." Admin, email, and non-prospecting tasks consume scheduled calling time. This dimension is the primary diagnostic for Perfectionism (P2).

---

### 7. Adaptive and Flexible

High-performing prospectors have acute situational awareness. They are able to respond and adapt quickly to changing situations and circumstances. They leverage the "adopt, adapt, adept" cycle: actively search out and adopt new ideas and best practices, then adapt them as their own, and work at it until they become adept at execution.

**Behavioral markers:**
- Tries new prospecting channels or messages when current approach stalls
- Early adopter of new techniques, tools, and tactics
- Does not defend an approach that is not working
- Willing to sound imperfect while learning something new

**Low score signal (1–2):** Rep defaults to the same channel and same message even when results deteriorate. Rigid in approach. "This is just how I prospect" framing.

---

## Score Interpretation Summary

| Total Score | Interpretation |
|------------|----------------|
| 30–35 | Strong baseline. Tactical interventions (the right P-specific plan) should hold. |
| 21–29 | Mixed. Identify lowest 1–2 dimensions as development priorities alongside P-specific plan. |
| 14–20 | Mindset work is foundational. Tactical fixes will not hold without addressing lowest-scored dimensions first. |
| < 14 | Significant coaching need. A manager conversation and structured development plan are recommended alongside P-specific intervention. |

---

*Source: Fanatical Prospecting, Jeb Blount (Wiley, 2015), Chapter 2: Seven Mindsets of Fanatical Prospectors, pp. 27–30.*

---
name: balanced-prospecting-cadence-designer
description: |
  Design a balanced multi-channel prospecting cadence that prevents single-channel-obsession — the career-limiting habit of defaulting to the one channel you are most comfortable with while avoiding the channels that generate friction. Use this skill when someone asks about "prospecting cadence", "channel mix", "balanced prospecting", "multi-channel outreach", "how much phone vs email", "sales sequence design", "cadence template", "which channels should I use", "prospecting strategy", "should I be doing more phone calls", "how to balance in-person and remote outreach", "what percent of my prospecting should be social", "I'm better in person than on the phone", "am I too dependent on email", "how to structure my outreach across channels", "mix of prospecting methods", "single channel prospecting problem", or "how to diversify my prospecting approach". This skill gathers the user's product, sales cycle length, territory type, quota state, territory tenure, and current channel habits — then produces three artifacts: (1) a recommended channel-mix with explicit percentages (e.g., 40% phone / 25% email / 20% social / 10% in-person / 5% text) tuned to the user's specific situation, (2) a day-by-day weekly cadence template with time slots assigned to each channel, and (3) an anti-pattern audit that checks for single-channel-obsession and the "I'm so much better at X" rationalization. Based on Chapters 3 and 4 of Fanatical Prospecting by Jeb Blount.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/fanatical-prospecting/skills/balanced-prospecting-cadence-designer
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: published
source-books:
  - id: fanatical-prospecting
    title: "Fanatical Prospecting: The Ultimate Guide to Opening Sales Conversations and Filling the Pipeline by Leveraging Social Selling, Telephone, Email, Text, and Cold Calling"
    authors: ["Jeb Blount"]
    chapters: [3, 4]
tags: [sales, prospecting, cadence-design, multi-channel, sdr, bdr, sales-strategy]
depends-on: [prospecting-objective-setter, prospect-list-tiering, prospecting-time-block-planner]
execution:
  tier: 2
  mode: hybrid
  inputs:
    - type: document
      description: "User's product or service description, sales cycle length, territory description (geographic density, industry vertical), prospect universe size, quota gap (on-target vs. behind), territory tenure (new/established), and current channel usage breakdown if known"
  tools-required: [Read, Write]
  tools-optional: []
  mcps-required: []
  environment: "Document directory — reads user-provided situation brief; writes balanced-prospecting-cadence-{date}.md to the working directory"
discovery:
  goal: "Produce a channel-mix recommendation with explicit percentages, a day-by-day weekly cadence template, and an anti-pattern audit identifying any single-channel-obsession patterns in the user's current approach"
  tasks:
    - "Profile the seller's situation across seven situational variables"
    - "Identify which channels are viable given the ICP and territory"
    - "Proportion the channel mix with explicit percentages adjusted to the situation"
    - "Design a Monday-through-Friday daily cadence template assigning each channel to time slots"
    - "Audit for single-channel-obsession and the 'I'm so much better at X' rationalization"
  audience:
    roles: [sdr, bdr, ae, inside-sales-rep, outside-sales-rep, founder-self-seller]
    experience: beginner-to-intermediate
  triggers:
    - "Rep is relying on one channel (usually email or social) and not hitting their number"
    - "Rep is new to a territory and needs to know how to distribute prospecting effort across channels"
    - "Rep says they are 'better at' one channel and is avoiding others"
    - "Manager wants to implement a structured multi-channel outreach standard across the team"
    - "Rep is transitioning from inside to outside sales (or vice versa) and needs a new channel mix"
    - "Rep's pipeline has dried up and they want to diagnose whether single-channel over-reliance is the cause"
  prerequisites: []
  not_for:
    - "Writing the actual call opener or email copy — use fanatical-prospecting:cold-call-opener-builder or cold-email-writer"
    - "Setting the objective for each individual touch — use fanatical-prospecting:prospecting-objective-setter"
    - "Prioritizing which specific prospects to call first — use fanatical-prospecting:prospect-list-tiering"
    - "Blocking and protecting the time for prospecting — use fanatical-prospecting:prospecting-time-block-planner"
    - "Calculating how many total touches are needed to hit quota — use fanatical-prospecting:prospecting-ratio-manager"
  environment: "Document set — reads situation brief from working directory or user input; writes cadence plan"
  quality: placeholder
---

# Balanced Prospecting Cadence Designer

## When to Use

You need to decide how to distribute your prospecting effort across channels — phone, email, social, text, in-person, and referral — and you want a concrete weekly cadence rather than a vague directive to "use multiple channels."

This skill applies the Balanced Prospecting methodology from Jeb Blount's *Fanatical Prospecting* to your specific situation: your product, your sales cycle, your territory, your quota state, and where you are in your territory tenure. It produces a channel mix with explicit percentages and a day-by-day cadence template you can execute starting Monday.

**The core problem this skill solves:** Single-channel obsession — the habit of defaulting to the one prospecting channel you are most comfortable with while rationalizing away the channels you find uncomfortable. As Blount states directly: "Putting all your prospecting eggs into a single basket is stupid. It's career suicide." The most common rationalization is "I'm so much better at X" — a phrase Blount identifies as a reliable predictor of underperformance.

**Who this skill is for:** SDRs, BDRs, inside sales reps, outside sales reps, AEs, and founder-sellers who run outbound prospecting. Especially valuable for reps whose pipeline has stalled despite feeling busy, reps moving into new territories, and reps who have become heavily dependent on one channel (usually email or social).

**Output:** `balanced-prospecting-cadence-{date}.md` — channel-mix percentages, daily cadence template (Monday–Friday), and anti-pattern audit.

**Dependency context:** This skill is upstream of the other planning skills in this set. Once the channel mix is designed here, use `prospecting-objective-setter` to set the right goal for each touch, `prospect-list-tiering` to decide which prospects get which channel treatment, and `prospecting-time-block-planner` to protect the time slots the cadence requires.

---

## Context & Input Gathering

### Required

To proportion the mix accurately, the skill needs:

1. **Product or service:** What are you selling? The nature of the product drives which channels are viable and which are the primary relationship-builders.
2. **Sales cycle length:** Days, weeks, or months? Short cycles favor phone-and-close channels; long cycles require relationship-building channels alongside appointment-setting ones.
3. **Territory description:** Industry vertical, geographic density (urban/suburban/rural), account size range, and the typical decision-maker role.
4. **Quota state:** Are you currently on target, ahead, or behind? A rep who is 30% behind quota needs a different channel intensity than one who is on pace.
5. **Territory tenure:** Are you new (less than 12 months in this territory), mid-tenure (1–3 years), or established (3+ years with a qualified database)?
6. **Current channel usage:** How are you spending your prospecting time today — even approximately? A rough breakdown by channel (or "mostly email, some LinkedIn, rarely phone") is enough.

### Useful (read from working directory if available)

- **`icp.md`** — Ideal customer profile for channel selection (e.g., if the ICP is a C-suite executive at a large enterprise, phone + LinkedIn + in-person outweigh cold email)
- **`prospect-list.csv`** — Geography and account-size distribution calibrates the in-person and density-driven channel weighting
- **`pipeline-ratios.csv`** — Historical activity-to-outcome rates by channel reveal which channels are already working and which are underutilized

### Defaults

If no documents are provided, the skill asks for the six inputs above. Two or three sentences per item is sufficient to start. If tenure or quota state is uncertain, the skill defaults to "new territory" and "on target" and flags the assumption for confirmation.

---

## Process

### Step 1: Profile the Seller's Situation

**Action:** Assess the user's situation across seven variables drawn from the Balanced Prospecting framework. For each variable, determine the directional signal it sends for channel weighting.

| Variable | What to assess | Channel signal |
|---|---|---|
| **Industry vertical** | What industries are the prospects in? | Some verticals require in-person; referral networks dominate others; trade shows deliver the highest-quality prospects in some |
| **Product or service type** | Consulting vs. software vs. physical product | Social selling heavier in consulting; inbound and email heavier in certain software categories |
| **Deal complexity** | Complex/contractual vs. transactional | Complex → phone + in-person dominate; transactional → email + phone often sufficient |
| **Company size and stage** | Large with existing database vs. startup building one | Large: phone + email most efficient; startup: must balance database-building (long-term) with pipeline-filling (short-term) |
| **Territory tenure** | New (< 12 mo) vs. mid (1–3 yr) vs. established (3+ yr) | New: heavy phone to build the database; established: referrals + social + timed calls to buying-window prospects become primary |
| **Geographic density** | High-density urban vs. suburban vs. rural/dispersed | High-density (downtown Manhattan, Chicago Loop): in-person more efficient than phone; rural/dispersed: phone and remote channels dominate |
| **Quota state** | On target vs. behind | Behind quota: increase phone intensity and in-person; ahead: can sustain current mix |

**WHY:** No single channel-mix formula works for every seller. Blount is explicit: "There isn't a one-size-fits-all formula for balanced prospecting. Every territory, industry, product, service, and prospect base is different." Profiling across all seven variables before prescribing a mix prevents the common error of copying another rep's cadence without accounting for situational differences — the specific failure mode of a new rep emulating a 20-year veteran whose database is already fully qualified.

**Output:** A one-paragraph situation summary that names the directional signals identified for each variable. This becomes the rationale for the channel-mix percentages in Step 3.

---

### Step 2: Identify Viable Channels for the ICP

**Action:** Determine which of the six prospecting channels are viable given the prospect's role, industry, and reachability. Not all channels are equally accessible for every ICP.

**The six channels:**

| Channel | Best when | Caution when |
|---|---|---|
| **Phone (outbound call)** | Decision maker has a direct line or reachable mobile; transactional or complex deal requiring conversation | Gatekeeper-heavy environments with no DM direct contact |
| **Email** | Prospect has a professional email address; deal requires time-to-think rather than immediate response; high-density prospect lists where one-to-one phone volume is impractical | Low open rates in spam-heavy industries; commoditized email reputation in the vertical |
| **Social (LinkedIn, etc.)** | Prospect is active on the platform; consulting/advisory sales where thought leadership drives trust; ICP title is well-represented on platform | Prospects in industries with low social adoption; executive titles who do not manage their own inboxes |
| **Text** | Prior familiarity has been established (prior call, email, in-person contact); short-cycle transactional products; field reps with a recurring customer base | Cold outreach to prospects who have never been contacted; violates familiarity threshold |
| **In-person** | High-density geography enables efficient territory routing; relationship-intensive industries; outside sales with established routes | Geographically dispersed territory; long drive times between prospects; inside sales model |
| **Referral** | Established relationship network; tenured territory with satisfied customers; high-trust industries | New rep with no network in the territory; startup with no customer base yet to source referrals from |

**WHY:** Proportioning a channel that is not viable for the ICP produces zero results regardless of how much time is allocated to it. A SaaS SDR calling mid-market ops directors does not need to account for in-person drop-ins; a uniform rental sales rep covering an industrial park should not be treating LinkedIn as a primary channel. Identifying viable channels first prevents wasted allocation.

**Output:** A named list of 3–5 viable channels for the user's ICP, with one-sentence notes on why each is viable or limited.

---

### Step 3: Proportion the Channel Mix

**Action:** Using the situation profile (Step 1) and viable channels (Step 2), assign a percentage of total prospecting time to each channel. The percentages should sum to 100% of prospecting activity time (excluding meetings, discovery calls, and closing activity).

**Reference starting mix (inside sales, complex deal, mid-tenure):**

| Channel | Starting % | Adjust up when | Adjust down when |
|---|---|---|---|
| Phone | 40% | Behind quota; new territory; transactional deal; high-density geography | Established tenure with qualified database; highly gatekeeper-heavy environment |
| Email | 25% | High-density prospect list; asynchronous-preferred ICP; deal requires time-to-think | Very warm territory where calls convert directly; email open rates below 15% |
| Social | 20% | Consulting/advisory sale; thought-leadership-driven ICP; mid-to-established tenure | Non-professional social users; industries with low LinkedIn adoption |
| In-person | 10% | High-density geography; relationship-intensive industry; outside sales territory | Geographically dispersed; inside sales model; long drive times |
| Text | 5% | Established familiarity with prospects; field rep recurring customer base | Cold territory; no prior contact established; legal or compliance restrictions |
| Referral (active ask) | 0–10% | Tenured rep with existing customers; high-NPS customer base | New rep; startup with no installed base |

The full channel-mix matrix with 12 scenario variants (enterprise SaaS, transactional SMB, field rep, consulting, startup, and others) is in `references/channel-mix-matrix.md`.

**WHY:** The percentage-based mix forces a concrete answer to the question that most prospecting plans leave vague: not "use multiple channels" but "40% of my prospecting time this week is phone, 25% is email." Without percentages, the tendency is to allocate effort based on comfort rather than strategy — which is precisely how single-channel obsession forms. Blount's investment diversification analogy is deliberate: just as a financial advisor does not tell you to "diversify" without giving you an actual asset allocation, a prospecting plan without explicit percentages is not a plan.

**Output:** A channel-mix table with named percentages, one-sentence rationale per channel, and the situation-profile signals that drove each adjustment.

---

### Step 4: Design the Daily Cadence Template

**Action:** Translate the channel-mix percentages into a Monday-through-Friday daily schedule, assigning each channel to specific time slots. Coordinate with the `prospecting-time-block-planner` output if available — channel blocks should fit within Golden Hours.

**Daily cadence design principles:**

- **Phone first.** Schedule the phone block at the start of the prospecting day. Calls require the most cognitive energy and the highest rejection-tolerance. Deferring the phone block until later in the day allows lower-effort channels (email, social) to absorb the entire day through inertia.
- **Email immediately after the phone block.** Follow-up emails sent within 30 minutes of a voicemail or a brief conversation have materially higher open rates than emails sent cold. Use the post-phone Platinum Hour window for email.
- **Social in off-peak windows.** LinkedIn engagement, content commenting, and connection requests do not require prospects to be at their desks. Schedule social in early morning or early afternoon — never during peak phone windows.
- **In-person on dedicated territory days.** If in-person is part of the mix, assign dedicated territory days (typically mid-week) and plan hub-and-spoke routes the night before in Platinum Hours. Do not mix drive time with phone blocks on the same day.
- **Referral asks embedded in close calls and customer conversations.** Referral prospecting is not a separate block — it is an action embedded in existing customer interactions. Schedule a standing prompt: ask one existing customer or close contact for a referral each day.
- **Text as a follow-up trigger.** Text messages belong after a prior touch establishes familiarity — not as a cold-open channel. If text is in the mix, it fires after phone voicemail or email, not before.

The extended example cadences for three selling archetypes (enterprise SaaS, SMB inside sales, and field rep) are in `references/example-daily-cadences.md`.

**WHY:** A cadence template converts the channel-mix percentages from a planning document into executable daily behavior. Without a day-by-day schedule, the channel mix exists only on paper — the rep still defaults to the comfortable channel because no specific time is blocked for the uncomfortable ones. The order of channels within the day matters as much as the allocation: phone first prevents the pattern where email and social fill the morning and the phone block is perpetually deferred.

**Output:** A Monday–Friday daily cadence table with named time slots and channel assignments.

---

### Step 5: Anti-Pattern Audit

**Action:** Audit the user's current or intended prospecting approach for the three most common single-channel-obsession patterns. For each pattern present, name it explicitly and provide the rebalancing action.

**Anti-Pattern 1: The "I'm So Much Better at X" Rationalization**

*Detection:* The user states or implies a strong preference for one channel ("I'm a relationship person, I do better in person," "Email is more professional in my industry," "My clients don't answer the phone"). This phrase, in any form, signals that a comfortable channel is being used to avoid an uncomfortable one.

*Blount's diagnosis:* "The 'I'm so much better at...' excuse is just that: an excuse to avoid other prospecting techniques that salespeople find unpalatable. More often than not, it's an excuse to avoid phone prospecting. The pipeline always reveals the truth." When this phrase appears, Blount states, that salesperson is underperforming against their number and "cheating themselves out of thousands of dollars in commissions."

*Janice's case:* Janice told Blount emphatically, "But I'm so much better in person!" She is the archetype of this pattern — using a genuine strength (in-person relationship building) to rationalize a genuine avoidance (phone prospecting). The fix is not to abandon the preferred channel; it is to add the avoided channel back into the mix at its appropriate percentage.

*Rebalancing action:* Name the avoided channel. Set a floor percentage for it — even 20% — and schedule it as the first block of the day for 30 days.

**Anti-Pattern 2: The One-Size-Fits-All Guru Channel**

*Detection:* The user's prospecting approach was shaped by a single book, course, or training program that advocated one method as the universal answer (social selling only, email sequencing only, inbound-only, cold calling only).

*Blount's diagnosis:* "There is an expert or so-called sales guru on every corner preaching to salespeople that their method is the one way to prospecting salvation... 'Do it my way and you'll get unlimited qualified leads.'" The guru's method may work for a specific situation but fails as a universal prescription because every territory, product, and prospect base is different.

*Rebalancing action:* Identify which channels the program excluded. Test each excluded channel for 30 days and track activity-to-outcome ratios. Let the numbers — not the dogma — determine the final mix.

**Anti-Pattern 3: The Rookie Imitating the Veteran**

*Detection:* The user is new to the territory (less than 12–18 months) and has modeled their prospecting approach on a tenured rep who appears to work low volume with high results.

*Blount's diagnosis:* "In fact, this is how many rookies get themselves into big trouble. They see Joe, the 20-year veteran, generating million-dollar months with what appears to be little effort. Then they emulate this behavior. On their way to failure, they miss the fact that Joe spent years qualifying his database and now he is tuned into his prospects' buying windows and knows exactly when to engage them."

*The structural difference:* Joe's low-effort phone volume is possible because his database is already qualified. He knows who to call and exactly when to call them. A new rep in the same territory has none of that infrastructure. Emulating Joe's channel mix without Joe's database leads directly to an empty pipeline.

*Rebalancing action:* New reps should treat heavy phone outreach as the database-building investment. As the database qualifies over 12–24 months, the mix can shift toward referrals, social, and timed calls — but not before.

**Output:** For each anti-pattern present: a named diagnosis, supporting evidence from the user's situation, and a specific rebalancing action.

---

## Output Template

```markdown
# Balanced Prospecting Cadence Plan
**Date:** [Date]
**Rep:** [Name]
**Prepared by:** fanatical-prospecting:balanced-prospecting-cadence-designer

---

## Situation Summary

[One paragraph profiling the seven variables and their channel signals]

---

## Viable Channels

| Channel | Viable? | Notes |
|---|---|---|
| Phone | Yes / Limited / No | [one sentence] |
| Email | Yes / Limited / No | [one sentence] |
| Social | Yes / Limited / No | [one sentence] |
| Text | Yes / Limited / No | [one sentence] |
| In-person | Yes / Limited / No | [one sentence] |
| Referral | Yes / Limited / No | [one sentence] |

---

## Recommended Channel Mix

| Channel | % of Prospecting Time | Daily Minutes (based on [X] prospecting hours/day) | Rationale |
|---|---|---|---|
| Phone | [%] | [min] | [one sentence] |
| Email | [%] | [min] | [one sentence] |
| Social | [%] | [min] | [one sentence] |
| In-person | [%] | [min/day average] | [one sentence] |
| Text | [%] | [min] | [one sentence] |
| Referral | [%] | [min] | [one sentence] |

---

## Weekly Cadence Template

| Time Slot | Monday | Tuesday | Wednesday | Thursday | Friday |
|---|---|---|---|---|---|
| [SLOT 1] | Phone block | Phone block | Phone block | [In-person / Phone] | Phone block |
| [SLOT 2] | Email follow-up | Email follow-up | Email follow-up | [In-person] | Email + Social |
| [SLOT 3] | Social | Social | Social | [In-person] | Social |
| [SLOT 4] | [Other channel] | [Other channel] | [Other channel] | [Other channel] | [Other channel] |
| End of day | Referral ask (1 per day) | Referral ask | Referral ask | Referral ask | Referral ask |

*Customize start/end times using your Golden Hours window from prospecting-time-block-planner.*

---

## Anti-Pattern Audit

| Anti-Pattern | Present? | Evidence | Rebalancing Action |
|---|---|---|---|
| "I'm so much better at X" rationalization | Yes / No | [quote or behavior observed] | [specific action] |
| One-size-fits-all guru channel | Yes / No | [program or influence identified] | [specific action] |
| Rookie imitating veteran | Yes / No | [tenure and behavior noted] | [specific action] |

---

## 30-Day Rebalancing Commitment

If any anti-pattern was flagged:

- [ ] [Avoided channel] is scheduled as the FIRST block of the day every day for 30 days
- [ ] [Avoided channel] floor: [X]% of prospecting time — not negotiable for 30 days
- [ ] Results tracked by channel at the end of each week: dials/sends → connects → meetings
```

---

## Key Principles

**Balance means actual percentages, not vague intent.** Saying "I'll use multiple channels" without assigning percentages is not a prospecting strategy — it is a plan to use whichever channel feels easiest that day. The investment analogy Blount uses is exact: a financial advisor who tells you to "diversify" without giving you an asset allocation has not advised you. The channel-mix percentages in this skill are the asset allocation for your prospecting portfolio.

**WHY:** Without percentages, the rep's actual channel usage is determined by comfort, not strategy. After two straight hours of cold calls with poor results, the instinct is to shift to email or LinkedIn because they feel less rejecting. The percentage constraint forces the phone block to run to completion even when the phone feels hard — which is precisely when it needs to run.

**The pipeline always reveals the truth about single-channel obsession.** A rep who insists they are getting results from one channel will have a pipeline that reflects it — either genuine results if the channel is appropriate for the ICP, or a shallow pipeline if the channel is over-relied on. Blount's observation is diagnostic, not punitive: "Salespeople who gravitate to a single prospecting methodology seriously sub-optimize their productivity." The pipeline is the evidence; the cadence is the fix.

**WHY:** Self-assessment of channel effectiveness is unreliable because reps naturally remember the successes from their preferred channel and attribute failure to external factors ("prospects just aren't responding to email right now"). Pipeline metrics — opportunities created per channel, conversion rate per channel, average deal size per channel — are objective. Tracking activity by channel for 30 days and comparing to pipeline outcomes is the only way to know whether the current mix is working.

**Territory tenure changes the optimal mix — but does not change the principle.** A new rep needs heavy phone to build a qualified database. An established rep can shift toward referrals, social, and timed calls. The balance point moves; the principle of balance does not. Blount states: "Striking a balanced approach with prospecting is the most effective means of filling your sales pipeline no matter your industry, product, or service."

**WHY:** The failure mode for established reps is the mirror image of the new rep's failure mode. A new rep who avoids the phone has no database and no pipeline. An established rep who abandons phone and email in favor of referral-only stops generating new-to-database prospects and allows the qualified tier of the pyramid to thin out. Both ends of the tenure spectrum require active management of channel balance.

---

## Examples

### Example 1: Enterprise SaaS AE (Inside Sales, Complex Deal, Mid-Tenure)

**Situation:** AE at an enterprise SaaS company selling a $75K/year platform to VP of Operations at companies with 200–2,000 employees. Sales cycle: 90–120 days. Inside sales only (no in-person). Two years in the role, qualified database of ~400 accounts. Currently at 85% of quota with one quarter to close.

**Situation profile signals:**
- Complex deal + contractual → phone + email are primary appointment-setting channels
- Inside sales model → in-person at 0%; text only for warm follow-ups
- Mid-tenure → database partially qualified; referrals emerging but not yet dominant
- Behind quota slightly → increase phone intensity

**Recommended mix:**
- Phone: 45% | Email: 30% | Social (LinkedIn): 20% | Text: 5% | In-person: 0% | Referral: embedded in customer calls

**Daily cadence:**
- 7:30–8:30 AM (Platinum): List prep, LinkedIn engagement, CRM review
- 9–10:30 AM: Phone block (Power Hour)
- 10:30–11:15 AM: Email follow-up to voicemails left in phone block
- 11:15 AM–12 PM: LinkedIn — connection requests + personalized InMail to target accounts
- 12–1 PM: Discovery calls / demos / lunch
- 1:30–2:30 PM: Phone block (Power Hour)
- 2:30–3 PM: Email sequences + LinkedIn follow-ups
- End of day: One referral ask embedded in a customer check-in call

**Anti-pattern check:** None flagged. Rep is using phone as primary — correct for complex inside sales.

---

### Example 2: SMB Inside Sales Rep (Transactional, New Territory)

**Situation:** Inside sales rep selling a $3,000/year SMB accounting tool to owners of businesses with 5–50 employees. Sales cycle: 1–2 weeks. One call can close. Six months in the role, territory database largely uncalled. Currently 60% of quota.

**Situation profile signals:**
- Transactional + inside sales → close on the phone; phone is highest-leverage channel
- New territory → must build the database fast; phone-heavy outreach is the database-qualification tool
- Behind quota → maximize phone intensity immediately
- SMB owner ICP → email has moderate effectiveness; LinkedIn has limited adoption in this segment

**Recommended mix:**
- Phone: 55% | Email: 30% | Social (LinkedIn): 10% | Text: 5% | In-person: 0%

**Anti-pattern check:** Rep reports "I'm better at email — I get more responses." Flagged as "I'm so much better at X" rationalization. The phone block must run first. Email response rates without phone warming are measuring a biased sample. Schedule phone as a mandatory first block for 30 days and measure phone-to-close ratios before adjusting the mix.

---

### Example 3: Field Rep in Rural Dispersed Territory (Outside Sales, Established)

**Situation:** Outside sales rep selling commercial maintenance contracts to manufacturing facilities in a rural 3-state territory. Accounts are 40–90 minutes apart. Sales cycle: 30–60 days. Five years in the territory, strong referral network, database fully qualified.

**Situation profile signals:**
- Outside sales + complex deal → phone for appointment-setting; in-person for close
- Rural/dispersed geography → in-person is resource-intensive; hub-and-spoke routing essential; phone call replaces spontaneous drop-ins
- Established tenure → referrals are a primary channel; social is secondary; phone is for buying-window calls, not cold database-building
- Strong referral network → referral should be an explicit channel with time allocation

**Recommended mix:**
- Phone: 30% | In-person: 25% | Referral (active ask): 20% | Email: 15% | Social: 10% | Text: 0% (not adopted in this industry)

**Cadence adjustment:** In-person allocated to 2 dedicated field days per week with routes planned in Platinum Hours the evening before. Phone block runs on the 3 office days. Referral asks embedded in every in-person meeting and customer check-in.

**Anti-pattern check:** None flagged. Five-year tenure with qualified database justifies the referral-heavy mix. However, if the rep were new to this territory, this mix would be flagged as the Rookie Imitating the Veteran pattern — the referral network took five years to build and cannot be replicated by a new rep on day one.

---

## References

| File | Contents |
|---|---|
| `references/channel-mix-matrix.md` | Full matrix of 12 scenario variants with recommended channel-mix percentages for each: enterprise SaaS inside sales, transactional SMB inside sales, field rep rural, field rep urban, consulting advisory, startup building-database, benefits/insurance, staffing, capital equipment, real estate, financial services, and SaaS mid-market |
| `references/example-daily-cadences.md` | Day-by-day cadence templates for three archetypes — enterprise inside sales AE, transactional SMB rep, and outside field rep — with time slots, activity descriptions, and output benchmarks per block |

---

## License

This skill is licensed under [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/).
Source: [BookForge](https://github.com/bookforge-ai/bookforge-skills) — Fanatical Prospecting by Jeb Blount (Ch. 3–4).

## Related BookForge Skills

For setting the right objective (appointment vs. qualify vs. close) for each touch in the cadence:
```
clawhub install bookforge-prospecting-objective-setter
```

For tiering your prospect list so each channel touches the right prospect at the right time:
```
clawhub install bookforge-prospect-list-tiering
```

For blocking and protecting the time slots the cadence requires:
```
clawhub install bookforge-prospecting-time-block-planner
```

Browse the full Fanatical Prospecting skill set: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

---
name: desirable-difficulty-classifier
description: Classify any learning activity, practice structure, or instructional design element as a desirable difficulty (strengthens encoding) or undesirable difficulty (creates friction without learning benefit). Use this skill when an instructional designer, trainer, teacher, or learner wants to audit a course design, training session, study method, or practice regimen for evidence-based difficulty management — even if they don't use the phrase "desirable difficulty." Applies to onboarding programs, corporate training, academic course design, self-study plans, coaching sessions, and skill development programs. Identifies which of six proven difficulty strategies are present or absent (spacing, interleaving, variation, retrieval, generation, elaboration) and generates specific redesign recommendations. Do NOT use this skill to build a full study schedule (use retrieval-practice-study-system), to assess learner readiness or aptitude, or to evaluate content quality unrelated to difficulty structure.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/make-it-stick/skills/desirable-difficulty-classifier
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: draft
source-books:
  - id: make-it-stick
    title: "Make It Stick: The Science of Successful Learning"
    authors: ["Peter C. Brown", "Henry L. Roediger III", "Mark A. McDaniel"]
    chapters: [4, 6, 8]
tags: ["learning-science", "cognitive-psychology", "evidence-based-learning", "instructional-design", "learning-difficulty"]
depends-on: []
execution:
  tier: 1
  mode: hybrid
  inputs:
    - type: description
      description: "Description of a learning activity, course structure, training program, or study method"
  tools-required: []
  tools-optional: [Read]
  mcps-required: []
  environment: "Any agent environment. No file access required unless the user provides a course document."
discovery:
  goal: "Classify every difficulty element in a learning design as desirable or undesirable, map present and absent strategies from the six-strategy taxonomy, and produce a prioritized set of redesign recommendations."
  tasks:
    - "Gather description of the learning activity and learner context"
    - "Screen each difficulty element against Bjork's two-part classification test"
    - "Map each desirable difficulty to one or more of the six named strategies"
    - "Identify which of the six strategies are absent and represent improvement opportunities"
    - "Generate a difficulty analysis report with bilateral contrast and recommendations"
  audience: ["instructional designers", "teachers", "trainers", "corporate L&D teams", "coaches", "self-directed learners"]
  triggers:
    - "Is this training design effective?"
    - "Why isn't the learning sticking?"
    - "Review this course for evidence-based difficulty"
    - "Are we making it too easy or too hard?"
    - "Help me redesign this practice session"
    - "Audit this onboarding program"
    - "Is this study method actually working?"
  not_for:
    - "Building a complete study schedule (use retrieval-practice-study-system)"
    - "Assessing whether a learner has a learning disability or cognitive limitation"
    - "Evaluating content accuracy or subject-matter quality"
  environment: "Can operate on a verbal description, syllabus document, training outline, or practice schedule"
  quality:
    completeness_score:
    accuracy_score:
    value_delta_score:
---

# Desirable Difficulty Classifier

## When to Use

You are reviewing or designing a learning experience and want to know whether the difficulty it creates strengthens or weakens learning. Typical situations:

- An instructional designer completed a course outline and wants an evidence-based difficulty audit before launch
- A trainer notices participants are not retaining material and suspects the difficulty structure is wrong
- A learner is working through a study method (e.g., rereading, re-watching lectures) and wants to know why nothing is sticking
- A corporate L&D team is redesigning onboarding and wants to know which difficulties to add or remove
- A coach wants to evaluate a practice regimen for an athlete, musician, or professional

Before starting, verify:
- Is a description of the learning activity available? (Enough to understand what the learner does during practice or study)
- What is the learner's background and the intended skill being developed?

**Mode: Hybrid** — The agent runs the classification analysis and generates the report. The human decides which recommendations to implement.

## Context and Input Gathering

### Required Context (must have — ask if missing)

- **Learning activity description:** What does the learner actually do during practice or study?
  → Check for: course syllabi, training outlines, practice schedules, session descriptions, study method descriptions
  → If missing, ask: "Describe the learning activity — what does the learner do, in what order, and for how long?"

- **Target skill or knowledge:** What must the learner be able to do after learning?
  → Check for: learning objectives, job competency requirements, exam descriptions
  → If missing, ask: "What should the learner be able to do after this training? What does success look like?"

- **Learner background:** Prior knowledge and skill level of the learner
  → Check for: prerequisite statements, audience profile, experience level
  → If missing, assume intermediate (some prior exposure to the domain, not expert)

### Observable Context (gather without asking)

- **Practice structure signals:** Any mention of blocked practice, random ordering, massed sessions, or spaced reviews
- **Assessment signals:** Whether the design includes tests, quizzes, or performance checks
- **Feedback signals:** Whether corrective feedback is provided and when

### Default Assumptions

- If no prior knowledge is specified → assume intermediate learner
- If no timeline is specified → assume multi-week program (not single-session)
- If the description mentions "lecture + notes" with no practice → flag as massed-passive baseline

### Sufficiency Threshold

```
SUFFICIENT when ALL of these are true:
  ✓ Learning activity is described clearly enough to identify practice structure
  ✓ Target skill or knowledge is known
  ✓ Learner background is known or acceptably assumed
BLOCK if: the description is so vague (e.g., "we do training") that no structural elements can be identified
```

## Process

### Step 1 — Map the Learning Activity Structure

Read the description and identify all structural elements of the learning design. Extract:

- **Practice format:** How content is delivered (lecture, demonstration, reading, video, simulation)
- **Practice timing:** How sessions are spaced or compressed (single block, daily, weekly, on-demand)
- **Practice order:** Whether topics are blocked (one type at a time) or mixed (interleaved)
- **Practice variation:** Whether the same scenario is repeated identically or varied
- **Assessment method:** Whether learners are tested, self-quizzed, or never formally assessed
- **Learner generation:** Whether learners are asked to produce answers, solve problems, or only receive information
- **Elaboration prompts:** Whether learners are asked to connect new knowledge to prior knowledge or to explain in their own words

**WHY:** Classification requires knowing the actual structure of what the learner does, not just the topic. A lecture on retrieval practice can be a passive event (low desirable difficulty) or an active one (high desirable difficulty) depending on whether learners are quizzed, asked to generate examples, or simply read slides. The same content can be either desirable or undesirable depending on the surrounding practice structure.

Output: A structured list of 5-10 design elements extracted from the description.

---

### Step 2 — Apply Bjork's Two-Part Classification Test

For each difficulty element identified in Step 1, apply both tests:

**Test A — Does the effort strengthen encoding?**
Ask: Does this difficulty require the learner to actively reconstruct knowledge from long-term memory, generate a response, or make discriminations? If yes → potentially desirable. If the effort is purely about overcoming an obstacle unrelated to the skill being learned → undesirable.

**Test B — Can the learner overcome this difficulty?**
Ask: Does the learner have the prerequisite background knowledge and skills to respond to this difficulty successfully? If yes → desirable. If the difficulty exceeds the learner's current capacity to respond → undesirable.

**The critical distinction:** A difficulty is desirable when it triggers encoding and retrieval processes. It becomes undesirable when the learner cannot overcome it, when it does not strengthen the specific target skill, or when it creates anxiety that consumes working memory capacity instead of directing it toward learning.

**Undesirable difficulty markers — flag these for removal or redesign:**
- Difficulty caused by missing prerequisite knowledge (learner cannot engage because the gap is too large)
- Difficulty caused by poor presentation quality (confusing language, broken technology, inaccessible format) that is unrelated to the target skill
- Difficulty that induces test anxiety sufficient to disrupt performance (working memory consumed by self-monitoring)
- Difficulty that matches learning style preference but has no empirical support (e.g., requiring visual-only delivery for self-identified "visual learners")
- Difficulty that requires overcoming a physical or cognitive limitation unrelated to the skill (e.g., requiring dyslexic learners to decode complex text when the target skill is mathematical reasoning)

**WHY:** The Bjork framework distinguishes between difficulties that slow apparent progress while strengthening durable learning (desirable) and difficulties that simply impede without cognitive benefit (undesirable). The test of "does the effort succeed?" is the pivotal discriminator: unsuccessful effort in the face of an insurmountable obstacle does not produce learning. Both conditions must hold for a difficulty to qualify as desirable.

Output: A classification table: each difficulty element labeled DESIRABLE, UNDESIRABLE, or AMBIGUOUS with the specific test that determined the classification.

---

### Step 3 — Map to the Six-Strategy Taxonomy

For each difficulty classified as desirable in Step 2, identify which of the six named strategies it represents. For each strategy, note whether it is PRESENT, ABSENT, or PARTIAL in the current design.

See `references/six-strategy-taxonomy.md` for the full bilateral contrast table. Summary:

| Strategy | Core mechanism | Counterpart (ineffective) |
|----------|---------------|--------------------------|
| **Spacing** | Practice sessions separated by time, forcing reconstruction from long-term memory | Massed practice (cramming): draws on short-term memory, rapid improvement, rapid forgetting |
| **Interleaving** | Different topics or problem types mixed within a session, requiring discrimination | Blocked practice: one type at a time, feels productive, produces narrow skill that fails to transfer |
| **Variation** | Problems, scenarios, and contexts varied across practice sessions | Identical repetition: builds narrow pattern-matching, fails in novel contexts |
| **Retrieval practice** | Learner produces answers from memory before checking (testing effect) | Rereading / re-watching: creates familiarity illusion, not actual retrievability |
| **Generation** | Learner must produce a response, attempt a solution, or formulate an explanation before being given the answer | Passive reception: information presented without learner output requirement |
| **Elaboration** | Learner connects new knowledge to prior knowledge, gives examples, or explains why it is true | Isolated encoding: material presented in isolation without connection to existing knowledge structures |

**Presence scoring:**
- PRESENT: The design explicitly includes this strategy (e.g., quizzes before feedback = retrieval; randomized problem order = interleaving)
- PARTIAL: Some elements exist but inconsistently (e.g., end-of-module quiz but no spacing across sessions)
- ABSENT: No elements of this strategy appear in the design

**WHY:** Naming which strategy is present or absent converts a subjective critique ("this training seems passive") into a specific, actionable gap. Each absent strategy represents a concrete redesign opportunity. Partial presence is often more actionable than complete absence — it means the design already has the right structural idea but applies it narrowly.

Output: A 6-row strategy presence table.

---

### Step 4 — Identify Redesign Priorities

Rank the gaps from Step 3 by expected learning impact. Prioritize:

1. **Absent retrieval practice** — highest single-strategy impact on long-term retention. If learners never produce answers from memory, all other strategies are less effective.
2. **Absent spacing** — without time between sessions, retrieval cannot draw from long-term memory, undermining the mechanisms of all other strategies.
3. **Absent generation** — learners who only receive information without producing responses show weak transfer.
4. **Blocked practice / absent interleaving** — blocking creates narrow skill that fails to transfer to real-world variation.
5. **Absent variation** — produces rigid pattern-matching, especially problematic for professional and applied skills.
6. **Absent elaboration** — reduces integration with prior knowledge; new learning remains isolated and less retrievable.

For each priority gap, generate a specific redesign suggestion that fits the existing design format. Do not recommend radical structural changes when a small addition achieves the goal.

**Redesign suggestion format:**
> **Gap:** [Strategy absent or partial]
> **Current design element:** [What currently exists]
> **Redesign:** [Specific change to add the strategy]
> **Effort:** [Low / Medium / High — how much design work is required]
> **Expected impact:** [What improves and why]

**WHY:** Prioritization prevents the instructional designer from feeling overwhelmed. The redesign suggestions are ordered so that the highest-impact changes are addressed first. Adding retrieval practice to a passive lecture (e.g., three quiz questions at the end of each session) is a low-effort change with disproportionately high impact. The effort estimate helps designers triage.

Output: 3-6 prioritized redesign recommendations.

---

### Step 5 — Produce the Difficulty Analysis Report

Compile the outputs of Steps 1-4 into a structured report:

**Report sections:**
1. **Learning activity summary** — 2-3 sentence description of what was analyzed
2. **Classification table** — all difficulty elements with DESIRABLE / UNDESIRABLE / AMBIGUOUS labels
3. **Strategy presence table** — all six strategies with PRESENT / PARTIAL / ABSENT status
4. **Undesirable difficulty list** — specific elements to remove or redesign
5. **Prioritized recommendations** — 3-6 redesign suggestions in ranked order
6. **Screening questions for ongoing design** — 6 questions the designer can ask about any future learning element (see Step 6)

**WHY:** A structured report makes the analysis actionable and shareable. The classification table gives evidence for each finding. The strategy presence table shows the overall difficulty profile at a glance. The screening questions equip the designer to self-assess future designs without re-running the full analysis.

---

### Step 6 — Provide Screening Questions for Ongoing Design

Deliver these six questions to the instructional designer for use in future design reviews. They are derived from Bjork's classification framework and the six-strategy taxonomy:

1. **Does the learner produce a response from memory before receiving feedback?** (Tests retrieval practice — if no, add low-stakes quizzing or recall prompts)
2. **Is practice distributed across multiple sessions with gaps of at least one day?** (Tests spacing — if no, redesign the schedule to prevent massed practice)
3. **Are different topics or problem types mixed within sessions rather than blocked?** (Tests interleaving — if no, randomize problem order or alternate topic blocks)
4. **Does the learner encounter varied scenarios, examples, or problem formats across sessions?** (Tests variation — if no, diversify the practice set)
5. **Are learners asked to attempt a solution or generate an answer before the solution is revealed?** (Tests generation — if no, add pre-solution attempts, even for material not yet taught)
6. **Does the design ask learners to connect new material to what they already know or to explain it in their own words?** (Tests elaboration — if no, add reflection prompts or explanation exercises)

**Bonus undesirable difficulty screening question:**
7. **Does this difficulty require prerequisites the learner does not yet have?** (If yes → it is undesirable; address the prerequisite gap first)

**WHY:** Providing screening questions converts the classification framework into a self-service tool. A designer who has the questions does not need to re-engage the skill for every design decision — they can self-audit in minutes. The questions are written to produce a binary yes/no answer because ambiguous criteria are not used in practice.

---

## Inputs

| Input | Required | Description |
|-------|----------|-------------|
| Learning activity description | Yes | What the learner does during practice or study |
| Target skill or knowledge | Yes | What success looks like after learning |
| Learner background | No (defaults to intermediate) | Prior knowledge and experience level |
| Course document or syllabus | No | File containing the full design structure |

## Outputs

| Output | Format | Description |
|--------|--------|-------------|
| Classification table | Inline markdown | All difficulty elements labeled DESIRABLE / UNDESIRABLE / AMBIGUOUS |
| Strategy presence table | Inline markdown | Six strategies with PRESENT / PARTIAL / ABSENT status |
| Redesign recommendations | Inline markdown | 3-6 prioritized, specific recommendations |
| Screening questions | Inline markdown | 7 questions for ongoing design self-audit |

---

## Key Principles

**1. Difficulty is not inherently good or bad — mechanism determines value**
The same activity can be a desirable or undesirable difficulty depending on whether it strengthens encoding and whether the learner can overcome it. A hard test given before the learner has any relevant knowledge is an undesirable obstacle. The same test given after initial instruction is a desirable retrieval event. The mechanism — not the felt difficulty — is what matters.

**2. Fluency is the enemy of durability**
Learning that feels easy, smooth, and productive is often the least durable. Rereading produces fluency (the text feels familiar) without retrievability (the learner cannot recall it without the text in hand). Massed practice produces performance gains (rapid improvement in the session) without long-term retention. Instructional designs that prioritize participant comfort consistently produce poor retention outcomes.

**3. The effort that succeeds is the effort that teaches**
Effortful retrieval that results in correct recall (with or without struggle) strengthens the memory trace. Effortful retrieval that fails because the difficulty is unsurmountable does not. The key is to calibrate difficulty to the learner's current level: enough to require reconstruction from long-term memory, not so much that the reconstruction fails entirely.

**4. All six strategies are additive**
The six desirable difficulty strategies are not mutually exclusive — they stack. A practice session that includes retrieval (quizzing from memory), spacing (scheduled one week after initial learning), interleaving (mixing problem types), and elaboration (explaining answers in own words) is dramatically more effective than any single strategy alone. Instructional designs should aim to incorporate multiple strategies rather than optimizing for one.

**5. Structure building requires difficulty**
Learners who are given information passively develop superficial familiarity. Learners who are required to generate, retrieve, and elaborate develop mental models — connected knowledge structures that enable transfer to new problems. The difficulty of constructing meaning cannot be shortcut; it is the mechanism of learning.

---

## Examples

### Example 1 — Corporate Onboarding Audit

**Input:** A new-employee onboarding program: Day 1 is a full-day lecture with slides covering company history, culture, and processes. Employees are given a manual to read. No assessment. Employees shadow a senior colleague for Day 2 and Day 3. Week 2 is independent work.

**Classification results:**
- Full-day lecture: UNDESIRABLE — passive reception with no retrieval requirement; massed (one day), no spacing
- Read-only manual: UNDESIRABLE — rereading analog; creates familiarity, not retrievability
- Shadowing: PARTIAL — observational, not generative; no retrieval or elaboration required
- Independent work (Week 2): DESIRABLE — real-world variation; generation required; implicit spacing from Day 1

**Strategy presence:**
- Retrieval practice: ABSENT
- Spacing: ABSENT (Day 1 lecture never revisited before independent work)
- Interleaving: ABSENT
- Variation: PARTIAL (Week 2 provides it)
- Generation: PARTIAL (Week 2 only)
- Elaboration: ABSENT

**Top recommendation:** Add three retrieval prompts at the end of Day 1: "Without looking at your notes, write down the three things from today that you'll need to do in your first solo task." Low effort, high impact.

---

### Example 2 — Medical Training Workshop

**Input:** A one-day continuing education workshop for physicians: Morning session is two hours of case presentations (attending presents, residents watch). Afternoon is small-group discussion of cases. Participants complete a satisfaction survey at the end.

**Classification results:**
- Case presentations (passive): UNDESIRABLE — observation only; no retrieval, no generation
- Small-group discussion: DESIRABLE — elaboration present (connecting to prior cases); generation partial (if participants must propose diagnoses before attending reveals it)
- Satisfaction survey: UNDESIRABLE difficulty marker (not a learning assessment)

**Strategy presence:**
- Retrieval practice: ABSENT
- Spacing: ABSENT (single-day event, no follow-up)
- Interleaving: PARTIAL (cases are varied topics)
- Variation: PRESENT (diverse cases)
- Generation: PARTIAL (discussion may require it, but not consistently)
- Elaboration: PARTIAL (discussion context encourages it)

**Top recommendation:** Restructure case presentations as retrieval events: present the case with findings, pause, ask participants to write their diagnosis before the attending reveals it. Same content, same time — but changes passive observation to active retrieval.

---

### Example 3 — Self-Study Method Audit

**Input:** A software developer studying for a certification exam: studies by watching tutorial videos twice through, then reads the official guide once. Exam is in four weeks.

**Classification results:**
- Re-watching videos: UNDESIRABLE — rereading analog; repeated exposure creates familiarity, not retrieval strength
- Reading official guide: UNDESIRABLE alone — passive encoding with no retrieval requirement

**Strategy presence:**
- Retrieval practice: ABSENT
- Spacing: ABSENT (all material consumed in a compressed initial period)
- Interleaving: ABSENT (one topic fully before moving to next)
- Variation: ABSENT (single source format)
- Generation: ABSENT
- Elaboration: ABSENT

**Assessment:** This method has zero desirable difficulty strategies. High effort with low expected retention. The learner will feel prepared (familiarity illusion) and underperform on the exam.

**Top recommendation:** Replace re-watching with self-quizzing. After watching each video once, close it and write down the five most important concepts from memory. Check against the video. Repeat for missed items only. This single change introduces retrieval practice, generation, and implicit spacing — three strategies at once.

---

## References

- `references/six-strategy-taxonomy.md` — Full bilateral contrast table for all six strategies with definitions, mechanisms, evidence summary, and counterpart descriptions
- `references/bjork-classification-criteria.md` — Detailed source notes on the Bjork framework for desirable vs. undesirable difficulty, with direct chapter citations

## License

This skill is licensed under [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/).
Source: [BookForge](https://github.com/bookforge-ai/bookforge-skills) — Make It Stick: The Science of Successful Learning by Peter C. Brown, Henry L. Roediger III, Mark A. McDaniel.

## Related BookForge Skills

This skill is standalone. Browse more BookForge skills: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

FILE:references/bjork-classification-criteria.md
# Bjork Classification Criteria — Desirable vs. Undesirable Difficulty

Source: *Make It Stick* (Brown, Roediger, McDaniel), Chapter 4: "Embrace Difficulties," Chapter 6: "Get Beyond Learning Styles."
Original framework: Elizabeth Bjork and Robert Bjork.

---

## The Core Definition

Desirable difficulties are conditions that "trigger encoding and retrieval processes that support learning, comprehension, and remembering. If, however, the learner does not have the background knowledge or skills to respond to them successfully, they become undesirable difficulties."

*— Elizabeth and Robert Bjork, quoted in Make It Stick, Ch. 4*

This definition contains both conditions:
1. The difficulty must trigger encoding or retrieval processes (mechanism test)
2. The learner must have the background to respond successfully (capacity test)

Both conditions must hold for a difficulty to be classified as desirable.

---

## The Two-Part Classification Test

### Test A: Mechanism Test — Does the effort strengthen encoding?

A difficulty is potentially desirable if it requires the learner to:
- Actively reconstruct knowledge from long-term memory (rather than reading it from a source)
- Generate a response, solution, or explanation
- Discriminate between similar cases or problem types
- Connect new material to prior knowledge
- Slow down and engage in deeper processing than passive reception would require

A difficulty is undesirable on mechanism grounds if it requires effort that:
- Is purely procedural (navigating a poorly designed interface, decoding unclear instructions)
- Is unrelated to the target skill (e.g., the difficulty is in the language of the material when the skill being learned is mathematical)
- Induces anxiety that occupies working memory without directing it toward learning

### Test B: Capacity Test — Can the learner overcome this difficulty?

A difficulty is potentially desirable if:
- The learner has sufficient prerequisite knowledge to engage with the challenge
- Increased effort can produce a successful response
- The difficulty can be overcome within the session or with reasonable persistence

A difficulty is undesirable on capacity grounds if:
- The learner lacks the prerequisite knowledge or skills to respond successfully
- The gap between the learner's current level and the difficulty level is too large for effort to bridge
- The difficulty induces a failure state rather than a productive struggle

---

## Named Undesirable Difficulties from the Source

The following are explicitly named as undesirable in the text:

### 1. Anxiety During Testing
"These studies point out that not all difficulties in learning are desirable ones. Anxiety while taking a test seems to represent an undesirable difficulty." (Ch. 4)

Mechanism: Anxiety consumes working memory capacity through performance self-monitoring ("How am I doing? Am I making mistakes?"), leaving less capacity available for the cognitive work the test requires. The difficulty is internal and competes with learning rather than directing it.

### 2. Prerequisite Gaps
"Difficulties are desirable because they trigger encoding and retrieval processes that support learning. If, however, the learner does not have the background knowledge or skills to respond to them successfully, they become undesirable difficulties." (Ch. 4)

Mechanism: A learner who cannot construct a bridge from current knowledge to the new material experiences the difficulty as an obstacle, not as a learning event. No encoding or retrieval process is triggered because there is no relevant prior knowledge to activate.

Example from the text: "Outlining a lesson in a sequence different from the one in the textbook is not a desirable difficulty for learners who lack the reading skills or language fluency required to hold a train of thought long enough to reconcile the discrepancy. If your textbook is written in Lithuanian and you don't know the language, this hardly represents a desirable difficulty."

### 3. Mismatched Learning Style Requirements
"While some kinds of difficulties that require increased cognitive effort can strengthen learning, not all difficulties we face have that effect. If the additional effort required to overcome the deficit does not contribute to more robust learning, it's not desirable." (Ch. 6)

This applies to the widely believed but empirically unsupported learning styles framework. Requiring a learner to receive instruction in a non-preferred modality (e.g., visual-only for a self-identified auditory learner) is not an undesirable difficulty because the evidence does not support the premise that modality matching matters for learning outcomes. However, presenting content in a format that genuinely exceeds the learner's decoding capacity (e.g., complex text for a learner with severe dyslexia when the target skill is unrelated to reading) is an undesirable difficulty.

### 4. Dyslexia and Reading Difficulties
"An example is the poor reader who cannot hold onto the thread of a text while deciphering individual words in a sentence. This is the case with dyslexia... the difficulty is a genuine impediment rather than a productive challenge." (Ch. 6)

Mechanism: When decoding consumes working memory capacity, no capacity remains for comprehension and conceptual processing. The difficulty does not strengthen the target learning; it prevents it.

---

## The Overarching Rule (Provisional)

From the text: "Is there an overarching rule that determines the kinds of impediments that make learning stronger? Time and further research may yield an answer."

The authors offer this provisional principle: "Intuitively it makes sense that difficulties that don't strengthen the skills you will need, or the kinds of challenges you are likely to encounter in the real-world application of your learning, are not desirable."

This points to a third test, beyond mechanism and capacity:

### Test C (Provisional): Relevance Test — Does the difficulty exercise the actual target skill?

A difficulty may be desirable mechanically (it requires effortful cognitive work) and within capacity (the learner can respond to it), but if it exercises a skill that is not the target of the learning, it adds work without benefit.

Examples from the text:
- "Having somebody whisper in your ear while you read the news may be essential training for a TV anchor. Being heckled by role-playing protestors while honing your campaign speech may help train up a politician. But neither of these difficulties is likely to be helpful for Rotary Club presidents or aspiring YouTube bloggers who want to improve their stage presence."
- A baseball player might practice with a weighted bat to strengthen swing mechanics, but teaching football players golf technique during balance training is not a desirable difficulty for football performance.

---

## Classification Summary

| Test | Question | Fail → Classification |
|------|----------|----------------------|
| Mechanism | Does the effort strengthen encoding or retrieval? | No → Undesirable |
| Capacity | Can the learner overcome this difficulty? | No → Undesirable |
| Relevance (provisional) | Does the difficulty exercise the target skill? | No → Likely undesirable |

A difficulty must pass all three tests to be classified as desirable.

---

## Practical Screening Heuristics

Derived from the source framework for rapid classification:

**LIKELY DESIRABLE if:**
- The learner must produce an answer without access to the source
- The learner encounters the material after a delay (not immediately after encoding)
- The learner must choose among problem types without contextual cues about which applies
- The learner must connect the material to something else they know
- The difficulty requires the learner to do something they find frustrating but not impossible

**LIKELY UNDESIRABLE if:**
- The learner has not been taught the prerequisite material
- The learner's anxiety about performance is consuming their attention
- The difficulty is in the delivery format, not in the cognitive task
- The learner is being required to overcome a limitation (reading disability, language gap) that is not the target of the training
- The difficulty makes performance feel hard without requiring any deeper cognitive engagement with the material

FILE:references/six-strategy-taxonomy.md
# Six Desirable Difficulty Strategies — Bilateral Contrast Table

Source: *Make It Stick* (Brown, Roediger, McDaniel), Chapters 4 and 8.
Bjork classification framework: Elizabeth and Robert Bjork, coined "desirable difficulties."

---

## Overview

A desirable difficulty is a learning condition that slows apparent short-term progress while producing stronger, more durable, and more transferable long-term learning. The term was coined by psychologists Elizabeth and Robert Bjork, who defined desirable difficulties as conditions that "trigger encoding and retrieval processes that support learning, comprehension, and remembering."

The six named strategies below are supported by empirical research across laboratory and applied settings. Each has a bilateral contrast — a counterpart practice that feels more productive but produces weaker long-term outcomes.

---

## Strategy 1: Spacing

**Definition:** Distributing practice sessions across time, with gaps between sessions long enough that the learner must reconstruct the material from long-term memory rather than working memory.

**Mechanism:** When a memory has partially faded and is retrieved again, the act of reconstruction strengthens the memory trace and its retrieval routes more than immediate re-exposure does. Spaced practice triggers reconsolidation — the memory is made pliable, updated, and re-stored with stronger encoding.

**What it feels like:** Slower, frustrating. Progress within each session appears less impressive than massed practice. The learner may feel they have forgotten what they previously knew and interpret this as failure.

**Evidence:** Research consistently shows 50% faster forgetting after massed practice compared to spaced practice over a one-week period. Spaced retrieval practice can "immunize" learning against forgetting — three spaced sessions dramatically outperform three massed sessions.

**Application signals (present):** Multi-session programs with days between sessions; follow-up quizzes weeks after initial instruction; review sessions built into later modules.

---

**Counterpart: Massed Practice (Cramming)**

**Definition:** Concentrating all practice into a single block or short period, typically just before a test or performance event.

**Why it feels better:** Within the session, performance improves rapidly. The learner experiences clear, satisfying progress. Short-term recall is high immediately after massing. This produces a fluency illusion — the learner believes they have learned the material because they can recall it right now.

**Why it fails:** Massed practice draws on short-term memory, not long-term memory. The brain is looping the information through working memory without consolidating it into long-term storage. Within 24-48 hours, 50-70% of massed learning is lost. The improvement seen in massed sessions is not an indicator of durable learning.

**Detection in course designs:** Single-day intensives; "read the chapter and take the quiz immediately"; bootcamps with no follow-up; one-time lecture series with no spaced review.

---

## Strategy 2: Interleaving

**Definition:** Mixing different topics, problem types, or skills within a practice session, rather than completing all practice on one type before moving to the next.

**Mechanism:** Interleaving forces the learner to identify which type of problem is being presented and select the correct approach before executing — this discrimination process builds a richer and more conditional representation of the skill. The learner cannot rely on context (the last ten problems were all curveballs) to make the response automatic; they must actively identify and retrieve the appropriate response.

**What it feels like:** Clunky, inefficient. The learner never develops a rhythm with any single problem type. Progress within each type seems slow. Learners and instructors often prefer blocked practice because it produces faster visible improvement.

**Evidence:** In a Cal Poly baseball study, batters who practiced with randomly interleaved pitch types (fastball, curveball, changeup) outperformed those who practiced the same pitches in blocked sets of 15 — despite the blocked group showing better within-session performance. Similarly, interleaved study of bird species or artist styles produced superior discrimination on tests, even though learners preferred blocked study.

**Application signals (present):** Random problem ordering in practice sets; mixed-topic quiz banks; training sessions that alternate between skills rather than completing one before starting the next.

---

**Counterpart: Blocked Practice**

**Definition:** Practicing one topic, skill, or problem type in full before moving to the next (e.g., 15 fastballs, then 15 curveballs, then 15 changeups).

**Why it feels better:** Within each block, the learner gets progressively better. The improvement is visible and motivating. The instructor can easily see that learners are mastering the content within each block. Practice feels organized and efficient.

**Why it fails:** Blocked practice builds a narrow skill that works when context signals which response is needed but fails when the context is ambiguous. In real-world application, the learner rarely has the luxury of knowing which type of problem they're about to face. Blocked practice builds conditional competence (can hit a curveball when I know it's a curveball coming) rather than unconditional competence (can hit a curveball when I don't know what pitch is coming).

**Detection in course designs:** Topic-by-topic course structures where each module is completed before the next begins with no revisitation; practice sets organized by problem type; training programs that fully complete one module before introducing any content from another.

---

## Strategy 3: Variation

**Definition:** Presenting the same underlying skill or concept through varied examples, scenarios, formats, and contexts across practice sessions.

**Mechanism:** Variation forces the learner to abstract the underlying principle that applies across different surface presentations. This produces more robust mental models that can be applied in novel situations. Without variation, the learner learns a narrow pattern-match (this specific type of question, in this specific format) rather than the underlying principle that determines the correct approach.

**What it feels like:** Less focused. The learner may feel they never get to truly "master" any single format because the format keeps changing. Instructors may feel the curriculum lacks consistency.

**Evidence:** Students who practiced tossing beanbags at baskets of varied sizes (two-foot and four-foot) later outperformed students who only practiced at the target size (three-foot) when tested at the target size. Varied exposure builds a flexible skill that performs better in the actual target context than practice at exactly the target.

**Application signals (present):** Different case examples for the same concept; multiple problem formats testing the same principle; cross-domain application of a technique; examples drawn from varied industries or contexts.

---

**Counterpart: Identical Repetition**

**Definition:** Practicing the same skill in the same format, context, and difficulty level in every practice session.

**Why it feels better:** Improvement is fast and clear. The learner develops strong performance on the practiced format. Drill-based identical repetition creates smooth, automatic execution.

**Why it fails:** Identical repetition builds pattern-matching to the specific stimulus, not the underlying skill. When the context changes (a different type of exam question, a different client situation, a novel presentation format), the learner's performance degrades because the narrow pattern they practiced does not match the new surface form. Expert performers who use varied practice transfer their skills more readily to novel contexts than those who use identical repetition.

**Detection in course designs:** Practice exercises that use the same template for every session; standardized case studies that are always the same industry; drills that never change the scenario or problem format.

---

## Strategy 4: Retrieval Practice

**Definition:** Requiring the learner to produce an answer or recall information from memory before checking it against the source — the testing effect.

**Mechanism:** The act of pulling a memory from long-term storage strengthens the memory trace and the retrieval routes more than re-exposure to the same material. Retrieval also triggers reconsolidation — the memory is updated and re-stored with new connections. Failed retrieval followed by corrective feedback is more effective than not having tried, because the gap in knowledge becomes salient and the correct answer is encoded in a context of motivated attention.

**What it feels like:** Harder and slower than rereading. Learners encounter gaps in their knowledge and experience discomfort. Early attempts at retrieval feel unproductive because answers are missing or wrong. This discomfort is frequently misread as evidence that the method is not working.

**Evidence:** A single retrieval session (no reread) outperforms three rereading sessions on one-week retention tests. Producing an answer (short-answer) outperforms selecting an answer (multiple choice) in retention. Writing a short essay produces stronger retention than either. The advantage of retrieval over rereading increases over time: immediately after study, the difference is small; after one week, it is large.

**Application signals (present):** Quizzes administered before the answer is revealed; practice problems with answers checked afterward; self-quizzing from memory before reviewing notes; flashcard systems that require producing the answer.

---

**Counterpart: Rereading / Re-Watching**

**Definition:** Revisiting source material (text, video, slides) as the primary study or review method.

**Why it feels better:** Familiarity increases with each pass. The material feels clearer and more comprehensible. The learner experiences a feeling of understanding that is indistinguishable (in the moment) from actual knowledge. Rereading is easy, comfortable, and appears to produce clear progress.

**Why it fails:** Rereading creates familiarity, not retrievability. The learner can read the text fluently and recognize correct answers but cannot recall the information in the absence of the text. This is called the fluency illusion or illusion of knowing. After rereading, learners consistently overestimate how much they will be able to recall without the source material — a bias called the Dunning-Kruger effect on a local, topic-specific scale.

**Detection in course designs:** Post-session review listed as "re-read chapter 3"; study guide says "review slides before the test"; no quizzes or practice tests in the design; assessment only occurs at end-of-course (no low-stakes practice tests before the high-stakes exam).

---

## Strategy 5: Generation

**Definition:** Requiring the learner to produce a response — attempt to solve a problem, formulate an answer, or generate an explanation — before being given the correct answer, even when the material has not yet been formally taught.

**Mechanism:** When a learner attempts to generate an answer, they activate related knowledge structures and prime the encoding pathways. When the correct answer is then provided, it is encoded in the context of the learner's active search — creating connections to the related knowledge that was fresh during the attempt. Even incorrect generation followed by corrective feedback produces better learning than passive reception of the correct answer.

**What it feels like:** Uncomfortable. Learners feel uncertain, sometimes frustrated. Being asked to attempt a problem before being taught how feels unfair or premature. Learners may resist, saying "just tell me the answer."

**Evidence:** Students who were asked to attempt a problem before seeing the solution retained the solution better than students who were shown the solution first. The same effect applies to fill-in-the-blank (stronger than multiple choice), short-answer (stronger than fill-in-the-blank), and essay (strongest). Unsuccessful generation attempts produce better learning than no attempt when corrective feedback follows.

**Application signals (present):** Pre-lesson problems before instruction; role-playing before debriefing; "attempt this before we show you how" prompts; learner-generated examples of a concept; requiring learners to formulate their own summary before seeing the instructor's summary.

---

**Counterpart: Passive Reception**

**Definition:** Presenting the correct information, procedure, or solution to the learner without requiring any prior generative attempt.

**Why it feels better:** Efficient and clear. No time wasted on wrong attempts. The learner receives accurate information immediately, avoiding the "errors-lead-to-learning-the-wrong-thing" concern that some instructors hold.

**Why it fails:** Passive reception produces weaker encoding because it does not activate prior knowledge or prime retrieval pathways. The learner's attention is not focused by the specific gap that generation reveals. Errorless learning — the philosophy that preventing errors prevents them from being learned — has been empirically disproven. Errors followed by corrective feedback are not learned; they are corrected. The attempt is what produces the benefit, not the error itself.

**Detection in course designs:** Lecture-only formats; tutorials that walk through solutions step by step before the learner attempts them; "watch how I do it" without "now you try before seeing the answer."

---

## Strategy 6: Elaboration

**Definition:** Requiring the learner to connect new material to prior knowledge, explain why something is true, give examples, or describe how it relates to other concepts they already know.

**Mechanism:** Elaboration integrates new knowledge into existing memory structures, creating more retrieval pathways to the new material and strengthening the mental model in which it is embedded. Meaning is constructed by the learner, not delivered by the instructor. The more connections a piece of knowledge has to other knowledge, the more ways it can be retrieved later.

**What it feels like:** Slower and more cognitively demanding than passive encoding. Learners must do mental work to make connections, not just receive content. Some learners resist because they feel they do not yet understand the material well enough to explain it.

**Evidence:** Students who wrote their own summaries of lecture content (restating in own words and generating examples) scored half a letter grade higher on exams than students who copied slides verbatim — using the same time, same content. Elaboration benefits persist over two months. The benefit is not from exposure to the content but from the constructive act of meaning-making.

**Application signals (present):** "Write to learn" exercises (summarize in own words); reflection prompts after each session ("how does this connect to what we covered in week 1?"); explaining a concept to a peer; generating personal examples of an abstract principle.

---

**Counterpart: Isolated Encoding**

**Definition:** Presenting new material as a self-contained unit without prompting the learner to connect it to prior knowledge or to other concepts.

**Why it feels better:** Content is clearly delineated. Learners can focus on one thing at a time. Module-by-module structure feels organized and manageable.

**Why it fails:** Without elaboration, new knowledge is encoded in isolation and has fewer retrieval pathways. It is less durable and less transferable because it is not woven into an existing knowledge structure. Transfer of learning — applying knowledge in new contexts — depends on having a rich, interconnected mental model. Isolated encoding produces factual knowledge without the conceptual scaffolding needed for application.

**Detection in course designs:** Modules that are designed to be fully independent with no reference to prior content; no reflection exercises; no "how does this relate to X?" prompts; assessment only tests recall of isolated facts without requiring connection or application.

---

## Summary Table

| Strategy | Core action | Counterpart | Failure mode of counterpart |
|----------|-------------|-------------|---------------------------|
| Spacing | Distribute practice across time with gaps | Massed practice | Short-term memory use; rapid forgetting |
| Interleaving | Mix topics and problem types | Blocked practice | Narrow skill; fails in novel context |
| Variation | Vary examples, formats, and contexts | Identical repetition | Pattern-matching; fails with surface change |
| Retrieval practice | Produce from memory before checking | Rereading / re-watching | Fluency illusion; familiarity without recall |
| Generation | Attempt before being given the answer | Passive reception | Weak encoding; no activation of prior knowledge |
| Elaboration | Connect to prior knowledge; explain why | Isolated encoding | Fragile; few retrieval pathways; poor transfer |

---
name: story-plot-selector
description: Pick the right story plot (Challenge / Connection / Creativity) and structure it so it drives the specific action you need — and decide whether to deliver it as a springboard story or a direct argument. Use this skill whenever the user needs to find, pick, or shape a story, anecdote, or case study for a message, talk, pitch, announcement, training session, change effort, or culture push. Activate on "what story should I tell", "find me an anecdote", "how should I open this presentation", "we need a story here", "help me structure a case study", "which of these stories is the right one", "need an inspiring example", "tell a story about", "I have three anecdotes — pick one", "make this talk more human", "how do I open the all-hands", "what's the right case study for this pitch", "story for a keynote", "story to rally the team", "story for onboarding", "change management story", "need a motivating example", "story that shows why this matters", "the talk needs a narrative", or whenever a draft is pure argument/data and the user wants to replace or supplement a claim with a single concrete tale. Also triggers when the user has raw story material (news clipping, customer anecdote, personal experience, historical event) and asks how to frame or structure it. The skill classifies the story need into Challenge (overcoming obstacles — inspires perseverance), Connection (bridging differences — inspires empathy and cooperation), or Creativity (mental breakthrough — inspires experimentation), applies the matching structure, and decides between a springboard story (audience has agency, diverse contexts, you want buy-in) versus a direct argument (single unambiguous action). Also decides whether the story should work as simulation (mental rehearsal of how to act) or inspiration (motivation to act), or both. The skill does NOT fabricate events or invent characters — it works with real stories the user provides or helps them mine from real material. It does NOT write full emotional appeals (use emotional-appeal-selector) and does NOT score the full stickiness rubric (use stickiness-audit).
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/made-to-stick/skills/story-plot-selector
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: draft
source-books:
  - id: made-to-stick
    title: "Made to Stick: Why Some Ideas Survive and Others Die"
    authors: ["Chip Heath", "Dan Heath"]
    chapters: [6, 13]
tags: [storytelling, communication, narrative, messaging, case-study, persuasion, change-management, springboard-story, public-speaking, instructional-design]
depends-on: []
execution:
  tier: 1
  mode: hybrid
  inputs:
    - type: document
      description: "The audience response the user wants (what the listener should do, feel, or decide after hearing the story)"
    - type: document
      description: "Raw story material — a draft anecdote, news clipping, customer quote, personal experience, or a shortlist of candidate stories to pick from"
    - type: document
      description: "Occasion and context — where the story will be told (keynote, all-hands, sales pitch, onboarding, memo, training module) and the surrounding argument"
  tools-required: [Read, Write]
  tools-optional: [Grep]
  mcps-required: []
  environment: "Any agent environment with file read/write. Document-set environment — the agent operates on short prose artifacts supplied by the user."
discovery:
  goal: "Classify a story need into one of three plots, structure the chosen story to drive the specific action, and decide the delivery mode (springboard vs direct, simulation vs inspiration)."
  tasks:
    - "Pick which of three candidate anecdotes is the right one to open a keynote"
    - "Classify a raw customer story and structure it to inspire a team behavior change"
    - "Decide whether to tell a story or make a direct argument for a change-management ask"
    - "Turn a news article into a structured case study matched to a specific intended action"
  audience:
    roles: [communicator, founder, marketer, manager, trainer, public-speaker, change-leader, product-marketer]
    experience: any
  when_to_use:
    triggers:
      - "User is writing a talk, pitch, memo, or training and needs a story for a specific section"
      - "User has raw anecdotes and wants to pick one and structure it for effect"
      - "User is planning a change effort and wants buy-in across diverse listeners"
      - "User is opening a presentation and needs the right first sixty seconds"
    not_for:
      - "Fabricating characters or events the user cannot verify"
      - "Full emotional-appeal selection (use emotional-appeal-selector)"
      - "Scoring the whole SUCCESs rubric (use stickiness-audit)"
  environment:
    codebase_required: false
    codebase_helpful: false
    works_offline: true
  quality:
    scores:
      with_skill: 0
      baseline: 0
      delta: 0
    tested_at: "pending"
    eval_count: 0
---

# Story Plot Selector

## When to Use

You have a specific communication moment — a talk, pitch, memo, all-hands, training module, change announcement, sales deck, fundraising appeal — and you need a *story* (not just an argument) to land one specific action or feeling. You either have candidate story material already (anecdotes, customer quotes, news clippings, personal experience) or you know what action you want and need to pick which kind of story will drive it. Before starting, confirm: (1) what the listener should do/feel/decide after hearing the story, (2) whether you have real story material or need to mine it from real sources, and (3) where the story lives — opening, middle, closing, or standalone.

The core mechanic: stories drive action in two distinct ways — **simulation** (mental rehearsal of how to act in a situation) and **inspiration** (motivation to act). The Jared Subway story, for example, gave listeners both: a vivid picture of how weight loss is done (eat Subway subs daily) *and* the emotional push to try it. Your job as the author is to know which lever the situation needs and pick a plot that pulls it.

Three plots classify more than 80% of the stories in the original *Chicken Soup for the Soul* collection and more than 60% of the non-celebrity stories in *People* magazine:

- **Challenge plot** — protagonist overcomes daunting obstacles. Inspires perseverance, effort, taking on hard things.
- **Connection plot** — people bridge a gap (social, racial, class, generational, functional). Inspires empathy, cooperation, helping across lines.
- **Creativity plot** — someone has a mental breakthrough or solves a problem in a novel way. Inspires experimentation, trying a new approach.

If none of these fit, the story is probably not the one — keep looking or write a direct argument instead.

## Context & Input Gathering

### Required Context (must have — ask if missing)
- **Intended audience response:** What should the listener do, feel, or decide after hearing the story?
  -> Check prompt for: verbs like "inspire", "convince", "rally", "get buy-in", "teach", "motivate", explicit "I want them to ___"
  -> Check environment for: `brief.md`, `talk-outline.md`, `core-message.md`
  -> If still missing, ask: "What do you want the listener to do or feel after hearing this story? One sentence."
- **Raw story material OR a shortlist of candidates:** The actual anecdote, news item, customer quote, personal experience, or list of options.
  -> Check prompt for: pasted story text, a link, a name ("the Jared story"), file paths
  -> If missing, ask: "Do you already have a story or anecdote, or do you need help finding one from a specific pool of material (your customers, your team, the news)?"

### Observable Context (gather from environment)
- **The occasion:** Where the story will be told — talk, memo, slide, pitch, training.
  -> Look for: `draft.md`, `talk.md`, `slides.md`, `pitch.md`
  -> If unavailable: ask for the channel and the time budget (30 seconds? 2 minutes? standalone article?).
- **Audience profile:** Who the listener is and how much agency they have to act.
  -> Look for: `audience-profile.md`, `brief.md`
  -> If unavailable: ask "who is the audience and what action can they actually take?"
- **Sibling draft signals:** Is the surrounding text a direct argument already? Is a story supplementing or replacing it?

### Default Assumptions
- If the occasion is unclear, assume "short-form spoken or written message" (1–3 minutes of time budget).
- If audience agency is unclear, ask — it is the single biggest input to the springboard vs direct decision (Step 4) and should not be defaulted.
- Never invent events, names, numbers, or quotes. If the user's material is thin, say so and ask for more.

### Sufficiency Threshold
SUFFICIENT: intended response + story material (or a clear pool to mine from) + occasion known
PROCEED WITH DEFAULTS: intended response + material known; occasion defaulted to short-form
MUST ASK: intended response unclear OR no real material AND no pool to mine from OR audience agency unknown

## Process

### Step 1: Clarify the intended action
**ACTION:** In one sentence, write down what the listener should do, feel, or decide after hearing the story. Write it as a verb the listener will perform ("apply our tool to a new domain next week", "forgive a teammate they're blaming", "try the new grinder design process"), not as a feeling word ("be inspired", "feel motivated").

**WHY:** Every downstream choice — plot, structure, delivery mode — is determined by this single sentence. A story that is "inspiring" in the abstract but does not drive the specific action is decoration. The whole point of stories in Chapter 6 is that they are tools for generating behavior; without a target behavior, you cannot pick between plots because all three plots are "inspiring" but in different directions. Challenge plots inspire effort, Connection plots inspire empathy, Creativity plots inspire experimentation. You cannot pick one until you know which of those three bowls the action falls into.

**Artifact:** `story-structure.md` — start the file with `## Intended Action:` followed by the one-sentence target behavior.

### Step 2: Classify the story need into one of three plots
**ACTION:** Using the decision rule below, classify the intended action into Challenge, Connection, or Creativity. If two plots seem to fit, pick the one that matches the *dominant* behavior you want — not the richest story. If none fit, go to Step 2b.

**WHY:** The three plots are not interchangeable — they trigger different downstream behaviors in the listener. Picking the wrong plot means the listener is motivated toward the wrong action. Jared's story (Challenge) works because it inspires *personal effort* to match Jared's perseverance; if Subway had told the same facts as a Creativity story ("Jared solved a nutrition puzzle"), listeners would have felt intellectual admiration rather than "maybe I could try this too."

**Decision rule:**

| If you want the listener to... | Pick | Core engine |
|---|---|---|
| Work harder, persevere, take on a daunting goal, push through an obstacle | **Challenge** | Protagonist vs daunting odds → success |
| Bridge a gap (help a stranger, trust a teammate, work across lines of difference, reach across conflict) | **Connection** | Protagonist crosses a social/relational gulf |
| Try a new approach, experiment, break a process pattern, solve a problem differently | **Creativity** | Protagonist makes a mental breakthrough |

**Test for daunting-ness (Challenge plot specifically):** The obstacles must seem daunting *relative to the protagonist*. Jared losing 245 pounds is a Challenge plot. Jared's neighbor shaving an inch off his waist is not. If your story's protagonist is only mildly challenged, it will not inspire listeners to take on their own hard things — the bar is too low to be motivating.

**IF** no plot fits cleanly -> go to Step 2b.
**ELSE** -> record `plot: {Challenge|Connection|Creativity}` in the artifact and proceed.

### Step 2b: No plot fits — decide story-or-not
**ACTION:** If none of the three plots match the intended action, the situation may not be a story problem at all. Before forcing a plot, ask: "Would a direct argument, a concrete constraint, or a data point do this job better?" If yes, stop and tell the user. If the user still wants a story, pick the plot closest to the action and flag the mismatch in the artifact.

**WHY:** Stories are not free. They take time, they carry emotional weight, and a mismatched story actively fights your message. The three plots cover ~80% of inspirational story cases — the remaining ~20% are usually better served by a concrete example, a direct claim, a statistic, or a one-sentence core message. Forcing a story into a plot it doesn't fit is how people end up with anecdotes that feel tacked on.

### Step 3: Decide the simulation / inspiration mix
**ACTION:** Mark the story as providing simulation (S), inspiration (I), or both (S+I). Use the test below.

**WHY:** Stories work as *mental simulators* and/or *motivators* — these are distinct effects. The Xerox copier-repair story (lunchroom shop talk about an E053 error) is pure simulation: no emotional uplift, but listeners learn a diagnostic pattern they can apply next week to a real broken machine. The Jared story is both — listeners learn that daily Subway sandwiches correlate with dramatic weight loss (simulation) *and* feel moved to try it (inspiration). Knowing which lever the occasion needs controls how you write the story in Step 5.

**Tests:**
- **Simulation needed (S)** if: the listener needs to know *how* to act in a specific kind of situation; the value is transferable pattern recognition; the story will be used in training, onboarding, or a how-to context; the listener will need to handle a similar case next week.
- **Inspiration needed (I)** if: the listener needs *motivation* to act on something they already know how to do; the value is emotional momentum; the story will be used in a rally, pitch, keynote open/close, fundraising moment, or change-kickoff.
- **Both (S+I)** if: the listener needs both a picture of the behavior *and* the push to start — typical of culture-change, behavior-change campaigns, and case studies used to drive adoption.

Record `mode: S | I | S+I` in the artifact.

### Step 4: Decide springboard story vs direct argument
**ACTION:** Decide whether the story should be delivered as a **springboard story** (tell a seed story, let each listener generate their own application) or as a **direct argument with illustrative story** (make the claim explicitly, use the story as proof). Use the rule below.

**WHY:** Stephen Denning's work at the World Bank showed that when you *hit listeners between the eyes* with a direct argument, they fight back — they evaluate it, criticize it, argue with the "little voice inside the head." A springboard story bypasses that by engaging the little voice: it gives the listener a tiny seed of possibility and lets them generate their own second story about how it applies to *their* context. This is why Denning could introduce a whole knowledge-management strategy at the World Bank in 10 minutes using one short story about a health-care worker in Zambia finding CDC data about malaria online — each executive in the room could mentally substitute their own project for "Zambia" and generate a version of knowledge management that fit their world. A direct argument could never have produced that breadth of buy-in in 10 minutes, because each executive would have argued with it from their own specific context.

**Rule — use a springboard story when ALL of these are true:**
- The audience has meaningful agency to act in *diverse contexts* (each person's application will look different).
- You want buy-in across skeptics, not compliance from subordinates.
- A seed of possibility is enough — you do not need to specify exact behavior.
- The audience is likely to argue back if you make a direct claim ("little voice" is loud).

**Use a direct argument with illustrative story when:**
- You need one specific, unambiguous action from everyone.
- The audience is friendly and the claim is not contested.
- The action has a fixed procedure (training / how-to / compliance).
- You have very limited time AND the story is carrying proof, not persuasion.

**IF** springboard -> keep the seed story lean, end with an unstated "could this work here?" implicit question, do NOT hand the listener the conclusion.
**ELSE** -> make the claim explicitly first, then use the story as a *single overwhelming example* (Sinatra-style).

Record `delivery: springboard | direct` in the artifact.

### Step 5: Structure the story using the matching arc
**ACTION:** Write the structured story using the arc template for the chosen plot. Keep it short (time-budget aware — 30 seconds / 2 minutes / 5 minutes). Include only details that pull the intended action lever. Cut everything that is just "interesting."

**WHY:** Each plot has a structural spine that makes the inspiration mechanism fire. A Challenge plot that buries the obstacle under biographical setup does not inspire perseverance — the reader forgets what was at stake. A Connection plot that skips the "gulf" between protagonist and other does not inspire crossing gulfs. A Creativity plot that omits the old approach does not inspire breaking patterns. The arc is the mechanism.

**Challenge arc:**
1. Protagonist + stakes (who, what they have to lose, who else is affected).
2. The obstacle is named and made to feel daunting *relative to the protagonist*.
3. Attempt and setback (shows the obstacle is real, not trivial).
4. Perseverance or clever effort.
5. Resolution + specific change in protagonist's world.
6. Implicit invitation: "you could take on your thing too."

**Connection arc:**
1. Protagonist and the "other" — name the gulf explicitly (social, racial, class, functional, generational). Modern audiences often miss the gulf in old stories (the Good Samaritan needs the "atheist-biker-gang-member" reframe to land today).
2. The moment of encounter — the protagonist could walk past.
3. The cost of crossing the gulf (time, money, status, comfort).
4. The act of connection, in concrete terms.
5. What the "other" received that the priest/Levite walked past.
6. Implicit invitation: "cross the gulf near you."

**Creativity arc:**
1. The old approach — named, and visibly slow, expensive, or stuck.
2. The frustration ("it was taking us longer to build a new grinder than it took to fight World War II").
3. The breakthrough moment — a concrete, unexpected act (tying plastic and metal samples to a car bumper and driving them around a parking lot).
4. The result (enough to show the new approach works).
5. Implicit invitation: "what test could you run this week, without permission?"

**Shackleton note:** Stories can combine plots — Shackleton's Antarctic expedition is a Challenge plot (survival odds) wrapped around a Creativity plot (assigning the complainers to sleep in his own tent to contain their influence). If your story is legitimately dual, lead with the plot that matches your intended action.

**Artifact:** Add `story:` (the structured draft) to `story-structure.md`.

### Step 6: Write the opening line
**ACTION:** Write the first sentence of the story. It must do one thing: make the listener want to hear the second sentence. Drop the reader mid-scene or mid-question; do not start with context, a thesis statement, or a summary of the point.

**WHY:** Stories compete with the listener's attention budget. An opening line that explains the point before telling the story kills the mechanism — listeners evaluate the thesis instead of entering the scene. "In the late 1990s, Subway launched a campaign based on a statistic: Seven subs under six grams of fat. It didn't stick." is a better opener than "Today I want to talk about how stories are more memorable than statistics" because it pulls the listener into a concrete moment that has not yet revealed its point.

**Rules:**
- Opening line names one concrete thing (a place, a person, a weight, a date, an object).
- Opening line does not summarize the moral.
- For springboard stories, the opening line is also the hook — the rest must earn the listener's continued "little voice" engagement.

**Artifact:** Add `opening_line:` to `story-structure.md`.

### Step 7: Self-check against fabrication and fit
**ACTION:** Re-read the structured story and verify four things. Fix any failures or flag for the user.

**WHY:** The skill is worth nothing if it fabricates or if it produces a beautifully structured story that drives the wrong action. These four checks cover the common failure modes.

**Checks:**
1. **No fabrication.** Every fact, name, number, quote, and event traces back to the source material the user provided. If any detail is invented, mark it `[invented — verify or remove]`.
2. **Plot matches the intended action.** Re-read Step 1 and Step 2 — does the plot still line up? If the story drifted into inspiration for the wrong action during structuring, re-pick the plot.
3. **Daunting enough (Challenge only).** If it is a Challenge plot, the obstacle must feel daunting relative to the protagonist. If it doesn't, the story won't inspire effort — either find a stronger version or switch to a different story.
4. **Delivery mode honored.** If springboard: the conclusion is unstated. If direct: the claim is explicit and the story follows it as proof.

**IF** any check fails -> fix and re-run Step 5–7.
**ELSE** -> mark the artifact complete.

## Inputs
- **Intended audience response:** one-sentence target behavior.
- **Raw story material:** real anecdotes, news, customer stories, personal experience (OR a pool to mine from).
- **Occasion:** channel, time budget, where in the draft the story lives.
- **Audience profile:** who the listener is and what agency they have.

## Outputs
- **`story-structure.md`** — the single deliverable. Template:

```markdown
# Story Structure

## Intended Action
{one-sentence target behavior the listener should perform}

## Plot Classification
**Plot:** {Challenge | Connection | Creativity | none-fit}
**Why this plot:** {one line tying the intended action to the plot's inspiration mechanism}

## Mode
**Simulation / Inspiration:** {S | I | S+I}
**Why:** {one line}

## Delivery
**Mode:** {springboard | direct}
**Why:** {one line referencing audience agency and context diversity}

## Opening Line
> {the first sentence}

## Structured Story
{the story, arc-aligned, within the time budget}

## Caveats
- {any [invented — verify] flags}
- {any dual-plot notes}
- {whether a direct argument would actually fit better}
```

## Key Principles

- **Pick the plot by the action, not by the story you love.** A beautiful Creativity story used to inspire perseverance will teach listeners to look for clever shortcuts instead of working harder. The plot-to-action mapping is not negotiable: Challenge drives effort, Connection drives empathy, Creativity drives experimentation.
- **Simulation and inspiration are separate levers.** Ask which (or both) the occasion needs before you write. Xerox lunchroom shop talk is pure simulation (no uplift, just transferable diagnostic patterns). Jared Subway is both. Most keynote openers are pure inspiration. Get the mix right and the story carries the right weight.
- **Springboard beats direct when the audience has diverse contexts.** If every listener will apply the idea in a different setting (executive committee, cross-functional reorg, distributed teams), a springboard story lets each one generate their own application — you get breadth of buy-in in minutes. A direct argument in the same slot triggers the "little voice" to argue back and you lose the room.
- **Name the gulf explicitly (Connection plots only).** Modern audiences miss the social distance in old stories. "Good Samaritan" lands for Bible-literate audiences; "atheist biker gang member helping a stranded priest" lands for everyone else. If the gulf is invisible, the cross is invisible, and the story inspires nothing.
- **Daunting is relative, not absolute.** A Challenge plot is defined by whether the obstacle feels daunting *to the protagonist*, not by the absolute scale. Rose Blumkin postponing her 100th birthday to keep her store running is a Challenge plot. A 210-pound neighbor losing an inch of waist is not. If the story's stakes are low, it will not inspire listeners to take on their own hard things.
- **You do not invent stories — you spot them.** The Heaths' core claim in Chapter 6 is that life keeps handing you usable material; the skill is recognition, not fabrication. If the source material will not support the plot you want, find a different story — do not add details.
- **The opening line drops you into a scene.** First sentences that name a concrete thing (a place, a weight, a date, a person) beat first sentences that announce the thesis. A thesis-first opener lets the listener evaluate the claim instead of entering the story.

## Examples

**Scenario: keynote opener for a health-product launch**
Trigger: Founder says: "I have 90 seconds to open the keynote. I want the audience to believe a single person's daily choice can produce a huge outcome. I have three candidate stories: a Subway customer named Jared, a Harvard nutrition study, and my own cousin's weight-loss journey."
Process: (1) Intended action: "start a daily habit this week." (2) Plot: Challenge — protagonist overcomes daunting obstacle through perseverance. (3) Mode: S+I — listeners need both the pattern (how weight loss was done) and the emotional push. (4) Delivery: direct — one specific action requested, friendly launch audience, 90-second budget. Skip the Harvard study (no plot, no protagonist) and the founder's cousin (not public, audience cannot verify). Pick Jared. (5) Structure the Challenge arc: 425-pound college junior, size XXXXXXL shirts, swollen ankles and edema diagnosis, father's warning about dying before 35, 245-pound loss on daily Subway subs. (6) Opening line: "In the spring of 1998, a college junior named Jared Fogle wore size XXXXXXL shirts and a 60-inch waist." (7) Self-check: all facts verifiable from Subway campaign, daunting obstacle clear, plot matches action.
Output: `story-structure.md` with Challenge-plot Jared story, S+I mode, direct delivery, and a scene-drop opener.

**Scenario: change-management kickoff for a knowledge-management initiative**
Trigger: Program lead says: "I have 10 minutes at the next leadership offsite to introduce a new knowledge-management strategy. The 15 execs in the room run wildly different parts of the business. I need all of them to champion this back in their units. I have one anecdote about a colleague who found malaria-treatment data on the CDC website from a remote office in Zambia."
Process: (1) Intended action: "champion a knowledge-management initiative inside your own unit this quarter." (2) Plot: Creativity — the health-care worker's breakthrough was finding data on the internet in 1996. (3) Mode: S+I. (4) Delivery: springboard — diverse contexts (15 different business units), meaningful agency, buy-in required, not compliance. Each exec must generate their own version of "what would knowledge management look like in my unit?" A direct argument would be fought. (5) Structure: lean Creativity arc — name the old approach (siloed project knowledge, no sharing across countries), the frustration (a water-treatment guru in Zambia never meets a highway-construction guru in Bangladesh), the breakthrough moment (the worker in Kamana logging on and finding CDC data), the result (acted more effectively against malaria), implicit invitation left unstated. (6) Opening line: "In June 1995, a health-care worker in Kamana, Zambia — 360 miles from the capital — logged onto the internet and tried to find out how to fight malaria." (7) Self-check: no fabrication, plot matches action, delivery mode honored (conclusion stays implicit).
Output: `story-structure.md` with Creativity-plot Zambia springboard story, S+I mode, unstated conclusion that lets each exec project themselves in.

**Scenario: sales-training story for a new customer-success team**
Trigger: Training lead: "I need a story for the onboarding session. New CSMs tend to escalate every tricky ticket to engineering instead of troubleshooting. I want them to pattern-match on complex error states and try one or two hypotheses first. I have a transcript of a Xerox copier repairman explaining how he chased a misleading E053 error."
Process: (1) Intended action: "try two hypotheses on a tricky ticket before escalating." (2) Plot: Creativity — troubleshooting is mental breakthrough. (3) Mode: Simulation only — this is training, not motivation; the listener needs a transferable diagnostic pattern, not emotional lift. (4) Delivery: direct — onboarding, single unambiguous behavior requested, friendly audience, no "little voice" resistance. (5) Structure: lean Creativity arc — old approach (escalate on misleading error codes), the E053 error showing up and being genuinely misleading, the hypothesis-testing that led to the bad dicorotron diagnosis, the payoff (running long enough to confirm). (6) Opening line: "A copier salesperson at lunch said: 'The new XER board won't cook itself anymore — instead it trips the 24-volt interlock and crashes with an E053.'" (7) Self-check: all facts in user's transcript, plot matches action, simulation mode honored (no inspirational flourish).
Output: `story-structure.md` with Creativity-plot Xerox story, Simulation-only mode, direct delivery, and a mid-scene opener that teaches the shop-talk pattern.

## References
- For an extended catalog of worked examples (Jared Subway / Rose Blumkin / Shackleton Antarctic / Xerox lunchroom / Denning Zambia / Ingersoll-Rand grinder "drag test" / Good Samaritan modern reframe) with full source attribution and plot-arc markup, see [references/plot-example-catalog.md](references/plot-example-catalog.md)
- For the output template and worked filled-in example, see [references/output-template.md](references/output-template.md)

## License

This skill is licensed under [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/).
Source: [BookForge](https://github.com/bookforge-ai/bookforge-skills) — *Made to Stick: Why Some Ideas Survive and Others Die* by Chip Heath and Dan Heath.

## Related BookForge Skills

This skill is standalone. Browse more BookForge skills: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

FILE:references/output-template.md
# Output Template — `story-structure.md`

Copy this structure verbatim and fill in each field. A completed example follows.

## Template

```markdown
# Story Structure

## Intended Action
{One sentence. The verb the listener will perform after hearing the story. Not "be inspired" — an actual behavior.}

## Plot Classification
**Plot:** {Challenge | Connection | Creativity | none-fit}
**Why this plot:** {One line. Tie the intended action to the plot's inspiration engine.}

## Mode
**Simulation / Inspiration:** {S | I | S+I}
**Why:** {One line. Does the listener need to learn how to act, be moved to act, or both?}

## Delivery
**Mode:** {springboard | direct}
**Why:** {One line. Reference audience agency and context diversity.}

## Opening Line
> {The first sentence of the story. Drops the listener into a concrete scene — a place, person, date, weight, object. Does not summarize the moral.}

## Structured Story
{The story, aligned to the plot arc, within the time budget. Include only details that pull the intended-action lever.}

## Caveats
- {any [invented — verify] flags for details not in source material}
- {any dual-plot notes — which plot leads and why}
- {whether a direct argument would actually fit better than a story}
```

## Filled-in example

```markdown
# Story Structure

## Intended Action
Champion a knowledge-management initiative inside your own business unit this quarter.

## Plot Classification
**Plot:** Creativity
**Why this plot:** A remote health worker made a mental breakthrough by going outside normal channels to find malaria-treatment data on the CDC website — the arc inspires experimenting with new channels, which is what each executive needs to do in their own unit.

## Mode
**Simulation / Inspiration:** S+I
**Why:** Executives need the pattern (someone found useful knowledge outside the usual silos) AND the push to try the same in their own units.

## Delivery
**Mode:** springboard
**Why:** 15 execs run wildly different business units — each must generate their own version of "what would this look like in my world." A direct claim would wake the little voice in each exec to argue from their own context. Denning's original telling delivered this exact payload in 10-12 minutes.

## Opening Line
> In June 1995, a health-care worker in Kamana, Zambia — 360 miles from the nearest capital — logged onto the internet and tried to find out how to fight malaria.

## Structured Story
Kamana is a small town 360 miles from Zambia's capital. The health-care worker there was trying to fight malaria. There was no way to tap World Bank internal knowledge — a water-treatment guru in one country never meets a highway-construction guru in another. So he logged onto the internet and landed on the Centers for Disease Control's website in Atlanta. That's where he found the answers. This was 1996, long before the internet was the obvious first stop for anyone looking for anything.

{Conclusion intentionally unstated — each executive fills in "what would this look like in my unit?"}

## Caveats
- No fabrication — all facts from Denning's original *The Springboard* account as cited in *Made to Stick* Chapter 6.
- Dual-plot note: this also has faint Challenge-plot elements (finding information against the odds) but the inspirational engine is Creativity (going outside normal channels). Leading with Creativity because the intended action is experimentation.
- A direct argument ("we should build a knowledge-management function") would have been fought by each exec. The story fits better than a direct claim here.
```

FILE:references/plot-example-catalog.md
# Plot Example Catalog

Worked examples of each plot from Chapter 6 of *Made to Stick*, marked up with arc elements and delivery notes. Use these to calibrate your own plot classification and story structuring — not to copy verbatim.

## Challenge Plot

### Jared Fogle — Subway
- **Old approach that failed to stick:** Subway's "7 Under 6" statistical campaign (seven subs under six grams of fat) was factually strong but forgettable.
- **Protagonist + stakes:** Indiana college junior, 425 lbs, size XXXXXXL shirts, 60-inch waist, father (a GP) warning him he might not live past 35.
- **Obstacle (daunting relative to protagonist):** Needs to lose ~245 lbs without surgery or a program.
- **Attempt + resolution:** Starts eating a foot-long veggie sub for lunch and a six-inch turkey sub for dinner every day, loses the weight.
- **Why it sticks:** Every SUCCESs dimension fires — simple (two subs a day), unexpected (fast food as diet), concrete (60-inch waist), credible (anti-authority — he's not a doctor), emotional (rooting for Jared), story (Challenge plot).
- **Mode:** Simulation + Inspiration. Listeners learn *how* (the daily sandwich pattern) AND feel moved to try.
- **Delivery:** Direct. One unambiguous action (try Subway).
- **Use for:** Inspiring personal effort, habit change, "you could take on your thing too."

### Rose Blumkin
- Nebraska Furniture Mart founder, postponed her 100th birthday party until an evening when the store was closed. Not famous, not dramatic — just daunting-relative-to-protagonist perseverance. Low-scale Challenge plots still inspire because the engine is the relative bar, not the absolute scale.

### Shackleton's Antarctic expedition (dual-plot)
- Classic Challenge plot at the top level (survival odds against a frozen continent).
- Wraps a Creativity plot inside: Shackleton assigned complainers to sleep in his own tent, containing their influence by colocating them with leadership. A creative solution to a social-dynamics problem.
- **Use for:** Illustrating that dual-plot stories exist; lead with whichever plot matches the intended action.

## Connection Plot

### The Good Samaritan (modern reframe)
- **The gulf:** Samaritans and Jews had tremendous mutual hostility. The priest and Levite in the story share the wounded man's in-group; the Samaritan does not.
- **Modern analogy required:** The Heaths suggest "atheist biker gang member" to make the gulf visible to a contemporary audience that doesn't feel the Samaritan-Jew distance.
- **Structural beat:** The point of the story is not "be nice" — it is "cross the gulf even when you could walk past." The priest and the Levite are in the story specifically to mark the walk-past option.
- **Use for:** Inspiring cooperation across lines of difference, compassion to out-group members, any case where the listener could walk past.

### Xerox lunchroom shop talk — as Connection? No.
- The Xerox lunchroom story is frequently miscategorized. It is *not* a Connection plot — it's a Creativity plot delivered as simulation (pattern-recognition training). The "connection" is incidental (two repairmen talking); the engine is diagnostic breakthrough. See Creativity section.

## Creativity Plot

### Ingersoll-Rand Grinder Team — the "Drag Test"
- **Old approach:** Industrial grinder product cycles taking ~4 years. Standard method for testing plastic vs metal casings: protracted tensile and compression studies.
- **Frustration line:** "It was taking us longer to introduce a new product than it took our nation to fight World War II."
- **Breakthrough moment:** Team members tied a sample of each material to the back bumper of a car during an off-site customer visit and drove it around.
- **Result:** Fast signal on durability, team culture shifted toward action over study.
- **Use for:** Inspiring experimentation, breaking procedural patterns, "what test could you run this week without permission?"

### Xerox Copier Repair — the E053 error (pure simulation)
- A copier salesperson tells other repairmen at lunch about chasing a misleading E053 error for four hours that turned out to be a bad dicorotron.
- No emotional uplift. No protagonist arc. Pure knowledge transfer through story — listeners learn a diagnostic pattern they can apply next week.
- **Use for:** Training, onboarding, how-to contexts. Shows that stories can be used for simulation alone without inspiration.

## Springboard Stories (Delivery Mode, not a plot)

### Denning at the World Bank — Zambia malaria story
- **Occasion:** Stephen Denning, 1996, 10-12 minutes in front of World Bank senior management to introduce knowledge management as a strategy.
- **Story seed:** A health-care worker in Kamana, Zambia (360 miles from the capital) logged onto the internet and found CDC malaria data, because there was no way to tap World Bank internal knowledge across siloed projects.
- **Why springboard (not direct):**
  - Each executive ran a wildly different project area.
  - Denning wanted buy-in across skeptics, not compliance.
  - A direct argument would have engaged each exec's "little voice" to argue back from their own context.
  - A seed story let each exec mentally substitute their own project for "Zambia" and generate their own version of knowledge management.
- **Key Denning insight:** "When you hit listeners between the eyes they respond by fighting back... with a story, you engage the audience — you are involving people with the idea, asking them to participate with you."
- **The little voice:** Denning's phrase for the internal critic in every listener. A direct argument wakes it up to debate; a springboard story gives it something to do (generate its own second story).
- **Use for:** Change-management kickoffs, cross-functional strategy introductions, any setting where diverse listeners must each apply the same core idea in their own context.

## Decision Quick-Reference

| Want listener to... | Plot | Mode (S/I/both) | Delivery |
|---|---|---|---|
| Persevere, work harder | Challenge | I or S+I | Direct (most) |
| Bridge a social/functional gulf | Connection | I | Direct or springboard |
| Try a new approach | Creativity | S+I | Springboard (if diverse contexts) |
| Learn a diagnostic pattern | Creativity | S only | Direct |
| Kick off a change initiative | Creativity or Connection | S+I | Springboard |
| Open a keynote with emotional lift | Any (pick by message) | I | Direct |

---
name: sticky-message-antipattern-detector
description: Scan a draft, pitch, or copy for the named failure modes that kill stickiness — buried leads, decision paralysis, common-sense sedation, semantic stretch, stats-without-story, abstract strategy talk, scope creep, and the direct-message fallacy. Use this skill whenever a user asks to audit a draft, diagnose why a message is not landing, review a pitch, find the problems in copy, spot issues in an announcement, critique a marketing page, debug a speech, or check an internal memo — even when they do not explicitly use the word "stickiness". Activate on phrases like "audit this draft", "what is wrong with this message", "why is not this landing", "find the problems in this copy", "review my pitch", "spot the issues", "this is not resonating", "my announcement fell flat", "tell me what is broken in this email", "diagnose this speech", "why does not anyone remember what I said", "critique my copy", or any situation where the user supplies a short-form prose artifact and asks for a rigorous problem diagnosis rather than a rewrite. The skill produces a flagged-passage report with each instance located, severity-scored, and paired with a fix strategy — it does NOT rewrite the draft end-to-end and does NOT cover the Curse of Knowledge (that is a separate detector) or score the full six-principle SUCCESs rubric (that is a separate audit skill).
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/made-to-stick/skills/sticky-message-antipattern-detector
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: draft
source-books:
  - id: made-to-stick
    title: "Made to Stick: Why Some Ideas Survive and Others Die"
    authors: ["Chip Heath", "Dan Heath"]
    chapters: [1, 2, 3, 4, 5, 6, 12]
tags: [communication, diagnostic, anti-pattern, messaging, copywriting, editing, audit, writing, marketing, persuasion]
depends-on: []
execution:
  tier: 1
  mode: hybrid
  inputs:
    - type: document
      description: "Draft to audit — a message, pitch, announcement, ad, explainer, speech, slide, memo, or product page as markdown or pasted text"
    - type: document
      description: "Audience profile — who the draft is for, what they care about, what they already believe"
  tools-required: [Read, Write]
  tools-optional: [Grep]
  mcps-required: []
  environment: "Any agent environment with file read/write. Document-set working environment: the agent operates on short-form prose drafts provided by the user."
discovery:
  goal: "Surface every instance of eight named stickiness failure modes in a draft, with location, severity, and a concrete fix strategy for each."
  tasks:
    - "Audit a pitch, ad, or announcement for named stickiness anti-patterns"
    - "Diagnose why a message is not resonating with an audience"
    - "Produce a prioritized defect list before running a full rewrite"
  audience:
    roles: [marketer, founder, communicator, product-marketer, public-speaker, copywriter, teacher, fundraiser]
    experience: any
  when_to_use:
    triggers:
      - "User pastes a draft and asks what is wrong with it"
      - "User says a message is not landing and wants a diagnosis"
      - "User wants a rigorous defect report before rewriting"
    prerequisites: []
    not_for:
      - "Rewriting the draft end-to-end — use a message-clinic skill"
      - "Scoring the full SUCCESs six-principle rubric — use a stickiness-audit skill"
      - "Diagnosing expert blind spots specifically — use curse-of-knowledge-detector"
  environment:
    codebase_required: false
    codebase_helpful: false
    works_offline: true
---

# Sticky Message Anti-Pattern Detector

## When to Use

You have a draft — a pitch, ad, announcement, ad copy, speech, memo, slide, or product page — and the user has asked what is wrong with it, why it is not landing, or wants a rigorous defect report before rewriting. Use this skill when the goal is **named-defect diagnosis**, not rewriting. The output is a flagged-passage report that lists every instance of eight specific failure modes, each located, severity-scored, and paired with a fix strategy.

**Preconditions to verify before starting:**
- The draft exists as text the agent can read (pasted, markdown, or file path).
- The target audience is named with at least role + what they already care about. Without audience context, "common sense" and "semantic stretch" cannot be scored.
- The user wants diagnosis, not a rewrite. If they want a rewrite, produce the report first, then hand off.

**The eight anti-patterns this skill detects (each with a book citation):**

1. **Burying the Lead** — the most important fact is not in sentence one. (Ch 1 — Nora Ephron's journalism-teacher story; Carville's "It's the economy, stupid" was an antidote to Clinton burying his own lead.)
2. **Decision Paralysis** — multiple co-equal "top priorities" with no hierarchy. (Ch 1, Epilogue — Iyengar jam study 24→6, Redelmeier-Shafir doctor study, Jeff Hawkins's Palm team.)
3. **Common-Sense Trap** — the message says what every reader already believes. (Ch 2, Ch 6, Epilogue — "customer service is important" fails; Nordstrom "gift-wrap from Macy's" sticks.)
4. **Semantic Stretch** — words like *unique*, *strategy*, *awesome*, *great*, *amazing* are used so broadly they have lost meaning. (Ch 5 — Heath & Gould 2005 Stanford working paper; "unique" is no longer unique, "relativity" now means "it depends".)
5. **Stats Without Story** — claims are defended with numbers alone, not human-scale anchors. (Ch 4, Ch 5, Epilogue — 63% of students remember stories vs 5% remember individual statistics; Rokia/Save the Children identifiable-victim study; nuclear warheads demonstrated as BBs in a bucket.)
6. **Abstract Strategy Talk** — sentences live at the strategy level (synergies, vision, shareholder value) with no concrete observable behavior. (Intro, Ch 3 — Beth Bechky silicon chip engineers vs manufacturers; "maximize shareholder value" vs JFK moon mission.)
7. **Scope Creep** — the message tries to make three or more co-equal top points and therefore makes none. (Notes p.175 — "If you say three things, you don't say anything"; related to but distinct from decision paralysis.)
8. **Direct-Message Fallacy** — raw abstract directives delivered where a springboard story would transfer the idea better. (Ch 6 — Stephen Denning at the World Bank: "hit the listeners between the eyes, they fight back"; Velcro theory of memory.)

For detailed detection criteria, consequences, and fix recipes for each pattern, see [references/antipattern-catalog.md](references/antipattern-catalog.md).

---

## Context & Input Gathering

### Required Context (must have — ask if missing)

- **The draft:** The actual text to audit — not a summary.
  -> Check prompt for: pasted text, file path, document attachment.
  -> Ask if missing: "Paste the draft you want audited, or give me the file path."

- **The audience profile:** Who the draft is for, and what they already believe.
  -> Check prompt for: audience description, target persona, reader role.
  -> Ask if missing: "Who is this draft for? One sentence on (a) their role, (b) what they already care about, (c) what they already believe is obvious about this topic."

### Observable Context (gather from environment)

- **Channel and constraint:** Is this an ad (character limit), a speech (time limit), an email (subject-line constraint), a slide (visual), or long-form prose? Affects severity scoring.
  -> Infer from: length, formatting, user framing.
  -> If unclear: ask one question — "What format and where will this run?"

- **Tone constraints:** Brand or legal tone limits change which fixes are legal.
  -> Look for: user comments like "it has to stay on-brand" or "legal signed off on this phrasing".

### Default Assumptions

- **Assumption: audience cannot ask follow-up questions.** Drafts are read asynchronously. If the user corrects this, raise severity of buried-lead and scope-creep flags (readers cannot re-ask for the core).
- **Assumption: the author is an insider.** Make the author a secondary stickiness risk: the common-sense trap and abstract-strategy talk are more likely when the author is deep in the domain.

### Sufficiency Threshold

- **SUFFICIENT:** Draft text + audience with role and "what they already believe" + known channel.
- **PROCEED WITH DEFAULTS:** Draft + role-only audience. Flag the missing beliefs list in the report so the user can confirm.
- **MUST ASK:** No draft, OR audience is "general public" with no narrowing (too vague to score common-sense or semantic-stretch hits).

---

## Process

### Step 0: Initialize task tracking
**ACTION:** Create a TodoWrite checklist with one item per detection pass (Steps 2–9) plus Step 1 and Step 10.
**WHY:** Each anti-pattern targets a different axis (structural, lexical, narrative, prioritization). Fusing passes into a single scan defaults to the most visible axis (usually jargon-ish word problems) and silently drops the subtler ones — buried assumptions about common sense, semantic stretch in background phrases, scope creep across sections. The checklist enforces that every axis gets its own independent pass.

### Step 1: Establish the audience belief baseline
**ACTION:** Write a short profile of the audience: (a) role, (b) what they already believe is true / obvious about this topic, (c) what would genuinely surprise them, (d) what they actually care about (outcomes, pains, wins), (e) what counts as credible to them (data, peer stories, authority, personal anecdote). Use the user's supplied profile plus your reasoning.
**WHY:** Three of the eight anti-patterns — common-sense trap, semantic stretch, stats-without-story — can only be scored relative to a specific audience. "Customer service is important" is common sense to customer-service managers and news to a junior engineer. "Unique" is semantic stretch to a marketing buyer and fresh to a child. Skip this and the report becomes generic clarity advice.

**Save:** The audience belief baseline as Section 1 of the output report.

### Step 2: Pass AP-02 — Burying the lead
**ACTION:** Read the draft's first sentence (and for long pieces, the first paragraph). Ask: "Is this the single most important thing the reader must walk away with?" Then scan the whole draft for the sentence that SHOULD be the lead — the single fact, offer, news, or claim whose loss would gut the piece. If that sentence is not in position 1, flag `AP-02: Buried Lead`.
**WHY:** Journalism's inverted-pyramid rule exists because readers stop reading. The Heaths' Epilogue names this as the first villain for speakers: "we're tempted to share it all." If the actual news is buried in paragraph four, the audience never reaches it. Detection is mechanical — compare sentence 1 to the sentence you would keep if forced to delete 90% of the piece.

**For each hit record:** the actual first sentence (quote), the sentence that should be the lead (quote + location), severity (High if the lead is in paragraph 3+ or absent; Medium if in paragraph 2), and a fix strategy — usually "promote sentence X to position 1" with any needed connective tweaks.

### Step 3: Pass AP-03 — Decision paralysis
**ACTION:** Count the number of sentences that claim to be "the most important", "our top priority", "the key thing", or equivalent. Also count the number of top-level bullet lists with 5+ items framed as co-equal. Flag `AP-03: Decision Paralysis` if there is more than one "top" or if a co-equal list of five or more priorities is presented without a designated single core.
**WHY:** Iyengar's jam study (24 flavors → 3% bought; 6 flavors → 30% bought) and the Redelmeier-Shafir doctor study (doctors delay treatment when forced to choose among multiple good options) show that audiences freeze when confronted with multiple equally-weighted "bests". The Heaths explicitly prescribe "relentless prioritization: 'It's the economy, stupid.'" Detection is a simple count.

**For each hit record:** the conflicting "top" claims (quotes), severity (High if 3+ top claims; Medium if 2), and a fix strategy naming a single recommended core (or asking the user to pick one).

### Step 4: Pass AP-04 — Common-sense trap
**ACTION:** For each standalone claim sentence, ask: "Would a member of the audience, based on the belief baseline, nod in agreement BEFORE reading?" If yes — flag `AP-04: Common Sense`. Especially target sentences like "customer service is important", "communication is key", "quality matters", "our people are our greatest asset", "we are committed to excellence", "safety first", and any variant. Also flag any "advice" section whose advice the audience would already give.
**WHY:** Chapter 2 names this explicitly: "common sense is the enemy of sticky messages." The reader's guessing machine is not broken, so nothing is encoded to memory. The test in Epilogue: Nordstrom's "gift-wraps packages from Macy's" sticks because it breaks the schema of what a store does. Detection: any sentence the audience would have written themselves fails.

**For each hit record:** the flagged sentence, why it is common sense relative to the audience baseline, severity (High if it is the lead, Medium elsewhere), and a fix strategy — either the counter-intuitive reframe (surface the uncommon claim hiding in the material) or deletion.

### Step 5: Pass AP-05 — Semantic stretch
**ACTION:** Scan for stretched words. The book-named list (Heath & Gould 2005 working paper, Stanford): *unique*, *strategy*, *strategic*, *awesome*, *amazing*, *fantastic*, *great*, *excellent*, *innovative*, *leverage*, *synergy*, *world-class*, *best-in-class*, *relativity* as "it depends", *revolutionary*, *game-changing*. For each occurrence, check whether the word is carrying its original distinctive meaning in context (a genuine one-of-a-kind claim for "unique"; a real strategic choice for "strategy") or whether it has been diluted into a generic positive vibe.
**WHY:** Heath and Gould documented that extreme synonyms for "good" (fantastic, amazing) are increasing in use faster than less-extreme synonyms — i.e., the vocabulary is inflating. Overused words do not just fail to impress; they flatten any sentence they touch because the reader's processing discounts them to zero. Detection is a fixed-list scan with a context check.

**For each hit record:** the stretched word (with surrounding phrase), whether the original meaning is intact or diluted, severity (High if 3+ stretched words in one paragraph or in the lead; Medium if 1–2), and a fix strategy — narrow it to a concrete claim ("our onboarding is 30 minutes, half the category average" beats "we have an awesome onboarding experience") or revive the word's original force via a vivid anchor.

### Step 6: Pass AP-06 — Stats without story
**ACTION:** Count every statistic, percentage, or quantitative claim in the draft. For each, check whether it is paired with a human-scale anchor, a named person, or a concrete analogy ("5,000 nuclear warheads" → "one BB per thousand people in a bucket"; "400,000 children in need" → "one child, Rokia"). Compute the ratio of bare stats to anchored stats. Flag `AP-06: Stats Without Story` if any high-stakes stat is bare, or if the ratio of bare-to-anchored is worse than 1:1.
**WHY:** The Heaths cite a student-speech recall study directly: 63% of listeners remember stories; 5% remember any individual statistic. The Rokia/Save the Children study showed that a single identified child raised more than statistics about millions. Statistics do not engage the machinery that produces caring. Detection is mechanical — count and check for pairing.

**For each hit record:** the bare statistic (quote), why a human-scale anchor is needed, severity (High if the stat is load-bearing for the argument, Medium if decorative), and a fix strategy — either wrap the stat in a physical analogy (Human Scale principle), pair it with a single named person, or cut it if the story does the job alone.

### Step 7: Pass AP-07 — Abstract strategy talk
**ACTION:** Re-read each sentence and classify it as ACTION-level (names a concrete actor doing a concrete verb on a concrete object) or STRATEGY-level (goals, synergies, visions, competencies, alignment). Flag every sentence that sits at strategy level without an adjacent action-level translation. Especially target: "maximize shareholder value", "drive outcomes", "align around", "leverage synergies", "operational excellence", "execute our vision", "deliver value", "transform the business", "our North Star is X" (without naming the number and the specific target). Apply the "soccer team test": if you were the coach with this as your message, would your players know what to DO on Monday?
**WHY:** Chapter 3 uses the Beth Bechky silicon chip study: designers and manufacturers could not coordinate because they worked at different levels of abstraction. The Heaths contrast JFK's "man on the moon" (concrete, sensory, time-bound) with a modern CEO's "maximize shareholder value" (unbounded, opaque, unactionable). Abstract-only prose is grammatical but un-actionable. Detection: look for sentences without an actor-verb-object.

**For each hit record:** the abstract sentence, whether there is ANY concrete translation in the draft, severity (High if the whole draft lives at strategy level, Medium if mixed), and a fix strategy — either add an actor-verb-object concretization ("grow revenue 20% this year by winning back 10 lapsed accounts") or replace the sentence entirely with the behavior it implies.

### Step 8: Pass AP-08 — Scope creep
**ACTION:** Count the number of distinct top-level points, themes, or "key takeaways" in the draft. If there are 3 or more with no explicit hierarchy, flag `AP-08: Scope Creep`. This is related to but distinct from decision paralysis: paralysis is about competing priorities presented as co-equal, scope creep is about a piece trying to communicate too many separate ideas at once.
**WHY:** The Heaths cite the "If you say three things, you don't say anything" principle from a named comms expert (Notes p. 175). Mechanism: multiple priorities cancel each other out and the audience retains none. Common trigger: high school research papers where students feel obligated to include every unearthed fact. Detection is a section / theme count.

**For each hit record:** the enumeration of top points (quotes or summaries), severity (High if 4+ themes or the draft is long-form; Medium if exactly 3), and a fix strategy — name THE one core message (Commander's Intent) and demote the rest to supporting evidence or cut them.

### Step 9: Pass AP-09 — Direct-message fallacy
**ACTION:** Scan for passages that deliver abstract directives ("we need to be more X", "you should Y", "the key is to Z", "it is important to A") without any narrative scaffolding — no springboard story, no worked example, no before/after. Flag `AP-09: Direct Message Fallacy` where the piece is making an argument or prescribing a change and relies entirely on assertion rather than story.
**WHY:** Chapter 6 tells the Stephen Denning World Bank story: Denning initially believed in being direct and thought stories were "too ambiguous, too peripheral, too anecdotal". He found that when you "hit the listeners between the eyes, they fight back" — abstract directives do not simulate the outcome, so they cannot engage the listener's reasoning machinery. The Velcro theory: more hooks = more stickiness. Direct assertion has few hooks.

**For each hit record:** the directive passage, the change it is trying to cause, severity (High if this is a change-management or adoption message; Low-Medium if a status update), and a fix strategy — suggest a springboard-story frame ("tell us one concrete story where this worked, then name the principle") or identify an analogy / comparison the user could draft.

### Step 10: Synthesize the report
**ACTION:** Combine the nine passes into a single prioritized report. Structure:
1. **Audience belief baseline** (from Step 1).
2. **Scorecard** — a table with each anti-pattern, hit count, and max severity.
3. **Top 3 fix targets** — the three highest-impact hits across all passes, ranked by (severity × how much of the draft they poison). Each gets: quote, anti-pattern ID, why it hurts, specific fix.
4. **Full flagged-passage table** — every hit with columns: anti-pattern ID, location, passage, severity, fix strategy.
5. **Handoff note** — one decisive sentence: "cosmetic fixes" (stretch + stats only) vs "structural rework" (lead + scope + paralysis) vs "rewrite from core message" (common-sense + strategy-talk dominate).

**WHY:** The report's value is in ranked, actionable specificity. An unranked dump causes decision paralysis — the exact failure mode named in AP-03. The top-3 is the action surface; the full table is the audit trail; the handoff note tells the user what to DO with the report.

**Save:** The full report to `antipattern-report.md` in the user's working directory.

### Step 11: Structural self-check
**ACTION:** Before returning, verify: (a) every flagged passage has a location, a severity, and a fix — not just "this is bad"; (b) the top-3 are ranked, not listed; (c) the scorecard counts match the flagged-passage table; (d) the handoff note is one decisive sentence, not a hedge; (e) AP-01 (Curse of Knowledge) is NOT included — that is a separate skill.
**WHY:** Specificity is what makes this skill outperform generic critique. A report that says "the tone could be punchier" is indistinguishable from baseline advice. Location + severity + fix strategy is what gives the user something to act on. Missing the hedge-note check is the most common late-stage failure.

---

## Inputs

- `draft` — the text to audit (markdown, pasted text, or file path).
- `audience_profile` — role, what they already believe, what they care about, what counts as credible to them.
- Optional: `channel` — ad / email / slide / speech / memo / long-form (affects severity weighting).

## Outputs

A single file, `antipattern-report.md`, with this shape:

```markdown
# Sticky Message Anti-Pattern Report — {draft name}

## Audience Belief Baseline
{role, pre-read beliefs, what would surprise, what they care about, what is credible to them}

## Scorecard
| Anti-Pattern | Hits | Max Severity |
|---|---|---|
| AP-02 Buried Lead | ... | ... |
| AP-03 Decision Paralysis | ... | ... |
| AP-04 Common Sense | ... | ... |
| AP-05 Semantic Stretch | ... | ... |
| AP-06 Stats Without Story | ... | ... |
| AP-07 Abstract Strategy | ... | ... |
| AP-08 Scope Creep | ... | ... |
| AP-09 Direct Message | ... | ... |

## Top 3 Fix Targets
1. **{quote}** — {AP-ID}. Why: {reason}. Fix: {specific}.
2. ...
3. ...

## Flagged Passages
| AP-ID | Location | Passage | Severity | Fix |

## Handoff Note
{one decisive sentence: cosmetic | structural | rewrite-from-core}
```

---

## Key Principles

- **Named defects beat vibes.** "This feels vague" is a stylistic reaction. "AP-07 Abstract Strategy Talk — sentence lives at the strategy level with no actor-verb-object; needs concretization" is a diagnosis. Every flag MUST carry an anti-pattern ID and a fix strategy, or it is noise.

- **Scoring requires a baseline.** Three of the eight patterns (common sense, semantic stretch, stats without story) cannot be scored without a specific audience. The belief baseline (Step 1) is not decoration — it is the denominator for the scoring function. Skip it and you produce generic critique.

- **Mechanical passes beat impression passes.** The book's methodology is six independent principles, not one fused heuristic, precisely because humans and agents cannot hold all axes at once. This skill enforces the same structure: one pass per pattern, independent, in order. Fusing passes silently drops the subtler ones.

- **Rank ruthlessly, report faithfully.** The top-3 is the action surface; the full table is the audit trail. Both are required — top-3 alone lacks justification, full-table alone causes the exact decision paralysis (AP-03) this skill detects. The report structure is load-bearing.

- **The skill diagnoses; it does not rewrite.** The book distinguishes the Answer stage from the Telling Others stage. This skill operates at the Telling Others diagnostic layer — it flags and suggests fixes but does not produce the new prose. Crossing that boundary erodes the per-passage specificity that makes the audit valuable and hands off cleanly to a rewriting skill.

- **Severity is a function of position and stake.** A common-sense sentence in the lead is fatal; the same sentence in a parenthetical is a minor hit. A buried statistic in a decorative list is low-stakes; the same bare statistic in the close of a fundraising letter is a flameout. Always weight by where the flaw sits in the reader's attention path.

---

## Examples

**Scenario: SaaS product announcement email**

Trigger: User pastes a 400-word product email that opens "At Acme, we believe that communication is the key to great teams. That is why we are incredibly excited to announce our amazing new unified platform, which represents our strategic commitment to driving better outcomes. Our customers — over 5,000 of them — have been asking for integrations, a better inbox, and smarter notifications. We think you will love it." Audience: "Product managers at mid-market SaaS companies who already use our product."

Process: (1) Audience baseline notes PMs already believe "communication matters" and already use the product. (2) AP-02: buried lead — the actual news (unified platform) is in sentence 2 but buried under belief framing; the real "what changed" is unspecified. (3) AP-03: three co-equal "asks" (integrations, inbox, notifications) with no hierarchy. (4) AP-04: "communication is the key to great teams" is pure common-sense sedation for this audience. (5) AP-05: "incredibly excited", "amazing", "strategic commitment", "better outcomes" — four stretched words in two sentences. (6) AP-06: "over 5,000 customers" is a bare stat with no human scale. (7) AP-07: "driving better outcomes", "strategic commitment" are strategy-level with no behavioral anchor. (8) AP-08: three themes crammed into one email.

Output: `antipattern-report.md` with scorecard showing 8 hits. Top 3: (1) cut the opening "we believe" sentence and lead with the single biggest user-visible change; (2) pick ONE of the three features as the core of this email and demote the other two to a "also shipping" line; (3) replace "amazing", "strategic commitment", "better outcomes" with a concrete behavioral claim. Handoff note: "Structural rework — lead repositioning plus scope reduction to one feature."

**Scenario: Nonprofit fundraising letter**

Trigger: User pastes a 600-word letter that leads with organizational history, cites "We reached 1.2 million children across 14 countries", and closes with "We are committed to lasting impact." Audience: "First-time donors, $25–$100 range."

Process: (1) Baseline notes first-time donors do not know the org, care about individual impact, are moved by specific stories. (2) AP-02: buried lead — the "why you should give" is absent from sentence 1. (3) AP-06: 1.2M children / 14 countries is a bare stat with no Rokia-style anchor; high severity because this is the emotional close. (4) AP-04: "committed to lasting impact" is common-sense sedation. (5) AP-07: "lasting impact", "sustainable outcomes" are strategy-talk. (6) AP-09: entire letter is direct assertion with no springboard story.

Output: Scorecard shows 5 hits. Top 3: (1) open with a single named beneficiary (Rokia effect); (2) replace the 1.2M stat with a one-child story or an analogy that scales to a donor's $50 gift; (3) cut the commitment-to-impact sentence. Handoff note: "Rewrite from core message — this letter is architected around the org, not the donor's decision."

**Scenario: Internal strategy memo**

Trigger: CEO pastes a 500-word memo: "Team, our North Star is net revenue retention. We will drive synergies across BUs, maximize shareholder value, and align around operational excellence. Quality is non-negotiable, our people are our greatest asset, and I am confident we will achieve excellence together." Audience: "All 400 employees, roles from engineering to facilities."

Process: (1) Baseline: most employees do not know NRR, BUs, or what "shareholder value" means for their week. (2) AP-04: "quality is non-negotiable", "our people are our greatest asset", "I am confident" — three consecutive common-sense sentences. (3) AP-05: "synergies", "operational excellence", "excellence together" — three stretched words. (4) AP-07: entire memo is at strategy level with zero action-level sentences; invokes the Boeing 727 / JFK test and fails. (5) AP-08: NRR, synergies, shareholder value, quality, people, excellence — six co-equal themes.

Output: Scorecard shows all-strategy, all-common-sense, heavy stretch. Top 3: (1) add a "what changes for you on Monday" paragraph per role category; (2) cut the entire "quality / people / excellence" paragraph (common-sense sedation); (3) replace "North Star is NRR" with the actual number and the behavior change needed to hit it. Handoff note: "Rewrite from core message — this is the canonical 'maximize shareholder value' failure at scale."

---

## References

- For the full eight-entry catalog with detection criteria, book citations, consequences, and fix recipes, see [references/antipattern-catalog.md](references/antipattern-catalog.md)

---

## License

This skill is licensed under [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/).
Source: [BookForge](https://github.com/bookforge-ai/bookforge-skills) — Made to Stick: Why Some Ideas Survive and Others Die by Chip Heath and Dan Heath.

## Related BookForge Skills

This skill is standalone (Level 0 foundation). Browse more BookForge skills: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

FILE:references/antipattern-catalog.md
# Sticky Message Anti-Pattern Catalog

Eight named failure modes that kill stickiness, with detection criteria, book citations, consequences, and fix strategies. Derived from *Made to Stick* (Chip Heath & Dan Heath, 2007). Use this as the deep reference for the `sticky-message-antipattern-detector` skill.

Note: The Curse of Knowledge (the book's "villain") is NOT in this catalog — it is covered by the separate `curse-of-knowledge-detector` skill. This catalog contains the eight secondary named failure modes the Heaths warn against throughout the book.

---

## AP-02 — Burying the Lead

**One-liner:** The most important fact is not in sentence one.

**Detection criteria**
- The first sentence is background, caveats, history, or belief framing — not news.
- The single fact whose loss would gut the piece sits in paragraph 2 or later.
- Test: if forced to delete 90% of the draft, which sentence would you keep? That is the lead. Check if it is currently in position 1.
- Nora Ephron's journalism-teacher test: given "Principal Kenneth Peters announced today that the entire faculty will be attending a seminar on new teaching methods", the real lead is "There will be no school next Thursday".

**Book citation**
- Chapter 1 (Simple) — journalism inverted-pyramid rule, Nora Ephron story, and the Carville "It's the economy, stupid" antidote: Carville had to stop Clinton from burying his own lead when Clinton's instinct was to lead with "balanced budget".
- Epilogue — "The first villain is the natural tendency to bury the lead — to get lost in a sea of information. One of the worst things about knowing a lot, or having access to a lot of information, is that we're tempted to share it all."
- Easy Reference Guide — "Inverted pyramid: Don't bury the lead."

**Consequence**
Readers stop before they reach the lead. Inverted-pyramid violations are silently fatal: the draft looks complete but the audience retains nothing usable.

**Severity rubric**
- High: the lead is in paragraph 3+ or absent entirely; OR the first sentence is pure common-sense framing.
- Medium: the lead is in paragraph 2.
- Low: the lead is in sentence 2–3 of the first paragraph.

**Fix strategy**
Promote the buried sentence to position 1. Demote or delete the prior content. If the lead does not exist in the draft at all, the user must first extract it (Commander's Intent: the single sentence the piece must convey if everything else is lost).

---

## AP-03 — Decision Paralysis

**One-liner:** Multiple co-equal "top priorities" with no hierarchy cause the audience to freeze, defer, or pick nothing.

**Detection criteria**
- Count sentences claiming "the most important", "our top priority", "the key thing", "what matters most". More than one = flag.
- Co-equal lists of 5+ priorities presented without a designated single core.
- Test: ask "if the audience could only act on one of these, which should it be?" If the draft does not answer, it is paralysis.

**Book citation**
- Chapter 1 (Simple) — Decision Paralysis: "Why is prioritizing so difficult? Because what if we can't tell what's 'critical' and what's 'beneficial'? ... people can be driven to irrational decisions by too much complexity and uncertainty."
- Iyengar jam study (Chapter 1 & Notes): 24 flavors produced ~3% purchase; 6 flavors produced ~30% purchase — 10x difference from reducing the option set.
- Redelmeier-Shafir doctor study (Notes): doctors delayed prescribing any treatment when forced to choose among multiple equally good drugs.
- Epilogue — Jeff Hawkins's Palm team freezing on features; "students who missed both a fantastic lecture and a great film because they couldn't decide which one was better".
- Easy Reference Guide — "Beat decision paralysis through relentless prioritization: 'It's the economy, stupid.'"

**Consequence**
Audience takes no action. Worse, they may discount the piece entirely because the lack of priority signals low author confidence.

**Severity rubric**
- High: 3+ co-equal "top" claims, OR the paralysis is in an action-requesting piece (CTA, fundraising, product decision).
- Medium: exactly 2 co-equal "top" claims.
- Low: paralysis is in decorative content (values page, about section).

**Fix strategy**
Force a single core (Commander's Intent). Demote the rest to supporting evidence OR cut them. If the user cannot pick, ask a disambiguating question: "If your audience remembered exactly ONE thing from this, what would it be?"

---

## AP-04 — Common-Sense Trap

**One-liner:** The message says what every reader already believes — so nothing is encoded to memory.

**Detection criteria**
- Scan for claims the audience (per the belief baseline) would nod at BEFORE reading.
- Tell-tale phrases: "customer service is important", "communication is key", "quality matters", "our people are our greatest asset", "we are committed to excellence", "safety first", "innovation matters", "we care about our customers".
- Advice sections whose advice the audience would already give.
- The Nordstrom test (Epilogue): an uncommon-sense claim breaks the reader's schema. "Nordies gift-wrap packages from Macy's" sticks because it breaks the schema of what a store does.

**Book citation**
- Chapter 2 (Unexpected) — "Common sense is the enemy of sticky messages. When messages sound like common sense, they breeze right through the brain." The reader's guessing machine is not broken, so nothing is encoded.
- Chapter 6 (Emotional clinic) — "Notice that there's nothing unexpected here — nothing that is uncommon sense. ... Most of the advice ... is both too abstract and too obvious to stick."
- Chapter 2 — the local-news reporter Adams episode: "Names, names, and names" seems like common sense to reporters, but Adams broke their schema by going radically further.
- Epilogue — "Surprise them by breaking their guessing machines — tell them something that is uncommon sense."

**Consequence**
The reader nods, feels agreement, and forgets. Worse than jargon — jargon at least triggers a "huh?" reaction. Common-sense sedation produces zero friction and therefore zero encoding.

**Severity rubric**
- High: the common-sense sentence IS the lead, or dominates the close.
- Medium: common-sense sentences appear in body paragraphs.
- Low: parenthetical or transitional.

**Fix strategy**
Surface the uncommon claim hiding in the material. Ask: "What is the genuinely non-obvious, counter-intuitive thing you believe about this that your audience does not already believe?" Lead with that. Alternatively, cut the common-sense sentence entirely — the draft usually gets stronger, not weaker, when generic sedation is removed.

---

## AP-05 — Semantic Stretch

**One-liner:** Powerful words have been used so broadly they have lost their original distinctive meaning.

**Detection criteria**
- Scan for the stretched-word list (research-backed from Heath & Gould 2005): *unique*, *strategy*, *strategic*, *awesome*, *amazing*, *fantastic*, *great*, *excellent*, *innovative*, *leverage*, *synergy*, *world-class*, *best-in-class*, *relativity* as "it depends", *revolutionary*, *game-changing*, *disruptive*, *seamless*, *powerful*, *intuitive*.
- For each occurrence, check whether the word is carrying its original distinctive meaning in context or whether it has been diluted into a generic positive vibe.
- "Unique" test: is this genuinely one-of-a-kind, or could you substitute "nice" with no loss? If "nice" works, "unique" has been stretched.
- "Strategy" test: does this name a real strategic choice (doing X and not Y), or is it a fancy word for "plan"?

**Book citation**
- Chapter 5 (Emotional) — "Semantic Stretch and the Power of Association".
- Easy Reference Guide — "USE THE POWER OF ASSOCIATION. The need to fight semantic stretch: the diluted meaning of 'relativity' and why 'unique' isn't unique anymore. Transforming 'sportsmanship' into 'honoring the game.'"
- Notes — "Chip Heath and Roger Gould, 'Semantic Stretch in the Marketplace of Ideas,' working paper, Stanford University, 2005... extreme synonyms for the word good (e.g., fantastic or amazing) are increasing in use faster than synonyms that are less extreme."

**Consequence**
Stretched words fail to impress and silently flatten any sentence they touch. Readers' processing discounts them to near-zero; the writer thinks they have packed the sentence with emphasis but has actually delivered a bland neutral.

**Severity rubric**
- High: 3+ stretched words in one paragraph, OR stretched words in the lead/CTA.
- Medium: 1–2 stretched words in body copy.
- Low: stretched words in navigation, metadata, or decorative footer.

**Fix strategy**
Narrow it to a concrete claim. "Our onboarding is 30 minutes, half the category average" beats "we have an awesome onboarding experience". Alternatively, revive the word's original force via a vivid anchor: "honoring the game" replaced "sportsmanship" in youth sports programming because it carried concrete ritual weight. Or cut the word entirely — most sentences tighten when stretched words are removed.

---

## AP-06 — Stats Without Story

**One-liner:** Claims are defended with statistics alone, which are forgotten almost instantly, instead of human-scale anchors or single-person stories.

**Detection criteria**
- Count statistics, percentages, and quantitative claims. For each, check whether it is paired with (a) a named person, (b) a physical analogy ("5,000 nuclear warheads" → "one BB per thousand people in a bucket"), or (c) a concrete scenario.
- Ratio test: bare stats to anchored stats. Worse than 1:1 = flag.
- Load-bearing test: if a stat is the emotional close or core credibility anchor, it MUST be paired. A bare close is always high severity.

**Book citation**
- Chapter 4 (Credible) — "Since grade school, we've been taught to support our arguments with statistical evidence. But statistics tend to be eye-glazing."
- Chapter 4 — 5,000 nuclear warheads anti-example: "The statistic didn't stick. It couldn't possibly stick. No one who saw the demonstration would remember, a week later, that there were 5,000 nuclear warheads in the world. What did stick was the [BBs in bucket demo]."
- Chapter 5 (Emotional) — Rokia / Save the Children study: a letter with statistics about millions of African children raised less than a letter about a single identified child, Rokia. Identifiable-victim effect.
- Epilogue (student-speech recall study) — "In the average one-minute speech, the typical student uses 2.5 statistics. Only one student in ten tells a story... when students are asked to recall the speeches, 63 percent remember the stories. Only 5 percent remember any individual statistic." 63% vs 5% is the foundational ratio.

**Consequence**
Audience recalls nothing quantitative. Worse, stats without story suppress emotional engagement — the reader's analytic mindset is activated, which dampens caring. This is the Mother Teresa effect in reverse: aggregate suffering moves people less than a single identified person.

**Severity rubric**
- High: the bare stat is load-bearing (in the lead, the close, or the primary evidence block).
- Medium: multiple bare stats in body copy.
- Low: decorative stat in a navigation element, footer, or background paragraph.

**Fix strategy**
Three options: (1) wrap the stat in a physical analogy (Human Scale principle — BBs in a bucket, football fields, houses per city block); (2) pair it with a single named person (Rokia, Jared from Subway); (3) cut it if the story can carry the argument alone. The default recommendation is Option 2 if the audience needs to feel, Option 1 if the audience needs to comprehend magnitude, Option 3 if the argument already has a strong narrative.

---

## AP-07 — Abstract Strategy Talk

**One-liner:** Sentences live at the strategy level (synergies, vision, shareholder value) with no concrete observable behavior — readers cannot name what anyone would DO differently tomorrow.

**Detection criteria**
- Classify each sentence as ACTION-level (actor + verb + observable object) or STRATEGY-level (goals, synergies, visions, alignment).
- Flag every strategy-level sentence without an adjacent action-level translation.
- Tell-tale phrases: "maximize shareholder value", "drive outcomes", "align around", "leverage synergies", "operational excellence", "execute our vision", "deliver value", "transform the business", "best-in-class experience", "our North Star is X" (without naming the number).
- Soccer-team test (from Chapter 3, via Stephen Covey): if you were the coach with this as your message, would your players know what to DO on Monday?
- Boeing 727 test: replace the abstract sentence with a concrete constraint ("seat 131 passengers, land on Runway 4-22 under a mile long"). Does the sentence gain or lose meaning? If concrete GAINS meaning, the abstract original is a hit.

**Book citation**
- Introduction — "Mission statements, synergies, strategies, visions — they are often ambiguous to the point of being meaningless. ... Let's take the CEO who announces... 'maximize shareholder value.' Is this idea simple? ... Is it concrete? Not at all."
- Chapter 3 (Concrete) — "Even the most abstract business strategy must eventually show up in the tangible actions of human beings. It's easier to understand those tangible actions than to understand an abstract strategy statement."
- Chapter 3 — Beth Bechky silicon chip study: engineers and manufacturers could not coordinate because they worked at different levels of abstraction. Coordination only happened when both groups walked the concrete chips on the factory floor.
- Chapter 3 — JFK "man on the moon by the end of the decade" contrasted with "maximize shareholder value".

**Consequence**
Grammatical but un-actionable prose. Audience reads, understands the words, and walks away with no behavior change. Cross-functional teams cannot coordinate because abstract language hides the concrete work each side must do.

**Severity rubric**
- High: entire draft lives at strategy level with no action-level translation.
- Medium: mixed, but the lead and close are strategy-only.
- Low: occasional strategy-level sentences in a mostly concrete draft.

**Fix strategy**
Add an actor-verb-object concretization for every flagged sentence. "Grow revenue" becomes "win back 10 lapsed accounts worth $500K by end of Q2 via personal outreach from the CS team". If the strategy sentence cannot be concretized, the strategy itself is probably incoherent — surface that to the user rather than trying to polish the prose.

---

## AP-08 — Scope Creep (Three Messages Equals No Message)

**One-liner:** The draft tries to make three or more co-equal top points and therefore makes none.

**Detection criteria**
- Count distinct top-level points, themes, or "key takeaways". 3+ with no explicit hierarchy = flag.
- Related to but distinct from AP-03 (Decision Paralysis): paralysis is about conflicting priorities presented as co-equal, scope creep is about a piece trying to communicate too many separate ideas at once.
- High school research-paper pattern: the author feels obligated to include every unearthed fact.

**Book citation**
- Notes p. 175 — "If you say three things, you don't say anything" (attributed comms expert quote).
- Chapter 1 — "If 'it's the economy, stupid' is the lead, then the need for a balanced budget can't also be the lead."
- Epilogue — "High school teachers will tell you that when students write research papers they feel obligated to include every unearthed fact."

**Consequence**
Audience retains zero. Multiple priorities cancel each other out. This is particularly pernicious in long-form copy where the author feels each paragraph is "important" — the sum is less memorable than any single paragraph would have been on its own.

**Severity rubric**
- High: 4+ themes, or the draft is long-form (speech, memo, landing page) with no hierarchy.
- Medium: exactly 3 themes with no designated core.
- Low: 3 themes with a clear primary and two supports.

**Fix strategy**
Name THE one core message (Commander's Intent). Demote the rest to supporting evidence for the core, OR cut them into separate drafts. Hard rule: one core per draft. If the user insists all three matter, split into three separate artifacts rather than combining.

---

## AP-09 — Direct-Message Fallacy

**One-liner:** Raw abstract directives delivered where a springboard story would transfer the idea better.

**Detection criteria**
- Scan for change-management or adoption messages delivered as abstract directives — "we need to be more X", "you should Y", "the key is to Z", "it is important to A".
- No narrative scaffolding: no springboard story, no worked example, no before/after.
- Especially dangerous in change-management contexts (new strategy, culture change, process change) where stories transfer adoption but directives trigger resistance.

**Book citation**
- Chapter 6 (Stories) — Stephen Denning, World Bank: "had always believed in the value of being direct, and he worried that stories were too ambiguous, too peripheral, too anecdotal. He thought, 'Why not spell out the message directly? ... Why not hit the listeners between the eyes?' The problem is that when you hit listeners between the eyes, they fight back."
- Chapter 6 — Velcro theory of memory: "A story is powerful because it provides the context missing from abstract prose. It's back to the Velcro theory of memory, the idea that the more hooks we put into our ideas, the better they'll stick."

**Consequence**
Listeners hear but do not internalize. Abstract directives do not simulate the outcome and so cannot engage the listener's reasoning machinery. Worse, direct directives in change contexts trigger defensive reactions ("fight back") — the opposite of the intended adoption.

**Severity rubric**
- High: the piece is a change-management or adoption message delivered entirely as directive.
- Medium: the piece is informational but relies on assertion where a story would work better.
- Low: the piece is a status update or FAQ where direct delivery is appropriate.

**Fix strategy**
Suggest a springboard-story frame: "tell us one concrete story where this worked, then name the principle". Denning's pattern at the World Bank: a single story of a health worker in Zambia finding CDC information online did more to spark the idea of a knowledge-sharing organization than any directive ever could. If no story is available, suggest an analogy or comparison the user could draft. Acknowledge that direct delivery is sometimes correct (status updates, FAQs) — the flag is only material in change contexts.

---

## Severity Weighting Summary

| Factor | Effect on severity |
|---|---|
| Hit is in the lead sentence | +1 level (Medium → High) |
| Hit is in the close or CTA | +1 level |
| Hit is in a change-management / adoption piece | +1 level for AP-09 specifically |
| Hit is in a decorative / navigation element | -1 level |
| Hit count in same paragraph ≥ 3 | +1 level (compound failure) |

---

## Cross-Pattern Interactions

- **AP-02 (Buried Lead) + AP-04 (Common Sense):** the most common compound failure. The buried lead symptom is usually caused by common-sense sedation in the first sentence. Fix common sense first; the lead often reveals itself.
- **AP-03 (Paralysis) + AP-08 (Scope Creep):** overlapping but distinct. Paralysis is about choosing among competing priorities; scope creep is about failing to choose. A draft can have both (too many themes AND no designated primary).
- **AP-05 (Semantic Stretch) + AP-07 (Abstract Strategy):** stretch words are the atomic units of strategy talk. A draft heavy on "leverage synergies to drive outcomes" is simultaneously a semantic-stretch hit and an abstract-strategy hit. Fix them together.
- **AP-06 (Stats Without Story) + AP-09 (Direct Message):** both are about using the wrong register. Stats without story fails because data does not simulate outcome; direct-message fallacy fails because assertion does not simulate outcome. Story solves both.

---

## What This Catalog Does NOT Cover

- **Curse of Knowledge (AP-001 in hunter findings):** handled by the separate `curse-of-knowledge-detector` skill. That skill covers lexical jargon, tacit shared context, and expert blind spots. This catalog's AP-07 (Abstract Strategy Talk) overlaps slightly, but is scoped to strategy-level abstraction as a stickiness failure rather than as an expert-audience mismatch.
- **The full six-principle SUCCESs scoring rubric:** handled by a separate stickiness-audit skill. This catalog is diagnostic (find defects), not evaluative (score the message).
- **Rewriting the draft:** this catalog and its parent skill produce defect reports. Rewriting is downstream and belongs to a separate message-clinic skill.

---
name: stickiness-audit
description: Run the full SUCCESs stickiness audit on a draft message, pitch, announcement, slide, speech, landing page, or internal memo — the book's capstone diagnostic. Scores the draft across the six SUCCESs principles (Simple, Unexpected, Concrete, Credible, Emotional, Stories) plus the Curse of Knowledge villain axis on a 0/1/2 per-dimension scale (it is a checklist, not an equation), quoting evidence from the draft for every score and producing a top-3 prioritized fix list ranked by impact times effort. Use this skill whenever the user says things like "audit this message", "score this draft", "is this sticky", "run the SUCCESs check", "run the checklist", "will people remember this", "how good is this pitch", "rate this against Made to Stick", "does this pass the kidney heist test", "will this land", "stickiness review", "why is nobody remembering our launch", "I need a communications review", or when any user pastes a draft and asks whether it will resonate, be remembered, or change behavior. Also triggers when a user is about to ship a message and wants a last-mile quality gate, when someone asks for a one-page communications critique, or when a team is choosing between two draft versions and needs a principled scoring method. This skill produces a stickiness scorecard with dimension-level verdicts, evidence, prioritized fixes, and a recommendation for which specialist skill to invoke next (curse-of-knowledge-detector, core-message-extractor, curiosity-gap-architect, concrete-language-rewriter, credibility-evidence-selector, emotional-appeal-selector, story-plot-selector, or sticky-message-antipattern-detector). It does NOT perform the end-to-end rewrite — that is owned by the message-clinic workflow.
version: 1.0.0
homepage: https://github.com/bookforge-ai/bookforge-skills/tree/main/books/made-to-stick/skills/stickiness-audit
metadata: {"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status: draft
source-books:
  - id: made-to-stick
    title: "Made to Stick: Why Some Ideas Survive and Others Die"
    authors: ["Chip Heath", "Dan Heath"]
    chapters: [1, 2, 3, 4, 5, 6, 12, 13]
tags: [communication, messaging, audit, scorecard, diagnostic, rubric, stickiness, success-framework, copywriting, communications-review]
depends-on:
  - curse-of-knowledge-detector
  - core-message-extractor
  - curiosity-gap-architect
  - concrete-language-rewriter
  - credibility-evidence-selector
  - emotional-appeal-selector
  - story-plot-selector
  - sticky-message-antipattern-detector
execution:
  tier: 1
  mode: hybrid
  inputs:
    - type: document
      description: "Draft to audit — a message, pitch, announcement, slide, landing page, memo, tweet, speech, or email body as markdown or pasted text"
    - type: document
      description: "Audience description — role, context, and what they care about"
    - type: document
      description: "Goal — what the user wants the audience to remember, feel, or do after reading"
  tools-required: [Read, Write]
  tools-optional: [Grep, TodoWrite]
  mcps-required: []
  environment: "Any agent environment with file read/write. Document-set working environment: the agent operates on short-form prose drafts supplied by the user."
discovery:
  goal: "Produce a rigorous, evidence-quoted SUCCESs + Curse-of-Knowledge scorecard for any draft, plus a top-3 prioritized fix list and a handoff recommendation to the right specialist skill."
  tasks:
    - "Score a draft pitch or announcement against the SUCCESs six-principle rubric"
    - "Decide which Made-to-Stick specialist skill should handle the highest-leverage fix"
    - "Compare two draft versions on a common stickiness scale before choosing one"
    - "Run a last-mile communications review before shipping"
  audience:
    roles: [marketer, founder, communicator, product-manager, teacher, technical-writer, fundraiser, internal-comms]
    experience: any
  when_to_use:
    triggers:
      - "User provides a draft and asks whether it will be remembered, resonate, or land"
      - "User wants a principled comparison between two or more draft versions"
      - "User is about to ship a high-stakes message and wants a pre-flight check"
    prerequisites: []
    not_for:
      - "Rewriting a draft end-to-end — hand off to message-clinic-runner"
      - "Running a single-axis check only — use the specialist skill for that axis directly"
  environment:
    codebase_required: false
    codebase_helpful: false
    works_offline: true
---

# Stickiness Audit

## When to Use

You have a draft message — a pitch, announcement, slide, landing page, memo, tweet, speech, or email — and you need a rigorous, evidence-grounded verdict on how sticky it is before shipping or choosing between versions. Use this skill when the goal is **diagnosis and prioritization**, not rewriting.

**Preconditions to verify before starting:**
- The draft exists as text the agent can read (paste, markdown file, or document).
- The audience is named (even roughly — "mid-market SaaS buyers", "all 400 employees", "first-time donors").
- The user's goal for the message is stated or can be extracted — what must the reader remember, feel, or do?

**The framing restated for the agent:** Sticky ideas — per the kidney heist urban legend used throughout Made to Stick as the gold standard — satisfy six principles and defeat one villain:
- **S**imple — Find the core and make it compact.
- **U**nexpected — Break a pattern; open a curiosity gap.
- **C**oncrete — Use sensory, observable language.
- **C**redible — Let the message vouch for itself (Sinatra test, vivid details, testable credentials).
- **E**motional — Make the reader feel something, usually by way of a specific person, not statistics.
- **S**tories — Use a plot (Challenge, Connection, or Creativity) that teaches or inspires action.
- **Villain: the Curse of Knowledge** — the expert blind spot that tempts the author to tap a tune only they can hear.

The scoring is **0/1/2 per dimension**, not a cumulative score. The book is emphatic: *"It's a checklist, not an equation."* A 2 on Emotional does not cancel a 0 on Simple. The audit surfaces gaps; the user fixes them.

---

## Context & Input Gathering

### Required Context (must have — ask if missing)

- **The draft:** The actual text to audit — not a summary.
  -> Check prompt for: pasted text, file path, document attachment.
  -> Ask if missing: "Paste the draft you want me to audit, or give me the file path."

- **The audience:** Who the draft is for.
  -> Check prompt for: audience description, persona, reader profile.
  -> Ask if missing: "Who is this for? One sentence: role + context + what they care about."

- **The goal:** What must the reader remember, feel, or do after reading?
  -> Check prompt for: phrases like "I want them to…", "the ask is…", "the takeaway should be…".
  -> Ask if missing: "If a reader forgets everything except one thing, what must that one thing be? And what do you want them to do next?"

### Observable Context (gather from environment)

- **Channel and length constraints:** A tweet and a keynote have different stickiness tolerances.
  -> Infer from: file name, format, stated character limits.
  -> Default if unclear: treat as a "short-form written message."

- **Prior versions:** A note like "we've already simplified it twice" tells you the Simple axis is already contested territory.
  -> Look for: user comments about previous drafts.

### Default Assumptions

- **Assumption: the draft's author is closer to the subject than the reader.** The Curse of Knowledge axis defaults to ON; you must actively score it.
- **Assumption: the reader cannot ask follow-up questions.** Most drafts are read asynchronously.
- **Assumption: "sticky enough" means the reader can recall the core message 24 hours later and act on it.** State this in the scorecard.

### Sufficiency Threshold

- **SUFFICIENT:** Draft text + audience description + stated goal.
- **PROCEED WITH DEFAULTS:** Draft + audience with role only. Flag the missing goal as `[assumed goal: X]` in the scorecard so the user can correct.
- **MUST ASK:** No draft, OR audience is "general public" with no narrowing (too vague to detect insider assumptions).

---

## Process

### Step 0: Initialize task tracking
**ACTION:** Create a TodoWrite checklist with one entry per dimension (Simple, Unexpected, Concrete, Credible, Emotional, Stories, Curse of Knowledge) plus "synthesize scorecard" and "structural self-check".
**WHY:** Seven axes in sequence is too many to hold in working memory; fused into one pass the agent defaults to whichever axis is most visible (usually Concrete or Simple) and under-scores the subtler ones (Curse of Knowledge, Emotional). The book's entire methodology is structured axis-by-axis because human authors cannot hold all seven at once. Tracking enforces the discipline.

### Step 1: Establish the audit frame
**ACTION:** Write a short frame at the top of your working notes that captures: (a) the draft's title or first sentence, (b) the audience in one line, (c) the stated goal (what must the reader remember / feel / do), (d) the channel, (e) whether this is a new draft or a comparison against a prior version. This is the lens you will score against.
**WHY:** Stickiness is always relative to an audience and a goal. A pitch that is 2/2 on Emotional for donors may be 0/2 for procurement buyers. Without an explicit frame every dimension score becomes a generic "is this good writing" judgment — which is exactly the failure mode a baseline agent produces.

**Save:** The audit frame as the first section of the scorecard.

### Step 2: Score dimension S — Simple
**ACTION:** Apply two tests. **Core test:** Can you state what the draft is *really* about in one sentence? If the draft makes more than one core claim, or the core is buried under context, it fails the core test. **Compact test:** Is the core expressed with a proverb-like compactness (short, memorable, pre-loaded with meaning)? Use the rubric in `references/success-dimension-rubric.md` for 0/1/2 criteria. Quote one passage as evidence for the score.
**WHY:** Chapter 1's central claim is that stickiness begins with Find the Core + Commander's Intent + proverb-compact expression. A draft that is missing a core is not "almost sticky" — it is structurally un-sticky, because there is nothing for the other principles to amplify. The Introduction's "maximize shareholder value" worked example is the canonical 0/2 on Simple: it states a vague goal the whole company could already agree with, which is the opposite of a core.

**If Simple scores 0 or 1** -> flag "core-message-extractor" as the recommended next step.

### Step 3: Score dimension U — Unexpected
**ACTION:** Ask two questions. **Pattern break:** Does the opening violate a schema the reader holds? Does it surprise them with something their mental model did not predict? **Curiosity gap:** Does the draft open a question in the reader's mind that the draft (or a follow-up) then closes? A draft that answers a question the reader was not yet asking cannot build curiosity. Score 0/1/2 per the rubric; quote evidence.
**WHY:** Chapter 2's mechanism is the gap theory of curiosity: readers only pay attention when they notice a gap between what they know and what they want to know. Drafts that lead with common-sense framing ("customer service is important") pre-fill the gap and lose attention in the first sentence. The kidney-heist story scores 2/2 here because "woke up in a bathtub of ice" violates every schema the reader holds.

**If Unexpected scores 0 or 1** -> flag "curiosity-gap-architect" as the recommended next step.

### Step 4: Score dimension C — Concrete
**ACTION:** Mark every noun in the draft that is either abstract (strategy, synergy, value, platform, solution, impact) or sensory/observable (ice, bathtub, runway, 131 passengers, Jared's pants). Compute rough ratio. **Boeing 727 test:** If you replaced the draft's abstract phrases with measurable constraints ("seat 131 passengers, land on a mile-long runway"), would meaning be lost or gained? If gained, the draft is under-concrete. Score 0/1/2 per the rubric; quote evidence.
**WHY:** Chapter 3 argues concreteness is the Velcro principle — more sensory hooks means more places for memory to stick. Abstract-only writing reads fine but leaves no residue. Non-experts can only anchor to concrete objects ("bishops moving diagonally", not "chess strategy"). JFK's "man on the moon this decade" is 2/2 Concrete; a modern CEO's "maximize shareholder value" is 0/2.

**If Concrete scores 0 or 1** -> flag "concrete-language-rewriter" as the recommended next step.

### Step 5: Score dimension C — Credible
**ACTION:** Identify every credibility move in the draft and classify it: **external authority** (expert quote, institutional citation), **anti-authority** (a credible first-person skeptic or ex-smoker type), **internal vivid details** (Hyundai cancer-cluster specificity), **statistics with a human anchor** (Nukes Stanford distance example), **Sinatra test** (one overwhelming example that alone makes the case — "if you can make it there…"), **testable credentials** (Wendy's "Where's the beef?" — a claim the reader can personally verify). A draft can score 2/2 with only one of these, done well. Drafts that lean on unverified adjectives ("world-class", "proven", "leading") score 0. Quote evidence.
**WHY:** Chapter 4's insight is that credibility is not the same as citations. The Heaths argue a single vivid detail (sweater color at the hospital visit) often out-credits a paragraph of statistics, because the reader's brain registers specificity as evidence of first-hand knowledge. Drafts that bury their credibility behind unverifiable adjectives fail here even if everything they say is technically true.

**If Credible scores 0 or 1** -> flag "credibility-evidence-selector" as the recommended next step.

### Step 6: Score dimension E — Emotional
**ACTION:** Ask three questions. **Who specifically?** Does the draft point to one identifiable person (Rokia, not "Africa's hungry")? **Which identity?** Does the draft connect to an identity the reader already holds ("Don't mess with Texas" triggers Texas-pride identity)? **Which associations?** Is the draft pulling emotional weight from associations the reader actually values (the reader's own kids vs. the author's abstract concern for "the community")? The Mother Teresa effect: a single identified victim beats a statistical many, every time. Score 0/1/2 per the rubric; quote evidence.
**WHY:** Chapter 5's claim is that emotion is not about making readers sad — it is about making them care, which requires wiring the message into an existing emotional circuit the reader already has. Statistics bypass emotion; specific people route through it. Drafts that try to manufacture emotion through adjective stacking ("devastating", "heart-wrenching") score lower than drafts with a named person and one concrete detail.

**If Emotional scores 0 or 1** -> flag "emotional-appeal-selector" as the recommended next step.

### Step 7: Score dimension S — Stories
**ACTION:** Determine whether the draft tells a story or merely asserts claims. A story has a **subject acting** (actor + verb), a **complication or challenge**, and a **resolution or lesson**. Identify the plot type if present: **Challenge plot** (underdog overcomes obstacle — Jared/Subway), **Connection plot** (bridge across a gap — Good Samaritan), **Creativity plot** (insight solves a puzzle — Apollo 13). A bullet list of features is not a story; a narrative about one user's specific day is. Score 0/1/2 per the rubric; quote evidence.
**WHY:** Chapter 6 argues stories are mental flight simulators — they rehearse behavior in a way assertions cannot. The kidney heist is a story; "the security of your body is at risk when traveling" is an assertion. The same idea, one sticks. Drafts that have strong Concrete and Emotional scores but 0 on Stories usually fail to change behavior because the reader never got to rehearse the action mentally.

**If Stories scores 0 or 1** -> flag "story-plot-selector" as the recommended next step.

### Step 8: Score the villain axis — Curse of Knowledge
**ACTION:** Re-read the draft from the audience's point of view. List every term, acronym, framework reference, named internal tool, or buried assumption that would force a non-expert reader to pause. Apply the tapper/listener heuristic: if the author "knows what they mean" but the reader would not, the draft is tapping. Score 0/1/2 per the rubric (0 = visibly corrupted by expertise, 1 = some insider residue, 2 = a non-expert could parse it cold). Quote evidence.
**WHY:** The Curse of Knowledge is the book's named villain, and the Epilogue treats it as the root cause of most stickiness failures. It is scored separately from Simple because a draft can have a clear core and still be Curse-corrupted (the core is clear to insiders and opaque to outsiders). Scoring it as a seventh dimension prevents the agent from collapsing it into Simple and under-counting its impact.

**If Curse of Knowledge scores 0 or 1** -> flag "curse-of-knowledge-detector" as the recommended next step for deeper diagnosis.

### Step 9: Anti-pattern sanity pass
**ACTION:** Before synthesizing, run a quick check for the three named anti-patterns the book warns about: **burying the lead** (is the actual news in paragraph 4?), **decision paralysis** (does the draft offer too many options so the reader picks none?), and **analysis by jargon / common-sense sedation** (sentences any reader would already nod along to before reading). If any fire, add them as cross-cutting findings to the scorecard — they usually explain why a draft can score 1s across the board but still fail.
**WHY:** These anti-patterns are not captured cleanly by any single dimension. A draft can be Concrete, Credible, and Emotional while still burying the lead in paragraph 4 — at which point no one reads far enough to hit the good stuff. For deeper diagnosis of these patterns, delegate to `sticky-message-antipattern-detector`.

### Step 10: Synthesize the scorecard
**ACTION:** Produce a single markdown file, `stickiness-scorecard.md`, using the template at `references/scorecard-template.md`. It must include:
1. **Audit frame** — draft title, audience, goal, channel.
2. **Scorecard table** — seven rows (S, U, C, C, E, S, Curse), each with: score (0/1/2), one-sentence verdict, quoted evidence.
3. **Kidney-heist comparison line** — one sentence naming which dimensions the draft hits at 2/2 kidney-heist level and which it misses.
4. **Top 3 rewrite targets** — ranked by (severity × how much of the draft they poison). Each target gets: dimension, quoted passage, specific fix, estimated effort (S/M/L).
5. **Handoff recommendations** — for each dimension that scored 0 or 1, the name of the specialist skill to invoke next and why that skill (not another) is the right next step.
6. **Final verdict** — one of: **Sticky (ready to ship)**, **At risk (fix top 2 before shipping)**, **Not sticky (structural rework required)**. State which thresholds triggered the verdict.

**WHY:** The user is not here for a long table — they are here for a decision. The scorecard's value is the top-3 + handoff + verdict. Without those three artifacts the audit produces decision paralysis, which is the exact anti-pattern Chapter 1 warns about. The kidney-heist comparison is the book's own gold-standard calibration — it forces the audit to be concrete about *how much better* the draft could be.

**Save:** `stickiness-scorecard.md` in the user's working directory.

### Step 11: Structural self-check
**ACTION:** Before returning, verify: (a) every dimension has a score, a verdict, AND quoted evidence — not just a number; (b) the kidney-heist comparison line is present; (c) the top-3 are actually ranked (not just listed) and each names an effort estimate; (d) the handoff recommendations name specific specialist skills from the dependency list, not generic advice; (e) the final verdict matches the dimension scores (cannot say "Sticky" with two 0s on the card); (f) no dimension was collapsed into "it's fine" without evidence.
**WHY:** The audit's value is specificity + decisiveness. A scorecard that says "could be improved" on every axis is indistinguishable from baseline agent output. Quoted evidence, ranked top-3, and named handoffs are what make this skill book-derived rather than generic writing feedback.

---

## Inputs

- `draft` — the text to audit (markdown, pasted text, or file path).
- `audience` — one sentence: role + context + what they care about.
- `goal` — what the reader must remember, feel, or do after reading.
- Optional: `prior_version` — a previous draft for comparative scoring.

## Outputs

A single file, `stickiness-scorecard.md`, following the template at [references/scorecard-template.md](references/scorecard-template.md). At a glance:

```markdown
# Stickiness Scorecard — {draft name}

## Audit Frame
- Audience: {...}
- Goal: {...}
- Channel: {...}

## Scorecard
| Dimension            | Score | Verdict (one line)       | Evidence (quoted)    |
|----------------------|-------|--------------------------|----------------------|
| Simple               | 0/1/2 | {...}                    | "..."                |
| Unexpected           | 0/1/2 | {...}                    | "..."                |
| Concrete             | 0/1/2 | {...}                    | "..."                |
| Credible             | 0/1/2 | {...}                    | "..."                |
| Emotional            | 0/1/2 | {...}                    | "..."                |
| Stories              | 0/1/2 | {...}                    | "..."                |
| Curse of Knowledge   | 0/1/2 | {...}                    | "..."                |

## Kidney-Heist Comparison
{One sentence: which dimensions match the gold-standard kidney-heist 2/2 and which miss.}

## Top 3 Rewrite Targets
1. **{Dimension}** — "{quoted passage}" — Fix: {specific}. Effort: S/M/L.
2. ...
3. ...

## Handoff Recommendations
- {Dimension that scored 0-1} -> invoke `{specialist-skill}` because {reason}.
- ...

## Final Verdict
**{Sticky | At risk | Not sticky}** — {one-sentence rationale matching the scores above.}
```

---

## Key Principles

- **It is a checklist, not an equation.** The Heaths are emphatic: summing scores misses the point. A 2/2 on five dimensions does not redeem a 0 on Simple, because a draft without a clear core has nothing for the other principles to amplify. Report per-dimension scores only; refuse to produce a "total".

- **Every score carries a quoted passage.** The audit's value is evidence. A score without a quote is just an opinion — and opinions are exactly what a baseline agent produces. Quoting the specific sentence that earned the score makes the audit auditable by the user, which is the skill's credibility test (see Chapter 4: "let the details vouch for the claim").

- **The kidney heist is the calibration point.** Every audit compares the draft to the kidney-heist urban legend as the 2/2-on-everything reference. This is not theatrical — it is the book's own gold standard. When a dimension scores 0 or 1, the audit must be able to say "here is how the kidney heist does this and here is what the draft is missing."

- **Dimension weakness dictates the handoff.** The audit does not fix drafts — it diagnoses them and routes the user to the right specialist skill. A 0 on Concrete means `concrete-language-rewriter`. A 0 on Simple means `core-message-extractor`. A 0 on Curse of Knowledge means `curse-of-knowledge-detector`. Never recommend "go make it better" — that is baseline advice and destroys the skill's delta.

- **Curse of Knowledge is scored separately.** A draft can have a crystal-clear core and still be Curse-corrupted. Collapsing the Curse into Simple under-counts its impact, which is the single most common audit error. Score it seventh, always, even if every other dimension looks fine.

- **Prioritize ruthlessly; report faithfully.** The top-3 is the action surface; the full scorecard is the audit trail. Without the top-3 the user drowns in findings (the decision-paralysis anti-pattern the book explicitly warns against). Without the full scorecard the user cannot trust the top-3. Both are required.

- **Deeper diagnosis belongs to specialists.** The audit runs a quick inline check per dimension. When a dimension scores 0 or 1 AND the user wants to act, invoke the specialist skill rather than attempting a deeper audit inline — that is what the depends-on graph exists for. The audit's job is routing, not forensic detail.

---

## Examples

**Scenario: "Maximize shareholder value" CEO memo (the book's canonical weak baseline)**

Trigger: User pastes a 300-word all-hands memo titled "Our North Star for FY26" containing phrases like "maximize shareholder value", "synergies across business units", and "best-in-class operational excellence." Audience: "all 400 employees, mixed roles, most have never attended strategy meetings." Goal: "get everyone rowing in the same direction."

Process: (1) Audit frame captures audience + goal. (2) Simple = 0/2: no identifiable core; "shareholder value" is a goal the whole company already knew. Evidence quoted. (3) Unexpected = 0/2: every sentence is something the reader would pre-agree with (common-sense sedation). (4) Concrete = 0/2: every noun is abstract; Boeing 727 test confirms measurable constraints would gain meaning. (5) Credible = 1/2: one internal statistic is cited but without a vivid anchor. (6) Emotional = 0/2: no named person, no identity hook. (7) Stories = 0/2: zero narrative — pure assertion. (8) Curse of Knowledge = 0/2: "North Star metric" and three internal initiative names assume reader context they don't have. (9) Anti-pattern pass flags burying the lead and common-sense sedation. (10) Synthesize: final verdict **Not sticky — structural rework required**.

Output: `stickiness-scorecard.md` with Top 3 = (1) extract a concrete core using `core-message-extractor`, (2) replace "North Star metric" with the actual metric and its target number using `concrete-language-rewriter`, (3) add a "what changes for you on Monday" paragraph per role group. Kidney-heist comparison: "Kidney heist scores 2/2 on all six; this memo scores 0/2 on five of seven dimensions — the Made-to-Stick canonical worked example of a structurally un-sticky message." Handoff: invoke `core-message-extractor` first because every other fix is downstream of it.

**Scenario: Nonprofit email blast ahead of giving day**

Trigger: User pastes a 400-word email opening "Our 2026 impact report shows 14 programs reached 47,000 beneficiaries across sub-Saharan maternal health." Audience: "first-time $25-$100 donors." Goal: "convert to a first gift."

Process: (1) Frame captured. (2) Simple = 1/2: there is a core ("your gift saves mothers") but it's buried in statistics. Evidence quoted. (3) Unexpected = 0/2: opens with a report finding, which is exactly what the reader expected. (4) Concrete = 1/2: the number 47,000 is concrete but not sensory; no named person. (5) Credible = 2/2: the program data itself is specific and testable. (6) Emotional = 0/2: pure statistics, Mother Teresa effect inverted — no named beneficiary. (7) Stories = 0/2: no narrative, only claims. (8) Curse of Knowledge = 1/2: "catchment area" and "M&E framework" leak through once each. (9) Anti-pattern pass flags burying the lead (the actual ask is in paragraph 4). (10) Final verdict **At risk — fix top 2 before shipping**.

Output: Top 3 = (1) open with a named beneficiary (one mother, one specific birth) via `emotional-appeal-selector`, (2) restructure to a Connection-plot story via `story-plot-selector`, (3) move the ask to the top via anti-pattern fix. Kidney-heist comparison: "credibility is kidney-heist-level; emotional and story axes are inverted — the draft leads with numbers where kidney heist would lead with one person in one bathtub." Handoff: `emotional-appeal-selector` first because it unlocks both the Emotional and the Stories axes.

**Scenario: Developer-tool landing page hero — comparing two versions**

Trigger: User pastes two versions of a landing page hero. V1: "Unified observability platform for cloud-native workloads." V2: "Know which of your 400 microservices broke in the last deploy before your customers do." Audience: "backend engineers at mid-size SaaS companies." Goal: "sign up for a 14-day trial."

Process: (1) Run the full audit on both versions. (2) V1 scorecard: Simple 1/2 (core exists but generic), Unexpected 0/2, Concrete 0/2, Credible 0/2 ("platform" is an adjective-of-assertion), Emotional 0/2, Stories 0/2, Curse 0/2 ("unified observability" is pure insider jargon). V2 scorecard: Simple 2/2 (core is "catch bad deploys before customers do"), Unexpected 1/2, Concrete 2/2 ("400 microservices", "last deploy"), Credible 1/2 (testable by the reader's own memory of past incidents), Emotional 1/2 (wires into the fear of a customer-reported incident), Stories 1/2 (implicit micro-narrative), Curse 2/2. (3) Kidney-heist comparison favors V2 across six of seven dimensions. (4) Final verdict: ship V2; V1 is "Not sticky — structural rework required".

Output: A scorecard for each version plus a one-line recommendation: "Ship V2. V1 loses to V2 on six of seven dimensions including the structural Simple and Concrete axes — this is not a stylistic preference, it is the SUCCESs rubric reporting a clean dominance." No specialist handoff needed — V2 is ready.

---

## References

- For the full 0/1/2 rubric per dimension with book-sourced pass/fail criteria, see [success-dimension-rubric.md](references/success-dimension-rubric.md)
- For the exact markdown template the scorecard must fill in, see [scorecard-template.md](references/scorecard-template.md)

---

## License

This skill is licensed under [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/).
Source: [BookForge](https://github.com/bookforge-ai/bookforge-skills) — Made to Stick: Why Some Ideas Survive and Others Die by Chip Heath and Dan Heath.

## Related BookForge Skills

This is a Level 1 hub skill — it delegates specialized diagnoses to the Level 0 foundation skills. Install from ClawhHub:

- `clawhub install bookforge-curse-of-knowledge-detector` — deeper diagnosis when the Curse axis scores low
- `clawhub install bookforge-core-message-extractor` — invoked when Simple scores low
- `clawhub install bookforge-curiosity-gap-architect` — invoked when Unexpected scores low
- `clawhub install bookforge-concrete-language-rewriter` — invoked when Concrete scores low
- `clawhub install bookforge-credibility-evidence-selector` — invoked when Credible scores low
- `clawhub install bookforge-emotional-appeal-selector` — invoked when Emotional scores low
- `clawhub install bookforge-story-plot-selector` — invoked when Stories scores low
- `clawhub install bookforge-sticky-message-antipattern-detector` — invoked when Step 9 flags burying-the-lead, decision-paralysis, or common-sense sedation

Or install the full book set from GitHub: [bookforge-skills](https://github.com/bookforge-ai/bookforge-skills)

FILE:references/scorecard-template.md
# Stickiness Scorecard Template

Copy this template when producing the audit output file. Every section is required. Every score needs a quoted passage as evidence. Do NOT add a "total score" row — the rubric is a checklist, not an equation.

---

```markdown
# Stickiness Scorecard — {draft name or first-line title}

## Audit Frame

- **Draft:** {title or opening line}
- **Audience:** {role + context + what they care about — one sentence}
- **Goal:** {what the reader must remember, feel, or do}
- **Channel:** {email / tweet / landing page / slide / memo / speech / other}
- **Compared against:** {prior version filename if applicable, else "first draft"}
- **Assumed default(s):** {any assumption filled in for missing context, e.g., "[assumed goal: sign up for trial]"}

---

## Scorecard

| Dimension            | Score | Verdict (one line)                              | Evidence (quoted from draft)             |
|----------------------|-------|-------------------------------------------------|------------------------------------------|
| Simple               | 0/1/2 | {e.g., "no identifiable core"}                  | "{quoted passage}"                       |
| Unexpected           | 0/1/2 | {...}                                           | "{...}"                                  |
| Concrete             | 0/1/2 | {...}                                           | "{...}"                                  |
| Credible             | 0/1/2 | {...}                                           | "{...}"                                  |
| Emotional            | 0/1/2 | {...}                                           | "{...}"                                  |
| Stories              | 0/1/2 | {...}                                           | "{...}"                                  |
| Curse of Knowledge   | 0/1/2 | {...}                                           | "{...}"                                  |

**Rubric reminder:** 0 = fails the dimension, 1 = partial, 2 = kidney-heist level. Do not sum the scores.

---

## Kidney-Heist Comparison

{One sentence: which dimensions the draft hits at 2/2 kidney-heist level and which it misses. Example: "Credibility is kidney-heist-level; Emotional and Stories axes are inverted — the draft leads with statistics where the kidney heist would lead with one person in one bathtub."}

---

## Anti-Pattern Findings (Step 9 cross-cutting pass)

- [ ] **Burying the lead** — {present / not present; if present, where}
- [ ] **Decision paralysis** — {present / not present; if present, which competing asks}
- [ ] **Common-sense sedation** — {present / not present; if present, which sentences}
- [ ] **Analysis by jargon** — {present / not present; if present, which terms}

(If any fire, these explain why a draft can score 1s across dimensions and still fail to land.)

---

## Top 3 Rewrite Targets

Ranked by (severity × how much of the draft they poison). Each target names the dimension, quotes the passage, prescribes a specific fix, and estimates effort.

1. **{Dimension}** — "{quoted passage}"
   - **Why it hurts:** {one sentence}
   - **Fix:** {specific rewrite direction, not "make it better"}
   - **Effort:** S / M / L

2. **{Dimension}** — "{quoted passage}"
   - **Why it hurts:** {...}
   - **Fix:** {...}
   - **Effort:** S / M / L

3. **{Dimension}** — "{quoted passage}"
   - **Why it hurts:** {...}
   - **Fix:** {...}
   - **Effort:** S / M / L

---

## Handoff Recommendations

For each dimension that scored 0 or 1, name the specialist skill to invoke next and say why that skill (not another) is the right move.

- **Simple 0/1** -> invoke `core-message-extractor` because {reason}.
- **Unexpected 0/1** -> invoke `curiosity-gap-architect` because {reason}.
- **Concrete 0/1** -> invoke `concrete-language-rewriter` because {reason}.
- **Credible 0/1** -> invoke `credibility-evidence-selector` because {reason}.
- **Emotional 0/1** -> invoke `emotional-appeal-selector` because {reason}.
- **Stories 0/1** -> invoke `story-plot-selector` because {reason}.
- **Curse of Knowledge 0/1** -> invoke `curse-of-knowledge-detector` because {reason}.
- **Anti-pattern hits** -> invoke `sticky-message-antipattern-detector` for deeper diagnosis of {specific anti-pattern}.

**First move:** {name the ONE skill to invoke first, and why it is upstream of the others.}

---

## Final Verdict

**{Sticky (ready to ship) | At risk (fix top 2 before shipping) | Not sticky (structural rework required)}**

{One-sentence rationale that matches the dimension scores above. Example: "Not sticky — Simple and Concrete both score 0/2 and those are structural; fixing downstream dimensions without a core would paper over the real gap."}

**Threshold rules used:**
- **Sticky** = no dimension scored 0; at most one scored 1; no anti-pattern hits.
- **At risk** = at most one dimension scored 0 AND no anti-pattern hits on burying-the-lead or common-sense sedation.
- **Not sticky** = two or more dimensions scored 0, OR Simple scored 0, OR a structural anti-pattern fired.
```

---

## Template usage notes

- The quoted-evidence column is mandatory. Scores without quotes are rejected by the Step 11 self-check.
- The kidney-heist comparison line is mandatory — it is the book's own calibration anchor and the audit's main anti-generic-advice defense.
- The "First move" line under Handoff Recommendations is the single most important handoff output — it answers the user's real question ("what do I do first?") and prevents the decision-paralysis anti-pattern inside the audit itself.
- Use the exact heading names in this template. Downstream skills (message-clinic-runner) parse these sections by header.

FILE:references/success-dimension-rubric.md
# SUCCESs Dimension Rubric — 0/1/2 per dimension

This is the scoring rubric for the `stickiness-audit` skill. Every dimension uses a **0/1/2** scale. The book is explicit: *"It's a checklist, not an equation."* Do NOT sum the scores. Report per-dimension verdicts only.

Each dimension below gives: the core question, the 0/1/2 criteria, the canonical kidney-heist benchmark (the book's gold-standard 2/2 example), and the canonical weak example (usually the Introduction's "maximize shareholder value" CEO memo).

---

## S — Simple

**Core question:** Does the draft have one identifiable core, expressed with proverb-like compactness?

**Two sub-tests:**
1. **Core test** — Can you state what the draft is *really* about in one sentence that the author would agree with?
2. **Compact test** — Is that sentence short, memorable, and pre-loaded with meaning (like a proverb or Commander's Intent)?

**0** — No identifiable core. The draft makes multiple competing claims, or the core is buried under context, or the "core" is a goal the audience already holds ("we will maximize value"). Fails both sub-tests.

**1** — A core exists but is either buried (reader must read past paragraph 2 to find it) or abstract (reader can recite it but cannot act on it).

**2** — The core is clear, compact, and actionable in a single sentence the reader can repeat.

**Kidney heist = 2.** One core image: "drugged traveler wakes up in bathtub of ice missing a kidney, call 911." The core is the whole story.

**"Maximize shareholder value" = 0.** No core the reader can act on differently tomorrow.

**Handoff when 0 or 1:** `core-message-extractor`.

---

## U — Unexpected

**Core question:** Does the draft break a reader schema and open a curiosity gap?

**Two sub-tests:**
1. **Pattern break** — Does the opening surprise the reader relative to what their mental model predicted?
2. **Curiosity gap** — Does the draft open a question the reader now *wants* answered?

**0** — Every sentence is something the reader would pre-agree with. Common-sense sedation ("customer service is important", "we value our partners").

**1** — Some pattern break exists but it is buried, or the curiosity gap is opened and then not closed (teasing without payoff).

**2** — Opens with a schema violation and either closes the gap satisfyingly or sustains curiosity for a defined payoff.

**Kidney heist = 2.** "Woke up in a bathtub of ice" violates every traveler-safety schema the reader holds.

**"Maximize shareholder value" = 0.** Zero schema violation.

**Handoff when 0 or 1:** `curiosity-gap-architect`.

---

## C — Concrete

**Core question:** Does the draft use sensory, observable language instead of abstractions?

**Two sub-tests:**
1. **Noun audit** — What fraction of the draft's nouns are abstract (strategy, synergy, value, solution, impact) vs sensory/observable (bathtub, 131 passengers, Jared's pants)?
2. **Boeing 727 test** — If you replaced the abstract phrases with measurable constraints, would meaning be lost or gained? If gained, the draft is under-concrete.

**0** — Abstract-only. No sensory nouns, no measurable constraints, no observable behaviors. The Boeing 727 test gains meaning when replacements are applied.

**1** — Some concrete details exist but are surrounded by abstraction. The draft reads concrete in patches but abstract overall.

**2** — Every claim is anchored to a sensory or observable specific. The reader can visualize what the draft is talking about.

**Kidney heist = 2.** Ice, bathtub, phone, note, stitches — every noun is sensory.

**"Maximize shareholder value" = 0.** Not a single sensory noun. Boeing 727 test: "grow revenue 20% in FY26 by winning back 10 lapsed accounts" gains meaning vs the original.

**Handoff when 0 or 1:** `concrete-language-rewriter`.

---

## C — Credible

**Core question:** Does the message vouch for itself without relying on unverifiable adjectives?

**Credibility moves the book catalogues (any ONE of these done well is enough for 2/2):**
- **External authority** — relevant expert or institution.
- **Anti-authority** — a credible first-person skeptic or ex-insider (the ex-smoker argument).
- **Internal vivid details** — specificity that signals first-hand knowledge (the Hyundai cancer-cluster description).
- **Statistics with a human anchor** — a number wired to something relatable (Nukes Stanford distance).
- **Sinatra test** — one overwhelming example that alone makes the case ("if you can make it there…"). Fort Knox security contract, Safexpress + Harry Potter.
- **Testable credentials** — a claim the reader can personally verify ("Where's the beef?" — you can weigh the patty yourself).

**0** — Relies on unverifiable adjectives: "world-class", "leading", "proven", "best-in-class". Reader has no way to check any claim.

**1** — Uses one credibility move but weakly (generic stat without human anchor; authority quote without domain match).

**2** — Uses at least one credibility move done well. The reader's response is "yes, that would convince me even if no one said it was true."

**Kidney heist = 2.** Friend-of-a-friend detail + specific operative timing + the "call 911" procedural detail all read like first-hand knowledge.

**"Maximize shareholder value" = 0-1.** Usually leans on adjectives or on a single unanchored statistic.

**Handoff when 0 or 1:** `credibility-evidence-selector`.

---

## E — Emotional

**Core question:** Does the draft make the reader *care*, usually by routing through one specific person or an identity the reader holds?

**Three sub-tests:**
1. **Who specifically?** Is there one identifiable person, not a statistical many? (Rokia, not "Africa's hungry".)
2. **Which identity?** Does the draft connect to an identity the reader already holds? ("Don't mess with Texas" wires into Texas pride.)
3. **Which associations?** Does the draft borrow emotion from associations the reader actually values?

**0** — No named person, no identity hook, emotion manufactured through adjective stacking ("devastating", "heart-wrenching", "unprecedented").

**1** — One of the three sub-tests passes; the other two don't. Emotion is present but thin.

**2** — At least two sub-tests pass. The reader recognizes themselves or someone they care about in the draft.

**Kidney heist = 2.** The traveler is "you" — identity hook is direct; the bathtub is visceral fear wired into body-safety identity.

**"Maximize shareholder value" = 0.** Zero identity hook. Shareholder value is an abstraction most employees cannot identify with.

**Handoff when 0 or 1:** `emotional-appeal-selector`.

---

## S — Stories

**Core question:** Does the draft tell a story, or does it only assert claims?

**A story has:** subject acting (actor + verb), a complication or challenge, and a resolution or lesson.

**Plot types to detect:**
- **Challenge plot** — underdog overcomes obstacle (Jared/Subway).
- **Connection plot** — bridge across a gap between people (Good Samaritan).
- **Creativity plot** — insight solves a puzzle (Apollo 13 CO2 filter).

**0** — No narrative. Bullets, claims, or assertions only. Reader is told what to think, not shown what happened.

**1** — A micro-narrative is present (one sentence of "user did X then Y") but not developed; the reader cannot mentally rehearse the action.

**2** — A full story with identifiable plot type. The reader could summarize what happened to whom and what they should take away.

**Kidney heist = 2.** Complete Challenge-plus-Connection plot: traveler meets stranger, wakes up victimized, must call 911. Full arc.

**"Maximize shareholder value" = 0.** Zero narrative.

**Handoff when 0 or 1:** `story-plot-selector`.

---

## Villain — Curse of Knowledge

**Core question:** Could a non-expert in the audience parse this cold?

**The tapper/listener heuristic:** The author "knows what they mean" — the question is whether the reader can hear it. Re-read the draft from the audience's POV and list every term, acronym, framework reference, named internal tool, or buried assumption that would force a non-expert to pause.

**0** — Visibly corrupted by expertise. Heavy jargon, internal tool names, buried assumptions on every paragraph. A non-expert stops reading in the first 20 seconds.

**1** — Some insider residue. A handful of terms assume reader context; the bulk of the draft is parseable but the residue is enough to lose part of the audience.

**2** — A non-expert could parse it cold. Any domain term is defined on first use or swapped for a common-language equivalent.

**Kidney heist = 2.** Zero jargon. Every noun is a shared-schema household object.

**"Maximize shareholder value" = 0.** Every key phrase assumes MBA-level schema.

**Handoff when 0 or 1:** `curse-of-knowledge-detector` (for deeper per-passage diagnosis) and/or `sticky-message-antipattern-detector` (for related anti-patterns: burying-the-lead, analysis-by-jargon, common-sense-sedation).

---

## Scoring discipline reminders

- **Quote evidence for every score.** A score without a quoted passage is an opinion, not an audit.
- **Do not sum the scores.** The rubric is a checklist, not an equation.
- **Score Curse of Knowledge separately from Simple.** A clear core can still be Curse-corrupted.
- **When uncertain between two scores, pick the lower.** The audit's job is to surface gaps, not to flatter the draft.
- **A single 2/2 dimension does not redeem a 0/2 elsewhere.** Report the full picture.