Story Craft for Builders
Translate customer pain into narratives engineers can implement without losing the emotional center of the problem.
Tuition (informational): ₩180,000
2 weeks · sprint · Sprint workshop
Overview
Stakeholder communication through storytelling. You practice story arcs that respect technical constraints, write crisp briefs, and pair with design on narrative prototypes that survive contact with code.
What is inside
- Story spine adapted for technical audiences
- Brief template with explicit unknowns
- Pairing exercises with design narrative prototypes
- Critique rubric for internal storytelling reviews
- Voice and tone guide for operational updates
- Slide-less readout formats
- Async feedback loops on two-minute Loom drafts
Outcomes you can show
- Deliver a story-led brief that engineering praised for clarity
- Run a critique session using the rubric without defensiveness
- Ship a customer anecdote pack support teams reuse
Facilitator
Eunji Park
Curriculum designer bridging narrative design and operational product craft.
FAQ
Is this marketing copywriting?
No. This is internal and partner-facing narrative for product decisions. External marketing copy is out of scope.
English skill level?
Advanced professional English recommended because peer feedback is text-heavy.
Limitation?
We do not record customer calls for you; you must bring sanitized transcripts you are allowed to share internally.
Experience notes
“Story spine exercise finally got PM and EM language aligned before build. Loom feedback sometimes felt slow due to time zones.”