← Files DeveloopARCHIVED FILE

skills/writing-strategy/references/fact_insight_action.md

1.85 KB · Oct 5, 2026 · 18:30 UTC

↓ Download file

# Fact → Insight → Action / 사실 → 인사이트 → 실행 구조

- English name: Fact → Insight → Action
- Korean name: 사실 → 인사이트 → 실행 구조
- Selection category: analysis
- Use when: Use when facts or data should lead to insight and a concrete next step.
- Avoid when: Avoid when the material is mostly emotional or character-led.

## Writing Pattern

**Follow this three-stage structure with a fixed section count**

- **Fact**: Objective data such as figures, current status, or cases
- **Insight**: Meaningful interpretation derived from the facts
- **Action**: Practical actions that should follow from the insight
- You may present multiple facts, and separate insights/actions when needed.
- If space is tight, combine facts with insights or summarize actions.

**Each major section should include**

- Section heading
- Core paragraph purpose (1–2 sentences)
- Make the logical connection explicit (e.g., “As a result,” “Based on this analysis”).

## Example Writing Outline

1. **Churn Analysis**: Churn increased 22% year over year; 58% of churn occurs within a day of first login. (Fact)
2. **Key Insight**: A poor first-time experience and overly complex onboarding drive early churn. (Insight)
3. **Recommended Action**: Cut onboarding to three steps and add guided walkthroughs to stem early churn. (Action)
4. **Projected Effect**: Simulations suggest churn could drop by up to 35% after onboarding improvements.
5. **Conclusion and Ask**: We should implement these data-backed changes within this quarter.

## Writing Notes

- Facts must be objective—use verified metrics, cases, or observed phenomena.
- Base insights on what the facts mean and why they matter—not mere summaries.
- Actions must be concrete and feasible, not wishes or declarations.
- Keep the flow logical so the reader leaves knowing exactly what to do next.

SHA-256: cd62a07768c6f84daaf060ddf1b930fa78dabf6f093a1509239d7f333dc53a74