← Files DeveloopARCHIVED FILE
skills/writing-strategy/references/issue_debate_conclusion.md
1.64 KB · Oct 4, 2026 · 12:29 UTC
# Issue → Debate → Conclusion / 이슈 → 쟁점 → 결론 - English name: Issue → Debate → Conclusion - Korean name: 이슈 → 쟁점 → 결론 - Selection category: debate - Use when: Use when a topic has identifiable issues and opposing arguments that need a reasoned conclusion. - Avoid when: Avoid if the piece should remain open-ended. ## Writing Pattern **Use a fixed three-step structure** - Issue - State the central topic clearly. - Include why discussion is needed, background context, and urgency. - Debate - Present multiple perspectives and conflicting claims fairly. - Cover pro/con, trade-offs of alternatives, and stakeholder differences. - Conclusion - Offer a clear conclusion, recommendation, or decision direction based on the debate. - This can become the organization’s position or the writer’s proposal. ## Example Writing Outline 1. **Should We Keep Remote Work?**: Since COVID-19, whether to continue remote work has become a key internal issue. (Issue) 2. **Pros and Cons**: Employee satisfaction rose, but concerns persist about collaboration efficiency and engagement. (Debate) 3. **Conclusion and Proposal**: Shift to a hybrid model and pair it with performance-based flexibility. (Conclusion) ## Writing Notes - Start the Issue in a neutral, objective tone—explain the phenomenon and why it merits discussion. - In Debate, cover multiple views evenly; summarize pros/cons and stakeholder perspectives without bias. - The Conclusion must link logically to the prior analysis and offer a specific recommendation or criterion. - When appropriate, translate the conclusion into a concrete plan or policy direction.
SHA-256: 1500674ef5cc4fd603c2350805070c01dce5942116c5a95a5cdc27acde22f349