skills/writing-strategy/references/question_experiment_conclusion.md

# Question → Experiment → Conclusion / 의문 → 실험 → 결론

- English name: Question → Experiment → Conclusion
- Korean name: 의문 → 실험 → 결론
- Selection category: inquiry
- Use when: Use when the article can be framed as a question tested through experiment or evidence.
- Avoid when: Avoid when no test, trial, or comparison exists.

## Writing Pattern

**Use this fixed three-step structure**

- Question
  - State the problem or inquiry clearly (e.g., “Why is this happening?”, “Is this method better?”).
  - Spark curiosity and set the direction of the talk.
- Experiment
  - Design for hypothesis testing or problem solving—A/B tests, applied cases, etc.
  - Summarize design, process, conditions, and tools concisely.
  - Include objective results and observations.
- Conclusion
  - Summarize key findings.
  - Answer “What was proven?” and “What did we learn?”
  - Include implications or future direction where helpful.

## Example Writing Outline

1. **What Drives Lower Satisfaction?**: We hypothesized that early friction, rather than missing features, drives recent dissatisfaction. (Question)
2. **A/B Test on Onboarding**: We compared conversion for 1,000 new users across Group A (current UX) and Group B (improved UX). (Experiment)
3. **Improved UX Raised Conversion by 28%**: The improved group achieved 28% higher conversion and 15% lower churn. (Conclusion)

## Writing Notes

- Frame a Question of strategic value; provide context that invites empathy.
- Base the Experiment on trustworthy data and keep the design crisp so engagement stays high.
- In the Conclusion, include clear results and the strategic/practical message they imply.
- Keep the arc natural: “What we asked → How we tested → What answer we got.”