← Files DeveloopARCHIVED FILE
skills/writing-strategy/references/past_present_future.md
1.8 KB · Oct 5, 2026 · 18:30 UTC
# Past → Present → Future / 과거 → 현재 → 미래 구조 - English name: Past → Present → Future - Korean name: 과거 → 현재 → 미래 구조 - Selection category: time - Use when: Use when historical change or evolution is the best organizing principle. - Avoid when: Avoid when the topic is not time-dependent. ## Writing Pattern **Organize the section flow using the guidance below** - Do not lock the number of sections; structure them flexibly to suit the topic. **Use this sequence** - **Past**: Problems, limitations, starting points, initial situations - **Present**: Triggers for change, execution results, current state - **Future**: Future direction, plans, expected outcomes - **Conclusion and Proposal**: Key summary or requested actions **Each major section should include** - Section heading - Core paragraph purpose (1–2 persuasive sentences) - Ensure each stage connects smoothly so time flows naturally, and help the reader accept why we changed and why the future direction matters now. ## Example Writing Outline 1. **Past Pain Point**: Manual processes and duplicate data entry made the legacy CRM inefficient. 2. **Catalyst for Change**: We needed automation to reduce repetitive work and errors. 3. **Present State**: After implementation, work time fell 40% and error rates dropped by half. 4. **Future Plan**: Add analytics capabilities and expand to personalized marketing. 5. **Conclusion and Ask**: Now is the right time to scale this foundation with added investment. ## Writing Notes - Keep the timeline seamless so Past → Present → Future reads as one story. - In Past, focus on why change was necessary—not nostalgia. - In Present, center on concrete results—outcomes, metrics, or cases. - In Future, show direction and expected impact and explain why to act now.
SHA-256: 08c69d05fdb4aeb974c01f3be82f017d9c0a0371e3aad50f15b66cc875b43cc5