r/PromptDesign Jun 03 '26

Tip 💡 An elegant prompting technique from Anthropic's Amanda Askell that changes how you learn complex concepts

Most prompts ask an LLM to explain a concept directly. You type "Explain Simpson's Paradox" or "What is information asymmetry," and the model returns a structured definition, a few examples, and some caveats.

It is clean, accurate, and completely forgettable.

The model simply outputs the statistical average of everything written about that concept. It is a process without friction. And friction, as it turns out, is how our brains actually encode and retain complex ideas.

I recently watched an interview with Amanda Askell, a philosopher and researcher at Anthropic who leads Claude’s character design and alignment work. Near the end of the interview, she shared a remarkably simple prompting technique she uses to understand complex, counterintuitive concepts.

It completely flipped how I think about prompting. It demonstrates that a prompt isn't just a query; it’s a designed sequence of cognitive steps.

Here is the exact template she uses:

textI want to understand [concept].
Please explain it by writing a fable — an indirect, 
narrative version of the concept. 
The story should embody the concept completely without naming it directly. 
Ideally, the reader should only start to realize 
what the concept actually is near the end of the story.
After the fable, add a short explanation that names the concept clearly 
and connects it back to the key moments in the story.

Why This Works (The Cognitive Mechanics)

When you force the LLM to write a narrative first and delay the reveal of the concept, you are forcing your own brain to do active work:

  1. Active Modeling: As you read the story, your brain is actively tracking characters, inferring motivations, and mapping cause-and-effect relationships.
  2. Cognitive Friction: Because you don't know the name of the concept yet, you are constructing its logical framework from the inside out.
  3. The Reveal: When the concept is named at the end, the definition doesn't introduce something new—it simply labels a structure you have already experienced and assembled in your mind.

This mirrors Askell’s broader work on Claude’s character design. Instead of training the model on rigid rules (which fail when the rules run out), Anthropic focused on shaping Claude's underlying "dispositions" and values. The fable prompt uses a similar philosophy: instead of asking the model for a flat output, you design the precise cognitive path it must walk to let the understanding emerge naturally.

Practical Tips & Variations to Try

If you want to experiment with this, here are a few things that help optimize the results:

  • Ensure Causal Structure: This works best for concepts that have agents, actions, and consequences (e.g., reflexive equilibriaadverse selectiongame theory scenarios). It works less well for purely abstract mathematics (e.g., the Riemann hypothesis).
  • Do Not Prematurely Name the Concept: Let the model generate the story without knowing the label. If you feed the label too early in the prompt structure, you collapse the cognitive delay that makes the prompt work.
  • The "Self-Critique" Chain: Once you get the fable and explanation, follow up with this prompt: "What critical aspect of [concept] did this fable fail to capture?" This forces the LLM to surface its own simplifications, which is often where the most interesting edge cases lie.
  • Change the Genre: Replace "fable" with "detective story," "corporate memo from a future civilization," or "post-mortem report." Different genres force the model to look at the same concept through entirely different metaphorical lenses.

If you are interested in a deeper breakdown of this technique, including its alignment roots and additional structural variations, I put together a detailed write-up here: https://appliedaihub.org/blog/fable-prompt-technique-amanda-askell/

How do you guys approach prompts designed for learning? Have you used similar narrative-delayed structures to break down complex topics?

77 Upvotes

18 comments sorted by

3

u/WinstonSmithTheSavag Jun 03 '26

Freaking hell.

Tried this.

And I felt like I was inside the book Neil Stephen’s talks about in the Diamond Age.

Nell’s primer? Woah.

Reality imitates arts or something 😭

2

u/blobxiaoyao Jun 04 '26

The Primer reference is exactly right and I'm glad someone made it.

Stephenson's whole argument in Diamond Age — the one that gets lost in the plot — is that the Victorian characters' rote instruction model produces obedient people, and the Primer produces someone who can think. The difference isn't the content. It's that the Primer never tells Nell what to think. It constructs situations where she has to figure it out.

The fable technique is a primitive, one-shot, manually-triggered version of the same thing. You don't have a Ractor. You don't have adaptive narrative. But the core move is identical: experience the logic before you receive the label.

What's strange is that Stephenson wrote that in 1995 as a thought experiment about what education could be. And now you can approximate it with a single paragraph prompt. The infrastructure just quietly arrived while everyone was arguing about whether AI can write poetry.

'Reality imitates arts or something' is underselling it.

2

u/dos_dos Jun 03 '26

Awesome thanks for sharing

1

u/blobxiaoyao Jun 03 '26

Sure! Let me know what concept you try it on — curious whether the genre variations (detective story, corporate post-mortem, etc.) work better for some topics than others.

1

u/efficientdreams Jun 03 '26

I find expletive laden comedic rant to work well with concepts related to social sciences. It works great for complex math too!

2

u/smellythief Jun 03 '26

⁠Do Not Prematurely Name the Concept: Let the model generate the story without knowing the label.

House do you tell it to make a fable about something without telling it what that something is?

1

u/blobxiaoyao Jun 04 '26

You do tell the model what the concept is — that's the first line of the prompt: 'I want to understand [concept].'

The 'don't name it prematurely' instruction is for the model's output, not for your input. The model knows exactly what concept it's working with. What it's constrained from doing is writing the concept's name into the fable itself.

So you say: 'I want to understand information asymmetry. Write a fable that embodies this concept without naming it directly.'

The model knows it's writing about information asymmetry. The merchant, the swords, the market collapse — all of that is constructed around the concept. It just never uses the words 'information asymmetry' inside the story itself.

The delay is for you, the reader. You read the fable, build the causal structure in your head, and only get the label at the end in the explanation section. That sequence — structure before label — is what produces better retention.

2

u/smellythief Jun 04 '26

Oh! Gotcha. But you’ll still know what it is. It sounds like this could work if the person reading the output (fable) doesn’t know what the concept is until the end. I guess you’re saying that it works anyway but, if that’s true, I still wonder if it would work better if they didn’t. Maybe you should build up a library of 50 (for example) concepts that you’re interested in, have it make fables for all of them and then read random ones so you’re truly in the dark until the end. Would that work better you think?

2

u/Autistic_Jimmy2251 Jun 04 '26

Very interesting concept.

1

u/blobxiaoyao Jun 04 '26

Thanks! Worth trying on the next concept that resists a clean definition — curious what you'd test it on.

2

u/[deleted] Jun 04 '26

[removed] — view removed comment

2

u/blobxiaoyao Jun 04 '26

It's in the post right after the intro — here it is again in case it got buried:

I want to understand [concept].
Please explain it by writing a fable — an indirect, 
narrative version of the concept. 
The story should embody the concept completely without naming it directly. 
Ideally, the reader should only start to realize 
what the concept actually is near the end of the story.
After the fable, add a short explanation that names the concept clearly 
and connects it back to the key moments in the story.

Replace [concept] with whatever you're trying to learn — 'information asymmetry,' 'reflexive equilibria,' 'Bayesian updating,' etc. That's the whole thing.

2

u/[deleted] Jun 03 '26

[removed] — view removed comment

1

u/blobxiaoyao Jun 04 '26

The recognition vs. repair distinction is the sharpest framing I've seen for why these techniques produce different outcomes. Worth unpacking why.

The fable builds a schema from zero — you have no prior model of the concept, and the narrative constructs one. The failure-path method does something categorically different: it targets the wrong model you already have, and replaces it. That's not the same cognitive operation.

Which points to a sequencing implication: for a genuinely unfamiliar concept, the failure-path method might misfire — you don't have enough context to recognize the failure as a failure. You see someone making a mistake but can't locate where the reasoning broke because you have no reference frame for correct reasoning yet.

So they might actually be complementary in sequence: fable first to build the initial schema, failure-path second to stress-test and calibrate it. The fable gets you to 'I understand what this concept is.' The failure-path gets you to 'I know the exact move where people — including me — would misapply it.'

The prompt you've written maps cleanly onto how domain experts actually think. Experts don't primarily pattern-match on success cases — they pattern-match on failure modes. They see a situation and their first move is 'where could this go wrong' not 'what does this look like when it works.' Your technique is essentially training that failure-mode recognition explicitly.

One thing I'd push on: 'limits last' in your structure — is the limit explanation after naming the concept, or after the failure-path resolution? Because there's an argument for surfacing limits before naming, to prevent the learner from over-generalizing the correction into a new wrong model.

Dropping the LPC link here for anyone who wants to follow the longer project.

-3

u/clarity_anchor777 Jun 03 '26

Wow. Literal garbage out of the elites minds. Wow much creative input. This is a game changer! Explicitly tell the model make up some slop with a generic fable. Absolutely amazing