← Files DeveloopARCHIVED FILE
skills/writing-strategy/references/pain_claim_gain.md
1.72 KB · Oct 2, 2026 · 00:29 UTC
# Pain → Claim → Gain / 고통 → 제안 → 기대 효과 - English name: Pain → Claim → Gain - Korean name: 고통 → 제안 → 기대 효과 - Selection category: persuasion - Use when: Use when a sharp pain point should lead to a claim and a tangible gain. - Avoid when: Avoid when the tone should be gentle or exploratory. ## Writing Pattern **Use a fixed flow** - **Pain**: Present the reader’s real inconvenience, problem, or pain directly - **Claim**: State your proposed solution or message clearly and forcefully - **Gain**: Show the concrete and emotional benefits once the proposal is accepted - Emphasize empathy in Pain, clarity in Claim, and both emotional and practical payoff in Gain. **Each major section should include** - Section heading - Core paragraph purpose (1–2 sentences) - Build toward a rising emotional curve and end with conviction or a clear call to action. ## Example Writing Outline 1. **The Daily Grind**: Average wait time for customer support is 8 minutes; 35% of negative reviews cite this. (Pain) 2. **The Fix Is Clear**: An AI chatbot can cut average response time to under 30 seconds. (Claim) 3. **No More Waiting**: Faster responses double satisfaction and raise review scores by ~1.4 points. (Gain) 4. **Now Is the Moment**: This is the right time to reduce pain and maximize value. (Gain + Call-to-Action) ## Writing Notes - In Pain, capture real feelings with concrete cases or data. - In Claim, make the core proposal unmistakable—what exactly should we do? - In Gain, include both quantitative (numbers) and qualitative (emotion) effects to build trust and anticipation. - This structure is optimized for motivating change by appealing to relief from pain—not just problem-solving.
SHA-256: a4a6a17532f2a6d9aa5c6214840a23bc784c9e94576b85acf710183d4541ce17