← Files DeveloopARCHIVED FILE
skills/writing-strategy/references/challenge_strategy_result.md
2.01 KB · Oct 5, 2026 · 18:30 UTC
# Challenge → Strategy → Result / 도전 → 전략 → 성과 - English name: Challenge → Strategy → Result - Korean name: 도전 → 전략 → 성과 - Selection category: achievement - Use when: Use for project, team, or organization stories where strategy converted a challenge into results. - Avoid when: Avoid when results are not yet visible. ## Writing Pattern **Use a fixed three-part structure** - Challenge - Describe the difficulty faced, external changes, or internal issues in concrete terms. - Make clear “What was the problem?” and “What constraints existed?” - Aim for empathy and engagement. - Strategy - Explain the strategy, approach, and execution plan chosen to overcome the challenge. - Present the strategic direction with specific actions. - Center on “What did we decide to do and how?” - Result - Summarize quantitative and qualitative outcomes achieved after execution. - Show numbers, customer responses, organizational changes, and improved indicators. - Answer clearly: “Did the strategy actually work?” ## Example Writing Outline 1. **Difficulties Entering a New Market**: Growth in the existing market hit a ceiling amid fierce competition; new revenue sources became urgent. (Challenge) 2. **Targeting a Cost-Sensitive Niche**: We planned a lower-priced lineup for cost-sensitive customers and reoriented distribution to online channels. (Strategy) 3. **8,200 New Customers in Six Months**: Within six months of execution, we gained 8,200 new customers and online revenue share rose from 15% to 38%. (Result) ## Writing Notes - In Challenge, present a realistic, contextualized problem with specific numbers and impacts—not a vague difficulty. - In Strategy, explain not only what you did but also why it was expected to work. - In Result, go beyond “it went well”—quantify outcomes and include customer or organizational feedback. - Keep the full arc: problem framing → strategic thinking → tangible results, so the reader grasps how we overcame the challenge.
SHA-256: 9bf0f195f2ab59315cb81aedb167ae7d3157cf4cf8c46c990cd063f58c117f25