← Files DeveloopARCHIVED FILE

skills/writing-strategy/references/voice_from_field_insight.md

1.74 KB · Oct 3, 2026 · 06:30 UTC

↓ Download file

# Voice from Field → Insight / 현장 목소리 → 인사이트

- English name: Voice from Field → Insight
- Korean name: 현장 목소리 → 인사이트
- Selection category: field
- Use when: Use when frontline voices, interviews, or field notes should reveal insight.
- Avoid when: Avoid when there is no concrete voice from the field.

## Writing Pattern

**Use this fixed flow**

- Collect and summarize diverse voices from the field
- Synthesize common patterns and core messages
- Summarize insights and propose actions
- Express field voices as quotes or paraphrased remarks—keep them direct and realistic.

**Each major section should include**

- Section heading
- Core paragraph purpose (1–2 sentences)
- Go beyond listing facts; craft messages that prompt a new perspective or a reason to act.

## Example Writing Outline

1. **Common Staff Complaint**: We kept hearing, ‘We spend more time writing reports than helping customers.’
2. **Recurring Issues**: The biggest issues at customer touchpoints were excessive reporting and communication overhead.
3. **Pattern and Cause**: Lack of a real‑time sharing system led to duplicated work and high fatigue.
4. **Derived Insight**: Shift from a ‘report‑centric’ to an ‘action‑centric’ operating model.
5. **Proposal and Expected Effect**: Simplify reporting and adopt real‑time collaboration tools to raise productivity and satisfaction.

## Writing Notes

- The more specific the field quotes, the more persuasive—use real quotations or concise cases.
- Insights must answer “Why is this happening?” and “What does it suggest?”—not just restate problems.
- End with a proposal the organization/reader can act on.
- Keep the rhythm understanding → analysis → change proposal.

SHA-256: 146b7e9736dfc81821f72522c7db05501fa88ba37634eb6907efaa993c5eaa06