# Need → Solution → Satisfaction / 니즈 → 솔루션 → 만족 구조

- English name: Need → Solution → Satisfaction
- Korean name: 니즈 → 솔루션 → 만족 구조
- Selection category: persuasion
- Use when: Use when the reader's need can be connected to a solution and a satisfying result.
- Avoid when: Avoid as a generic problem-solution substitute unless the need is vivid. This is a generic structure; select it only after checking more distinctive options.

## Writing Pattern

**Follow this fixed three-step structure**

- **Need**: The reader’s or target’s problem, desire, or inconvenience
- **Solution**: The product, service, or idea that addresses the need
- **Satisfaction**: The changes, results, and emotional satisfaction after adoption
- You may add detail as needed, but keep the overall flow.
- If the article must be short, combine Need+Solution or Solution+Satisfaction.

## Example Writing Outline

1. **The Core Need**: Complex processes and high costs hinder automation adoption. (Need)
2. **Our Solution**: A cloud-based automation system enables quick, low-cost rollout. (Solution)
3. **Expected Outcome and Satisfaction**: Work time fell 40% post-implementation and satisfaction rose to 92%. (Satisfaction)
4. **Conclusion and Proposal**: Adopting now will put us three months ahead of competitors in digital transformation.

## Writing Notes

- For Need, support with concrete situations, statistics, or user behavior—not just “we need it.”
- For Solution, emphasize value and strengths, not just the method.
- For Satisfaction, include quantitative (data), qualitative (reviews), and emotional (relief) effects.
- Design the narrative so the reader feels, “This solution really solves my problem.”