skills/writing-strategy/references/problem_analysis_solution_outcome.md

# Problem → Analysis → Solution → Outcome / 문제 → 분석 → 해결책 → 기대 효과

- English name: Problem → Analysis → Solution → Outcome
- Korean name: 문제 → 분석 → 해결책 → 기대 효과
- Selection category: analysis
- Use when: Use for diagnostic proposals where the problem needs careful analysis before solution and outcome.
- Avoid when: Avoid as a reflexive structure for every improvement topic. This is a generic structure; select it only after checking more distinctive options.

## Writing Pattern

**Use this fixed four-step structure**

- Problem
  - Diagnose concrete issues, inefficiencies, losses, and pain points in the current state.
  - Surface core issues that require action—not mere complaints.
- Analysis
  - Analyze root causes from multiple angles.
  - Use objective materials—statistics, feedback, market research, internal audits—to explain causes and structure.
- Solution
  - Propose feasible solutions based on the analysis.
  - Go beyond stopgaps; address root causes and outline execution steps.
- Outcome
  - Present the expected changes and results after applying the solution.
  - Include quantitative effects (ROI, time saved) and qualitative ones (satisfaction, efficiency).

## Example Writing Outline

1. **Low Retention**: Our retention rate is 18% below the industry average; churn concentrates within two weeks of signup. (Problem)
2. **Churn Analysis**: Early usage feels flat and paywall prompts come too soon, undermining trust. (Analysis)
3. **Solution — Trial-Centric Onboarding Redesign**: Strengthen the first 7-day experience and delay pay prompts until after day 10. (Solution)
4. **Expected Outcome**: Simulations show +12% conversion and −24% churn; next‑quarter rollout projects 2.3× ROI. (Outcome)

## Writing Notes

- Define the problem as a core business/strategic issue, not a list of symptoms (e.g., cite NPS, repeat rate).
- In Analysis, answer “Why did this happen?” and use tables/graphs/insights appropriately.
- Ensure the Solution is actionable and flows naturally from the analysis.
- Increase trust by quantifying Outcomes—prefer “change vs. prior state.”