skills/writing-strategy/references/status_problem_solution.md

# Status → Problem → Solution / 현황 → 문제점 → 해결책

- English name: Status → Problem → Solution
- Korean name: 현황 → 문제점 → 해결책
- Selection category: general
- Use when: Use for status reports that must move from current state to issue and response.
- Avoid when: Avoid as the default for broader essays or stories. This is a generic structure; select it only after checking more distinctive options.

## Writing Pattern

**Use a fixed three-step flow**

- Status
  - Describe the current situation objectively with statistics, observed facts, market trends, or processes.
  - Include positives and latent risks to set up the problem naturally.
- Problem
  - Surface the core problem derived from the status.
  - Focus on root causes over symptoms; compress to one or a few issues and explain impact/severity.
- Solution
  - Present feasible alternatives to resolve the problem.
  - Explain as an execution strategy, not just an idea; include expected impact and application hints.

## Example Writing Outline

1. **Status — Acquisition Flow**: Traffic comes from many channels, but conversion has stalled. (Status)
2. **Problem — Low Conversion**: 68% of visitors bounce within three seconds; landing-page messaging lacks clarity. (Problem)
3. **Solution — Messaging + A/B Testing**: Revamp with a stronger hook and redesign UX around the user flow to reduce churn. (Solution)

## Writing Notes

- Back Status with objective materials and guide toward the Problem with bridging language (e.g., “Yet these figures fall short of expectations…”).
- For Problem, focus on a single core issue; if complex, structure by sub-issues while keeping one main thread.
- For Solution, include feasibility and a plan—hints to who/when/how improve effectiveness.
- Keep a natural logic: “Because the current state is X → Y problem occurs → Therefore we will respond with Z.”