skills/writing-strategy/references/phenomenon_insight_proposal.md

# Phenomenon → Insight → Proposal / 현상 → 인사이트 → 대안 제시

- English name: Phenomenon → Insight → Proposal
- Korean name: 현상 → 인사이트 → 대안 제시
- Selection category: insight
- Use when: Use when a visible phenomenon should be interpreted and turned into a proposal.
- Avoid when: Avoid when the phenomenon is only a symptom of a simpler problem.

## Writing Pattern

**Use a fixed three-part structure**

- **Phenomenon**: The situation, data point, or problem occurring now
- **Insight**: Interpretation and root-cause analysis
- **Proposal**: Concrete, feasible solutions
- You may include multiple phenomena and pair each with its own insight and proposal.
- If article space is limited, merge insight and proposal or focus on essentials.

**Each major section should include**

- Section heading
- Core paragraph purpose (1–2 sentences)
- Make reasoning explicit (e.g., “Therefore…”, “Based on this analysis…”).

## Example Writing Outline

1. **When Customers Churn**: 62% of churn follows a failed first purchase, with 45% occurring right after cart abandonment. (Phenomenon)
2. **Why They Leave**: Limited comparison tools and complex checkout drive new users away. (Insight)
3. **What to Propose**: Introduce cart recommendations and one‑click payments to lower churn. (Proposal)
4. **Expected Results**: Comparable cases show churn down 30% and repeat purchases up 1.8× after similar upgrades.
5. **Conclusion and Next Steps**: Prioritize these experience improvements within the current quarter.

## Writing Notes

- Ground Phenomenon in measurable data, observed patterns, or field feedback.
- In Insight, answer why the phenomenon occurs—not just what it is.
- Proposals must be actionable and resource-aware, directly tied to the insight.
- Design the sequence to answer “How do we interpret this?” and “So what should we do?” in order.