← Files DeveloopARCHIVED FILE
skills/writing-strategy/references/experience_lesson_application.md
1.72 KB · Oct 3, 2026 · 06:30 UTC
# Experience → Lesson → Application / 경험 → 교훈 → 적용 - English name: Experience → Lesson → Application - Korean name: 경험 → 교훈 → 적용 - Selection category: reflection - Use when: Use for personal, team, or field experience that should yield a lesson and practical application. - Avoid when: Avoid when experience is anecdotal but no transferable lesson exists. ## Writing Pattern **Use a fixed three-step structure** - Experience - Describe a real incident, project, success/failure, or benchmarking experience. - Storytelling works well; provide enough context for immersion. - Lesson - Summarize the insights or important learnings from the experience. - Go beyond impressions—distill practical principles others can apply. - Application - Propose how to use the lesson in current or future situations. - Connect it to strategy, direction, policy, or ways of working. ## Example Writing Outline 1. **2023 Support Process Renewal**: We overhauled our process in response to rising churn. (Experience) 2. **The Most Important Lesson**: The core issue wasn’t response time—it was building trust in the first impression. (Lesson) 3. **How We’ll Apply It Now**: We’ll target a reply within five minutes and use a friendly greeting tone to secure early goodwill. (Application) ## Writing Notes - Keep the experience concise but clear—include the when/where/what (e.g., “In H2 last year, during our CRM rollout”). - The Lesson should answer “What did we learn?” and elevate it into a universal message. - In Application, show how the lesson connects to the current context—ideally as a concrete plan. - Balance storytelling with actionable proposals, keeping the logic between steps tight.
SHA-256: 068c5d034147544b352d1c5d551bd93170938c72f64136c57fd0ba851c467cd7