← Files DeveloopARCHIVED FILE
skills/writing-strategy/references/customer_centric_story.md
2.15 KB · Oct 2, 2026 · 00:29 UTC
# Customer-Centric Story / 고객 이야기 중심 - English name: Customer-Centric Story - Korean name: 고객 이야기 중심 - Selection category: case - Use when: Use when a customer or user scenario should make the value concrete and empathetic. - Avoid when: Avoid when the customer story would be invented without enough realism. ## Writing Pattern **Follow this fixed flow** - Customer intro — background, role, industry, and challenge - Problem situation — difficulties faced or goals pursued - Touchpoint and change — why our product/service was adopted and the initial reaction - Application — how it was used specifically - Outcomes — quantitative and qualitative effects - Close and message — summary and the takeaway for the target reader **Each major section should include** - Section heading - Core paragraph purpose (1–2 sentences) - Craft messages so empathy builds naturally along the story arc. ## Example Writing Outline 1. **Customer — ABC Tech’s Marketing Team**: ABC Tech is a small B2B IT company; its lean marketing team has to run large campaigns. 2. **The Challenge**: Limited headcount and resources caused heavy load from planning to draft creation. 3. **Meeting the proposed writing workflow**: By adopting a outline-based writing workflow, drafting time fell to a quarter. 4. **How They Used It**: They adapted section outlines to their briefs and leveraged AI-suggested section outlines to finalize reader-centered drafts. 5. **Results**: Draft quality rose while production time dropped; team focus improved by 35%. 6. **In the Customer’s Words**: “External partners told us the quality of our published writing has noticeably improved.” ## Writing Notes - The customer may be fictional, but the scenario should be concrete and realistic (industry, scale, challenges). - The emotional arc matters; design the story so the reader feels “this could be our story.” - Express outcomes with concrete numbers or quotes where possible (e.g., 40% time saved, “Our team’s results have really improved.”). - Close with a universal message or lesson drawn from the case (e.g., “SMBs can raise article quality through automation.”).
SHA-256: d885d0bd743866a686c089fc89048082600cc0df5824d6fbc608978fdb703c4a