skills/writing-strategy/references/observation_pattern_insight.md

# Observation → Pattern → Insight / 관찰 → 패턴 → 인사이트

- English name: Observation → Pattern → Insight
- Korean name: 관찰 → 패턴 → 인사이트
- Selection category: insight
- Use when: Use when scattered observations reveal a pattern and a deeper insight.
- Avoid when: Avoid when there are too few observations to form a pattern.

## Writing Pattern

**Use this fixed three-step structure**

- Observation
  - Individual cases, user behavior, field reactions, data points
  - Present observations from multiple angles; cite method/source when possible
- Pattern
  - Derive commonalities, repeated elements, and trends among observations
  - Conceptual structures (classification, clustering, cycles) help
  - Move from isolated facts to meaningful relationships
- Insight
  - Interpret what the pattern implies conceptually or strategically
  - Answer “What is the core message this pattern reveals?”
  - Connect to policy, product strategy, or action steps

## Example Writing Outline

1. **Observing Review Keywords**: Among 1,200 reviews in the last 3 months, ‘slow,’ ‘complex,’ and ‘unclear docs’ recur often. (Observation)
2. **Pattern Across Repeats**: Complaints about complexity cluster among new users and occur within the first three days. (Pattern)
3. **We Must Improve Onboarding UX**: Complex early UX is driving churn; simplifying the onboarding flow is the key improvement. (Insight)

## Writing Notes

- In Observation, curate information that connects to the topic—don’t merely list.
- In Pattern, focus on logical relations (similarity, repetition, correlation) across observations.
- In Insight, present new perspectives or direction that’s hard to see from raw data alone.
- Insights can include concrete actions or serve as conceptual premises for strategy.
- Keep the chain: “We observed X → We see pattern Y → Therefore we interpret Z.”