| name | nasa-persuasion |
| description | Use when writing persuasive content (sales pitches, blog posts, speeches, marketing copy) or structuring an argument. Applies the NASA method (Need → Acceptance → Solution → Acceptance) to make sure context is loaded into the listener's attention before the solution is proposed. |
NASA — Need, Acceptance, Solution, Acceptance
People sell to themselves. Equip the listener with the information they need to reach the conclusion on their own. Never assume context is "in their RAM" just because it's in their long-term memory.
The loop
- Need — Establish a pain point. Example: "I get home from work too late every day."
- Acceptance — Don't move on until you get a verbal or non-verbal cue that the listener has accepted the need.
- Solution — Propose the abstract solution. Example: "I want a tool that speeds up my end-of-day routine."
- Acceptance — Don't move on until the abstract solution is accepted.
Only after the loop can you sell the concrete thing. In the example above, the listener's need was "get home earlier." The abstract solution was "a tool that saves time." What you actually sold them in the end was bookkeeping software.
Where to apply
- Sales conversations
- Pitch decks
- Blog posts and media — scaffold context before conclusions
- Internal proposals
Structure the content so the reader always has the necessary scaffolding in RAM. Don't assume.
Related
story-why-how-what maps closely: Need ≈ Why, Solution ≈ How. Use NASA for dialogue, WHW for one-directional narrative.
