# Challenge Design

## Table of Contents

1. [Why Challenge Comes First](#why-challenge-comes-first)
2. [Finding the Real Challenge](#finding-the-real-challenge)
3. [Creating the Cognitive Gap](#creating-the-cognitive-gap)
4. [Common Pitfalls](#common-pitfalls)

---

## Why Challenge Comes First

A presentation is not training. Training teaches procedures. A presentation transmits **judgment**.

The audience will not absorb an answer to a question they haven't felt. Before providing the model or solution, the audience must first:

1. **Recognize** the challenge in their own life ("I face this too")
2. **Feel** the inadequacy of obvious solutions ("My usual approach doesn't work here")
3. **Want** a new lens ("I need a different way to think about this")

Only then does the model land with force. Without this sequence, even the best model sounds like unsolicited advice.

**Rule of thumb:** In a 5-minute talk, spend at least 40% on the challenge. In a course module, spend the entire opening on it. In a knowledge card, make the challenge the headline.

---

## Finding the Real Challenge

The user's raw material usually presents a **surface challenge** -- the specific problem they faced. The job is to find the **universal challenge** underneath.

### Technique: The "You Too" Test

Ask: "Would someone in a completely different role/industry nod and say 'I face this too'?"

| Surface challenge (fails the test) | Universal challenge (passes) |
|------------------------------------|-------------------------------|
| "I had too many screenshots to process" | "High-value outcomes are buried under mountains of low-signal noise" |
| "Our quarterly reports took too long" | "Recurring crises steal time from the work that actually compounds" |
| "New hires kept making proposal errors" | "When people keep failing, is it a people problem or a structure problem?" |
| "I couldn't get the design team to take my input seriously" | "When you lack the artifact, you lack the authority" |

### Technique: Laddering Up

When the surface challenge is too specific, repeatedly ask "Why does this matter?" until reaching universal relevance:

```
"I had 200 screenshots of contacts" 
  -> Why does it matter? "Because I couldn't track business leads"
  -> Why does that matter? "Because I was losing potential partnerships"
  -> Why does that matter? "Because high-value outcomes require filtering 
     massive noise -- and I had no system for it"
```

The last level is the universal challenge.

---

## Creating the Cognitive Gap

A cognitive gap is the moment where the audience's existing mental model is revealed as insufficient. This creates genuine motivation to adopt the new model.

### The 3-Beat Structure

**Beat 1: Establish the familiar approach.**
Present how most people (including the audience) currently handle this challenge. Make it feel normal and reasonable.

> "The obvious response is to try harder -- more training, closer supervision, tighter deadlines."

**Beat 2: Show why it fails.**
Reveal a specific way the familiar approach breaks down. Use concrete evidence, not abstract criticism.

> "But after three rounds of additional training, error rates hadn't budged. If more training was the answer, it would have worked by now."

**Beat 3: Create the opening.**
Frame the gap -- the audience now knows their current approach is insufficient but doesn't yet have an alternative.

> "The problem wasn't that people needed to be better. The problem was invisible."

The model (Step 2 of the conversion engine) fills this gap.

### Phrasing Patterns for Cognitive Gaps

Use these structural phrases to signal that the old answer is insufficient:

- "The instinct is to [obvious approach]. But [specific reason it fails]."
- "If [obvious solution] worked, [evidence it would have succeeded by now]."
- "The question isn't [surface question]. The real question is [deeper question]."
- "Most people think this is a [X] problem. It's actually a [Y] problem."
- "We don't need a better version of [old approach]. We need a different [frame]."

---

## Common Pitfalls

### Pitfall 1: Skipping the challenge and jumping to the solution
**Symptom:** The output starts with "Here's what I did" or "Here's the framework."
**Fix:** Always open with the challenge. The audience earns the solution by experiencing the tension.

### Pitfall 2: Stating the challenge abstractly
**Symptom:** "Communication is hard" or "Efficiency is important."
**Fix:** Ground the challenge in a vivid, specific scenario the audience recognizes. Specificity triggers empathy; abstraction triggers tuning out.

### Pitfall 3: Making the challenge too domain-specific
**Symptom:** Only people in the exact same role would care.
**Fix:** Apply the "You Too" test and ladder up until the challenge crosses domain boundaries.

### Pitfall 4: Presenting a strawman challenge
**Symptom:** The "old approach" is obviously wrong, so defeating it feels trivial.
**Fix:** The old approach must feel **reasonable**. Making the familiar approach look smart before showing its blind spot is what creates genuine surprise.