# Before → Journey → After / 여정 기반 구조

- English name: Before → Journey → After
- Korean name: 여정 기반 구조
- Selection category: narrative
- Use when: Use when the process, struggle, or learning journey is as important as the before/after contrast.
- Avoid when: Avoid when the journey lacks concrete events.

## Writing Pattern

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

- Before — The prior state, problems, constraints, or tasks
- Journey — The execution path for change, challenges and how we overcame them
- After — The post-change state, outcomes, results, and lessons

**Each major section should include**

- Section heading
- Core paragraph purpose (1–2 sentences)
- Keep the logic explicit so each step naturally answers “So what?”

## Example Writing Outline

1. **Before — Repeated Deadline Delays**: We struggled to meet due dates because dozens of proposals were built manually every week. (Before)
2. **Our Attempt to Change**: We adopted a outline-driven writing system and redesigned the proposal workflow. (Journey)
3. **Unexpected Challenges**: Initial user adaptation issues arose, but phased training and feedback sped up adoption. (Journey)
4. **After — Higher Operational Efficiency**: Proposal build time dropped 60%, and on-time delivery improved to 95% across the team. (After)
5. **Key Lesson**: Even small flow changes can lead to significant performance gains. (After)

## Writing Notes

- Emphasize the problem sufficiently in “Before” so the “After” outcomes stand out.
- Replace vague issues with numbers, cases, and repeated patterns.
- In “Journey,” spotlight the overcoming of obstacles—not just a list of steps.
- Make the story vivid: what difficulties arose, and how were they solved?
- Let “After” go beyond outcomes to convey insights or hope the reader can carry forward.