skills/writing-strategy/references/problem_solution.md

# Problem → Solution / 문제 → 해결 구조

- English name: Problem → Solution
- Korean name: 문제 → 해결 구조
- Selection category: general
- Use when: Use only when the user asks for a direct fix or the material is truly simple.
- Avoid when: Avoid as the default; check more specific strategies first. This is a generic structure; select it only after checking more distinctive options.

## Writing Pattern

**Build the article outline using the criteria below**

- Keep the section count flexible and scale to the topic.

**Follow this flow**

- **Problem Definition**: What problem is occurring
- **Impact**: Losses, friction, or missed opportunities caused by the problem
- **Solution**: A practical alternative we propose
- **Expected Outcome**: Changes after applying the solution
- **Summary and Proposal**: Recap and call to action

**Each major section should include**

- Section heading
- Core paragraph purpose (1–2 sentences)
- Keep the problem concrete and describe the solution in terms of feasibility and impact.
- Support expected outcomes with numbers or cases where possible.

## Example Writing Outline

1. **Problem Definition**: Customer churn is rising, mainly due to a complex sign‑up flow.
2. **Impact**: Conversion has fallen and profitability vs. marketing spend is worsening.
3. **Solution**: Adopt simple login options and improve UX to streamline onboarding.
4. **Expected Outcome**: Expect a 30% lift in conversion and higher customer satisfaction.
5. **Summary and Proposal**: Reducing churn depends on easier access and a user‑centered experience.

## Writing Notes

- Connect problem and impact causally—not as isolated lists.
- Keep solutions realistic; avoid idealized scenarios.
- Use concrete figures or cases to make outcomes persuasive.
- Maintain logical flow so the reader concludes, “We should act.”