← Files DeveloopARCHIVED FILE
skills/writing-strategy/references/before_after_next_challenge.md
1.86 KB · Oct 2, 2026 · 00:29 UTC
# Before → After → Next Challenge / 변화 전 → 변화 후 → 다음 과제 - English name: Before → After → Next Challenge - Korean name: 변화 전 → 변화 후 → 다음 과제 - Selection category: change - Use when: Use when a transformation is complete enough to show results but still opens a next agenda. - Avoid when: Avoid when the ending should feel fully resolved. ## Writing Pattern **Use a fixed three-stage flow** - Before - Describe the state before attempting change. - Present problems, limits, and inefficiencies with concrete numbers or cases. - The key is helping the reader recognize why change was necessary. - After - Explain what improved after the change. - Use comparable metrics, user reactions, or internal efficiency so “before vs. after” is clear. - Emphasize positive results to validate the change. - Next Challenge - Present the new challenges we must now tackle. - Specify remaining issues after the change or next goals for the next level of growth. - Stress that change is the beginning of continuous improvement, not the end. ## Example Writing Outline 1. **Pre-Renewal Service UI**: Poor information architecture and weak mobile optimization drove high churn. (Before) 2. **Key Improvements After the Renewal**: After simplifying the UI, average time-on-site rose 32% and monthly signups increased 1.5×. (After) 3. **Next Challenge — Improve Retention**: Acquisition is up, but long-term retention remains low; we need a stronger CRM strategy. (Next Challenge) ## Writing Notes - Write the Before and After using comparable metrics and real user experience; avoid vague “it got better” phrasing. - Treat the Next Challenge as a new starting line, not the finish—“now it begins,” not “now it’s over.” - Ensure a natural time flow so the reader doesn’t wonder “what’s next?”—answer it proactively.
SHA-256: f03ec91316ee3c4584c94ab16f845b8813bbcab95fa288cdbdcc5b263a1849c9